Database Develop

Cannot boot after TWRP restore

As title suggest I'm having trouble booting after a successful restore in TWRP. I went to back to oOS nougat rom and didn't like how stripped down it was compared to resurrection remix.
I decided to restore NANDROID backup from the prior day. TWRP restored it correctly but it will not boot.
I restored the exact same backup without any issues previously.
Any suggestions?

I would try to dirty flash the corresponding ROM (RR it sounds like) over it. After restore in TWRP, wipe cache and davlik then flash the ROM. Make sure it's the same as what your restoring. This should realign the system and boot images but keep the data.

restoring from TWRP, bootloop

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

TWRP Backup of OOS doesn't work.

I was trying out a few Lineage ROMs and decided to go back to OOS (stock backup). But when I restore my backup, I am stuck at boot screen. I was running Sultan's LOS14.1 before attempting to restore my OOS 4.1.3 backup. Anyone know what would cause my backup to go bad? in TWRP (3.1.0-1) it shows the partitions I backed up are System, Data, and Boot.

Ascertion said:
I was trying out a few Lineage ROMs and decided to go back to OOS (stock backup). But when I restore my backup, I am stuck at boot screen. I was running Sultan's LOS14.1 before attempting to restore my OOS 4.1.3 backup. Anyone know what would cause my backup to go bad? in TWRP (3.1.0-1) it shows the partitions I backed up are System, Data, and Boot.
Click to expand...
Click to collapse
Not sure what could have gone wrong but at least you can go into TWRP, looks like you might have to flash stock OOS again

Clean flash OOS and restore the backup afterwards.

Anova's Origin said:
Clean flash OOS and restore the backup afterwards.
Click to expand...
Click to collapse
I'll give this a try. Will I always have to do this when going from OOS to Lineage?

Ascertion said:
I'll give this a try. Will I always have to do this when going from OOS to Lineage?
Click to expand...
Click to collapse
I guess there is some change to how encryption works between the two roms. If true, then yes. I would also advise to backup the whole user partition to a pc before trying.

Nandroid backup problem on Android pie

I have flashed Nitrogen OS, Colt OS and NLOS OS. All pie based ROM on my 3t.
While switching from one ROM to other I always take the nandroid back up and save it to my PC.
My device is decrypted, and I was using NLOS 16.
Last night, I tried to flash to flash baikal OS but unfortunatley I got bootloops so I decided to restore the latest nandroid back up of NLOS 16.
While restoring ,I was aware that NLOS is 5.0.8 fw based ROM as of now, so I first flashed the firmware then I started restoration, after hitting reboot system; phone went to bootloader mode. I again tried but in vein.
So I decided to take the nandroid back up of COLT OS with similar steps but again the phone showed the bootloader screen.
Now, finally I tried Nitrogen OS nandroid back up. It booted successfully.
So I want to know, what is causing the trouble in NLOS and COLT OS nandroid back which force the system to go to bootloader screen. I recall when I was on oreo ROM but encrypted, I could restore the nandroid back up easily by just flashing the recommended firmware first and then restoring.
Is it due to the fact that my device is decrypted and I am taking nandroid back up of sellinux enforcing builds of NLOS and COLT OS .
afaik Nitrogne OS use the sellinux in permissive mode while others are all enforcing.

I'm pretty sure you took Nitrogen backup with latest TWRP and the other two backups with the second-last TWRP which had problems backupping and restoring. Nothing to do with encryption.

mvalda01 said:
I'm pretty sure you took Nitrogen backup with latest TWRP and the other two backups with the second-last TWRP which had problems backupping and restoring. Nothing to do with encryption.
Click to expand...
Click to collapse
No, I used the same TWRP 3.3..0-1 for all ROMs.
I was using NLOS which I did flash through TWRP 3.3.0-1 and took the back up first then I proceeded to flash other ROM but restoration of the same NLOS ROM was unsuccessful.

sandeep_kumar said:
No, I used the same TWRP 3.3..0-1 for all ROMs.
I was using NLOS which I did flash through TWRP 3.3.0-1 and took the back up first then I proceeded to flash other ROM but restoration of the same NLOS ROM was unsuccessful.
Click to expand...
Click to collapse
So mvalda was correct. You are using the version of TWRP that couldn't restore /system from your backup. (The System Image option would have worked). The latest build, 3.3.1-0, fixes that issue.
Another way to get the backup working on the old build was to restore the backup and immediately dirty flash your ROM again.
Update your TWRP to latest and take a backup.
Edit: Flashing Firmware before restoring a backup is pointless. The backup will immediately overwrite it.

How to restore the nandroid's backup on the note 9?

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?