Develop Bugs

Worth decrypt a Oneplus 3 ?

Hell guys. I switched from OOS 3.4.2 to CM13 last week. The Phone ist still encrypted. Now my question.
Is it worth to decrypt the phone via TWRP or ADB command ? I mean, i disabled PIN at boot. So i think im able to flash updated CM13 zip's and TWRP updates. I hope i'm right but i think it's possible.
What do you guys think ? Is my phone much faster after decrypting ?

Nvm. I decrypted it with TWRP and installed all new. Now it's not encrypted with CM13.

Well i did some research and i don't believe decrypting would be much of a boost in performance. What are your findings right now? noticed any boost in performance? and what exactly did you do in TWRP to decrypt it?

what re the benefits of decrypt. I believe im still encrypted as I have never wiped my data...

i think its a bit faster now. but its not really noticeable

Probably the only reason you would unencrypt is to install MultiROM I guess.

rirozizo said:
Probably the only reason you would unencrypt is to install MultiROM I guess.
Click to expand...
Click to collapse
yeah I mean I haven't found the need to decrypt and don't see a need neither. I don't even know how to use multiroom. I rather just back up two roms and restore between the two I feel like multi rom is a bit too complex to set up two roms. my understanding is that everything has to be flashed in a certain way or it wont work.

egren58 said:
yeah I mean I haven't found the need to decrypt and don't see a need neither. I don't even know how to use multiroom. I rather just back up two roms and restore between the two I feel like multi rom is a bit too complex to set up two roms. my understanding is that everything has to be flashed in a certain way or it wont work.
Click to expand...
Click to collapse
It's really not that hard.. you will get used to it after your first time using it. And its so much worth it instead of doing the backup-restore method :good:

Misanful said:
It's really not that hard.. you will get used to it after your first time using it. And its so much worth it instead of doing the backup-restore method :good:
Click to expand...
Click to collapse
I might give it a try if I decrypt my device. Also just the thought of being able to switch to OOS for the camera in a snap is not suvh a bad idea..

i'm running sultan's CM and still have encryption on - OTA updates via CM still work fine, it just requests I enter the same password/PIN I do every time the device boots (As well as whenever I go into recovery).
it's annoying during flashing and updating but I'm glad to see it work since if someone stole my device they woudln't get any of my data nor would they be able to flash anything malicious onto my device without my knowing, and i don't notice any lag in day to day use.

Pixel XL ROM/Recovery/Root Questions

I'm thinking about picking up a Pixel XL soon (currently still using a Nexus 6) and I kind of just assumed that development on the Pixels was moving fine, until I started looking into it tonight, only to find that there is still only RC versions of TWRP that sound super buggy, and Lineage doesn't even have official builds for either device because of some issue with Google Apps and the partition system on the phone.
So, this leads me to a few questions:
1) Is the TWRP RC2 build for the Pixel XL fairly stable, functional and safe to use? I only ever really do the very occasional backup/restore within TWRP and flash stuff, so as long as the basic functionality is working I'd be happy.
2) This whole two partition thing sounds like a bit of a nightmare to me and sounds like a way riskier setup. Is it easier to brick this phone than other phones that use a normal partition layout, and is it possible to recover from something like that fairly easily?
3) For anyone that uses Invisiblek's unofficial Lineage builds, do they work fine? I know it has some crashing issue when trying to record multiple 30 FPS videos in succession, but that doesn't matter to me at all really. Is it possible to simply flash the official Lineage root file on this unofficial build to have the built in root, or would I be required to use SuperSU?
4) I see people talking about vendor images, and something about the phone getting hot or having super high CPU and memory usage until they reflashed this image. What is this about?
Thanks in advance to anyone who is able to answer any of my questions!

admiralspeedy said:
I'm thinking about picking up a Pixel XL soon (currently still using a Nexus 6) and I kind of just assumed that development on the Pixels was moving fine, until I started looking into it tonight, only to find that there is still only RC versions of TWRP that sound super buggy, and Lineage doesn't even have official builds for either device because of some issue with Google Apps and the partition system on the phone.
So, this leads me to a few questions:
1) Is the TWRP RC2 build for the Pixel XL fairly stable, functional and safe to use? I only ever really do the very occasional backup/restore within TWRP and flash stuff, so as long as the basic functionality is working I'd be happy.
2) This whole two partition thing sounds like a bit of a nightmare to me and sounds like a way riskier setup. Is it easier to brick this phone than other phones that use a normal partition layout, and is it possible to recover from something like that fairly easily?
3) For anyone that uses Invisiblek's unofficial Lineage builds, do they work fine? I know it has some crashing issue when trying to record multiple 30 FPS videos in succession, but that doesn't matter to me at all really. Is it possible to simply flash the official Lineage root file on this unofficial build to have the built in root, or would I be required to use SuperSU?
4) I see people talking about vendor images, and something about the phone getting hot or having super high CPU and memory usage until they reflashed this image. What is this about?
Thanks in advance to anyone who is able to answer any of my questions!
Click to expand...
Click to collapse
Hello,
I think I can answer some of your questions...
1 - TWRP is stable enough for the usual tasks. Some people seem to have issues with restoring partitions on RC2 and end up with some partitions word. Some others say they have no problems. Who's right, who's wrong, is it a particular scenario that makes this problem occurs, I don't know. I just use RC1 without issue...
Also, you are not obliged to install TWRP. You can "fastboot boot twrp.img" RC1 version, do your things and reboot. If you want to stay on stock firmware, it's a nice feature, since you won't have to reflash stock boot.img to take an OTA (Recovery is now part of the boot.img unlike older version which had a proper recovery partition).
2 - I feel you here. I felt scared as well the first time I had to deal with the beast. The only advise I can give you is: read, read and... read again. It's not so hard once you understand how it works. Also, you can still ask for some help if you are unsure, people here are really helpful!
Some users have bricked their devices and those got fixed. But as far as i remember, none that got hard bricked (I only read the Pixel XL forum since two months, so of course I may have missed some ).
3 - I'm a Pure Nexus user. Works very well, if you are looking for a stable alternative. :angel:
4 - I have never had this problem, sorry... But just take a look at this if you want to know the vendor.img is: https://plus.google.com/+JeanBaptisteQueru/posts/akHWypRNEn3
Every months with new security patch, a new vendor.img is included in the factory image or OTA.
If you install lineage OS from maybe April 2017 you'll likely have to flash N2G47E vendor.img which you can find here: https://developers.google.com/android/images inside the factory image archive.
If you install lineage OS April updates, you are fine with this vendor.img.
But in May, you'll have to flash a new vendor.img. Usually you will be notified by the ROM developer, which vendor.img is needed. Considering Google sometimes release two or three builds every months.
Hope that helps a little bit... :good:
Good luck...

(SCRIPT) Disable force encryption.

Hi all,
I'm currently not encrypted and prefer to keep it that way, I don't like entering passwords everytime I go to TWRP and I prefer the old school android system where encryption was a choice, not a mandatory decision made for you.
So when I install a ROM I run a few commands prior to installation to avoid forced encryption, unless it has an option within aroma to disable force encryption which most don't
Thanks to @j to the 4n for help with this, legend
Anyway if you'd like to install a ROM like lineage or aosp or resurrection remix etc and remain not encrypted? Keep reading.
*Note: if you're encrypted prior to doing this then stop, this is for people who've chosen to disable force encryption already but would like to retain it after installing aosp / lineage ROMs.
However if you'd like to remove encryption you'll need to format data via TWRP, not a wipe! Format.
Make sure you back up prior to doing this as it will format data, best to have the ROM on your SD card too so you don't end up with no OS.
If you've done the above or you already have a ROM installed without encryption, then you should be good to go.
------------------------------------------------------------------------------------------------
Just before youre about to install a ROM, let's say resurrection remix ( tested )
Make sure your phone is in TWRP and you're connected to your PC then just before you're about to click install, open up a command prompt on your PC then from ADB shell send the following commands to the device from your PC..
For Magisk:
echo "KEEPFORCEENCRYPT=false" >> /cache/.magisk
If the rom uses SuperSU, send the following commands.
echo "KEEPFORCEENCRYPT=false" >> /data/.supersu
echo "KEEPFORCEENCRYPT=false" >> /cache/.supersu
Then install your rom as normal.
Obviously for ROMs like viper your don't need to do this as there is an option within aroma, but for the likes of RR or lineage this will mean your phone will not encrypt on boot.
Should work for all ROMs but I've not tested this on all of them so if it goes wrong then it's not on me, this worked perfectly for me on RR coming from viper whilst not encrypted.
*Note: if you're not sure what root method your ROM uses then simply send all three commands and you should be good to go.
By using these you're not going to find yourself in TWRP being asked for a password you don't have as your device has been encrypted, I've lost data myself this way and it's extremely annoying.
:good:
If I can ask if anyone tries this and it works, would you mind replying with what it worked on so I can update the OP.
Cheers.
PS: if you're not sure what this is or have any questions, please ask away

Anyway to do this from the device for when your not near a PC?

JohnFawkes said:
Anyway to do this from the device for when your not near a PC?
Click to expand...
Click to collapse
Yes i believe it is, would need to write up a script which is ran prior to installing the rom, i've not got around to doing it yet.
Strictly speaking this should be an option with all roms, it's not exactly a lot of work is it?

Deleted

Works pretty well on Stock ROM.
Just RUU'd, and before rebooting went into download mode, flashed Recovery, flashed SuperSU, used this Command. and boom.
Multirom works.

I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/

Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app

dladz said:
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah it pisses me off. But at least with this handy zip you can flash it anyway and have some mental relief that you stay decrypted.

Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...

Haldi4803 said:
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...
Click to expand...
Click to collapse
Sorry I hadn't tested with all ROMs, not even sure Pure Fusion was even available when I had my HTC 10.
Stick to the script, it's quick, easy and works, you can try a zip but unless someone has gone before you you're potentially walking into a bad time.

Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.

Haldi4803 said:
Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.
Click to expand...
Click to collapse
That's absolutely fine. Because this thread isn't about the zip..I have nothing to do with that, so in regards to the zip you flash it at your own risk.

Deleted

Though i do agree with him that having a .zip and not needing a Computer every time would be pretty usefull.
Does anyone know how to create TWRP flashable zips that includes only this 2 commands?

Hello I tied this for RR rom but I got this message in the cmd, am i doing something wrong?
edit i found my fault I had to adb shell

I know it's been about a year, since somebody posted, but: if anbyone else like me stumbles across this thread, have a look at: https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
It gives you even more information how to enable or disable encryption or dm-verity while usinf magisk.
Btw. you can use the terminal in twrp also, see link.

Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?

Subh4sh said:
Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?
Click to expand...
Click to collapse
Ofcourse,cause echo command is available everywhere.just make sure you install the magisk/supersu first before running the command

hi,
If I format /data, then the encryption is gone and LOS can be installed where backup with TWRP work?
I have U11, but i think it is the same...

Nvidia Experience 5.2 ROM

I have not been able to update my shield tv 2015 16gb device to 5.2.
The device is rooted with latest 3.1.1 TWRP recovery. Each time I select upgrade with the stock settings it will reboot into recovery and won't update.
Does anyone have a link to the latest ROM or know where Nvidia stores the OTA file? I would rather flash the image my self if I can find get the ROM.
I'm sure this we'll help a few other people I can't be the only one with this issue. Need the 5.2 image not the 5.0.2 which is the previous version of Shield experience update.

you should not flash TWRP to your device reflash original recovery and remove su then try update again

BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)

Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
.)
Click to expand...
Click to collapse
i didnt know that :good:
but if he has TWRP installed couldnt he format data pation from TWRP thus saving hours of thumb twiddling

Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Click to expand...
Click to collapse
Obviously thats a much longer and worse route.
afgok said:
you should not flash TWRP to your device reflash original recovery and remove su then try update again
Click to expand...
Click to collapse
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?

On another thread looks like others are having this same issue with only this version 5.2.. ill just wait for the Dev Images to show up hopefully soon.

I unrooted but still got the same issue, it wont install. But I also have another issue, i can't restore my 2015 shield 16gb by using official recovery rom and official tutorials. It consistently fails to flash system.img and vendor.img by saying that the data is too large. The only way I got my system back was by flashing this file https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062 through twrp

Diehardshorty said:
Obviously thats a much longer and worse route.
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.

Ichijoe said:
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Click to expand...
Click to collapse
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0

If you're rooted, the right answer is to wait for Nvidia to release the 5.2 image.
If you absolutely need 5.2 right now for some reason, several people said that doing a factory restore worked. Just unrooting and restoring stock recovery won't do it, you need to do a full restore.

Diehardshorty said:
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
Click to expand...
Click to collapse
The Dev images are quite a bit different, and are also on an entirely different timeline to either the Preview, (Which I'm on), or the most current version.
But, yeah I could see how those would work. Alas mores the pitty that the rooted asspects of those Dev Images, only go as far as ADB, and not say a full /system wide root. Than again... It's probably for the best that way.
But, that doesn't really change the answer if you want / need to update (From root), than you are going to have to bite the big One, and run a Factory Reset. Which again, on the Pro, means a 2h+ reformating (zeroing out), of the /data Partition.

16gb version doesn't take as long to format but I've always remember flashing SuperSU.zip after ROM just incase. Short response for now at work.

Diehardshorty said:
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Use to be here:
/data/data/com.nvidia.ota/app_download
You obviously need root to reach that folder...
If i have time i will upload later this small OTA update to MEGA.

I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886

sammarbella said:
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
Click to expand...
Click to collapse
Sweet thanks I'll give that a try from the sounds of it it might not work but I'll give a shot after work. Thanks

No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS

Diehardshorty said:
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update

Cameron581 said:
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Click to expand...
Click to collapse
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.

Diehardshorty said:
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Click to expand...
Click to collapse
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.

Cameron581 said:
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Click to expand...
Click to collapse
Ahhhhh that missing point for "error 7".
So the new app bypass that problem!
Thanks for posting it. :good:

Question Grateful for root and bootloader unlockables but ..

I am grateful and I bought this because next tk Samsung s22 yktra this phone is definitely #2 in my opinion, which is saying a lot.
However the root process is tedious because I am not around a computer I am just lazy to get ito do flashing etc.
My question is, why do. We not have a a real recovery and ability to back up and restore various roms we or flash zips senselessly.
So my question is (since I just bought this) do you guys rhibj we will have to dastboir flash everything or at least much harder then with cwmod or twrp recovery. Is it not possible to have a recovery like those on t his phone?
Is there a better phone in the us that is unlockaable but has the quality like this phone and screen or the Samsung s22 yktra phone?
Thanks

Without a PC you can't run fastboot commands to unlock bootloader and root it. Twrp isn't available for stock a12, let alone the upcoming release of a13

Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly

jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
I don't think that you will find too many phones from the primary companies (Google, Samsung, etc) nowadays that will have TWRP builds. As time progresses, the technology (and what is available) progresses as well.

jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
This is the most recent news about Android 12 compatibility for TWRP:
TWRP 3.6.2 Released
TWRP 3.6.2 is out now for most currently supported devices.
twrp.me
We are continuing work on Android 12. There is no ETA currently. You can follow our status on Zulip
Click to expand...
Click to collapse
Disclaimer: I am not advocating signing up for "Zulip", and I won't be doing so myself. When/if TWRP for Android 12 becomes available, I'll hear about it whether I sign up on there or not. It's also likely Android 13 will be stable by then.
Supposedly, the Official TWRP App (not itself updated since 2020) will notify when there's a new version - but I don't know if that applies to when there's no current version of TWRP Recovery already installed.

The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.

96carboard said:
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
Click to expand...
Click to collapse
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have

Pixel devices do not have a recovery partition; recovery lives in /boot with the kernel, as well as whatever patches you've applied. Currently, TWRP and Magisk cannot coincide for whatever reason. You can patch a boot image with TWRP, and it'll work AFAIK....but if you try to patch it with Magisk too, you'll get a boot loop.
Because we have full fastboot access, there's not really any need for TWRP. You can dump and backup partition contents using fastboot, but it's tedious.

jgrimberg1979 said:
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have.
Click to expand...
Click to collapse
ADP, Nexus, and Pixel devices have NEVER needed a recovery to function fully. This goes right back to the first Android phone in 2008. So nothing really has changed in this respect. Its mostly the "other" brands that need a recovery to work around various restrictions.
Backups can be taken from within the main OS, and restored similarly, and this is actually much preferred since the backup can be stored to a remote location such as a self-hosted Nextcloud server. You can look into seedvault (integrated solution) and neobackup (root solution).

Since Android 11 you cannot have TWRP and Magisk installed at the same time or it will lead to a bootloop. However, you can fastboot boot TWRP (without installing it) and have Magisk installed without getting into a bootloop. At least this is the way it was on Android 11 with the Pixel 2 XL.
Haven't used TWRP in a long time and don't miss it at all, to be honest.