yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco X3 Pro] Tomo123:
New member + all of the above. Recipe for disaster.

Don't come crying later on how your Poco suddenly bricked... without any reason whatsoever...
[Xiaomi Poco X3 Pro] SampreethSivakoti:
Bruh i am just a new member but not my first time for all this. 🫡
[Google Pixel 7 Pro] jake.99x3:
Hi all, I hope this isn't a thread that has already been posted... I found it interesting that there is no TWRP or any custom recovery for Pixel 7/7 Pro. I understand it's not needed to flash different rom's such as Paranoid Android or Spark OS but I figure it would be helpful no? My prior device was a iPhone 12, haven't run a rooted android since my Galaxy s4 way back in the day. Is this something somebody is actively pursuing or no as it's not needed? Curious on what the situation is with this, loving my p7 pro. Cheers!
[Google Pixel 7 Pro] JakeDHS07:
TWRP has been nearly an entire Android version behind for awhile now so I haven't been able to use it on my last couple phones. I believe it is still being worked on but since it's been so far behind due to the changes to Android and it's migration to ramdisk installation it's mostly fallen out of use sadly. I do miss it sometimes as well.
[Google Pixel 7 Pro] 96carboard:
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
[Google Pixel 7 Pro] old_fart:
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.

Can there be a lesson learned from that ?
[Google Pixel 7 Pro] HipKat:
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
[Google Pixel 7 Pro] JakeDHS07:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
[Google Pixel 7 Pro] HipKat:
Exactly! I used to do a complete backup, periodically. One day I screwed something up playing around at work, went to Recover and flashed my backup. Fixed it in a few minutes
[Google Pixel 7 Pro] JakeDHS07:
Yeah it would be nice to have for sure 😓
[Google Pixel 7 Pro] Misterxtc:
Same here, a nice custom recovery would be sweet. If I had any clue how to build one I would be all over it.
[Google Pixel 7 Pro] EtherealRemnant:
Is it even possible to do a nandroid backup anymore with the changes to Android filesystems and permissions? I mean you can't even flash a full firmware package in fastboot anymore, part of it has to be done from fastbootd.

The A/B system is not for power users who manually flash things. It's so that updates for the 99% who use their phones normally can be done in the background. It also adds a failsafe in case one slot gets corrupted since it will automatically boot the other slot after so many failures. Previously such a failure would be an automatic brick.

Also, I think most of us power users are using the A/B system normally at this point too. You have to go out of your way to not flash an update to the other slot, all the defaults do.
[Google Pixel 7 Pro] 96carboard:
That's insane. And dangerous. When it messes up, good luck fixing it.
[Google Pixel 7 Pro] HipKat:
Ummmm, what??
[Google Pixel 7 Pro] Beefheart:
TWRP is a big miss for me. Nandroid Backups and phone based file explorer without having to boot to Android were just two of the numerous features I used regularly. To say it would be useless is ridiculous.

I for one would be very happy to have it make an appearance on the Pixel 7 Pro. I'm not holding my breath though, the Pixel 6 and 6 Pro still don't have it I believe.
[Google Pixel 7 Pro] Renate:
I've used TWRP in the past. I've never understood the attraction.

Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?

Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.

As Patrick Henry said, "Give me ADB or give me death!"
[Google Pixel 7 Pro] Beefheart:
You sure you've used it? TWRP is fully touch screen.
[Google Pixel 7 Pro] Renate:
You're right. I'm conflating stock recovery with TWRP.

I do remember big tiles and tapping on them.

Still, I prefer to keep my fingers on the (desktop) keyboard.
[Google Pixel 7 Pro] Beefheart:
I'm as much of a command line fan as the next nerd, but TWRP offers multiple features not available via ADB.
[Google Pixel 7 Pro] HipKat:
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
[Google Pixel 7 Pro] Renate:
Ok. You're doing backups to a USB flash drive? Fair enough.

But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
[Google Pixel 7 Pro] HipKat:
No, doing backups to internal storage, actually. How am I going to access a USB flash drive with a telephone if I’m sitting at a friend’s house and something gets corrupted, phone won’t boot, and I have to reboot to recovery where I can access an internal back up? Which cannot be done with stock recovery.
[Google Pixel 7 Pro] Renate:
Well, you should be more particular in your choice of friends. Make sure that they have complete flashing facilities, UARTs, protocol analyzers, oscilloscopes... :p
[Google Pixel 7 Pro] HipKat:
Meanwhile, back in the real world...... ;)
[Google Pixel 7 Pro] FlipNDip:
What would be the next best thing to TWRP?
[Google Pixel 7 Pro] Markeee:
📳🔥PixelFlasher for Google Pixel 7 Support Thread.

This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...

xdaforums.com
[Google Pixel 7 Pro] halfbytecode:
A custom recovery with data decryption support, like TWRP, would be a valuable addition for our device. The ability to wipe the data partition minus the internal storage, from the recovery, would be a god send, saving us all the time involved in backing up all our files, while switching ROMs and even while clean flashing certain ROM updates. All other benefits would also be appreciated.

I saw one developer is trying to bring TWRP support for Pixel 6 series, followed by Pixel 7 series. Hopefully, things work out for Pixel 6 and 7 series.

Regarding the installation process, it can possibly work similar to how the flashable Magisk patches the ramdisk included in the init_boot partition, and then it flashes the resultant image which includes Magisk. Similarly, it may be possible for the recovery part of the vendor_boot to be patched on the device, to replace the stock recovery with the custom recovery, making the resultant vendor_boot.img flashable normally, through apps like Kernel Flasher, or the entire process be done through a dedicated recovery app, like the TWRP app, or better yet the entire process can be carried out through a flashable zip, similar to Magisk, that can be flashed over ADB through existing recoveries, such as those included with various custom ROMs.

Edit: I just remembered that, about a decade ago, during the initial days of ClockWork Mod recovery and maybe TWRP too, devices like Samsung Galaxy S2 did not have a dedicated recovery partition, but rather the recovery was part of the kernel even then! Custom recoveries were actually installed in a manner, similar to some of the ideas, I shared above.
[Google Pixel 7 Pro] halfbytecode:
I just found an useful topic detailing the typical process to install TWRP on devices that don't have a dedicated recovery partition.

https://xdaforums.com/t/tutorial-ho...hat-does-not-have-recovery-partition.4572311/
[Google Pixel 7 Pro] prana_Sky:
now all we need is someone knowledgeable enough for portng TWRP,

Fingers🤞 it's doable. would make the pixel line worthy
[Google Pixel 7 Pro] Dr.Pepper:
Why do you need TWRP? For what?) Only for backups probably...(the only feature i miss)
[Google Pixel 7 Pro] HipKat:
Right??

I haven't missed it. Even when I had it, I think I actually had to use a Nandroid once
[Google Pixel 7 Pro] schmeggy929:
Ye

Same here, I haven't needed TWRP for the last 6 or 7 phones. HTC days would have been the last time I had it. I don't see the need for it, I have pictures, app data and text messages that are over 10 years old. I never once used a Nandroid Backup in that span.
[Google Pixel 7 Pro] prana_Sky:
Nah man, I use twrp for everything!!

It really help me get things done when I need it the most. It's like having a super computer in my pocket. When I'm down and out I can look to twrp to cheer me up. It's beautiful
[Google Pixel 7 Pro] CZ Eddie:
I used TWRP all the time when it was working well on older phones I've had.

I'd spend hours setting up my favorite ROM and all the customizations I liked just the way I wanted them.

Then, I'd back up the ROM and anytime I found a new ROM I wanted to try, I'd give that a try. And then I'd restore my previous ROM if I didn't like the new one.

By being able to restore the full ROM, I'd save countless hours of not having to set things up all over again each time.

I hardly ever test new ROM's anymore, since there is no TWRP.
[Google Pixel 7 Pro] HipKat:
OK, that's a good point
[Google Pixel 7 Pro] teknowiz23:
I'm not updating and reflashing even though I think I may have installed telestra firmware for a Verizon Pixel 7 Pro.. but it works. And I don't have the time to back everything up, manually and some what automatically.. then do all the stuff.. reinstall and then redownload all apps and possible re enter login info etc.. just don't have the time. If I had a twrp backup to fall back to.. it would make it such less of a risk of a waste of time or something I'd have to fix right away and spend more time with
[Google Pixel 7 Pro] teknowiz23:
I dunno if bounties are allowed anymore, but I'd definitely throw in a lunch for it
[Google Pixel 7 Pro] Dr.Pepper:
Emmm, google account save all passwords you need perfectly)
[Google Pixel 7 Pro] zepherz:
rsync works wonderfully for data backup/restore, but it will not help if you soft-bricked yourself and need to re-flash a ROM.

rsync in Termux can do backups quickly and wirelessly while only transferring the data that has changed. This could also be scripted and done on a schedule. If your second machine runs windows then you will need to install cygwin. When the second machine is Linux or Android it is even easier.

Here are some examples:

# From a remote machine, sync all user data from Android to PC folder (Android must be rooted), backup all user data only if it is newer and delete old files in the backup site if they no longer exist in source
rsync -vahu --progress --no-whole-file --inplace --stats --open-noatime --delete --omit-dir-times --no-perms -e 'ssh -p 8022' --rsync-path="sudo rsync" u0_a500@10.0.0.100:/sdcard/ /cygdrive/x/

# From Android, sync a single large file from Android to remote machine (Android does not need to be rooted), copying/updating only the parts that changed.
rsync -vah --progress --no-whole-file --inplace --stats -e 'ssh -p 22' /sdcard/Download/archlinux-rootfs.sfs username@10.0.0.101:/cygdrive/c/Users/username/Downloads/

Notes:

-e 'ssh -p 8022' #change your ssh port as needed

--rsync-path="sudo rsync" #this is needed to bypass Android file restrictions when you are entering the command on a remote machine

Of course you can also backup any app's data directory in /data/data/* (with root) but if you want to restore apps, then pair rsync with apps like Neo Backup or Swift Backup (which you can easily restore the .apk and backup folder to a new device with rsync).
[Google Pixel 7 Pro] Dave_247:
While it still arguably has some use, it's not as invaluable as it once was which is likely why people stopped actively trying to maintain or even trying to port it, as there just isn't enough to justify going to the trouble of it anymore on a lot of devices. Basically it's that thing where "it would be nice to have" but that's it.

Really what is needed is for someone to spend time creating an entirely new solution from the ground up that takes into account of all of the newer changes made to Android, rather the continue to try to piece together a relic of the past. It sadly is just what it is.
[Google Pixel 7 Pro] halfbytecode:
I think TWRP is quite needed at this point. A lot of ROM updates that includes major changes, require data wipe. Right now that means I will have to backup the entire internal storage, and have to restore it all after clean flashing the ROM update, requiring a lot of time to do so. This is also true while switching ROMs. I will also have to buy a flash drive especially for this, due to high amount of free storage required.

With TWRP and data decryption support, we can would we able to avoid all of that, and just wipe the data partition, minus the internal storage.

In the past, one of my phones would not fully boot due to overheating issues. TWRP worked and allowed me to backup all my data to a flash drive. With Nandroid backup and Titanium Backup, I was also to even extract and restore app data. Manually backing up app data from TWRP was also possible for me.

Moreover, I could disable Magisk modules in case of bootloops, by creating a file in the required folder through TWRP itself, thanks to the data decryption support again.

I was also able to manually place certain files in system partition that was not possible from within Android, with Magisk installed.

There are a lot more uses of TWRP, and I would say it is very much needed.
[Google Pixel 7 Pro] JohnTheFarm3r:
So....Lemme clarify a few things here.

- Even if the TWRP has decryption "support", you still need to format the data (storage too) if the developer (ROM) states so. Encryption is unique for each ROM and just because you can decrypt the storage, it doesn't mean that the Y ROM you flashed on top will now boot (it won't till you wipe the previous encryption "FORMAT DATA"). You need to FORMAT the storage regardless because the whole internal storage and data were previously encrypted by the X ROM. Those times you're talking about are in past.

- Disabling Magisk modules can be done via an ADB connection either through a PC or another Android phone that is rooted. If that's not an option, there are two other options, one, a bootloop protector module that will disable all the modules if your phone fails to boot multiple times to an XY module, and another option is using Magisk DELTA (HuskyDG dev) that has inbuilt bootloop protection that behaves the same as the previously mentioned module.

- Manually replacing or modifying the files via TWRP doesn't work anymore, and TWRP was not the reason why you could do that. Partitions are shipped only as RO (Read Only) since Android 11 and no matter if it's TWRP or even ROOT access, you can't modify the files inside the partitions by default anymore.
[Google Pixel 7 Pro] halfbytecode:
It has always been stated in the past too that changing ROMs will require wiping the data and internal storage. However, as long as the installed ROM and the target ROM have the same kind of encryption, it has always worked with just wiping the data, minus internal storage. If the newly flashed ROM boots after that, which has happened for me always, there really are no issues afterwards, with just wiping the data minus internal storage, since it removes the data from the earlier ROM that could interfere with the new ROM.

Clean flashing the updates of the same ROM, when needed, with just wiping the data minus internal storage through a recovery like TWRP, should work now at least.

It has always been possible to do stuff through ADB, but it relies on having access to a computer or another phone. Moreover, I have had bootloop protector module not work for me at least once. With TWRP, we did not even need any module to do the necessary.

Searching around a bit revealed at least one recovery flashable zip project that enables making changes to the system directly through the recovery even on Android 13.

A custom recovery like TWRP has always brought a lot of functionality, with a lot of it being only possible through a custom recovery, and the rest being usable without having access to a computer or another phone always. It is also worth adding that a lot of devices that are officially supported by TWRP 12, have unofficial support for Android 13 added for quite some time now. As such, TWRP is being used on all sorts of devices.
[Google Pixel 7 Pro] Wishmasterflo:
Yes exactly. I got a Pixel 7a today and before I used Oneplus phones since a few years back and always had TWRP or Orangefox recovery running on it and I like it to have a custom recovery like TWRP or Orangefox.
[Google Pixel 7 Pro] sawdoctor:
I remember nearly bricking an s2 because of that lol. I had no idea recovery was part of the kernel at the time as I'd only used clockwork on the note 2 which was different
[Google Pixel 7 Pro] halfbytecode:
Sounds like you tried to flash the recovery image on the S2, which would have flashed it over the kernel.

Now TWRP can be booted using the provided image through fastboot, and installed permanently from the phone itself, on supported devices.

While flashing a ROM through TWRP, it also gives an option to retain TWRP after the flash process completes. There is also a Magisk module that can be flashed before installing an OTA update to preserve TWRP after the update, if the update is being installed through the ROM's OTA updater.
[Google Pixel 7 Pro] HipKat:
I remember when Clockwork and TWRP were choices and more people used CW
[Google Pixel 7 Pro] Lughnasadh:
I may or may not have been one of those people 🤣
[Google Pixel 7 Pro] HipKat:
I definitely was. TWRP was the newcomer
[Google Pixel 7 Pro] kkjb:
Way back in the dawn of artisan custom recovery. HTC Zara. Only works on charger... Every once in a while I recheck my expectations on modern devices and what we had......way back when.
[Google Pixel 7 Pro] xtcislove:
Ahhh clockworkmod. I still can find my first threads here on xda. I released a "custom" rom for the htc desire in 2010. :-D I had a thread annoouncing S-off for the HTC Sensation and the people did not had hopes that im right.

Golden
[Google Pixel 7 Pro] kkjb:
Nice to see old timers. This is slightly newer build.

I believe I had to do motherboard short trace to get into engineering mode.

I am always amazed by our expectations on touch events, I use this and it's a 2-4 count in your mind from commanded action to screen results. Since I'm actually really old....I can say "I remember when"

Sorry if I hijacked thread...back to original programming.
[Google Pixel 7 Pro] Sredna76:
As new user of Pixel 7 pro I can just agree that TWRP is very much needed for backup and restore especially when you have failed in flashing an upgrade and also want to test other custom fw. It has saved me lot of time in the past with other phones such as OnePlus 8t 6t etc. All my android phones have had a decent Recovery such as TWRP or similar. If someone will make a TWRP for Pixel 7 Pro I will be much happy.
[Google Pixel 7 Pro] wangdaning:
You could always try to build it and see what happens. Three pages and no one has.
[Google Pixel 7 Pro] HipKat:
...and no one has even mentioned Multirom!
[Google Pixel 7 Pro] wangdaning:
It could work
[Google Pixel 7 Pro] DroidRommer:
In my opinion what makes a custom recovery such as twrp nice is that you can literally backup and restore multiple roms on the go. Also, I myself get bored of the same rom after a while so I'll jump to another for fun. For those of you unaware, there is a magisk module called data backup creator you can find on GitHub that allows you to use terminal commands to backup a rom similar to how a custom recovery does. It's a bit of a learning process but it creates the backup really fast and restoring involves another module that is called data restore carrier. I'm gonna look into it some more to see if it's possible to side load the backup file or something along those lines in a new recovery like lineages temporary one. I will say that in my opinion it blows any apps I've used since titanium backup out of the water. If anyone has any advice or wants any links to these files feel free to let me know!

DROIDROMMER
[Google Pixel 7 Pro] scorpio76r:
Can you please share the links?
[Google Pixel 7 Pro] DroidRommer:
Yeah no probs!

This is the data_backup module

and this is The restore_courier module

Be careful though, so far it's worked for me on evolution x rom and stock but I always make sure I use another means for backup such as google one just in case. The instructions are decent so just read over them carefully and you should be fine. Any questions just let me know and I'll try to help if I can. I need to experiment more with it myself
[Google Pixel 7 Pro] V0latyle:
I'm late to the conversation, and I hope I'm not rehashing anything that's already been pointed out...

Firstly, we have to understand that the Pixel series are A/B devices and do not have a recovery partition. The recovery kernel is compressed into the boot image, alongside the system kernel. Due to this compression, it is not possible to "install" a custom recovery unless it supports the compression method; flashing a TWRP image to /boot will result in /boot being overwritten with the TWRP image only, so the phone will only boot to TWRP.

The workaround for this is to "live boot" the TWRP image: fastboot boot twrp.img

In this context, we are telling fastboot to boot the image we send it over ADB, so instead of loading the /boot partition, it boots the TWRP kernel, and you're then able to use TWRP. When the device reboots, however, it will load the contents of /boot which will start the system kernel.

Is TWRP useful? Yeah...to a point. The bootloader is pretty limited in what it can do - it can't resize or delete partitions (which you should be very careful when doing) and the stock recovery's userspace mode (fastbootd) will only accept signed images AFAIK. So, in this sense TWRP is useful for installing legacy style ROMs in .zip format.

That being said...The Pixel 7, like most Pixels, is a Treble enabled device, which means that it's meant to run generic one-size-fits-all kernel images, as well as generic system images. The HALs that would typically be built into the kernel are now in /vendor_boot, and the device specific features that would typically be built into the system images are now in /product. This means that the device can run any GSI with any GKI, and you can flash both partitions from bootloader, obviating the need for TWRP.
[Google Pixel 7 Pro] Albirew:
Well, thanks for the full reminder =)

Most of the people wanting twrp here are using it as a simple way to full data backup/restore.

In this case, `fastboot boot twrp.img` would be more than enough, but i believe we would still need a customized recovery image with device encryption support.
[Google Pixel 7 Pro] Wishmasterflo:
I think I will have a Orangefox recovery ready soon for my Pixel 7a.

Some small things needs some adjustments so I will try to build a successfull build of Orangefox in the next days.
[Google Pixel 7 Pro] Yeedatoy:
Who's TWRP device tree is that on GitHub? P7P. Someone in here?
[Google Pixel 7 Pro] Yeedatoy:
GitHub - Peter-Levine/android_device_google_cheetah: TWRP Common Tree for Google Pixel 7 Pro

TWRP Common Tree for Google Pixel 7 Pro. Contribute to Peter-Levine/android_device_google_cheetah development by creating an account on GitHub.

github.com