Full Nandroid Backup Solution for LineageOS 17??

[dadu1257]

I got Lineage 17 w/ Magisk root running now neat and great and I want to perform a full NANDroid Backup.

After some research it seems crucial to have a custom recovery like TWRP for that. There is the online nandroid thing - but I would need CWM or anything like this to restore?!

So my question is
a) is there another custom recovery (compatible with Pixel 3a XL w/ lineage 17 based on android 10) I can install and perform Nandroid backup with?
b) any other solution to perform this backup and restore? I heard there are cmd commands for that as well , but I'm a noobie not so sure to do that.
of course there are several apps out there to backup data.. but I don't trust ''any'' app to get root permission. In F Droid I couldn't find what I was looking for. Suggestion?

thank you for help!

 

[LoganDark]

1. It is unsafe to perform backups while booted into Android, as files may be changed/added/removed while the backup is taking place.
   
   This is why it tends to be a feature of custom recoveries.
2. Titanium Backup is good. It doesn't support split APKs like YouTube but the data restore works flawlessly. This is an old utility app so you can trust it with root. You can find Titanium Backup on the play store, it is the one with the star and "root required".

If you want to perform full backups of your PHONE you will want TWRP. If you want to perform full backups of your APPS then you will want to use an app like Titanium Backup (however Titanium Backup is not updated for split APKs, like I said above), which will allow you to transfer your backups to a new phone and fully restore all apps & data (as long as both phones have root).

 

[dadu1257]

Sure problem is I want to perform a full backup of my phone, but TWRP ist not available. What are my options?

 

[LoganDark]

Sure problem is I want to perform a full backup of my phone, but TWRP ist not available. What are my options?

Does TWRP for Pixel 3a XL not work for you? All you have to do is download the "twrp-installer-3.4.0-0-bonito.zip", install it as a Magisk module, then direct install Magisk again, then reboot into recovery and you'll have TWRP.

When accepting OTAs, you will want to use the "TWRP A/B retention script" before you install Magisk to the inactive slot. The script is available as part of the Magisk modules repository, so you should be able to install it directly from within Magisk Manager.

 

[dadu1257]

TWRP doesnt work for me, see here what user 41rw4lk wrote, too..
Is there a tutorial on how to install twrp as a masgisk module?

Also, how else can I perform a backup img for my phone?
thank you

 

[LoganDark]

TWRP doesnt work for me, see here what user 41rw4lk wrote, too..
Is there a tutorial on how to install twrp as a masgisk module?

Also, how else can I perform a backup img for my phone?
thank you

https://puu.sh/GWiul/2611f0cdf4.mp4 - video showing how to install TWRP

Edit: https://puu.sh/GWiAe/6f620419c8.mp4 is more compatible and smaller. same video

 

[adm1jtg]

.....

 

[adm1jtg]

https://puu.sh/GWiul/2611f0cdf4.mp4 - video showing how to install TWRP

Edit: https://puu.sh/GWiAe/6f620419c8.mp4 is more compatible and smaller. same video

Benn trying to get this to work for a little bit now and no luck at all....

Let me start by saying i an NOT running LOS so that might be the whole issue...

I have tried with pure stock and stock with ex kernel
Same results for each
1) TWRP loads as the recovery and can be booted into, BUT the rom is now soft bricked and wont boot at all
2) Even when in twrp I cannot flash anything, cannot see sdcard and cannot backup data partition (the data partition shows as 0 space)

Perhaps the LOS kernel or rom adds something thats missing in my two setups?

The sample video is for another phone. My recolection is that twrp and pixels on android 10 or 11 wont work. Lineageos 17.1 is android 10 based. I think it worked on that other phone as it was not a pixel.

Can anyone confirm or deny if this works in any configuration of android 10 or 11 on our phones?

 

[LoganDark]

Benn trying to get this to work for a little bit now and no luck at all....

Let me start by saying i an NOT running LOS so that might be the whole issue...

I have tried with pure stock and stock with ex kernel
Same results for each
1) TWRP loads as the recovery and can be booted into, BUT the rom is now soft bricked and wont boot at all
2) Even when in twrp I cannot flash anything, cannot see sdcard and cannot backup data partition (the data partition shows as 0 space)

Perhaps the LOS kernel or rom adds something thats missing in my two setups?

The sample video is for another phone. My recolection is that twrp and pixels on android 10 or 11 wont work. Lineageos 17.1 is android 10 based. I think it worked on that other phone as it was not a pixel.

Can anyone confirm or deny if this works in any configuration of android 10 or 11 on our phones?

Huh, that's weird... I apologize, I'm not very good at supporting devices I don't own. I'm not running Lineage either, I'm running stock plus mods.

It's possible that it doesn't work on your phone for whatever reason. There are a couple ways to install TWRP nowadays, check them out maybe? I promise TWRP is what you want for backups.

 

[adm1jtg]

Huh, that's weird... I apologize, I'm not very good at supporting devices I don't own. I'm not running Lineage either, I'm running stock plus mods.

It's possible that it doesn't work on your phone for whatever reason. There are a couple ways to install TWRP nowadays, check them out maybe? I promise TWRP is what you want for backups.

Agreed but twrp simply doesnt work on our phones, or even any pixel 3 or above. It can't read the partitions correctly. Just trying to keep people from soft bricking their phone. Something about andriod 10 and 11 and the phones a/b partition configuration

 

[LoganDark]

Agreed but twrp simply doesnt work on our phones, or even any pixel 3 or above. It can't read the partitions correctly.

Where did you hear this? I'll admit, I haven't heard about TWRP not working on Pixels, but it's relevant and it would be good to know if I ever help another Pixel user in the future.

Something about andriod 10 and 11 and the phones a/b partition configuration

That's interesting, because my OnePlus 7 Pro runs Android 10 with an A/B configuration and TWRP works just fine. Haven't found a single feature that didn't work. Flashing custom ROMs, changing boot slots, etc. all work fine. So it can't be the A/B configuration.

 

[adm1jtg]

Where did you hear this? I'll admit, I haven't heard about TWRP not working on Pixels, but it's relevant and it would be good to know if I ever help another Pixel user in the future.


That's interesting, because my OnePlus 7 Pro runs Android 10 with an A/B configuration and TWRP works just fine. Haven't found a single feature that didn't work. Flashing custom ROMs, changing boot slots, etc. all work fine. So it can't be the A/B configuration.

You can read through this:

TWRP 3.3.1-1 for Pixel 3A XL [OFFICIAL]

Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...

forum.xda-developers.com

And this:

tips for preserving twrp from Pie to Q

hi i'm not an expert so sorry maybe for foolish question but coudn't find a clear answer yet.. i'm still on pie and twrp 3.3.1.1; i'd like to upgade to ten but preserving twrp (maybe upgrading to 3.4.0 if necessary) which are the steps to keep...

forum.xda-developers.com

No method I have tried results in anything but an unusable twrp or a boot loop. Cant even fastboot boot current version. All about dynamic partitions and lzma compression as I guess the partition isnt big enough. But bottom line is I have yet to find anyone including myself who can get twrp to in any way shape or form be usable on our phones for android 10 or newer.

this is what command prompt gives with fastboot boot
Sending 'boot.img' (65536 KB) OKAY [ 1.509s]


Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')

This is likely due to the kernels I use likely not having lzma. Checking into it.



fastboot: error: Command failed