[TWRP][3.7.0-13][instantnoodle]TWRP for OnePlus 8/8Pro ][OFFICIAL][BETA 3]

[jon214m]

Does this not work on a13 f13? I installed but getting bootloader/recovery is corrupted.

You must have flashed the wrong image , so the system doesn't have a record of that file. Go back to you original PATCH_boot.IMG file, there might be on your PC when you Magisk or make a new ones and flash it . Or If you updated something make sure your boot.IMG are matching and patched . It will boot to normal

 

[deepongi]

Sometimes the error is because what you are trying to flash is not compatible, it's a safety measure to prevent flashing something that can harm your device.

You might be surprised what kinds of issues that updating/downgrading TWRP will fix.

could be a bad zip also

 

[PieceKeepr]

I have looked and cannot find a satisfactory answer to this queston that makes me comfortable. Which version, ext4 or erofs, do I need for a North American version of the OP 8 Pro? Thanks in advance.

 

[Nimueh]

I have looked and cannot find a satisfactory answer to this queston that makes me comfortable. Which version, ext4 or erofs, do I need for a North American version of the OP 8 Pro? Thanks in advance.

Depends on your OOS version. From the explanations I got on Telegram ext4 = OOS 11 and erofs = OOS 12-13.

Disclaimer: I'm just repeating what I was told, no guarantees lol

 

[ppajdek]

Adding my two cents, custom roms use ext4 or erofs, you have to find it yourself

 

[PieceKeepr]

Depends on your OOS version. From the explanations I got on Telegram ext4 = OOS 11 and erofs = OOS 12-13.

Adding my two cents, custom roms use ext4 or erofs, you have to find it yourself

Thanks for the replies, I'll try booting it when I have time instead of flashing it. I'm running the stock rom and recently updated to OOS 13. TWRP used to be so easy to figure out.

 

[rmedure]

I have looked and cannot find a satisfactory answer to this queston that makes me comfortable. Which version, ext4 or erofs, do I need for a North American version of the OP 8 Pro? Thanks in advance.

I'm using twrp_op8_erofs-3.7.0-b3.img on my IN2025 running stock OOS 13 (11_F.15). Definitely attempt boot before flash. Not sure if this is absolutely necessary, but I also made sure to install the new OOS 13 to both slots first.

Cheers!

 

[rmedure]

I have looked and cannot find a satisfactory answer to this queston that makes me comfortable. Which version, ext4 or erofs, do I need for a North American version of the OP 8 Pro? Thanks in advance.

Additionally, you can verify the filesystem type of your system partition and data partition using DevCheck or similar app.

 

[Nimueh]

Additionally, you can verify the filesystem type of your system partition and data partition using DevCheck or similar app.

Where exactly in DevCheck though? I looked a while back and couldn't find anything

 

[Rootk1t]

Where exactly in DevCheck though? I looked a while back and couldn't find anything

Stock OOS13 is using EROFS filesystem.
You can find out what the FS is of the "system" (odm, product, vendor, my_*, ...) logical partitions by looking at the output of the mount command.

 

[Nimueh]

Stock OOS13 is using EROFS filesystem.
You can find out what the FS is of the "system" (odm, product, vendor, my_*, ...) logical partitions by looking at the output of the mount command.

Yea I know 13 is erofs, I said that this morning. I meant in DevCheck since that was mentioned earlier, I happen to have it installed and wanted to know for future reference. Thanks though

 

[Rootk1t]

I happen to have it installed and wanted to know for future reference. Thanks though

DevCheck -> Hardware tab -> Internal Storage -> Filesystem.

 

[Nimueh]

DevCheck -> Hardware tab -> Internal Storage -> Filesystem.

Great - that says f2fs on my stock OOS 11, so I'm even more confused now

Thanks anyway

 

[Rootk1t]

Great - that says f2fs on my stock OOS 11, so I'm even more confused now

Different partitions use different FS.
Data is using F2FS like on your screenshot, System is using ext4 on OOS11.
Tap Show near Disk Partitions.

 

[Nimueh]

Different partitions use different FS.
Data is using F2FS like on your screenshot, System is using ext4 on OOS11.
Tap Show near Disk Partitions.

Ahhhhh yes, now I see it - thank you so much

 

[PieceKeepr]

I'm using twrp_op8_erofs-3.7.0-b3.img on my IN2025 running stock OOS 13 (11_F.15). Definitely attempt boot before flash. Not sure if this is absolutely necessary, but I also made sure to install the new OOS 13 to both slots first.

Cheers!

It booted fine but the backup fails with error 255. It looks like TWRP stumbles over the swapfile but I'm not sure how to tell it to ignore the file. Can I delete swapfile without any issues? It's been a while, and a couple of phones, since I have messed with it.

I:addFile '/data/nandswap' including root: 1
libtar: ==> set selinux context: u: object_r:nandswap_file:s0
libtar: failed to lookup fscrypt tar policy for '/data/nandswap' - '1ab2bbc9c89884da'
I:Closing tar
Splitting thread ID 0 into archive 20
I:addFile '/data/nandswap/4PI+FDAAAAg,nbYGkZ5miPe+6IVUfQDf' including root: 1
libtar: ==> set selinux context: u: object_r:nandswap_file:s0
I:Error adding file '/data/nandswap/4PI+FDAAAAg,nbYGkZ5miPe+6IVUfQDf' to '/data/media/0/TWRP/BACKUPS/c68e271e/OP8Pro TWRP/data.f2fs.win019'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/c68e271e/OP8Pro TWRP/data.info'
createTarFork() process ended with ERROR: 255

EDIT: Deleted swapfile and TWRP completed the backup without any other issue and swapfile regenerated on reboot.

 

[CurlyTemple]

My OP8 keeps trying to reboot to recovery mode, but gets stuck on the screen saying bootloader is unlocked. How do I reboot it to system, so I can get back into ADB debugging?

I tried
fastboot flash recovery_a twrp_op8_ext4-b3.img
and then
fastboot flash recovery_b twrp_op8_ext4-b3.img.
Both showed successful, but the phone now gets stuck on the bootloader unlocked screen. I can press Volume Up + Power to turn it off. It started to system again twice, but now only keeps trying to start to recovery -- which apparently didn't install properly. Please help!

 

[CurlyTemple]

Also, the phone turns on when I connect the USB cord. I did enable USB debugging for this computer automatically, but adb devices and fastboot devices commands don't return device ID.

My OP8 keeps trying to reboot to recovery mode, but gets stuck on the screen saying bootloader is unlocked. How do I reboot it to system, so I can get back into ADB debugging?

I tried
fastboot flash recovery_a twrp_op8_ext4-b3.img
and then
fastboot flash recovery_b twrp_op8_ext4-b3.img.
Both showed successful, but the phone now gets stuck on the bootloader unlocked screen. I can press Volume Up + Power to turn it off. It started to system again twice, but now only keeps trying to start to recovery -- which apparently didn't install properly. Please help!

 

[rodken]

My OP8 keeps trying to reboot to recovery mode, but gets stuck on the screen saying bootloader is unlocked. How do I reboot it to system, so I can get back into ADB debugging?

Your boot sector/partition seems to be corrupted.
-- Use the MSM Tool.

 

[CurlyTemple]

Your boot sector/partition seems to be corrupted.
-- Use the MSM Tool.

Do you think this is necessary even after it booted to system twice after the flash, but won't do so again?