I was wondering can a twrp non encrypted backup be restored on another note 4/ or different model phone or does the restore file only work on device it was created on. Weird question but was just curious .
Not recommended
Related
I'm using TWRP 3.1.0-1, running Resurrection Remix-N v5.8.0-OnePlus 3T. I want to go back to OOS, I have a TWRP backup of OOS before I flashed RR and I want to restore from that.
So in TWRP -
- Took another backup of RR
- Wiped Dalvik, System, Data and Cache
- Restored OOS
OOS starts and prompts to use my swipe pattern, I swipe my pattern and it's "incorrect", (I didn't forget my pattern, same one I have used for a long time). Ok so back to RR, so I did the same wipes and restored latest RR, now it bootloops. I restored OOS again and wiped. I'm back to OOS, but of course it's "new".
Is there a way to restore OOS successfully or any of RR from my TWRP backups?
Don't know if it makes a difference, but had some issues originally flashing RR, had a bunch of problems, DM-verity and softbricked, I restored to stock using this:
https://forum.xda-developers.com/oneplus-3t/how-to/guide-return-youre-op3t-to-stock-lock-t3569383
After restoring to stock, I successfully removed the default encryption following another guide. I guess I don't know if RR by default encrypts or not, if that matters.
Have you changed your twrp after doing the initial backup
Because twrp before 3.0.4.1 does backups differently and will not restore if restore them by using twrp 3.0.4.1 or newer
kunal1540 said:
Have you changed your twrp after doing the initial backup
Because twrp before 3.0.4.1 does backups differently and will not restore if restore them by using twrp 3.0.4.1 or newer
Click to expand...
Click to collapse
To the best of my knowledge I am using the same version both to backup and restore. I definitely used the same version to backup/restore the latest RR (which bootloops).
RocKKer said:
To the best of my knowledge I am using the same version both to backup and restore. I definitely used the same version to backup/restore the latest RR (which bootloops).
Click to expand...
Click to collapse
Normally, I'd say the backup is just damaged or has some error, preventing proper restore of it. But it's strange that you have two RR backups which won't restore.
If the intent is to get RR working, with your previous user data; maybe try to flash RR, then just use TWRP to restore the data partition?
If you plug your phone in your computer and you computer recognizes your phone, then you can use ADB to wipe everything again. I had the same problem but my phone only charge if I plugged it into my PC so I wasn't able to revive it...
I've got the same problem here. Running TWRP 3.1.0-1, and sultan CM13 20170402. Backed up everything. Tried:
1. restore everything
2. restore only system
3. restore only system and data
None worked. Bootloop immediately after OnePlus splash screen. I also tried the above in combination with wiping everything, wiping system only and wiping data only. File systems are ext4/f2fs/f2fs on system/data/cache.
This is making me go nuts. The only thing I can think of is to try restoring under TWRP 3.0.4.
@RocKKer
try this
go to TWRP Home >> Settings >> tick use rm -rf instead of formatting
and then restore your backup
maybe this helps
cheers
I have the latest twrp 3.1.1.1 it works perfectly fine after a weeks of flashing roms and stuff.But today I tried to make a back-up and it shows System(19374482841mb) so technically it might be a bug or something.I flashed older twrps even 3.0 but still it shows like 1837428291mb.However the System image,cache and data works.
I was trying a new rom so I made a twrp backup, I was on MIUI 9 stable, It was an Oreo based rom, flashed gapps, custom kernel and magisk and MIUI firmware
Trying to restore the twrp backup after formatting (Tried Every option to format) It basically shuts off the phone while restoring, just the system (or system Image) partition, restoring data was working fine. I had to flash the system manually, then restoring data, which worked fine. Just for testing I tried to recreate a backup and restoring It Just After and the same behaviour happened! Even without flashing anything. Whats happening?
lukypuie said:
I was trying a new rom so I made a twrp backup, I was on MIUI 9 stable, It was an Oreo based rom, flashed gapps, custom kernel and magisk and MIUI firmware
Trying to restore the twrp backup after formatting (Tried Every option to format) It basically shuts off the phone while restoring, just the system (or system Image) partition, restoring data was working fine. I had to flash the system manually, then restoring data, which worked fine. Just for testing I tried to recreate a backup and restoring It Just After and the same behaviour happened! Even without flashing anything. Whats happening?
Click to expand...
Click to collapse
There is a new twrp version (3.2.0.0) which is supposed to show better oreo support. Are you on that version?
Sounds a little confusing how you described what you flashed in which order ... Also I don't get exactly which rom you're trying to restore. Can you give more accurate and precise info?
I remember there was a common issue with TWRP backup and restore when you had at least one dual app enabled. The TWRP will throw an error createTarFork() whenever I tried to backup.
Has this been fixed now with MIUI 12? Can anyone confirm if they have successfully backeup and restored through TWRP with dual apps enabled?
Thanks
On my phones I have always used the backup's function offered by TWRP's recovery .
I've always been able to restore the nandroid's backups without any problems.
However, whenever I try to restore a backup on my Note 9, the phone always goes into bootloop.
I've never had this happen with my other phones (S3 and LG G5).
I wouldn't want to have to do other things to do a successful restore.
I can't restore a nandroid backup as well on my Note 9 exynos. I think it had something to do with force encryption of the phone.
I found in an XDA thread a zip to disable dm-verity and force encryption, flashable via twrp.
After successfully disabling ecryption of my Note 9, I was able to successfully restore a previous nandroid backup.
XTrail02 said:
I can't restore a nandroid backup as well on my Note 9 exynos. I think it had something to do with force encryption of the phone.
I found in an XDA thread a zip to disable dm-verity and force encryption, flashable via twrp.
After successfully disabling ecryption of my Note 9, I was able to successfully restore a previous nandroid backup.
Click to expand...
Click to collapse
Thank you for your reply.
I mean, let me get a better understanding of what you did.
Did you first flash the "Disable_Dm-Verity_ForceEncrypt"'s zip and then restore the nandroid backup?
These are the steps I did, but not sure of the exact order:
1. Format data & reboot to Recovery
2. Flash rom (I'm using LOS 17.1 w/ microG) & reboot to Recovery
3. Flash magisk & reboot to Recovery
4. Flash the zip below
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
5. Reboot to System, complete the start up of the new Rom and confirm that the phone is now decrypted.
6. Go to Recovery and restore my nandroid backup (I created this nandroid backup when my phone is already decrypted. I haven't tested restoring a previous backup with my still encrypted phone).
I successfully restored my nandroid backup finally. Before I always fail, giving me a hard time restoring my individual apps using TBackup or Migrate.
XTrail02 said:
These are the steps I did, but not sure of the exact order:
1. Format data & reboot to Recovery
2. Flash rom (I'm using LOS 17.1 w/ microG) & reboot to Recovery
3. Flash magisk & reboot to Recovery
4. Flash the zip below
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
5. Reboot to System, complete the start up of the new Rom and confirm that the phone is now decrypted.
6. Go to Recovery and restore my nandroid backup (I created this nandroid backup when my phone is already decrypted. I haven't tested restoring a previous backup with my still encrypted phone).
I successfully restored my nandroid backup finally. Before I always fail, giving me a hard time restoring my individual apps using TBackup or Migrate.
Click to expand...
Click to collapse
I already do all this when I install the new rom. So, my phone should be decrypted.
Then after some time I make a nandroid backup. However, when I go to restore the backup the phone goes into bootloop.
So, it means that with the restore the phone comes back encrypted again. That's why it goes into bootloop.
Before, I'm flashing the 'no-verity-opt-encrypt-6.1.zip' but always ended up encrypted after reboot. Only after I flashed 'disable_dm-verity_forceencrypt.zip' that my phone became decrypted, and perform a successful nandroid restore later. I'm using twrp 3.4.0.
XTrail02 said:
Before, I'm flashing the 'no-verity-opt-encrypt-6.1.zip' but always ended up encrypted after reboot. Only after I flashed 'disable_dm-verity_forceencrypt.zip' that my phone became decrypted, and perform a successful nandroid restore later. I'm using twrp 3.4.0.
Click to expand...
Click to collapse
If I understand correctly, before restoring a nandroid backup you flashed 'disable_dm-verity_forceencrypt.zip' and then did the restore.
Right?