So since there in no TWRP for the pixel 4 currently is there anyway too make a nandroid backup?
If I remember correctly this is where the entire partition(s) is/are backed up like as in a snapshot was taken of the way every little minute detail about it was arranged. Since TWRP does this backing up for us and it's not available how can we back up our phones in this type of detail? Titanium does a decent job but it's not an actual exact duplicate of the way things were at a certain point in time on the partition like a nandroid is. Basically, if someone flashes a ROM (one not requiring TWRP to flash, namely pixeldust, I believe it has a patched boot partition allowing unsigned files to be flashed w/ stock recovery) and something hangs it up for whatever reason there needs to be a nandroid backup to revert to if the flash goes to hell in a hand basket, right?
Is there a way to make an old skool nandroid like TWRP makes?
One could ADB pull partition copies to make backups of partitions but how this would turn out with the android 10 "dynamic partitions" is still beyond my understanding.
Related
Hello,
My device is a NEXUS 7 3G (GSM / HSPA +) and am using Twrp recovery and have a question about backup menu.
Are the default options checked enough (Boot, System and Data)? Do I click check the radio option? When it is necessary the radio option?
I Know cache and recovery are not necessary but the question is the radio.
Thanks and sorry for my writing in English, very poor ... sorry
It would be rather unusual for a radio to be flashed by anything other than a factory ROM; so the need to be restoring it is somewhat unusual.
As with the bootloader, it is probably best to minimize the amount of flashing you do of the radio partition.
TWRP also lets you choose which partitions are restored using the same toggles, so even if it were present in a backup, I don't think TWRP forces you to restore it.
I have a grouper (not tilapia) N7, and (besides more typical ROM backups) I keep a pure-stock, completely unconfigured ROM TWRP backup including the stock recovery standing by (plus a copy stored safely off the device).
I think having pure stock backups is something everybody should do. Not only for factory return scenarios, but also for applying OTAs (make custom ROM backup, revert to pure stock, apply OTA, capture yet another pure-stock backup, restore back to custom ROM). This gets you:
- return to stock any time
- for RMA / relock scenarios
- no problem OTA installs
- reference stock ROMs from every release (for restoring individual stock files)
good luck.
bftb0 said:
It would be rather unusual for a radio to be flashed by anything other than a factory ROM; so the need to be restoring it is somewhat unusual.
As with the bootloader, it is probably best to minimize the amount of flashing you do of the radio partition.
TWRP also lets you choose which partitions are restored using the same toggles, so even if it were present in a backup, I don't think TWRP forces you to restore it.
I have a grouper (not tilapia) N7, and (besides more typical ROM backups) I keep a pure-stock, completely unconfigured ROM TWRP backup including the stock recovery standing by (plus a copy stored safely off the device).
I think having pure stock backups is something everybody should do. Not only for factory return scenarios, but also for applying OTAs (make custom ROM backup, revert to pure stock, apply OTA, capture yet another pure-stock backup, restore back to custom ROM). This gets you:
- return to stock any time
- for RMA / relock scenarios
- no problem OTA installs
- reference stock ROMs from every release (for restoring individual stock files)
good luck.
Click to expand...
Click to collapse
Thank you very much for the reply. Now I have the bootloader open and I'm leaving the tablet as I like and I intend to make a backup before root.
Thanks
Hey guys,
So my N7 had gone into this auto-shutdown phase before. But in the past I always managed to fix it. This time however it's different. I get stuck in bootloop.
I've left it on charge for about 1hour+, still bootloop. Reflashed ROM, still bootloop. I'm hoping I don't need to full wipe or restore the factory image to solve it, so I'm hoping there is another solution.
Thanks.
Poor Man's TiBu after bootloop occurs
TU;DBR (Toolkit Users Don't Bother Reading)
Bootloops are generally caused by stuff that lives in the /data partition, not in the /system partition.
So, if you did a dirty flash of the ROM that won't change anything.
If your /data filesystem is healthy (can be mounted by the recovery), make a nandroid backup using TWRP and pull it off the tablet.
The TWRP <partition>.ext.win backup files are just .tar images, so there is always the possibility of recovering your market apps & data with a little bit or learning and effort on your part. But no kidding, it's not for the faint of heart. The basic outline of the idea is to:
- nandroid & get copy off tablet for safety sake
- manually delete everything in /data excepting /data/media, /data/app, and /data/data
- go in to /data/data and manually delete all folders not associated with your market apps ( stuff like com.android.* or com.google.*)
- go into /data/app and delete any .apks which are updates to system apps (gmail, etc) [*1]
- nandroid backup again - call this "nandroid2"
- boot OS and configure minimally.
- boot back into TWRP
- (manually using tar? [**2]) restore the TWRP data backup (data.ext.win) without wiping
- perform "fix permissions" in TWRP
- boot up and profit
Note that "manually" here means using the command line (via adb shell to custom recovery).
If something goes wrong with this procedure, you can always restore the first nandroid backup (the bootlooping condition) and iterate until you get things right. (That right there shows you what freedoms you get by making backups.)
If you read this far you can see that what this process does is very similar to what TiBu does - except you are doing it *after* a boot loop has occurred.
[*1] optional - might not be needed
[**2] it might be possible to just "dirty flash" the data partition from the "nandroid2" backup rather than futzing around with tar at the command line. The reason I wrote this step as shown above is because I wasn't sure if a nandroid restore to /data automatically does a factory reset of /data or whether it will allow "dirty overwrites". Note also that TWRP allows you to selectively backup/restore partitions, so you don't need to involve /system or the boot partition in any of this.
good luck
Ladies and gentlemen,
Recently, whilst flashing a new ROM, I had an issue. I tried to restore a backup that I created with TWRP 2.6.0 with the same version. I got to the "Restore data" stage in the logs, and it failed.
I have two data.ext4 files in my TWRP backup folder: the first is data.ext4.win000 and data.ext4.win001. I'm thinking this is the issue.
I have already flashed a ROM and booted, so I am out of the woods. Just wanted to know if anyone has had any success with split data files in a TWRP recovery.
Thanks for your time.
richardpunch said:
Ladies and gentlemen,
Recently, whilst flashing a new ROM, I had an issue. I tried to restore a backup that I created with TWRP 2.6.0 with the same version. I got to the "Restore data" stage in the logs, and it failed.
I have two data.ext4 files in my TWRP backup folder: the first is data.ext4.win000 and data.ext4.win001. I'm thinking this is the issue.
I have already flashed a ROM and booted, so I am out of the woods. Just wanted to know if anyone has had any success with split data files in a TWRP recovery.
Thanks for your time.
Click to expand...
Click to collapse
Look for TWRP-Recovery-jfltespr-2.5.0.2 seems to be the most reliable for backup and restores right now.
The 'splitting of the EXT/data is NOT the problem. That's the way twrp is compressing the images.
Also there are some ROMs that have partition problems with certain kernels, so take note of that.
I make a crap load of nandroids and switch back and forth pretty often. 2.5.0.2 has been the most reliable for me.
Once more thing I do is verify the nadroid via the AFV app. I boot to recovery, create backup (always of every partition) then boot to ROM and run the AFV app on the backup and make sure it verifies. Then I'll boot back to recovery and wipe/format and flash away according to the dev's instructions.
Leader,
Thanks for such an informative write up. I will check into rolling back to a different twrp build. It's an unpleasant solution, but if it works I'll have to bite the bullet.
Thanks again!
-Mobile post
I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.
Splice_9 said:
I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.
Click to expand...
Click to collapse
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.
I backed up all 53 partitions and stored in my harddisk. It's less than 5GB.
I left out only the data partition because for that I use Titanium Backup and RSync.
Yet I haven't backed up the partition table, also this is important...
NZedPred said:
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.
Click to expand...
Click to collapse
if i backup my efs and persist in a custom rom 64 bits that backup won't work in stock right? it is intact
Backup everything... although it may be too late already, but any working backup is better than nothing.
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.
nicolap8 said:
Yet I haven't backed up the partition table, also this is important...
Click to expand...
Click to collapse
acejavelin said:
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.
Click to expand...
Click to collapse
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?
prokaryotic cell said:
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?
Click to expand...
Click to collapse
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).
acejavelin said:
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).
Click to expand...
Click to collapse
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?
prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?
Click to expand...
Click to collapse
Yes, you can restore your efi folder to correct this most of the time, if you have a clean backup. Otherwise you need to get it JTAG programmed
prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device.
Click to expand...
Click to collapse
Just to clarify that you understand, you can't return your bootloader status to untampered but you can lock it again. However it really isn't necessary to do that just to get OTAs. All you need to do is return to your stock with stock recovery and no-root (fastboot method not TWRP flashable.) OTAs work fine once you have done so. I have restored a TWRP backup just by booting into TWRP but it seems like I had some issue unrelated to OTA, although I don't recall what they were and is was on my previous phone (Moto G4).
For the life of me I cant restore a backup of my current rom. What am I missing?
Ive tried backup on both slots and attempted to restore Individually.
enigma2446 said:
For the life of me I cant restore a backup of my current rom. What am I missing?
Ive tried backup on both slots and attempted to restore Individually.
Click to expand...
Click to collapse
Backing up with encryption is messy...
If you disable all security with the OS booted... And are on F2FS... You probably stand the best chance...
Otherwise... Might I recommend Migrate or Titanium Backup and forget about the backup feature in TWRP altogether...
Or use adb backup with your PC... But I don't know if that is restorable either
I'm not sure what goes wrong for people with TWRP backup's? I often see people talking here and on telegram about this. I didn't get my ph-1 till late September of last year so I missed the unofficial TWRP builds and I'm sure there were lots of improvement's made along the way. This being said, backup's work flawlessly for me and I use them almost daily since December when I started flashing lots of different ROMs. The only time I've run into a problem restoring a backup is from custom to stock or vice versa.
When I run into a backup not restoring I flash that ROM plus TWRP zip and then try again I don't even boot into the system just reboot and try again and it works for me. I hope this helps you.
I am encrypted on all my setups these days and always flash the exact same way from TWRP : select install , choose rom zip, select add more zips, select TWRP zip, flash/ select home button, select reboot, select recovery. Again from TWRP: select install, choose gapps (if needed), choose add more zips, select Magisk, flash and reboot into the system.
I stated the obvious above because I assume there must be either a subtle nuance btwn the way that people flash or something btwn the phone and twrp changed at some point before December (when I began using regularly)
@rignfool isn't alone in his belief that TWRP backup's don't work well. He is also one of many people that know more about Android development and the ph-1 then myself. However I disagree with anyone who would say TWRP backup's don't work well because I depend on them and they do work, precisely as they are supposed to.