Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
mkhcb said:
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
Click to expand...
Click to collapse
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
scott.hart.bti said:
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
Click to expand...
Click to collapse
I came from the OnePlus realm and owned the OPO + OP5T. My parents had the OPO and currently have the 7 Pro. I have been beyond spoiled with TWRP.
Needing a computer to flash and update + keep flash is a pain in the butt... Plus the uninstall Magisk, update, then flash method has never worked for me and 2x I lost all my data + pictures.
mkhcb said:
I came from the OnePlus realm and owned the OPO + OP5T. My parents had the OPO and currently have the 7 Pro. I have been beyond spoiled with TWRP.
Click to expand...
Click to collapse
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
scott.hart.bti said:
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
Click to expand...
Click to collapse
Well if you want to lose the inactive dev title, I 100% will support that . I know many people would appreciate it!
i'd certainly spend my money for a twrp!
I hate adb and hate having to connect my pixel (or any other phone) to a pc for install whatever i want
TWRP was a thing when phones had SD card slots. It still would be nice, however, just not as handy as it were then. ;-)
scott.hart.bti said:
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
Click to expand...
Click to collapse
I'm coming straight from S5 and can say even with Source Code available it's really hard to see functional updates.
Aroma Installer support was lost for about 5 years. Then an interested developer finally came up and fixed it but didn't want to maintain it, but still it became official ipdate for device tree not unofficial. However the next two updates after it (as far as I know there haven't been more) by an official maintainer skipped all the fixes he did (Aroma Installer support is just the most important). So TWRP for S5 is back to be bugged like for last 5 years and I don't expect it to get fixed ever again.
So no: even if source is available, you can't expect to have good TWRP support.
I'm quite shocked about the S20 development: It's a flagship phone only 2 years old but Stock based development is down to one ROM and one kernel actively maintained, Vanilla Android (based) ROM is not there only LOS based (okay this is Vanilla based in the end, but itself modified and all the ROMs start from this one) and as this one is still not bug free, all depending ROMs are not bug free.
Back in the active days of S5 you had 3-5 Stock ROMs active, AOSP, AOKP and than Cyanogen (based) ROMs available, quite a lot. And Samsung was always hated for their undocumented changes that gave developers quite the headache and reverse engineering was needed a lot. I think GSI should make development easier compared to S5 or has Custom Android development gone down at all?
scott.hart.bti said:
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
Click to expand...
Click to collapse
Huh? My Samsungs and Oneplus had TWRP, it's not rare just not on Pixel
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
But maybe by now, someone has made it for Android 12 in general and I just haven't heard about it, who knows. I used it some on my Pixel 1, but I really haven't missed it.
Edit: There are several TWRP-related threads in this section, and here's some news I shared a month after I got my Pixel 6 Pro:
[General] TWRP 3.6.0 major parts rewritten from scratch to support Google's Android 11 changes, so they are hopeful for a much quicker Android 12 release
So it took them quite a while to get Android 11 support in general.
cpufrost said:
TWRP was a thing when phones had SD card slots. It still would be nice, however, just not as handy as it were then. ;-)
Click to expand...
Click to collapse
Use a USB C to USB A dongle. Works like a charm and also works in TWRP.
TWRP is still being worked on from what I just checked, but they have no ETA when it'll be finished. There's a status page on Zulip with more info, but I'm not signing up for it.
TWRP 3.6.1 Released
TWRP 3.6.1 is out now for most currently supported devices.
twrp.me
mkhcb said:
Use a USB C to USB A dongle. Works like a charm and also works in TWRP.
Click to expand...
Click to collapse
True, I forgot about those. I even have a 128GB tiny Sandisk USB drive that is USB C native that does work so there's that.
roirraW edor ehT said:
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
But maybe by now, someone has made it for Android 12 in general and I just haven't heard about it, who knows. I used it some on my Pixel 1, but I really haven't missed it.
Edit: There are several TWRP-related threads in this section, and here's some news I shared a month after I got my Pixel 6 Pro:
[General] TWRP 3.6.0 major parts rewritten from scratch to support Google's Android 11 changes, so they are hopeful for a much quicker Android 12 release
So it took them quite a while to get Android 11 support in general.
Click to expand...
Click to collapse
yes
namely the fold 3 - however with samsung devices, encryption needs to be disabled for TWRP to work and be able to access the data partition and thus make and store nand backups of userdata etc.
Firstly it transpred that disabling encryption broke a whole range of samsung and google things such as samsung Dex mode and even downloading attachments from gmail.
Then it transpired that data backups were not being sucecssful (although system partition backups were still possible)
In the end it wasn't worth it and the Dev moved over to pixel 6 pro lol
roirraW edor ehT said:
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
Click to expand...
Click to collapse
It was only officially ported to Android 11 in November 2021, so I doubt there's any official A12 builds yet.
I think reliance on TWRP has dwindled over the past few years due to slow releases, dev's releasing ROM's that are flashable with fastboot, kernels being flashable while online, and most root mods moving towards systemless Magisk modules.
I mainly used TWRP to do an image backup of my phone before doing anything "dangerous". I really hate having to before each monthly update in the hopes something doesn't go wrong that will cause me to have to wipe my phone. With TWRP, I could do an image backup, screw something up, and be back up and running right where I was in a matter of minutes.
Am I missing something here? Is there another way to do a full image backup and restore it quickly? I have Titanium Backup but using that to backup each individual app and it's data, transfer that backup off the phone, then if I have to wipe the phone, I have to copy everything back, then do a restore of each app, will take literally hours!
What's the quickest way to do an image backup if not TWRP?
Thanks,
Dave
Dataman100 said:
Am I missing something here? Is there another way to do a full image backup and restore it quickly?
Click to expand...
Click to collapse
There has "always" (very, very long time) been a way to do image backups manually using ADB, however, it's unreliable - the only reason TWRP or other recoveries were slightly more reliable was that they could "verify" the backup and ensure that what it sees in the partition is indeed what is backed up.
With the ADB commands, you might not find out your backup isn't good until you restore it, and that's no help.
I still found TWRP backups to be hit and miss, at least six years ago when I was still using it.
Dataman100 said:
I have Titanium Backup but using that to backup each individual app and it's data, transfer that backup off the phone, then if I have to wipe the phone, I have to copy everything back, then do a restore of each app, will take literally hours!
Click to expand...
Click to collapse
I switched to Swift Backup and I don't even backup locally as most of my 512 GB of space is filled with music. I have it backup to my Google Drive directly. It's slower to restore stuff from the cloud, but at least they aren't taking up precious space, and I know wiping the phone won't cause me to lose my backups.
FYI, you can set up cloud backups in Titanium Backup as well, or tell it to do that manually. In TB's case, the cloud backups don't replace the local backups, but I have used them before just in case I have to wipe. I've been away from Titanium Backup long enough that I don't recall if TB restores could be done from the cloud, however (unlike Swift Backup, which can restore directly from the cloud). TB's method is probably closer to your manual copy the files back method, so only slightly an improvement as you can schedule the TB cloud backups to happen automatically.
roirraW edor ehT said:
There has "always" (very, very long time) been a way to do image backups manually using ADB, however, it's unreliable - the only reason TWRP or other recoveries were slightly more reliable was that they could "verify" the backup and ensure that what it sees in the partition is indeed what is backed up.
With the ADB commands, you might not find out your backup isn't good until you restore it, and that's no help.
I still found TWRP backups to be hit and miss, at least six years ago when I was still using it.
I switched to Swift Backup and I don't even backup locally as most of my 512 GB of space is filled with music. I have it backup to my Google Drive directly. It's slower to restore stuff from the cloud, but at least they aren't taking up precious space, and I know wiping the phone won't cause me to lose my backups.
FYI, you can set up cloud backups in Titanium Backup as well, or tell it to do that manually. In TB's case, the cloud backups don't replace the local backups, but I have used them before just in case I have to wipe. I've been away from Titanium Backup long enough that I don't recall if TB restores could be done from the cloud, however (unlike Swift Backup, which can restore directly from the cloud). TB's method is probably closer to your manual copy the files back method, so only slightly an improvement as you can schedule the TB cloud backups to happen automatically.
Click to expand...
Click to collapse
Thanks! Yeah, I was aware of all those options. It's still a very manually intensive and time consuming process with either Swift or TB to the cloud.
I came to the P6P from an LG V30s which had TWRP. Right before any major update, (OS, Magisk, etc). I'd do a quick full image backup to the SD card. It took about 20 mins max. Then I'd perform whatever update task, and if it boot looped, or soft bricked, I'd immediately reboot into TWRP and restore. I remember having to do that at least twice on the LG. Each time the backup restored properly and I was up and running again in 20 mins or less. There's no current backup/restore process for the Pixel that even comes close. Titanium even lets you restore individual apps/data from a TWRP backup image. You don't have to restore the entire thing. Which I'd done several times on the LG.
It's a shame. One of the reasons I chose the P6P was because I thought with it's popularity, it wouldn't take long for TWRP to be available. It may not be as valuable or necessary as it was in the past for it's flashing functions, but it certainly would be very useful, (to me anyway) for it's image backup function.
I'd definitely chip in for a TWRP bounty. For the backup alone.
Dataman100 said:
Thanks! Yeah, I was aware of all those options. It's still a very manually intensive and time consuming process with either Swift or TB to the cloud.
Click to expand...
Click to collapse
I have Swift backup to the cloud automatically every night at ~2 AM whenever the battery is at 50% or more. I never have to do anything for that manually. That way, if I'm going to do something dangerous, there's that much less I have to worry about.
I think I used to have Titanium Backup sync to the cloud nightly on a schedule also, besides having it do a scheduled new backup beforehand.
I only actually ever restore select app data - I always start with the Google Cloud restore, and then probably just a few apps that don't use Google Cloud backup, so I manually restore the data for those apps as I come across them in normal use. I never do like I used to do in Titanium Backup and do a restore all.
Dataman100 said:
I came to the P6P from an LG V30s which had TWRP. Right before any major update, (OS, Magisk, etc). I'd do a quick full image backup to the SD card. It took about 20 mins max. Then I'd perform whatever update task, and if it boot looped, or soft bricked, I'd immediately reboot into TWRP and restore. I remember having to do that at least twice on the LG. Each time the backup restored properly and I was up and running again in 20 mins or less. There's no current backup/restore process for the Pixel that even comes close. Titanium even lets you restore individual apps/data from a TWRP backup image. You don't have to restore the entire thing. Which I'd done several times on the LG.
It's a shame. One of the reasons I chose the P6P was because I thought with it's popularity, it wouldn't take long for TWRP to be available. It may not be as valuable or necessary as it was in the past for it's flashing functions, but it certainly would be very useful, (to me anyway) for it's image backup function.
I'd definitely chip in for a TWRP bounty. For the backup alone.
Click to expand...
Click to collapse
Nice. It is definitely good to have options.
mkhcb said:
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
Click to expand...
Click to collapse
Yeah if the p6pro gets official lineage os would even be cool to have lineage recovery
Just a thought.
Related
So I've reset my phone as part of switching between SKUs and am now setting up my device, essentially as if it just came out of the factory. Unfortunately, Android didn't prompt me to restore my phone from a backup and I am looking at the prospect of manually installing all of my apps.
Is there any way to tell Android (Nougat, 4.27.531.6) to do this?
Htc backup stopped working ages ago and since then there has been no way to backup and restore this device.
Without making a backup with an app like "gobackup" then yes, you're looking at manually installing everything all over again. Be careful with which data you restore as you can easily cause a bootloop. I prefer manual setup due to the fact that restoring old data that may not be 100% compatible can bork the phone and make the restore process A LOT longer.
Googleplay won't detect due to the firmware being a different version from the one one record.
Beamed in by telepathy.
shivadow said:
Htc backup stopped working ages ago and since then there has been no way to backup and restore this device.
Without making a backup with an app like "gobackup" then yes, you're looking at manually installing everything all over again. Be careful with which data you restore as you can easily cause a bootloop. I prefer manual setup due to the fact that restoring old data that may not be 100% compatible can bork the phone and make the restore process A LOT longer.
Googleplay won't detect due to the firmware being a different version from the one one record.
Beamed in by telepathy.
Click to expand...
Click to collapse
I was never keen on HTC Backup, as I have moved between several Android devices. But the Android backup service seemed to promise the ability to restore apps between devices - I guess I overestimated its purpose.
computerslayer said:
I was never keen on HTC Backup, as I have moved between several Android devices. But the Android backup service seemed to promise the ability to restore apps between devices - I guess I overestimated its purpose.
Click to expand...
Click to collapse
Always read the small print. You will learn the hard way if you don't!.
For example, you could hire a maid that'll clean your property with the opportunity for "extras". You get caught with your pants round your ankles, your c**k in your hand and she's screaming at you "it means I'll make a cup of tea if you ask"..
Don't ask how I know..
Beamed in by telepathy.
Fair advice.
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
WyldOne91 said:
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
Click to expand...
Click to collapse
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Badger50 said:
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Click to expand...
Click to collapse
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
WyldOne91 said:
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
Click to expand...
Click to collapse
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Badger50 said:
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Click to expand...
Click to collapse
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Badger50 said:
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
Click to expand...
Click to collapse
Yeah for sure. I'm always willing to learn!
CyberpodS2 said:
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Click to expand...
Click to collapse
Yeah I actually already ran a backup with Titanium Backup and moved it to my PC last night just in case I did something stupid haha but I appreciate the tips!
Can I restore a nandroid backup made on a different device to a new device? I am getting a new RMA unit soon and I want to restore a nandroid backup made on my old device to the new one. I don't know if it is possible though.
EDIT: I have tried it and it doesn't work. All the data and apps are restored and the device mostly works but Pixel imprint will refuse to add any fingerprints at all.
Look into how this was done on the Nexus 6P - the finger prints and lockscreen stuff would be screwed up, but could be fixed with modifications to certain files. Having said that, I'm not sure if this would trip SafetyNet with the Pixel 2 XL (I was using system root with SuperSU back on the N6P, so I didn't care about SafetyNet.)
Also, I'm not even sure the same fixes would work, but it's worth exploring if need be.
Don't think it's a good idea and could cause problems...
darkfire404 said:
Can I restore a nandroid backup made on a different device to a new device? I am getting a new RMA unit soon and I want to restore a nandroid backup made on my old device to the new one. I don't know if it is possible though.
EDIT: I have tried it and it doesn't work. All the data and apps are restored and the device mostly works but Pixel imprint will refuse to add any fingerprints at all.
Click to expand...
Click to collapse
You can do restores all day long with HTC 7,8,9,10,11's and Nexus 6 among others. But I have failed so many times on OG Pixel and P2-XL.
Haven't given up, but it doesn't look good.
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.
I tried backup and restore on POCO F3 and I think it was successful on A11 but I dont think restore ever worked since A12. Always had error 255 at the beginning of restoring data partition. Has anyone been successful restoring a backup of android 13?
Aserar said:
I tried backup and restore on POCO F3 and I think it was successful on A11 but I dont think restore ever worked since A12. Always had error 255 at the beginning of restoring data partition. Has anyone been successful restoring a backup of android 13?
Click to expand...
Click to collapse
Of course. Backup and restore work fine on OrangeFox.
Bit unrelated, but I always use Swift Backup for backing up apps+appdata. It can backup other things as well.
Requires Root, but you can always uninstall Magisk Root
DarthJabba9 said:
Of course. Backup and restore work fine on OrangeFox.
Click to expand...
Click to collapse
Both OFX and TW failed me at restore I can't think of any reason why if it's working with others. Do you remove screen lock before backing up? Never had to before but it's the only thing I could think of
cyanGalaxy said:
Bit unrelated, but I always use Swift Backup for backing up apps+appdata. It can backup other things as well.
Requires Root, but you can always uninstall Magisk Root
Click to expand...
Click to collapse
Yeah I do a swift backup also messages call log all of it but setting up the rest of the phone, logging back into accounts, is a pain, plus I always find an app or something that I forgot to refresh its backup. Nothing is like nand backup if you're testing new rom and might just go back
Aserar said:
Both OFX and TW failed me at restore I can't think of any reason why if it's working with others. Do you remove screen lock before backing up? Never had to before but it's the only thing I could think of
Click to expand...
Click to collapse
Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.
And you might want to read this wiki very carefully.
DarthJabba9 said:
Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.
And you might want to read this wiki very carefully.
Click to expand...
Click to collapse
Oh I've gone through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though
Aserar said:
Oh I've went through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though
Click to expand...
Click to collapse
1. Idk about EU. But I have backed up and restored stock MIUI 14 many times, with no problem.
2. "Error 255" is always accompanied by an explanatory message in the recovery logs, which will show what caused the error.
3. Firstly, ensure that your OrangeFox is actually up-to-date (ie, that you are using the latest release).
4. Whether or not you have a screenlock before making the backup should not affect anything (as long as there is no screenlock set up at the time of restoring the backup). The lockscreen PIN/password is not included in the backups.
DarthJabba9 said:
1. Idk about EU. But I have backed up and restored stock MIUI 14 many times, with no problem.
2. "Error 255" is always accompanied by an explanatory message in the recovery logs, which will show what caused the error.
3. Firstly, ensure that your OrangeFox is actually up-to-date (ie, that you are using the latest release).
4. Whether or not you have a screenlock before making the backup should not affect anything (as long as there is no screenlock set up at the time of restoring the backup). The lockscreen PIN/password is not included in the backups.
Click to expand...
Click to collapse
Yeah screen lock was never an issue before but it is the only thing I could think of. It could be something with EU. And yes I keep recovery up to date even when I don't switch roms. I made a backup of AOSP rom that I will probably restore soon. I'll keep you updated if the issue persists.
Aserar said:
Yeah screen lock was never an issue before but it is the only thing I could think of. It could be something with EU. And yes I keep recovery up to date even when I don't switch roms. I made a backup of AOSP rom that I will probably restore soon. I'll keep you updated if the issue persists.
Click to expand...
Click to collapse
Well, I have now made backups and restores of the latest EU ROM (14.0.6.0) - boot and data partitions - without any problem (both with and without screen locks - obviously there must be no lockscreen PIN/password when restoring).
DarthJabba9 said:
Well, I have now made backups and restores of the latest EU ROM (14.0.6.0) - boot and data partitions - without any problem (both with and without screen locks - obviously there must be no lockscreen PIN/password when restoring).
Click to expand...
Click to collapse
And I restored my AOSP backup with no errors! I wish I hadn't deleted my EU backup that I got the error with. The EU rom I had was the latest weekly release V14.0.23 bc the official release had issues but I doubt its that. I'm at a loss :/
Aserar said:
And I restored my AOSP backup with no errors! I wish I hadn't deleted my EU backup that I got the error with. The EU rom I had was the latest weekly release V14.0.23 bc the official release had issues but I doubt its that. I'm at a loss :/
Click to expand...
Click to collapse
Do you have a link for that release?
Sorry for also deviating, just my two pennies worth,
I moved away from Migrate-GPE and Swift backup and have been using DataBackup.apk, this also requires root.
As usual DB saves your Apps and there Data, you also have the option to save Media Folders, DCIM, Download, Music, Pictures, Folders, i also save these to my Usb Stick using a OTG adaptor, DataBackup can be found is my "Temporary Recovery" folder.
DarthJabba9 said:
Do you have a link for that release?
Click to expand...
Click to collapse
Honestly I can't be sure of the exact release since its weekly. I looked it up and I can narrow it down to like 3 or 4 releases but it could be this one
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.23.4.10.DEV/xiaomi.eu_multi_HMK40_POCOF3_V14.0.23.4.10.DEV_v14-13.zip/download
johnr64 said:
Sorry for also deviating, just my two pennies worth,
I moved away from Migrate-GPE and Swift backup and have been using DataBackup.apk, this also requires root.
Click to expand...
Click to collapse
Is this on the Play Store?
johnr64 said:
As usual DB saves your Apps and there Data, you also have the option to save Media Folders, DCIM, Download, Music, Pictures, Folders, i also save these to my Usb Stick using a OTG adaptor, DataBackup can be found is my "Temporary Recovery" folder.
Click to expand...
Click to collapse
Having an alternative backup plan is good. But I have always found nandroid backups sufficient - as long as you know what you're doing.
Aserar said:
Honestly I can't be sure of the exact release since its weekly. I looked it up and I can narrow it down to like 3 or 4 releases but it could be this one
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.23.4.10.DEV/xiaomi.eu_multi_HMK40_POCOF3_V14.0.23.4.10.DEV_v14-13.zip/download
Click to expand...
Click to collapse
I have backed up and restored this release as well, with no problem. I have satisfied myself (again) that there is no problem with backup/restore in OrangeFox Recovery, so, for me, this investigation is concluded.
DarthJabba9 said:
I have backed up and restored this release as well, with no problem. I have satisfied myself (again) that there is no problem with backup/restore in OrangeFox Recovery, so, for me, this investigation is concluded.
Click to expand...
Click to collapse
Lol there was no need for investigating my friend! The point of the thread was to see if its generally working with others and so eliminate it as the reason for the fail.
DarthJabba9 said:
Is this on the Play Store?
Having an alternative backup plan is good. But I have always found nandroid backups sufficient - as long as you know what you're doing.
Click to expand...
Click to collapse
Sorry for not getting back sooner,
I found DataBackup while watching youtube videos "Like You Do",
the source is on GitHub
Aserar said:
Lol there was no need for investigating my friend! The point of the thread was to see if its generally working with others and so eliminate it as the reason for the fail.
Click to expand...
Click to collapse
It's no big deal. I always try to investigate problems, since they might possibly point to a problem in the recovery.
Same here. Since a12 that nandroid gives error on restoring. After that I don't count with that anymore. Ive been relying on Google to restore some apps, and on swift backup to restore the ones that are out of ps.
Before I was using migrate, but have put it aside, since the last time I've got error on zip file and so unable to restore my apps (a real pita). Swift have working flawlessly, and with the advantage of restore app settings too.