So I realized the other day that restoring a TWRP backup that has an older security patch does the same thing as flashing a rom with an older patch. Encrypts EVERYTHING.
So my question is this: What are the steps to restoring a TWRP backup with an older security patch? Do you just format userdata in TWRP, copy the backup from a PC, and restore? Is there more steps than this? Thanks!
H4X0R46 said:
So I realized the other day that restoring a TWRP backup that has an older security patch does the same thing as flashing a rom with an older patch. Encrypts EVERYTHING.
So my question is this: What are the steps to restoring a TWRP backup with an older security patch? Do you just format userdata in TWRP, copy the backup from a PC, and restore? Is there more steps than this? Thanks!
Click to expand...
Click to collapse
I'm interested in this too
Anybody? Any ground rules here?
H4X0R46 said:
Anybody? Any ground rules here?
Click to expand...
Click to collapse
In theory this should work , but i personally didn't try it ..
You can better put this question on the mauronofrio's twrp thread...
Related
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Tried clearing cache? Also, what things did you precisely backup?
DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache
setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.
DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?
Try it without the system image.
DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.
setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something
setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?
Yes
oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through
oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!
I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
Our MiA1 is fast, I know.. but can be faster (I think)
Does someone have an image with forced encryption disabled? December boot.img? I tried with "format data" option in twrp but I get bootloop and haven't tried with magisk
I also want boot image with forced encryption disabled.
Have you tried dm-no-verity.zip?
zeyaan said:
Have you tried dm-no-verity.zip?
Click to expand...
Click to collapse
No, I haven't tried that. I am running Oreo latest January patch rooted with Magisk.
Please guide me step by step:
how to disable forced encryption
Restore my Data with TWRP (I already have TWPR backup of Data).
Kindly also provide link of flashable zip.
I have tried the following steps to disable forced encryption with magisk but it didn't worked.
Factory Reset / Data wipe with TWRP
flashing of Magisk15.3.zip
Restoration of Data
Reboot
I think I can use latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ but main issue is that I also want my Data back using TWRP. I don't want to backup and restore apps using Titanium Backup.
armujahid said:
No, I haven't tried that. I am running Oreo latest January patch rooted with Magisk.
Please guide me step by step:
how to disable forced encryption
Restore my Data with TWRP (I already have TWPR backup of Data).
Kindly also provide link of flashable zip.
I have tried the following steps to disable forced encryption with magisk but it didn't worked.
Factory Reset / Data wipe with TWRP
flashing of Magisk15.3.zip
Restoration of Data
Reboot
I think I can use latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ but main issue is that I also want my Data back using TWRP. I don't want to backup and restore apps using Titanium Backup.
Click to expand...
Click to collapse
We gotta wait as the zips are device specific as per my understanding. Unless some builds it we have no option but wait.
Any news about this? I'm interested
Hi. I have a Moto G Plus US variant XT1644. I did a clean backup (stock ROM) when I was on NPJS25.93-14.7-3 (boot, system and data).
After that I installed many custom ROMs, all of which caused my phone to drain battery and heat up so I decided to go back to stock by restoring my backup.
After I restored my backup I instantly received a new update via OTA (build NPJS25.93-14.7-5). So in order to install it "officially" I grabbed a stock recovery.img (in this forum) and flashed it before tapping on INSTALL so that everything keeps unmodified before applying the update. But when it reboots and tries to install the update I get a message "Error!".
Please any help would be much appreciated.
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
echo92 said:
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
Click to expand...
Click to collapse
I think he can flash the 14.7 US Retail without deleting the Data Partition to get back to Stock and then do the OTA updates.
He can check this thread out:
https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page15
echo92 said:
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
Click to expand...
Click to collapse
1) I definitely took the backup after allowing modifications so this is probably why.
2) yes
3) no
Danny1976 said:
I think he can flash the 14.7 US Retail without deleting the Data Partition to get back to Stock and then do the OTA updates.
He can check this thread out:
https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page15
Click to expand...
Click to collapse
Yeah, I´ve been following that thread. I will try to do that and try to make clean backups (without allowing modifications). BTW how should I make a backup of the recovery and bootloader with TWRP ? Thanks.
hernaner28 said:
1) I definitely took the backup after allowing modifications so this is probably why.
2) yes
3) no
Yeah, I´ve been following that thread. I will try to do that and try to make clean backups (without allowing modifications). BTW how should I make a backup of the recovery and bootloader with TWRP ? Thanks.
Click to expand...
Click to collapse
You don't have to flash TWRP, just boot to it. Use the command fastboot boot twrp-3.1.1.0-athene.img and keep it read only. Make a backup of the system and boot. Root with ElementalX and Magisk. Then use Flashify to backup recovery, if you have not flashed TWRP.
[Solved (look at bottom of post)]
so, hopfully this is in the right place.
Following the procedure I've done on my nexus 6p many times over; I created a TWRP backup on my 6t then tried restoring the backup I made with twrp and when it finished I pressed reboot to system. The device then only booted into twrp. I saw it was on the "a" partition and I knew I was previously on the b partition so I manually switch partitions and now I'm stuck in fastboot boatloader I have tried flashing a temp twrp.img but im getting an error "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" in fastboot
After that I switched active partition in fast boot and got into twrp but my data appears to be encrypted and after restoring sys,data,efs,vendor (skipping boot as it holds the recovery now) I only have fast boot in both a/b partitions. I'm going to try to fast boot twerp then install twerp permanently and see if i can get a wotking twrp if not then ill have to get a factory image to get back to stock but was hoping to get some data off but whatever..
I'm kind of new to this a/b partition setup. any help is appreciated.
Edit: for future reference All I was doing was trying to restore a backup? how do I restore a backup on an a/b partition system? As far as I know I did it right...
1) remove lockscreen pin ect..
2) backup boot,sys,ven,data
When restoring
1) mount partitions
2) select restore backup and restore all .....
What am I missing?
____
Solved:
twrp for 6t is borked when it comes to backing up/ restoring...
The version in question: twrp-installer-fajita-3.2.3-1.zip
I restored my 6t to stock with msmdownloadtool and reinstalled twrp then made a test backup. After restoring it I was left in a twrp bootloap and encrypted data partition.
I don't think you should ever need to manually switch slots.
If you are on slot A, and flash an update, it will install to slot B. When you restart your phone, it will automatically switch to B for you.
Also, you shouldn't be flashing the TWRP.img, but booting it instead.
You could try starting fresh with the msmdownloadtool which is found in these forums.
fireeyeeian said:
[Solved (look at bottom of post)]
so, hopfully this is in the right place.
Following the procedure I've done on my nexus 6p many times over; I created a TWRP backup on my 6t then tried restoring the backup I made with twrp and when it finished I pressed reboot to system. The device then only booted into twrp. I saw it was on the "a" partition and I knew I was previously on the b partition so I manually switch partitions and now I'm stuck in fastboot boatloader I have tried flashing a temp twrp.img but im getting an error "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" in fastboot
After that I switched active partition in fast boot and got into twrp but my data appears to be encrypted and after restoring sys,data,efs,vendor (skipping boot as it holds the recovery now) I only have fast boot in both a/b partitions. I'm going to try to fast boot twerp then install twerp permanently and see if i can get a wotking twrp if not then ill have to get a factory image to get back to stock but was hoping to get some data off but whatever..
I'm kind of new to this a/b partition setup. any help is appreciated.
Edit: for future reference All I was doing was trying to restore a backup? how do I restore a backup on an a/b partition system? As far as I know I did it right...
1) remove lockscreen pin ect..
2) backup boot,sys,ven,data
When restoring
1) mount partitions
2) select restore backup and restore all .....
What am I missing?
____
Solved:
twrp for 6t is borked when it comes to backing up/ restoring...
The version in question: twrp-installer-fajita-3.2.3-1.zip
I restored my 6t to stock with msmdownloadtool and reinstalled twrp then made a test backup. After restoring it I was left in a twrp bootloap and encrypted data partition.
Click to expand...
Click to collapse
I'm currently stuck in TWRP with encrypted data after restoring a backup. I didn't know you couldn't restore backups on this phones. That sucks. I guess I'm going to have to start over now. That really really sucks.
imucarmen said:
I'm currently stuck in TWRP with encrypted data after restoring a backup. I didn't know you couldn't restore backups on this phones. That sucks. I guess I'm going to have to start over now. That really really sucks.
Click to expand...
Click to collapse
Yup, I felt the same.. it's a huge bummer especially when you get it all set up and perfect. Use msm to fix it if you can't use twrp. Hopefully twrp gets fixed soon (I'm really surprised I can't find more people who have noticed this or even twrp team talking about it) for now Im waiting for proof it works on the op6t. I even tried to use Chainfire's flashfire to make a backup and.. no it doesn't work.
fireeyeeian said:
Yup, I felt the same.. it's a huge bummer especially when you get it all set up and perfect. Use msm to fix it if you can't use twrp. Hopefully twrp gets fixed soon (I'm really surprised I can't find more people who have noticed this or even twrp team talking about it) for now Im waiting for proof it works on the op6t. I even tried to use Chainfire's flashfire to make a backup and.. no it doesn't work.
Click to expand...
Click to collapse
I think I just hard bricked my phone. https://forum.xda-developers.com/oneplus-6t/help/bricked-phone-t3914413
imucarmen said:
I think I just hard bricked my phone. https://forum.xda-developers.com/oneplus-6t/help/bricked-phone-t3914413
Click to expand...
Click to collapse
Use Msm download tool:
https://www.google.com/amp/s/forum....-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
I think that's the right post but make sure it matches your device. I used msmdownloadtool around 6 time just testing twrp and only had one hiccup where Msm wasn't detecting my one plus 6t but I eventually got it working.
use the other twrp unofficial but problem you had with would be fixed with big file system fat32 can't do it right
ecompton59 said:
use the other twrp unofficial but problem you had with would be fixed with big file system fat32 can't do it right
Click to expand...
Click to collapse
Could you post a link to it and are you sure? I used the unofficial version so which one are you talking about? I'd really not like to have to re-setup my daily driver from scratch.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482 your using early version of twrp the black one is made by same guy download unofficial twrp.zip not twrp.img reboot recovery flash twrp.zip then magisk it may work if not then format data (erases phone) then twrp,magisk reboot recovery to see if it stuck I flash magisk again when it starts up go to magisk thread get the manager 18.1 don't insall it
ecompton59 said:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482 your using early version of twrp the black one is made by same guy download unofficial twrp.zip not twrp.img reboot recovery flash twrp.zip then magisk it may work if not then format data (erases phone) then twrp,magisk reboot recovery to see if it stuck I flash magisk again when it starts up go to magisk thread get the manager 18.1 don't insall it
Click to expand...
Click to collapse
Which one? I've tried the 3.2.3.28 last and restoring didn't work. Should I try the most recent installer in the list? And can you confirm that backup&restoring works on the one plus 6t? Also is there anyway to backup my phone without twrp before I try this? I'd really would not like to have to use msm again?
sorry that didn't help format data then flash twrp then magisk should boot without msm
---------- Post added at 01:06 PM ---------- Previous post was at 12:52 PM ----------
i had to use extfat format on htc 8gb backup to get it to work maybe devs will fix that
Has there been an improvement on twrp for the 6t yet? Just curious if I can rely on a backup is there any updates?
So I've done some testing and after a couple msmdownloadtool sessions I've come to the conclusion that the backup/restore feature in the official and unofficial TWRP for Oneplus 6t (I tested twrp-installer-fajita-3.2.3-1 and TWRP 3.2.3-28 Unofficial by mauronofrio) is borked. If you create a backup of boot,sys,vend,data and then restore it you end up only being able to boot to twrp and encrypted data? Is there currently any way to backup partitions without twrp? I tried flashfire which doesn't work on the 6t. can you backup in fastboot? Is this issue known? I can't seem to find much info on this.
Edit: Is there any alternitives to twrp atm for full backups?
fireeyeeian said:
So I've done some testing and after a couple msmdownloadtool sessions I've come to the conclusion that the backup/restore feature in the official and unofficial TWRP for Oneplus 6t (I tested twrp-installer-fajita-3.2.3-1 and TWRP 3.2.3-28 Unofficial by mauronofrio) is borked. If you create a backup of boot,sys,vend,data and then restore it you end up only being able to boot to twrp and encrypted data? Is there currently any way to backup partitions without twrp? I tried flashfire which doesn't work on the 6t. can you backup in fastboot? Is this issue known? I can't seem to find much info on this.
Click to expand...
Click to collapse
In the thread they are mentioned that not to restore vender.
Sent from my ONEPLUS A6013 using Tapatalk
..
vichao.s said:
In the thread they are mentioned that not to restore vender.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Thanks, I didn't see that. What post was that in?
If that's the only reason it breaks then that's good.
vichao.s said:
In the thread they are mentioned that not to restore vender.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Just tried restoring a backup excluding vendor and same issue happens. Boots to twrp and only twrp plus encrypted data
I have tried so many different ways to back up and restore all with problems I have given up. I just use TWRP to flash zips until a Dev or someone with direct knowledge chimes and in responds to a simple question with regard to a proper back up and restore thats all I will use it for.
Archangel said:
I have tried so many different ways to back up and restore all with problems I have given up. I just use TWRP to flash zips until a Dev or someone with direct knowledge chimes and in responds to a simple question with regard to a proper back up and restore thats all I will use it for.
Click to expand...
Click to collapse
Yes, after about 3-4 times having to resort to using msmdownloadtool after trying to find out what I was doing wrong. I'm going to do the same. Really wish that would have been listed as an issue on there site. I would have thought something like this would have been noticed by the twrp devs but intill it's fixed or adressed guess that's all we can use it for atm.
Thanks for the reply. It's nice to know that I'm not the only one having issues.
I don't know if it's related or not, but I've read somewhere that while backing up the boot partition it's adviced to remove the screen lock/fingerprint beforehand to avoid some issues during the restore.
Twrp restore is broken.
I don't use it anymore too
daspyki said:
I don't know if it's related or not, but I've read somewhere that while backing up the boot partition it's adviced to remove the screen lock/fingerprint beforehand to avoid some issues during the restore.
Click to expand...
Click to collapse
yeah I always do that when backing up. not sure why the data becomes encrypted still. maybe its corrupted