yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] v12xke:
Flashing TWRP removes Magisk, so this is to be expected. I usually flash TWRP.zip, kernel.zip, magisk.zip together. You can queue all 3 of them up (using add more zips) before booting to system.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Supaman45:
Hey guys,

Any help out there? I've messed up somewhere along the line and have myself stuck on a black screen with only the ability to boot into bootloader screen. However, I'm unable to get my pc to recognize the device in order to communicate. Any ideas?

I had originally booted to the twrp image then from there I flashed the twrp zip. Once I rebooted, I no longer had the device to pc connection so I elected to reboot to recovery and restore the device and that's how I ended up in my current predicament.

Any help is appreciated.

SAS
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
If you can get to the bootloader than there is an issue with the pc not seeing the device.

Can you try a different usb port, usb cable or PC?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] NepoRood:
You need to flash the stock firmware, remove the "-w" from the flash-all script and you will keep your data
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Supaman45:
That was it! Thx. I tried two of the four before I posted this yesterday.

All is well now.

:good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] PistolSlap:
Hello there,

I have a major problem with my twrp on my Pixel 3. I can make backups just fine, but when I attempt to restore it it says it's restoring fine, but in reality it's deleting my entire system and boot partitions and softbricking the device. I can only rescue it by hard rebooting into bootloader and flashing stock system.img and boot.img, and that will let it boot but there will be strange issues unless I flash the entire image using flash-all.bat. This sucks. :( Making full backups is the main reason I use TWRP so this is really ****ty. Does anyone know why this is happening? I appreciate any help.

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
First, unless you're a developer and helping to work on twrp I wouldn't call it really ****ty. It would also help to know what you're backing up and trying to restore. Are you backing up boot partition, data partition, and system image and trying to restore all that? With that said, these dual slot devices are difficult to play with and I've also had issues restoring. I've found it easiest to flash the factory image with the flash-all batch file, less the -w to return to stock.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] PistolSlap:
Well I mean really ****ty in the sense that it's really unfortunate that I can't make backups -- I find it so much easier to have a snapshot of the system that I can go back to rather than returning to factory stock and having to reroot and reconfigure everything etc.

I was yes backing up boot data and system, and there is also new items vendor and system image which I havent seen before and I'm not sure if I should be doing.

Is the trick that I have to be on the same slot (i dont know what it is, only that there's A & B) while restoring as you were when you backed up? I know you can switch slots in TWRP but I dont know what use that is. This is totally new stuff to me with these new systems. :/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] NepoRood:
Boot, System

Image

and Data, that's what you want to backup and restore. Sometimes the factory firmware doesn't boot (goes to a black screen) You would then reflash the factory firmware using fastboot, but remove the "-w" from the flash-all script(s), so it doesn't wipe your data.

You will need to install TWRP and Root again though, this isn't a problem when using the few custom ROMs available
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
You should probably start here https://xdaforums.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123

If you want to backup system you should be backing up (and restoring) system-image instead.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
Happy New Years everyone :)

Friendly reminder for the New Year

XDA etiquette

If someone helps you, etiquette requires you thank the person that helped you.

The way to do that on XDA is tap the thanks button/icon or tap the Developer's donate link.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] CZ Eddie:
I haven't trusted a TWRP restore in a couple phones now. Pixel 1 and 5T and now pixel 3.

Perhaps calling it for what it is, is required.

---------- Post added at 07:55 AM ---------- Previous post was at 07:53 AM ----------

With that said, I am still so thankful for TWRP for a multitude of other reasons.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] PistolSlap:
Well at least I'm not the only one. :/ Nandroid backups have been a huge boon to me for as long as I've had smartphones, so it sucks if a change in hardware renders them inoperable or even unreliable. Maybe a fix will be found.

Also thanks to [MENTION=4487388]jcmm11[/MENTION] for the helpful guide :)

---------- Post added at 08:50 AM ---------- Previous post was at 08:45 AM ----------

I actually tried running the bat without -w and yes it left my sdcard storage intact, but also the operating system, it would go through the whole process and say everything was all good and reboot and the old OS was still there except a lot of things behaved really screwy. It was only by wiping all that it would do a full reset of the OS.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Unfortunately security dictation from Google has made for a trust solution that makes it harder for restoring system under a dm-verity kernel. It requires a lot of user education and dedication. A/B slots have made it harder, and the removal of dedicated recovery partition to have our own sandbox. All these have caused lots of heartburn for education, and has been slowly making it harder for casual users to backup their phone via their own methods.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] CZ Eddie:
Yessir, I am not here to put down your hard work. :)

You guys are doing a phenomenal job despite Android making it a PITA the last few years. :up:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] PistolSlap:
Ah that's frustrating, well I'll try to find a tutorial. Thanks for working on it anyway :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Axelay.mk3:
Hello! I posted this question in another thread a while back, and it was recommended that I post it here to try to get further information. I'm attempting to create a nandroid backup and am getting an error message which states createTarFork() process ended with ERROR=255.

Device: Pixel 3 XL, Google version, unlocked bootloader, rooted via Magisk

TWRP version: 3.2.3-3-crosshatch running from an image via fastboot boot

I was able to ADB pull the recovery.log and am attempting to figure out what is causing the 255 error, but I can't make heads or tails of what I'm seeing. Here are the previous several lines before the error in the log.

I:addFile '/data/vendor_ce/0' including root: 1

==> set selinux context: object_r:vendor_data_file:s0

failed to lookup tar policy for '/data/vendor_ce/0' - 'ae2a034a0014e5c2'

I:Error adding file '/data/vendor_ce/0' to '/data/media/TWRP/BACKUPS/8AAY0GHR3/1970-03-18--19-18-39_PQ1A181105017A1/data.f2fs.win000'

Error creating backup.

I:ERROR tarList for thread ID 0

Error creating backup.

I:InfoManager saving '/data/media/TWRP/BACKUPS/8AAY0GHR3/1970-03-18--19-18-39_PQ1A181105017A1/data.info'

createTarFork() process ended with ERROR: 255

Backup Failed. Cleaning Backup Folder.

This phone has been running a stock ROM ever since I got it (and I don't currently have any plans to go for a custom ROM). All I have done was to get the TWRP image running from the bootloader so that I could get Magisk installed and rooted. The first attempt at getting Magisk installed resulted in a complete failure and bootloop, so I had to wipe and reinstall the whole OS from a Google downloaded image. My last several phones were all running custom ROMs, so I've never actually run a TWRP backup without including every partition. Should I not be including that if this is a stock ROM...? Why would having a stock ROM prevent me from backing up a nandroid? Sorry is this is a stupid question. Anyone have any insight as to what is going on here...? I'd greatly appreciate the help. Thank you!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
The general consensus is to not backup the Vendor image. Just backup Boot, Data, and System image.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Hi, did you happen to add an additional user to the device?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Axelay.mk3:
Negative, I am the sole user on the device.

---------- Post added at 09:11 AM ---------- Previous post was at 09:08 AM ----------

OK, so if I don't include the Vendor image, if I go to restore from the backup, I assume that means that I would need to first reinstall the Vendor image before proceeding any further? And I would need to reinstall the exact same Vendor image, and not any newer one? I ask because my device has been nagging me to update Magisk Manager, and I have a sinking suspicion that if I try to do this, it's going to brick the device. It already did this once to me when I was first installing everything on it and I had to start all over again because I didn't have a nandroid backup made yet.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
In my experience the data partition is the only one that really does me any good. Make any changes, different rom, a new install, etc. Then restore the data partition with twrp. Your apps and app data will restore. Anything on the sdcard will be wiped so back that up separately if you want to save anything. Magisk update should not "brick" your device. Also, if the device isn't totally dead it's not bricked.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Axelay.mk3:
Oh, sorry! Meant to say bootloop. Duh.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jawonder:
Getting this error when i try to backup Dirty Unicorn with January patch :-View attachment 4684693
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
In TWRP after getting error go to Advanced, Copy Log then attach copy of log to post. You'll find it in /sdcard/recovery.log
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jawonder:
Updated post with Recovery Log. Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
I:addFile '/data/vendor_ce/10' including root: 1

==> set selinux context: u:object_r:vendor_data_file:s0

failed to lookup tar policy for '/data/vendor_ce/10' - '1818945ea48a2bb6'

I:Error adding file '/data/vendor_ce/10' to '/data/media/0/TWRP/BACKUPS/8B1Y0SNRR/DirtyU/data.f2fs.win000'

Error creating backup.

So do you, or did you, have multiple users on this phone?

Looks like remnants from additional users (assuming they're not currently active)

Remove the directory /10/ from /data/vendor_ce/

Also remove it, if it exists, from

/data/[vendor_de misc_ce misc_de system_ce system_de user_de]

Then try again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jawonder:
Yes i have two google account and for the fun of it i added the other account as another user, didn't know that would cause an issue backing up . Removed it and backup is good now . Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] devsk:
Running into the same issue with error 255.

I never added another user, other than the owner. There is a Guest user but I can't delete it. I have several folders in /data

1|crosshatch:/ # find /data -name 10
/data/misc/gatekeeper/10
/data/misc/user/10
/data/misc/vold/user_keys/ce/10
/data/misc/vold/user_keys/de/10
/data/misc/profiles/cur/10
/data/vendor_ce/10
/data/vendor_de/10
/data/system/users/10
/data/system/usagestats/10
/data/system_de/10
/data/system_ce/10
/data/misc_de/10
/data/misc_ce/10
/data/user/10
/data/user_de/10
/data/media/10

Is this Guest user?

Or does it create these folders for another gmail account you add? As owner user, I have added 2 google accounts: one for work and one personal. And I need both of those. But those are not "users", they are both under the user "owner".

Fundamental question is: why does it have trouble with multiple users anyway?

How do I proceed here?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
Delete the 10 folders. As Google makes these devices more secure it's getting harder and harder to tweak them. The people at teamwin are doing their best but it's not as easy to get twrp to work like it used to. You'll just have to put up with it unless you can help teamwin with development.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] devsk:
But they contain a lot of stuff!! What is that stuff and why did Google create it if its not needed?

I wish we had an option in TWRP to ignore files that can't be backed up and give us a list at the end of files not backed up.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] devsk:
I think the complication is that there is a lot of files there which are encrypted with the other user's encryption key. I don't know who that other user is because I see only "owner" and "Guest" in the list in Settings, and I never activated Guest. But those files are definitely encrypted.

I wonder if we want to skip past this encryption hassle and just 'dd' copy the /data partition. With enough zeroes, it will compress to about the same size or even more to what it will do with FS copy. Only gotcha is creating the zero balloon to fill the empty space for better compression. But I think the cost is worth avoiding all this hassle.

---------- Post added at 10:12 PM ---------- Previous post was at 10:02 PM ----------

Interesting...10 was the guest user indeed. The key to removing the Guest account is to change to it by clicking on it from Multiple Users in Settings->System->Advanced. Once inside, pull down notification and click "Remove Guest". It will take you to Owner account. All the "10" folders are now gone. Will try to back up and see if it works now.

Update: Yup, it works after deleting Guest account.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ubergeek77:
Quick question - why does the OP and the official TWRP page say that ADB doesn't work? Because it does. ADB does work, and it's working from fastboot too.

I just fastbooted TWRP 3.2.3-3 to do the January update, and I was able to use ADB with no problems whatsoever. I've never flashed TWRP on my Pixel 3XL, and it looks like I'll never need to.

I was holding off from updating my Pixel for a while because I was under the impression ADB wasn't going to work from fastboot, but that's not true. I'm sure a lot of others arriving here from Google, or people who only read the first post, were under the same impression. The TWRP download page hasn't been updated either.

Can the OP and the TWRP page be updated to be more accurate?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
What do you mean by adb works in fastboot? Adb and fastboot are two different things. You use fastboot when booted into the bootloader and adb when booted to system or recovery. I think what the OP meant is that adb sideload doesn't work in twrp.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
In the beginning adb would not work if you fastbooted the TWRP image. It did work if TWRP was flashed to the phone.

That has since been fixed. See https://xdaforums.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623/post78392266

I assume (dangerous word, and I haven't confirmed this) that adb sideload also now works. I may try it with the next OTA (normally I just flash the full image after removing -w).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
I'll admit that I haven't tried sideloading either. I update the same as you. I guess you get into a habit and do it the same way reach time. I'll be curious to hear your results.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ubergeek77:
It does. I used ADB sideload to re-install Magisk.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Darkwing_Duck:
Confused, there is no "remove"???
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
If you are referring to the flash-all you need to remove from the file the -w.

If you are referring to removing twrp "fastboot flash boot boot.img". Boot.img can be found in the firmware zip.

Hope this helps.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gogoffm:
Can confirm it works. Flashed latest Kiri Kernel via Sideload.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] David B.:
On the 3 XL?

---------- Post added at 09:35 PM ---------- Previous post was at 09:15 PM ----------

I imagine this has already been asked and answered somewhere but I cannot find where so I will ask: Can I update stock without TWRP getting wiped each time?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Negative. Twrp will get wiped no matter how you update.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] David B.:
Okay. One more question: can I still sideload the update via TWRP though?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Not recommend. You'd be better served doing it through stock recovery, or fastbooting the factory image :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] David B.:
Dang. I was hoping that I could install stock updates without ever needing to make use of a computer. ? I'm not questioning the recommendation, but I am curious about what makes sideloading through TWRP undesirable. I can understand not using the OTAs but even the full factory image is no good?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Have an interesting issue. If I take a backup from one pixel 3 xl and restore it to another pixel 3 xl I am not able to set a new fingerprint on the restored phone.

Background:

backed up and restored only /data. Have tried backing up and restoring boot and system image too.

restore phone fresh flash with -w and basic setup completed with no fingerprint or pattern set.

removed pattern and fingerprint from original phone before backup.

removed settings_fingerprint.xml and locksettings.db, locksettings.db-shm, locksettings.db-wal before backup.

Any ideas would be helpful. This issue will cause those that want to restore for RMA purposes no to be able to set a fingerprint. Even if you remove all security before the backup.

Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dadenet:
Dear friends ,

someone can tell me the correct procedure to do a backup on pixel 3xl ? .........every time that a try a custom room , and after restore the backup of my stock rom , the operation does not work , device go in bootloop and I need to reflash the stock image every time.

I usually create the backup with , system , boot and data .........needs something else ?....... It's better to create the backup without finger password ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] NepoRood:
TWRP for Pixel 3/XL has had issues since the beginning, when it comes to Stock. You can restore custom ROM's all you want, apparently.

You can do a restore of Stock, then flash the firmware using fastboot, if you remove the "-w" from the script you will have your data still intact. All that work is the reason I'm not on Stock anymore ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Do you have the backup and restore logs to see what happened?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
System or System image?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Topse:
I backup only the data partition (stock,customROM).

The other stuff is easy flashed with flash-all without -w.

Or with customROM zip.

Also I only boot TWRP(latest version).

Before I flash magisk I boot my freshly flashed Rom first and boot TWRP again !

I have no issues since I do it this way.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dadenet:
First of all thank you to all for the precius help.

PATH=%PATH%;"%SYSTEMROOT%\System32"

fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5034669.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash radio radio-crosshatch-g845-00023-180917-b-5014671.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot -w update image-crosshatch-pq1a.190105.004.zip

............Must I rewrite like following : fastboot update image-crosshatch-pq1a.190105.004.zip ?

I'm sorry but after the restore , my device is been in bootloop , no possible to give you the logs.

I flagged , on twrp , system , boot and data like usually.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jawonder:
I’m now getting error 255 when i try to restore a backup . My backup were restoring fine until i tried a GSI rom . I did went back to January stock Rom after a complete wipe and then installed DU . I Did a backup DU then wipe and installed AospExtented . Backup up Aosp extended and then wiped Sytem, data and cache and tried restoring DU backup which gave me error 255 . I then wiped and tried to restore AospExtended and got the same error as seen in screen shot below .

View attachment 4694758
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Have had the same issue a few times messing around with ROMs.

Try a flash with the factory and -w then restore.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
Did you get a recovert log in twrp after you got the error? If you did you can see what file is causing the problem.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jawonder:
I did do a log, is there a way to get it from TWRP Incase i can’t boot and have to go back to Stock . If I go back to Stock not sure if it would be wise to flash without the -w . Gonna try wipe and flash Du or AospExtebded , i have those rom zip on my sd .
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
The log should go to the same location as the TWRP backup. Do you have more than one user on your device, or even used the guest account. That's most likely the problem. It creates some additional folders and since it's not the main account the encryption is different and twrp fails trying to decrypt it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jawonder:
I know where to find the log . Afraid it might get wipped if I have to flash Stock with -w .No, only one user . I had that multi user problem awhile back but had fix it after finding the issue .
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
You should be ok flashing with the -w removed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
I'm telling you just flash factory with -w.

Don't even finish the setup and boot to bootloader and fastboot twrp.

Do your restore.

I have had this issue with restores.

Can't tell you the cause. Might be because of ROMs or a defect with twrp.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jawonder:
I just did that and tried to restore a backup which i stored on my pc and that restore also failed . I then had to flash Stock with the -w and did a fresh install of the same rom i was trying to restore . Which was DU . I wondering if installing the GSI rom left something over that’s causing the inssue , which should’ve be because i flashed Stock with -w.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Just for s**ts and giggles try the restore over a fresh flash of factory with -w.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jawonder:
When i flash a fresh stock i wiped System, data and cache and tried to restore a backup of DU from my PC and it didn’t work . You are saying i should try this again ? . Or you are taking about restore a Stock Rom after flashing Stock with -w .
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
You did what I said.

Try a factory flash with -w

Install du and twrp

Restore just /data

That should get you back.