Database Info

How to Restore backup || TWRP

Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
UPDATED:
After some testing the problem only occurs when i take back up for all partitions which isn't mandatory, but when i take back for (system, boot, data) which is enough for working backup and the restoring process is flawless
I did not disable security (PIN code) and restoring was successful
Short answer:
Only take backup for data, system, boot

R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter

R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
What about security? Did you have to disable all security before the backup?

I did not disable security (PIN code) and restoring was successful.

R1skNt said:
I did not disable security (PIN code) and restoring was successful.
Click to expand...
Click to collapse
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.

lollyjay said:
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
Click to expand...
Click to collapse
Please see the 1st post (update)

PeterGuru said:
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
Click to expand...
Click to collapse
For what it's worth, I think I found a solution to why I couldn't restore the data partition. I can't explain why, but now it's working.
Previously, and historically, whenever I did a restore, I always wiped my device: system, data, boot.
This time; however, I did not wipe the device. I simply did the restore and everything worked. Therefore, the problem is somehow associated with the wipe.
Peter

I did a nanroid backup (boot, system, data only as per the instructions) of 5.1.8, rooted with magisk 16.6, ROM, installed lineage OS, than restored my backed up OOS ROM the restore process completed successfully but got stuck on boot logo, flashed magisk again along with the custom kernel but all to no joy, keeps bootlooping, however lineage restored fine and booted, any help be much appreciated, cheers.

joemossjr said:
You guys are crazy and I feel I need to answer your questions. So here we go. So just becuase there's multiple partitions doesn't mean you can dual boot or set up other things. So the way it works is the userdata partition is one partition. There are 2 system partitions for seamless updates two boot partitions for seamless and two firmware slots. In theory yes you can have two roms on both slots. Will they work? No. They will both use the same userdata partitions. So it will be incompatible.now you could in theory have lineage on one slot and oos on the other and if you ever want to go back just format userdata and fastboot --set-active=other to get to the other slot. But that doesn't really seem like a good idea. If you guys have other questions feel free to ask me!
Click to expand...
Click to collapse
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.

Bonito77 said:
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Click to expand...
Click to collapse
totally irrelevant to this thread, cheers.

"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?

bannannn said:
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
Click to expand...
Click to collapse
I assume you're in the directory twrp.img is in and are using the img file instead of the zip file? Also you renamed the img file to twrp.img?

after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.

kingwicked said:
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
Click to expand...
Click to collapse
I followed your guide. But I'm stuck at the boot animation...

RheinPirat said:
I followed your guide. But I'm stuck at the boot animation...
Click to expand...
Click to collapse
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck

kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
I was on 9.0.2
I restored the phone with the MSM tool and updated the ROM to 9.0.2 via manual system update like before.
Question:
Is it not possible to restore the whole system? Or only Data like you said under point 8?
Do I need verity? Because I think my phone is encrypted (flashed never a verity file)
Could I restore the whole system from a full TWRP (all partitions included) - only select data, system?

restoring system and other never worked for me. always failed. but only restoring data partition always worked
when you restore only data. your all apps. settings messages everything will restore even magisk modules.
im not sure about encrypted because. encrypted phone when restoring twrp messed up my whole internal memory. and i had no choice but to wipe it.
so there is no issue with no verity. as it helps not to scramble the internal memory of your device and you wull not loose any data or get stuck on qualcomm dump mode
but remember the steps to verity when installed on already used rom with data. you have to format data to remove encryption
only restoring data is the best option. you can try without no verity to restore i think may work but follow all options i mentioned
but i dont recommend to use with no verity.since using no verity i have never got to wipe my internal memory

I've bricked my device twice after trying to restore and always resorted to just a clean flash of stock using the MSMDownloadTool... wish I'd found this thread sooner as you just solved my third backup restore soft-brick!
I'll also remember to just backup system/data/boot going forward...
Thanks!

kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
Thanks buddy, It worked like a charm.
About the pin removal, as you siad there is a good tutorial in below link which can be used.
https://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/

Thank you!!!
You saved my phone (and life).
I can confirm your procedure is working with my back up made on 10.3.2 using a usb c key.
I just restored the DATA. Nothing else!
Thank you so much!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse

[GUIDE] How to install android P GSI Roms

Here a more complete guide.
Hi guys, i finally managed to get Havoc OS Pie fully working, this method should theoretically work on any pie gsi, if not tell me
Its not obligatory to follow this guide by letter, but you should have this things done:
Boot partition with TWRP and Magisk installed(some roms don't boot without root, they stay on splash image)
Formatted data
Selinux set on permissive on boot time(if it's enforcing camera, flashlight and headphones won't work)
Force encryption disabled in fstab.qcom(to fix wrong internal storage space)
Here's the step:
Install TWRP
Reboot recovery and flash magisk zip and this module if you want to install a selinux enforcing rom(you have to select permissive when installing). If you don't know flash to be sure, it doesn't harm.
reboot to bootloader and flash system
Code:
fastboot flash system "system image"
flash userdata.img from stock rom
Code:
fastboot flash userdata images/userdata.img
reboot and rom should boot normally(you should have a wrong storage space due to encryption)
with a rooted file manager edit /vendor/etc/fstab.qcom and change "forceencryption=footer" to "encryptable=footer" to disable encryption, then reboot to recovery
do a format data from TWRP and reboot
Not all these steps are needed on every roms because some don't need rooted kernel, some are permissive and maybe some handles encryption correctly, but by doing all these steps should make any pie rom bugless.
What i have tested(on havoc): camera, wifi, mobile data, hotspot(work but its always without password), headphones, audio, bluetooth, notch(yes, its recognised correctly), flashlight and sms.
Notice: first time you have to set preferred sim for mobile data and sms to get them working.
Huge thanks to
@Voodoojonny for encryption disabling
@d1ngh, @Dees_Troy and Team Win for official TWRP
@Jordan~Kurniawan for the hint of setting selinux to permissive

Great news!
thanks for the guide buddy.

Please explain by video?

Stock camera workink? Or need flash mi a1 cam module?

blue4 said:
Stock camera workink? Or need flash mi a1 cam module?
Click to expand...
Click to collapse
everything is working
you just can't set password for hotspot
if you are using your phone as a hotspot. it will be open

Gapps?

ouroboros12 said:
Gapps?
Click to expand...
Click to collapse
Since this guide's first step is to install TWRP, use TWRP to flash the latest Gapps.

On the note of the final point, "do a format and reboot" how should I go about that?
Using the ROM's factory reset, flashing the stock userdata.img again, or using TWRP?

rosiepie said:
On the note of the final point, "do a format and reboot" how should I go about that?
Using the ROM's factory reset, flashing the stock userdata.img again, or using TWRP?
Click to expand...
Click to collapse
It's the same because now encryption is disabled(formatting data in the classic way with encryption enabled cause a bootloop, this is why i suggest to use userdata from stock).
I will update mainpost.

When you flash userdata.img, why is from stock rom and not from your actual rom?.

Txatxiquesi said:
When you flash userdata.img, why is from stock rom and not from your actual rom?.
Click to expand...
Click to collapse
Because the one from your actual rom is encrypted and can't be read by other roms(if not you can skip this step, but i assume not).
I don't know why formatting with twrp cause a bootloop if device is encrypted, the only way i've found to clean data without issue is flashing userdata from stock... if anyone find another please tell me .

Thx for guide. Working.

blue4 said:
Thx for guide. Working.
Click to expand...
Click to collapse
Welcome, did you followed the entire procedure or only the hints at the top?
I want to be sure that the procedure is correct because i've made a some tests and in fact the procedure i've used it's not exactly the same.
Also, i've found offline charging not working, this seems caused by magisk, could you please check if you have also this issue?

Thank you for this guide! Sadly, we still have the situation to choose between encryption and working twrp. At the first boot, havoc encrypts storage, sothat twrp will not be longer able to encrypt data. "Encryptable=footer" disables encryption, but after that, you will not be able to encrypt phone anymore - I tried under a few scenarios, but encryption just stopped without anything.
And important with Havoc - every securitypatch level of stock leads to other problems - such as no wifi or other bugs. Best results - no bugs @All I got with the combination of @yshalsager´s twrp (18.08.) as kernel combined with stock 9.6.4.0 (july sec patch). You can patch the old twrp with the official afterwards.
Twrp inofficial yshalsager: - mtp not working, vendor not able to being backuped vs official twrp: sdcard not working... And no twrp that can work with pie encryption... Hopefully some dev will find a solution!

Voodoojonny said:
Thank you for this guide!
Click to expand...
Click to collapse
Welcome!
Voodoojonny said:
Sadly, we still have the situation to choose between encryption and working twrp. At the first boot, havoc encrypts storage, sothat twrp will not be longer able to encrypt data.
Click to expand...
Click to collapse
I've seen that re-installing twrp fixes, could you try?
Voodoojonny said:
"Encryptable=footer" disables encryption, but after that, you will not be able to encrypt phone anymore - I tried under a few scenarios, but encryption just stopped without anything.
Click to expand...
Click to collapse
You could just revert the change, flash stock userdata and reboot, this should tehoretically make encryption working again(while deleting all data).
Voodoojonny said:
And important with Havoc - every securitypatch level of stock leads to other problems - such as no wifi or other bugs.
Click to expand...
Click to collapse
Give me a logcat, maybe i will find why.
Don't work even with selinux permissive?

mac12m99 said:
Welcome!
I've seen that re-installing twrp fixes, could you try?
You could just revert the change, flash stock userdata and reboot, this should tehoretically make encryption working again(while deleting all data).
Give me a logcat, maybe i will find why.
Don't work even with selinux permissive?
Click to expand...
Click to collapse
I tried to reinstall twrp with
a) patched stock 9.6.4.0 with and without dm-verity
b) patched stock 9.6.9.0 same as above
Both leads to bootloop flashing userdata.bin doesn't fix
c) a and b with magisk and permissiver - > bootloop
Only Yshalsager's twrp as boot with 9.6.4.0 vendor works... All other vendors: broken wifi; all other kernels: bootloop (no dm verity, permissiver, root - nothing helps)
And if you flash userdata.bin you can read data with twrp, but booting havoc will change data, sothat twrp can't read it anymore. Flashing official twrp installer doesn't change anything...
It'slike a circle... Simply: stock twrp is only compatible with encryption of stock userdata... Only solution: decrypt...
I will send you logs tomorrow! Thank you!

mac12m99 said:
Welcome, did you followed the entire procedure or only the hints at the top?
I want to be sure that the procedure is correct because i've made a some tests and in fact the procedure i've used it's not exactly the same.
Also, i've found offline charging not working, this seems caused by magisk, could you please check if you have also this issue?
Click to expand...
Click to collapse
Yes and no. I flashed directly patched_boot.img for magisk and only booted twrp with fastboot for flashing Gapps and format data. But this procedure is good. The rom is very fast but sometimes micro-lagging more than stock.
Offline charging not work. (Rooted boot.img issue)
---------- Post added at 09:53 PM ---------- Previous post was at 09:07 PM ----------
Pixel Experience working too and smoother than Havoc for me. (Cam)

Apparently, since the last build of Havoc, is not necesary changing selinux, no bootloop on enforcing.

mac12m99 said:
Hi guys, i finally managed to get Havoc OS Pie fully working, this method should theoretically work on any pie gsi, if not tell me
Its not obligatory to follow this guide by letter, but you should have this things done:
Boot partition with TWRP and Magisk installed(some roms don't boot without root, they stay on splash image)
Formatted data
Selinux set on permissive on boot time(if it's enforcing camera, flashlight and headphones won't work)
Force encryption disabled in fstab.qcom(to fix wrong internal storage space)
Here's the step:
Install TWRP
Reboot recovery and flash magisk zip and this module if you want to install a selinux enforcing rom(you have to select permissive when installing). If you don't know flash to be sure, it doesn't harm.
reboot to bootloader and flash system
Code:
fastboot flash system "system image"
flash userdata.img from stock rom
Code:
fastboot flash userdata images/userdata.img
reboot and rom should boot normally(you should have a wrong storage space due to encryption)
with a rooted file manager edit /vendor/etc/fstab.qcom and change "forceencryption=footer" to "encryptable=footer" to disable encryption, then reboot to recovery
do a format data from TWRP and reboot
Not all these steps are needed on every roms because some don't need rooted kernel, some are permissive and maybe some handles encryption correctly, but by doing all these steps should make any pie rom bugless.
What i have tested(on havoc): camera, wifi, mobile data, hotspot(work but its always without password), headphones, audio, bluetooth, notch(yes, its recognised correctly), flashlight and sms.
Notice: first time you have to set preferred sim for mobile data and sms to get them working.
Huge thanks to
@Voodoojonny for encryption disabling
@d1ngh, @Dees_Troy and Team Win for official TWRP
@Jordan~Kurniawan for the hint of setting selinux to permissive
Click to expand...
Click to collapse
Installed aex, the camera does not work. Havoc does not work either.But there is a good news. I made a backup in twrp and then restored it. Restoration of backups works fine.
Then I tried to flash the gsi project treble. In twrp, I did wipe data, system, dalvick and internal storage. then it rebooted into twrp.connected to the computer and downloaded gsi havoc.a, then clicked the installation setting img. and chose the system image. after installation, I rebooted the phone in twrp, and then booted into the system. and the system worked well. the camera and hotspot did not work.

I think many problems people are having here are due to the fact the tutorial, while useful, is incomplete. I had to stuggle a bit but I got everything working as it should (well, besides SELinux Enforcing). I can make a clear English-language thorough tutorial if anyone wants. I don't want to steal anyone's thunder.
Enjoying some Havoc Pie myself atm

twrp issue

Follow up from magisk thread
Twrp data mount issue
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post78395499

Did you do a factory wipe after installing TWRP?

Beanvee7 said:
Did you do a factory wipe after installing TWRP?
Click to expand...
Click to collapse
No, I didn't. Is that a necessity?

Because of encryption TWRP can't read the data partition until you've wiped in TWRP using the wipe method that makes you type in 'yes' to wipe.
After wipe TWRP can then read it. Afaik this is the only work around, you can flash things to turn off encryption, but iirc it doesn't undo encryption already there.

Are you using latest twrp version 3.2.3.0
Did you flash version 6 of the no verity opt zip
And I am going to assume that you formated data and not wipe data partition.

Are you running Oreo?
Because Samsung added quota support in their Oreo update for the /data partition. The official TWRP version isn't able to deal with the quota support yet, so you can't mount /data.
You should check out this post of Tkkg1994:
https://forum.xda-developers.com/ga...rp-herolte-t3333770/post77296102#post77296102
Tkkg1994 added quota support in that TWRP version he links in his post.
Don't use the official or twrp version in the 1st post, because those don't have the quota support yet.

@haro_h yes he is running on Oreo. Didn't know twrp for the s7 hasn't been updated for Oreo and the quota support many thanks.
@kiwigi follow the link provided by @haro_h it should take you straight to the post and at the bottom the download links. You can use either method (Odin or twrp ) it will overwrite current twrp.
Once done you will have to repeat the steps you have done already ie::
Format data
Flash no verity opt zip
Flash rmm state bypass zip

spawnlives said:
Are you using latest twrp version 3.2.3.0
Did you flash version 6 of the no verity opt zip
And I am going to assume that you formated data and not wipe data partition.
Click to expand...
Click to collapse
Thanks @spawnlives
also
thanks to @haro_h
and thanks @Beanvee7
That is exactly how I did it.
So a little change to what you mentioned here
1. Back apps and data
2. Unlock bootloader
3. Flash twrp with Odin - use latest version of twrp
4. Boot straight into twrp and FORMAT data.
5. When finished the format using twrp menu reboot back into twrp
At this stage if you reboot back into system it will re-encrypt your phone.
6. Flash no verity opt encrypt zip - this will prevent phone from re encrypting when booting into system.
https://build.nethunter.com/android-...y-opt-encrypt/
Flash RMM-State_Bypass_v2.zip(The only such file I found here)
7. Flash magisk
8. Reboot into system

kiwigi said:
Thanks @spawnlives
also
thanks to @haro_h
and thanks @Beanvee7
That is exactly how I did it.
So a little change to what you mentioned here
1. Back apps and data
2. Unlock bootloader
3. Flash twrp with Odin - use latest version of twrp
4. Boot straight into twrp and FORMAT data.
5. When finished the format using twrp menu reboot back into twrp
At this stage if you reboot back into system it will re-encrypt your phone.
6. Flash no verity opt encrypt zip - this will prevent phone from re encrypting when booting into system.
https://build.nethunter.com/android-...y-opt-encrypt/
Flash RMM-State_Bypass_v2.zip(The only such file I found here)
7. Flash magisk
8. Reboot into system
Click to expand...
Click to collapse
Glad it is all working.
It should be noted the rmm state bypass zip is the same version ( 1 or 2 ) doesn't matter where you download it from same as no verity zip.
Also you should.keep the no verity zip and rmm state bypass zip on your SD card or PC as I think you mentioned that you are moving and planning on re-,flashing your rom so you will have to redo all the steps again.
FYI all the rmm state zip does is modify a value in the build prop file and delete a system folder/file which prevents relocking of your bootloader when restarting your phone.

How to upgrade rooted/unlocked OOS 9 to latest without losing anything?

I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3

https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
Post #3 has the instructions you need
Long story short you need to flash the update via TWRP.

unknown00 said:
I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3
Click to expand...
Click to collapse
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system

tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk

RASTAVIPER said:
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?

unknown00 said:
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?
Click to expand...
Click to collapse
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.

Like above.
Flashing ROM Will also flash stock recovery so after ROM you need to flash twrp again,if you reboot without it it's lost.
Also why magisk isn't flashed right away is because: when you choose to reboot to twrp after the twrp flash it Will change slot, this way you Will get magisk on the correct slot.
All this can be done from the OS.
Install the ROM upgrade as usual,don't reboot.
Open magisk app
Search for a module a/b twrp (you Will only find one module) and install it.ndont reboot just yet.
Go to main screen of magisk
Press install, install, install to inactive slot (after OTA). After this install you can reboot.
Both works, I find the twrp way to be more convenient

I don't about stable i am on open beta 10 i root every beta without twrp using patch boot image i got update every time around 1.5 GB because i am rooted after update i just lose root everything same before update phone not wipe anything

I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).

akxak said:
I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).
Click to expand...
Click to collapse
No need to reinstall TWRP in the first method?

unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
I do not have TWRP installed, it is basically not necessary as OOS can be updated with the settings/manual update tool and Magisk can be reinstalled via Magisk manager.
I had to use TWRP solely to downgrade to Magisk 17.2 from Magisk 18 as this cannot be done with Magisk Manager. But for that purpose, it's enough to temporarly make TWRP available via fastboot boot command without permanently installing it.
If you have TWRP and want to keep it, that easy process doesn't work to upgrade the OS.

unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
If you wanna keep TWRP you do the way I described few posts up.....

tabletalker7 said:
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.
Click to expand...
Click to collapse
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.

thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.

tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.

thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
thejase said:
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.
Click to expand...
Click to collapse
As promised, I'm writing back with my findings. I believe some enabled module in magisk was the issue. What I did was uninstall magisk 18 with the latest uninstaller. Thinking it was V18 itself that was the problem, I then proceeded to install v17.3 on both slots (reboot to recovery in betweene). This worked and booted! It started to occur to me that I had not disabled any of my modules before installation of the rom/magisk. This is a big mistake as a lot of magisk modules are still using old formatting and cause new installations to fail if left enabled. Since an uninstall also disables all modules, I believe using 17.3 was not necessarily the solution but rather either disabling modules before an install, or uninstalling whatever version magisk was installed to begin with (which essentially disables/uninstalls those modules anyway). After installing 17.3 and getting it to boot, I just updated via magisk manager to v18 with no issues to speak of! Now comes the part where I need to remember all the installed modules I had and test them one by one.
For uninstallation of modules in twrp, you can use https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 Or https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
I hope this helps someone!

I might have hard bricked my op7pro

So this happened a couple minutes ago, i prepared my op7pro to update to the latest version available.
Here are the steps i took:
- Made a backup of the apps via Titanium Backup
- Removed all Magisk modules
- Downloaded the latest firmware via Oxygen Updater
- Moved it to root directory
- Checked the firmware via settings -> System Updates
- DID NOT INSTALL IT
- Went back to Masigk, installed the module "TWRP A/B Retention Script ", did not reboot
- Magisk again -> Install Magisk (install to inactive slot)
- Rebooted, and it stuck on the loading screen, i waited half an hour but kept stuck. So i decided to to reboot using the POWER BUTTON + ARROW UP Combination.
- Accessed TWRP via POWER BUTTON + ARROW DOWN Combination.
And here, is when i panicked. NO ACCESS TO THE INTERNAL STORAGE. I don't care about any data i have, i make backups, but i might **** my pants if i bricked the internal storage partition or something else. Right now i'm downloading the Fastboot roms, and the MSM Guac for All.
Which version of fastboot rom should i choose?
Additional Information:
- TWRP : 3.4.0.0 by mauronofrio
- Oneplus 7 pro EUROPE
- Bootloader Unlocked
EDIT: I was able to fix the partition using TWRP WIPE Data -> Format Data -> Reboot to Recovery
EDIT2: Flashed the firmware that i downloaded via the official Oneplus website via TWRP and it's working again.
I wouldn't have made the post if it wasn't for the partition problem, i've been flashing roms since the G1, this is embarassing. Anyways this issue has been SOLVED.

drakruka said:
So this happened a couple minutes ago, i prepared my op7pro to update to the latest version available.
Here are the steps i took:
- Made a backup of the apps via Titanium Backup
- Removed all Magisk modules
- Downloaded the latest firmware via Oxygen Updater
- Moved it to root directory
- Checked the firmware via settings -> System Updates
- DID NOT INSTALL IT
- Went back to Masigk, installed the module "TWRP A/B Retention Script ", did not reboot
- Magisk again -> Install Magisk (install to inactive slot)
- Rebooted, and it stuck on the loading screen, i waited half an hour but kept stuck. So i decided to to reboot using the POWER BUTTON + ARROW UP Combination.
- Accessed TWRP via POWER BUTTON + ARROW DOWN Combination.
And here, is when i panicked. NO ACCESS TO THE INTERNAL STORAGE. I don't care about any data i have, i make backups, but i might **** my pants if i bricked the internal storage partition or something else. Right now i'm downloading the Fastboot roms, and the MSM Guac for All.
Which version of fastboot rom should i choose?
Additional Information:
- TWRP : 3.4.0.0 by mauronofrio
- Oneplus 7 pro EUROPE
- Bootloader Unlocked
EDIT: I was able to fix the partition using TWRP WIPE Data -> Format Data -> Reboot to Recovery
EDIT2: Flashed the firmware that i downloaded via the official Oneplus website via TWRP and it's working again.
I wouldn't have made the post if it wasn't for the partition problem, i've been flashing roms since the G1, this is embarassing. Anyways this issue has been SOLVED.
Click to expand...
Click to collapse
I see the mistakes you made,
You need to remove module then install OOS
Don't reboot, install retention then install magisk to inactive slot. Reboot.

@soka said:
I see the mistakes you made,
You need to remove module then install OOS
Don't reboot, install retention then install magisk to inactive slot. Reboot.
Click to expand...
Click to collapse
Yes, thanks for taking the time, i forgot to install OOS that's what happened. I managed to fix it now. Thanks again

So you know this would be considered soft brick. Hard brick is no life no edl without test points. Just for clarification on the future

TheMadScientist said:
So you know this would be considered soft brick. Hard brick is no life no edl without test points. Just for clarification on the future
Click to expand...
Click to collapse
Yup

drakruka said:
Yes, thanks for taking the time, i forgot to install OOS that's what happened. I managed to fix it now. Thanks again
Click to expand...
Click to collapse
Glad you are back up and running. :good: