yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Bradl79:
Great, glad u got everything working good.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mrnovanova:
Any idea why I'm unable to restore my backups. It starts then I get red writing and when I try to reboot I end up in fastboot. Which TWRP version should I be using?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
TWRP 3.3.1-33 Unified Op7/Op7Pro/Op7Pro5G:

Fixed the unified script for a better compatibility with kernels (Before this build OnePlus 7 users were able to flash oneplus 7 pro kernels)

TWRP 3.3.1-33 Unified Unofficial by mauronofrio

TWRP 3.3.1-33 Unified Unofficial Installer by mauronofrio
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] kyledowling:
Well duh. No where in the OP does it say that this TWRP (official or unofficial) supports Android Q DP 2. Half the stuff in OOS Q is broken too. Developer Previews are meant for exactly those people, developers.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] runningnak3d:
Before I tear into this, I figured I would ask if there was something obvious I was missing. I searched the thread and only found one other mention of adb not working while in TWRP.

I checked, and adbd is running with valid parameters, so am I missing something obvious, or is adb support not fully enabled yet?

PS - I come from the LG world, so I may know general Android inside and out, OnePlus specifics will take me a bit.

-- Brian
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
Adb is working
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] runningnak3d:
adb sideload is working, but adb shell / adb push .. etc is not.

I have 3.3.1-33 installed.

-- Brian
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Nekromantik:
working fine here

you might need to update your drivers
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
Or maybe adb and fastboot binaries. In all cases i have not problems too
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] runningnak3d:
Well I am an idiot today. Like I said, I come from LG, and I use Linux. I had my udev rules setup for the USB ID of an LG device so that I didn't have to run fastboot / adb as root. The OP7Pro has a different USB ID, so obviously that isn't going to work.

I updated the udev rules, and all is good. Sorry for the lame a** post, but at least when I have two people telling me that it works fine I knew I had better start looking for something on my end.

Thank you both.

By the way -- very nice job on the TWRP build. It is kinda disappointing that coming the OP world there are so many active devs that have been with OP for so long that there really isn't much to do - lol.

Everytime I think: "hey maybe I could do....." nope, someone has already done it, and done a nice job. I am sure I will find something that needs work ;)

-- Brian
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Nekromantik:
this breaks kernel flashing for 5g

i get unsupported device error when flashing kernel
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
This because i setted the proper values, you should ask to the kernel developer to add OnePlus7ProNR to device supported
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Nekromantik:
oh ok
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
Kernel Flashing Script and Right Props

So [MENTION=6047959]dabug123[/MENTION] [MENTION=3428502]Freak07[/MENTION] [MENTION=3910111]pappschlumpf[/MENTION] [MENTION=4684315]flar2[/MENTION] [MENTION=1211160]HolyAngel[/MENTION] can you please add OnePlus 7 Pro 5G to yours kernel flashing script? (Always if it is not supported don't add it)

These are the props used in the stock rom and also in the TWRP:

ro.product.name=OnePlus7ProNR
ro.build.product=OnePlus7ProNR
ro.product.device=OnePlus7ProNR
ro.vendor.product.device=OnePlus7ProNR
ro.display.series=OnePlus 7 Pro 5G

You need only to add in anykernel.sh a new device like this:

device.name5=OnePlus7ProNR

It should be enough.

Thanks in advance to all and sorry for the massive tag.

Have all a good day.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Jerreth:
Likely I'll get flamed for this but are there steps for a proper restore from scratch. I had backed up boot vendor data and system and restored all but vendor did not boot had to use MSM restore tools can someone give me the proper steps or is restoring not functioning at this point
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
Sorry, you used the MSM Tool and the device is not booting?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Jerreth:
No the MSM tool got me back and going. After trying to restore boot system and data the device would boot to the bootloader with no bootloader version or radio version. Not sure what happened was using the latest stable from twrp.me.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
have you backupped system_image and vendor_image? or normal vendor and system?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Jerreth:
Normal only. What items should I back up? I am not a noob to flashing ROMs recovering phones rooting it just seems with later phones coming out now things are changing and I am not certain what should be backed up now with these newer phones and which should be restored.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
You should backup: system_image, vendor_image, data (or userdata), boot.

Optionally modem and efs.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Jerreth:
Okay perfect I've never backed up the _image of any of them but have always been able to restore my phone's of course I was using a pixel this is my first OnePlus and I'm loving it I will back up the image versions of them and try restore and see how it goes thank you very very much for your time and input

---------- Post added at 05:10 PM ---------- Previous post was at 05:03 PM ----------

One last question, can you explain the difference between the _image and the non _image
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] RandomPooka:
Is there any good reason to back up those partitions NOT as an image? Would it even be possible to remove the option of doing so from the partition selection screen?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Jerreth:
Is that what it means? To back it up as an image? I legitimately don't know...
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] loshabih:
createTarFork() process ended with ERROR: 255

Hi

When i try to take backup it fails with createTarFork() process ended with ERROR: 255

I've attached the log

Edit 1:

The solution was

go to terminal emulator

su

pm remove-user 999
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] skeeter123:
Any luck with this?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] H4X0R46:
Here's a theoretical question for anyone that might know. Is it theoretically possible to flash a bunch of different roms and try them without formatting (only wiping userdata) so long as they're on the same security patch without encryption issues? Is that how that works?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
I think is not possible, but i will make some tries when i will have a bit of time
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Nekromantik:
would be good.

thats how it works on pixel devices.

as long as you wipe system and /data you can switch ROMs without wiping internal storage.

otherwise if you have like 50GB of data stored then you have to save and copy it back each time which will mean you spend hours on flashing ROMs.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] RandomPooka:
It's possible, if they're the same android version, on most phones.

It's not always a good idea. While it may boot and run, there's always a chance that your userdata may contain settings and app info from one ROM that conflicts with another you might flash.

The simplest and least problematic example is of sound files for ringtones and notifications that exist in ROM A, but not ROM B.

If you experience bugs, it isn't necessarily the fault of a ROM that you dirty flashed over another, and you should attempt a clean flash to be sure the bugs aren't coming from dirty flashing.

---------- Post added at 12:31 PM ---------- Previous post was at 12:16 PM ----------

Backing up a partition NOT as an image Bajaj creates a zip of all the files on that partition. Restoring it deletes the files and restores the ones in the backup. It also breaks any system that checks the integrity of the system partition to see if it's been modified, because you're deleting and writing files to the system partition.

Backing up as an image is more along the lines of cloning the entire partition. You snapshot the entire drive, save a copy of it. When you restore it, twrp obliterates the entire partition and replaces it with the backed up complete image of system that has never been tinkered with
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] BossNexusS:
I've done this on my OP6 you can do it. But since encryption on ROMs isn't always the same I had the issue where I went from rom a to rom b and my twrp was encrypted so it was all just letters and numbers but the system worked fine, just twrp was messed. I had to wipe internal storage to fix that issue.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] runningnak3d:
If backing up system and vendor as tar balls no longer works, those options should be removed. They were usually smaller than doing an image backup, but again .. kinda pointless if you cant restore them :)

-- Brian
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
Yes i'm planning this, i also already did a new build
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Nekromantik:
No I do not mean swap ROMs with keeping user data.

I mean swapping ROMs without wiping internal storage,

i.e photos videos etc.

Currently Lineage requires full wipe to install inc internal storage,

I do not want to wipe my internal storage between ROMs. You should not need to do this. On Pixel 2 XL I was encrypted and but all I needed to do was wipe data and system between ROMs. Not my internal storage.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] runningnak3d:
I hit the thanks button, but again, I want to say thanks .. and seriously great job on the build and your responsiveness to issues.

So far, everyone on the OP community seems great.

-- Brian
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] RandomPooka:
That's what I was asking about a few hours ago. It hasn't worked for me since I don't even know when. Nexus 6 maybe? It seems like a good thing to put to rest and never see again :)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] galaxys:
Also agree on removing them...
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] gururoop:
Just a small matter of concern, when I try to boot into TWRP using the command fastboot boot twrp-3.3.1-33-guacamole-unified.img, it always gives me the following error:

Sending 'boot.img' (56624 KB) OKAY [ 1.232s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed

I am using the latest version of platform-tools from Google. I am on OOS v 9.5.8, and I thought that this problem of not being able to fastboot boot TWRP was fixed after 9.5.4. However, flashing TWRP from Magisk works fine. I would like to add that I had accidentally tried to fastboot boot TWRP before the problem was fixed and it had screwed up my phone. I had to fastboot flash OOS and wipe all my data to get it working again. Maybe this problem is related to this? How can I provide logs? I have GM1911.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
Just update.your rom using phone settings local update and not fastboot roms
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] runningnak3d:
It is not just you. I also had an issue (it wasn't unknown command like you -- which IS weird since you are on 9.5.8), but I was getting another issue. I finally just flashed TWRP to boot, so I could boot it, and then fixed my boot once I was in TWRP. I really miss having a seperate recovery partition (and in the case of LG and Samsung a third boot partition for download mode). Eff up your phone so it won't boot on OP and you MUST have a PC to fix it these days....

-- Brian
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
New Unified TWRP 3.3.1-35 for OnePlus 7/ 7 Pro / 7 Pro 5G:

Removed system and vendor option from backup menu ( You must use system_image and vendor_image);

Removed TWRP app;

Updated the Installer.

TWRP 3.3.1-35 Unified Unofficial by mauronofrio

TWRP 3.3.1-35 Unified Unofficial Installer by mauronofrio

Have you flashed magisk after the twrp installer?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] djsubterrain:
Amazing work mate, many thanks.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] skeeter123:
Just installed the -35 unified version. Backup completed successfully. (Have not attempted a restore yet).

This process brought to mine two questions:

1) all of the boxes were checked as default. Is this the recommended setting for complete backup?

2) this may be a noob question but I have to ask it anyway.

If one creates a backup with the security PIN in place, is one forced to use the PIN to restore? Even if you have removed the PIN from the operating system at the time of the restore? Does that make sense lol?

Thank you for the tremendous work on this as well!

..
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Pvt WhoOkid:
I just want to say. Thank you for this. Honestly. you saved me from wiping everything.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] explosivequack:
Okay so I just want to make 100% clear because I feel like I'm starting to get it, but I feel as if people are leaving 1 key thing out of every tutorial.

To install magisk, are you installing it from your devices internal storage or are you using an otg adapter?

Whenever I flash the ota, and twrp installer, reboot into twrp, my data is encrypted, so at this point I should bust out the otg cable and install Magisk and the ota should boot correct?

Or when you flash the ota and twrp installer, when you reboot into twrp is your storage not encrypted? Because I've been seeing a lack of otg cable discussion around this forum, and I've never had a device with a/b partitions, so if it's not encrypted after rebooting back into twrp what am I missing?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] nanodan:
I'm confused. Are you saying your data is encrypted and you can't decrypt it? Like, your password no longer works?

1-download update (full zip only) and put it in root of sdcard

2-install update (full zip) from System Update page (local zip), don't reboot. Your boot slot is now the other slot.

3-use Magisk or EXKM to flash TWRP installer. Both slots now have a stock boot image with TWRP.

4-use Magisk to install Magisk *to inactive slot*. Whatever slot is currently not booted (aka the slot that your OTA update was installed to) now has Magisk. Install it "directly" as well if you doubt it and want to be sure. This will install it to the current slot, which will be inactive once you reboot, so doing this is useless, but it won't hurt.

5-reboot and enjoy your update with twrp and Magisk.

It's that simple. No USB-OTG required.

These devices force-encrypt data by default. When you set a screen lock during setup (not the fingerprint), it encrypts your data with that password. When you boot into TWRP, you must enter that password to decrypt, just like you do when you boot into system.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] explosivequack:
So I'm doing it through twrp, the oxygen ota works great and I have no problems with that.

Through twrp install the ota and twrp installer, reboot to recovery to switch slots, data is encrypted, my question is is this normal and should I just use an otg to flash Magisk so the phone will boot again, or is it supposed to encrypt the data.

The secure lock screen doesn't matter, I can have no secure lockscreen, boot into twrp and not be asked for a pin or pattern and data is not encrypted, but as soon as I flash the ota and twrp and reboot back into recovery the device gets encrypted.

Edit: I've got a gm1915 (t-mo) converted to int (aa) installing the aa ota through twrp 3.3.1-30.

This has happened to me with romaur, flashing any aosp rom(but the aosp roms boot without magisk) and flashing the ota, nobody is mentioning otg adapters, but I've been searching around and see people use an otg for Magisk and gapps on the op6t.

I'm new to a/b devices and just trying to figure out if this is normal or if I'm missing something.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] nanodan:
It doesn't matter if you don't set a lock of not, your data is still encrypted. AFAIK in order to be "unencrypted" you need a kernel that supports it and an fstab that doesn't have the force-encrypt flag on data.

This is gonna sound silly, but have you tried using "no password" as the password?

If you aren't on OOS then nevermind, I have no idea what is supported and what isn't with custom ROMs these days.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] explosivequack:
Okay so I'll give you a step by step.

Phone is completely fresh, bootloader just unlocked, phone has only booted to enable USB debugging, (no secure lockscreen, WiFi, accounts, etc) only files on sd card is the rom (romaur, ota, aosp, etc) and magisk, twrp installer and possibly gapps.

Reboot to recovery, wipe data factory reset, install rom and twrp installer, reboot recovery.

Twrp asks to be able to wipe system, as it does every time you freshly install it, enable it, system is encrypted. I just need to know if this is expected.

Aosp roms boot without magisk, while romaur or ota need Magisk to boot. If I try to boot without Magisk it boots back into recovery, or into the aosp rom with safe mode.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] nanodan:
Wait, your system is encrypted? Totally not expected.

It should just ask you if you want to enable modifications, to which you say yes. Then you flash what you need to and go on your merry way.

As to the Magisk thing, yep that's normal. If you have a Magisk-patched ROM it won't boot if you don't reinstall it. Not sure why though. Not an issue for me since I always have Magisk.

---------- Post added at 01:20 AM ---------- Previous post was at 01:16 AM ----------

The big factory reset button on the wipe page is the same as a reformat. You're screwing up your ROM by wiping the entire sdcard. You just need to go to advanced wipe and wipe /data, not the entire sdcard. This is why you're having problems after rebooting to recovery.

If you're switching to an AOSP ROM, then you need to flash it, factory reset as you have been and boot into it without anything else so it can format and encrypt your sdcard as it wants. Then you can reboot to recovery, copy your mods and Magisk back over, and flash them.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] explosivequack:
No when you click wipe and swipe to factory reset. I'm not wiping the sdcard. The file system is still there it's just encrypted.

Okay after my phones backed up im going to tinker and figure it out, thanks my guy.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] nanodan:
Try this please.

Boot into TWRP.

Wipe /system using the advanced wipe menu.

Flash romaur.

Flash twrp.

Take your important stuff off your sdcard and format user data.

Reboot to system so your sdcard and data can be setup properly.

Once booted, head back into recovery.

Swipe to allow modifications.

Put your data back into sdcard.

Optional step, might be important, might not: Wipe /data using advanced wipe menu.

Flash Magisk.

Reboot into ROM and everything should be good.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] explosivequack:
Can I try this with just a 9.5.8 ota zip?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] nanodan:
If it is a full zip and not an "OTA update," yes. Those steps should work for every ROM flashed through TWRP.

You can't flash zips with "OTA" in the file name through TWRP or anywhere if you have Magisk. It's gonna break things.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Hidarihitomi:
Unable to flash aroma version of gapps
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] BossNexusS:
Your problem I think is you went back and forth between aosp ROMs and OOS. You can't do that without wiping your internal storage or else your data will look encrypted in twrp.. The only way to have it not encrypted anymore is to completely wipe your internal storage from twrp.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] andre0005:
Well yes, decryption isn't working after all.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Mithri6:
I had the same problem. Windows recognized the op7p when oos was running but I had to manually install driver when it was in fastboot.

Go in Windows, settings, devices etc

If you only see it as Android and with no working driver then try to install.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] WillyRy:
This was going to be my next "check your pockets" suggestion. But you'd had it sorted by the time I woke up

I ran into same problem when I used a a GoPro usb-c cable.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] JanTehMan:
I flashed the boot image following the instructions, but now wifi and the Sound are broken. So I tried to flash the provided stock boot image, but this ends up in a bootloop, respectively it boots once, fails, and then boots back to the Stock recovery.

So I flashed once again the twrp image to get the device started at all and wanted to reset everything. But here's a problem too, it boots to twrp and freezes or at a different time it was unable to mount anything. So flashing a zip file though twrp is also impossible.

What do I have to do? Thanks in advance
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] zoman7663:
Flash from OTG or ADB sideload
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Logan0829:
Can I sideload magisk over adb sideload in twrp? Or does that need to be flashed with otg?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Mr.Crucial:
You can sideload
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] MTL33:
Sorry, but im not really good at these things. It wasn't really clear (at least to me), but if my active slot was "B" to begin with, did I have to switch to "A" before flashing twrp? Or was I right in keeping it at "B" (and do I now switch it to "A")?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] JanTehMan:
Thanks, I'll try that later.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] hagar006:
The install instructions in OP work exactly as they should and apart from "failing to mount data" works just fine using usb-otg... Havent tried sideload but im fine with this..

OS 9.5.4 on GM 1913

Massive thanks to all involved!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] rav101:
Hey,

I was wondering if you have everything you need to work on getting decryption working or if you need user feedback in the form of logs or anything like that?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
Yes i have a telegram test group
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] JanTehMan:
adb sideload is failing...

I tried different versions of twrp (3.3.1-2, -4 and -5), in each one wifi and sound are broken. I assume this correlates with the used boot image.

Furthermore, I tried to install the stock roms (https://forums.oneplus.com/threads/...a-oxygen-os-repo-of-oxygen-os-builds.1033129/) for my device (GM1913, OxygenOS 9.5.4 GM21BA) via adb sideload or local upgrade, both are failing.

So then I wanted to flash the stock boot image, also provided at the oneplus forums, which results in a boot loop...

I'm getting kind of desperated
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mauronofrio:
You should make a format data
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] JanTehMan:
How exactly? twrp is unable to do anything