Related
hi there guys,
I have some questions about how to make a total back-up of your rom, so you don't have to setup your apps and stuff like that, when you wanna try something new. Setting everything up when I wanna go back,is holding me back.
hope this is not a total repost, if it is just show me the old thread, cause I couldn't find it.
Errr... A classical Nandroid (whole Rom with Kernel, Apps and Settings) and/or Titanium Backup (Apps and Settings - possible to transfer data between different roms) should offer everything you need
...via Tapatalk
when I bake a backup with clockwork, I still need to set everything up, and install my apps again. What am I doing wrong?
Safidk said:
when I bake a backup with clockwork, I still need to set everything up, and install my apps again. What am I doing wrong?
Click to expand...
Click to collapse
I always backup and restore from recovery menu of clockwork, this means when restoring everything is put back as it was.
Not sure why this isn't working for you
Sent from my HTC Desire S
I downloaded (and paid for) the newest version of clockwork manager from the marked. How do you do it, just from the app or do you boot in recovery? When you say full recovery does that include everything, so you don't have to setup anything?
Yes mate, boot into recovery, select "backup and restore", then backup - this will save a full copy of your system as it stands. When you backup from the recovery menu it will put everything back exactly as it was when you backed it up - ie all apps & data already setup
Sent from my HTC Desire S
and before I recover I need to do a complete wipe, right. System, catch and factory?
No.. you dont need to wipe before restrore.
Sent from my HTC Desire S using XDA Premium App
ok, tnen I'm gonna try again. Don't see why its not working for me. There's not a secieal setup I need to do? I haven't done anything else than installing the app ;-)
Confusion?
I believe that there is a couple of differing questions are being asked and answered here.
A Nandroind backup or full device backup (excluding RADIO) will enable you to restore your device back to the exact state that it was in when taken. All the phone partitions SYSTEM/DATA/BOOT/CACHE/etc are all backed up. Therefore restoring one of these backups will ensure that the ROM, kernel and data will be restored together and the phone will be operational.
A Titanium Backup backs up applications and setup data that enables you to easily restore your installed applications and configuration. After a factory reset or a re-install of the same ROM.
It can often be problematic to use a titanium backup after changing the version of the ROM you used or when moving from one ROM to a completely different one. In fact quite often ROM cooks recommend that you don't use a Titanium backup restore in the setup of their ROM.
That being said I still take both types of backups on my device. As titanium backups are useful for restoring individual applications to a previous state if they encounter a problem or corruption.
I believe that the Nandroid backup is the most useful recovery tool we have available to us and always take one, before flashing any new ROM or ZIP file, better to be safe than sorry.
Although I'd also recommend that all personal data ie calendar & contacts should be backed up by sync'ing to the cloud and never just kept locally on the device.
Hello Guys,
Since I totally bricked my old Nexus 5 16GB(KTU84P) I am going to get a new one. But I am thinking of getting the 32GB version this time.
Now before it got bricked I made a full nandroid back-up with the help of the Nexus Root Toolkit and TWRP.
Now here are a few (stupid) questions:
~Is it possible to restore a nandroid backup from one phone to another and even in this case a "different" version of the phone?
(I've skipped over this thread real fast http://forum.xda-developers.com/showthread.php?t=728266 which says it is possible for phones of the same model)
~If it is possible how should it be done?
~And well if the first question isn't possible, is there a way to read out out the created back-up files which TWRP created and manually restore them(preferable the data partition)
I hope you guys can help me out
Kind regards
Yes, you can do it. Just make sure you're not restoring the efs partition or you'll have another brick on your hands.
Sent from my Nexus 5 using XDA Free mobile app
Also don't use toolkits next time. Please use the manual methods which are better, safer and teach you the basis you need to recover.
All guides and info threads can be found in general > sticky roll-up thread
Sent from my Nexus 5 using Tapatalk
When you run into issues, as many do after nandroid restoring from one device to another... Wiping and Flashing stock with fastboot is the Fix.
Thought I'd cover that up front. ?
jd1639 said:
Yes, you can do it. Just make sure you're not restoring the efs partition or you'll have another brick on your hands.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
rootSU said:
Also don't use toolkits next time. Please use the manual methods which are better, safer and teach you the basis you need to recover.
All guides and info threads can be found in general > sticky roll-up thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey guys sorry I didn't answer immediately, but after I saw the posts I immediately ordered a new Nexus 5 (32GB this time). I got it delivered today and like you said I've done the unlocking, custom recovery and rooting manually this time instead of using a toolkit. Which was to be honest way easier than I thought but also way faster than using a toolkit.
But now I've kinda run into a other 'problem'
When I restore my previous made backup (the one from the bricked phone) I first of all only get the options to restore the 'system' partition and the 'data' partition (which is totally fine cause those are the only ones I actually need).
But when I restore the system partition a lot of apps crash on default(It is basically bricked then), and even when I just restore the data partition the same thing happens. (To be completely fair this problem might come from the fact that I used the MD5 verification option when I made the backup but I can't really remember that. but some of my backup files end with the .MD5 extension) Saying this I also used the restore option with check MD5 verification, but needless to say I get the message that they verifications don't match.
So here are a few questions again.
~Like I said before I only really care about the 'data' partition, Is there an option that I still can use TWRP to restore it properly?
~If the above is not possible is there a manual way to read out the made backup file using a program like 'Ext2Explore'(This crashes though when I open the file)
Or did I just completely screw up by checking the MD5 verification?
Once again kind regards
p.s. If the problem isn't clear tell me and and I'll try to explain it in a different way
You missed quote from post #4. ?
I believe that with a new device.... It should be a clean start. And I read post after post in different device sections of issues from restoring from other devices.
And so I never recommend it. It can, possibly, bring lots of issues.
But to each their own.
Good luck. ?
KJ said:
You missed quote from post #4. ?
I believe that with a new device.... It should be a clean start. And I read post after post in different device sections of issues from restoring from other devices.
And so I never recommend it. It can, possibly, bring lots of issues.
But to each their own.
Good luck. ?
Click to expand...
Click to collapse
Ohh right, sorry I completely read over your post my bad. But then again If I have to wipe the device wouldn't that totally remove the point of restoring the data partition ? or is the wipe command just for the system partition?
sambo940 said:
Ohh right, sorry I completely read over your post my bad. But then again If I have to wipe the device wouldn't that totally remove the point of restoring the data partition ? or is the wipe command just for the system partition?
Click to expand...
Click to collapse
What I'm getting at, is don't restore the data partition. You can try, but I often read of lots of issues doing it.
Yes, I implied wipe the device clean. Flash stock. Start fresh.
Now if you had a titanium backup of user apps on your pc... I'd say you'd have a much easier time restoring that to the new phone.
Just my 2 cents of course.
KJ said:
What I'm getting at, is don't restore the data partition. You can try, but I often read of lots of issues doing it.
Yes, I implied wipe the device clean. Flash stock. Start fresh.
Now if you had a titanium backup of user apps on your pc... I'd say you'd have a much easier time restoring that to the new phone.
Just my 2 cents of course.
Click to expand...
Click to collapse
I made a clean start yes. Unfortunately I don't have a titanium backup and I get that storing the data partition to a other device isn't a good idea. But well I never had the intention of making a back up and restoring it to another device but unfortunately my other phone got completely bricked. And yes in hindsight I should have made backups in multiple ways.
But like I said I don't really care about the system(including the apps and app settings) it is literally all about the actual data (pictures and stuff), that is also the reason why I asked if there is a way to manually read/open the back-up files.
sambo940 said:
I made a clean start yes. Unfortunately I don't have a titanium backup and I get that storing the data partition to a other device isn't a good idea. But well I never had the intention of making a back up and restoring it to another device but unfortunately my other phone got completely bricked. And yes in hindsight I should have made backups in multiple ways.
But like I said I don't really care about the system(including the apps and app settings) it is literally all about the actual data (pictures and stuff), that is also the reason why I asked if there is a way to manually read/open the back-up files.
Click to expand...
Click to collapse
The pictures are gone. A nandroid doesn't back those up or anything on the internal sdcard
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
The pictures are gone. A nandroid doesn't back those up or anything on the internal sdcard
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well that certainly is a bummer, and also very misleading from the nexus toolkit. From now on I shall back-up my phone more properly and well stop using those darn toolkits,
Thank you for your time.
sambo940 said:
Well that certainly is a bummer, and also very misleading from the nexus toolkit. From now on I shall back-up my phone more properly and well stop using those darn toolkits,
Thank you for your time.
Click to expand...
Click to collapse
Did you make an adb backup in the tool kit? That would have your pics. But a flashable nandroid you flash in recovery would not.
Sent from my Nexus 5 using XDA Free mobile app
sambo940 said:
I made a clean start yes. Unfortunately I don't have a titanium backup and I get that storing the data partition to a other device isn't a good idea. But well I never had the intention of making a back up and restoring it to another device but unfortunately my other phone got completely bricked. And yes in hindsight I should have made backups in multiple ways.
But like I said I don't really care about the system(including the apps and app settings) it is literally all about the actual data (pictures and stuff), that is also the reason why I asked if there is a way to manually read/open the back-up files.
Click to expand...
Click to collapse
Would Nandroid Manager be what you're looking for? EDIT: as above, it won't find and restore any of your pictures/music, as a nandroid backup does not include any of these. There is a chance you find and restore your apps and settings if you so wish. I've used that app before.
Incidentally, I successfully transferred all of my data and ROM from one Nexus 5 to another (had to RMA)
The process I used is:
- Unlock bootloader, install custom recovery on new N5
- Nandroid backup on old N5
- Copy whole /sdcard partition from old to new N5. Basically, all files and folders on the 'root' of the drive when connected to PC. This included all photos, music and the nandroid backup itself.
- Restore nandroid backup on new N5 (only /system, /data and boot.img / kernel), as if you were restoring any nandroid backup really. Though do not restore efs partition as advised above (it wasn't backed up, but worth mentioning again anyway).
Took a while, but the ROM and settings were carried over successfully.
jd1639 said:
Did you make an adb backup in the tool kit? That would have your pics. But a flashable nandroid you flash in recovery would not.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Nope, I did not. And the ignorant person that I am just assumed that the nandroid backup would back up everything since the toolkit says "Make full Backups"
So well I guess I just have to accept the fact that I lost those things
eddiehk6 said:
Would Nandroid Manager be what you're looking for? EDIT: as above, it won't find and restore any of your pictures/music, as a nandroid backup does not include any of these. There is a chance you find and restore your apps and settings if you so wish. I've used that app before.
Incidentally, I successfully transferred all of my data and ROM from one Nexus 5 to another (had to RMA)
The process I used is:
- Unlock bootloader, install custom recovery on new N5
- Nandroid backup on old N5
- Copy whole /sdcard partition from old to new N5. Basically, all files and folders on the 'root' of the drive when connected to PC. This included all photos, music and the nandroid backup itself.
- Restore nandroid backup on new N5 (only /system, /data and boot.img / kernel), as if you were restoring any nandroid backup really. Though do not restore efs partition as advised above (it wasn't backed up, but worth mentioning again anyway).
Took a while, but the ROM and settings were carried over successfully.
Click to expand...
Click to collapse
Not exactly what I was looking but I'll keep it in the back of my head in case something similar might happen in the future(lets hope not) Thanks.
Install Foldersync and set your sdcard to sync to a computer wirelessly
Sent from my Nexus 5 using Tapatalk
eddiehk6 said:
Would Nandroid Manager be what you're looking for? EDIT: as above, it won't find and restore any of your pictures/music, as a nandroid backup does not include any of these. There is a chance you find and restore your apps and settings if you so wish. I've used that app before.
Incidentally, I successfully transferred all of my data and ROM from one Nexus 5 to another (had to RMA)
The process I used is:
- Unlock bootloader, install custom recovery on new N5
- Nandroid backup on old N5
- Copy whole /sdcard partition from old to new N5. Basically, all files and folders on the 'root' of the drive when connected to PC. This included all photos, music and the nandroid backup itself.
- Restore nandroid backup on new N5 (only /system, /data and boot.img / kernel), as if you were restoring any nandroid backup really. Though do not restore efs partition as advised above (it wasn't backed up, but worth mentioning again anyway).
Took a while, but the ROM and settings were carried over successfully.
Click to expand...
Click to collapse
I am assuming that you used a tool like Android File Transfer.
So what I'm trying to do is the same thing, backup my entire old N5 32GB as I had also requested an RMA of the device. Is it accurate in stating that you want me to copy every folder that shows up on the AFT window (Note: I am using a MAC) and copy that onto a folder on my computer. Then copy over everything on the new device (bootloader unlocked, rooted, same TWRP version installed) and restore via the Nandroid backup from my old phone (which was also transferred as indicated above).
dcxgod said:
I am assuming that you used a tool like Android File Transfer.
So what I'm trying to do is the same thing, backup my entire old N5 32GB as I had also requested an RMA of the device. Is it accurate in stating that you want me to copy every folder that shows up on the AFT window (Note: I am using a MAC) and copy that onto a folder on my computer. Then copy over everything on the new device (bootloader unlocked, rooted, same TWRP version installed) and restore via the Nandroid backup from my old phone (which was also transferred as indicated above).
Click to expand...
Click to collapse
I didn't use AFT, just plugged straight into PC, sorry no experience with Mac
Basically both phones were connected, and I copied the whole "/sdcard" straight from one phone to another, without making an initial copy to the PC
You want to replicate the same file structure
Hello again good people,
You may remember me asking questions in this forum recently, thank you again for all those who replied.
I'm back again after waiting for the official twrp to be released and reading all the forum posts in the guides section for the threads about twrpless-root (magisk) and the stickied twrp root guide by Funk Wizard. I am still a bit confused about a couple of things though. And still deciding which way is the best for me now that I still have a stock device. Please correct any mistakes I make.
When I root, in case something goes wrong, I cannot do a system settings -> factory reset. (Because it would softbrick?)
Is this where twrp comes in? Or will I still have to flash a stock image regardless, like I would if I go twrpless?
Is it true that I can make, and restore from a backup I make with twrp in case something goes wrong?
Isn't that something I can also do with Titanium Backup?
Twrpless root seems like it's a lot more easy to maintain with OTA's (download from the settings, reinstall magisk on second partition) than a twrp install would (having to connect my device to my pc and going through the steps again every time an OTA gets pushed).
The main reason I'm asking all these questions is because I still find it hard to pinpoint exactly why more experienced people in these forums favor one way or the other, and what exactly the added benefit would be of twrp in my situation. Personally, I want my phone to be more customizable (black theme, adaway, yt vanced and so on) but keep all the functionality. Banking apps, wifi, cellular and everything.
I'm not going to install custom roms. And a little bit of added ease of use with OTA sounds really good to me.
I have read that the systemless magisk twrpless might be the best fit for my needs, but after hearing your advice from my previous questionthread I decided to wait for twrp. Now twrp official is released and I dove into reading just about everything I could find I have doubts if it is something I actually need. In short I just keep swaying without being able to make a decision.
Sorry for the long post, I hope my questions are clear enough, since it's pretty late when I'm typing this. I just want to be thoroughly informed about all of this, I rather post too many questions and root correctly without concerns instead of having to make an SOS post later when my phone has exploded, lol.
And maybe there will be other newlings who can benefit from this information.
Thanks for reading!
Ok lets first address the types of backups.
Type one is system apps and data. This backup saves all apps (apk) and all data that is stored within the app folders. This is a Titanium backup.
Type two is a Nandroid backup. This backup saves your entire phones data including the internal storage, data, apps, pictures, music, cache, settings, passwords, EFS (encrypted file system) and even the Titanium backups backup itself.
Now let me explain what each of these backups are capable of. First we will start with Titanium Backup. If for some reason you brick your phone and lose all of your data. In order to use Titanium Backup you will have to install your operating system, unlock your bootloader, root your phone, install Titanium Backup and merge your data from wherever you have it to your device and install your apps + data one at a time.
Nandroid backup. Same scenario bricking or losing your data. You can simply fastboot the twrp.img once your phone boots into recovery you can merge nandroid backup point TWRP to the restore location and you have your operating system and all of your data back in place as if nothing happened. You will then flash Magisk back to your device then you would install TWRP clear your cache and once you reboot everything is just the way it was when you created the nandroid backup.
Installing an update with TWRP is as simple as downloading the update and flashing both the update and Magisk, clearing cache and rebooting.
Having TWRP would allow you to wipe and reinstall fresh like factory settings or you can restore everything you backed up.
Make Nandroid backups bi-weekly or monthly so you can always have an updated copy of your data.
Titanium backups I have scheduled once a week with 2 max backups. Why 2? If I update an app and my backup runs tomorrow I would be stuck with an app update that may be broken. This way I have the previous weeks backup to reinstall the app and data with.
Whichever you choose always always always keep redundant backups. One on the phone, one on your computer, one on a thumb drive ect ect.
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Thank you for making the time writing this, it is relief to hear that you figure this out. Will try this first in the morning.
I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.
tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
This guide can also be used to restore from other roms;
b217260 said:
I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.
Click to expand...
Click to collapse
What did you do?
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
petran07 said:
This guide can also be used to restore from other roms;
Click to expand...
Click to collapse
I guess so. I never had to use a backup to restore on a custom ROM yet.
tabletalker7 said:
What did you do?
Click to expand...
Click to collapse
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.
b217260 said:
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.
Click to expand...
Click to collapse
It's my bad. I always store my backups on an SD card with my OTG card reader. I forget others don't think like I do sometimes
tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.
b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Had faced this many times. ...after trying diff options and failed Qualcome MSM method works perfectly.
Yep, You cant restore data i think as it being already formated as per knowd based on your steps above on diff posts
ahacker said:
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.
Click to expand...
Click to collapse
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.
tabletalker7 said:
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.
Click to expand...
Click to collapse
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.
ahacker said:
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.
Click to expand...
Click to collapse
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble
tabletalker7 said:
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble
Click to expand...
Click to collapse
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.
ahacker said:
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.
Click to expand...
Click to collapse
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.
tabletalker7 said:
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.
Click to expand...
Click to collapse
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.
ahacker said:
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.
Click to expand...
Click to collapse
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.
tabletalker7 said:
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.
Click to expand...
Click to collapse
-It is as horrible as not being able to restore a full backup. No more, no less.
-Twrp has an ability to encrypt your backups, with your experience you must know this.
-You are suggesting someone to switch to iphone only because they point out that the things are wrong or dont add up.
-It is quite a common knowlege that you get good security out of encryption if you make things explicit and clear. And not how you may think it is. Cause you don't seem to know where the keys are stored for the data partition. Obviousely, because the phone eventually decrypts your data, the keys must be stored somewhere or derived from you swipe pattern.
tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
Following these instructions seems to be the only way of restoring a nandroid backup (at least for my Op6 bought on AliExpress from China). Important: step 1 wipes your sdcard, so the backup you want to restore must be on otg usb stick.
After spending many hours I managed to restore a backup at least once. Fortunately for me I have no plans of upgarding Android and will likely forever stick with the following set:
1) 5.1.11-OREO-OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT.zip (found here)
2) twrp-3.2.3-x_blu_spark_v9.85_op6.img + twrp-3.2.3-x_blu_spark_v9.85_op6.zip (found here)
3) Magisk-v18.1.zip (found here)
My plan is to fully debloat the phone and then I will keep everything unchanged for years, because nowadays updates are more about twisting your arms than giving you usefull features. I almost got to that state, but one little glitch forced me to roll back and the whole hell with the Nandoid backups on Op6 started.
PS: It's very interesting what is really going on with this A/B system. There must be a storage where the encryption keys are stored (if it is the encryption that does prevent the phone from restoring. Which I doubt because Twrp sees the files fine). There also probbaly stored what slot is used. That information does not get captured by the Nandroid backup.
(Btw, It seems that blu_spark Twrp is really NOT encrypting your backups with the passwod you supply. Official Twrp does. I have plenty of old encypted backups, from wich I could not extract any personal data (/data/data folder) but yesterday I could extract my private information from a backup done by blu_spark Twrp. This is serious iussue. I'll double check and will post if confirmed.)
Not confirmed, I was looking at unencrypoted file.
Greetings,
I had lineageos 17 on my one+6 and after making a twrp backup and making sure i had all my files that i wanted i took the plunge and upgraded to lineage 18.
This would have been great except that I didnt actually have all the files I wanted. I critically forgot to make a manual separate backup of signal messenger. I need to get the history of signal messenger back. The only way i can think to do this, is to restore the twrp backup i made before upgrading and then making a backup with signal messenger app and then restoring the signal backup in lineage 18.
I attempted to restore my TWRP backup. When I made the TWRP backup I had checked ALL the boxes and saw no errors on the screen. When i attempted to restore i checked all the boxes on the screen and got what appears to be a fairly common error (255) when attempting to restore data (not sd/usb).
After, when i went to reboot twrp notified me that there was no OS installed. I rebooted anyway. I ended up stuck in a bootloader loop. I then downloaded
10.3.6-OnePlus6Oxygen_22.J.48_OTA_048_all_2010042239_c0c1fee2ee-FASTBOOT.zip
Click to expand...
Click to collapse
Then i unzipped that file and typed in the linux terminal:
fastboot -w update images.zip
Click to expand...
Click to collapse
I now have a working phone again.
I would like to know how do i restore the TWRP recovery image that I made at the beginning of the whole process. I'm pretty sure if I can do that I can then make a new Signal backup and be fine.
While doing lots of trouble shooting for the last 36 hours or so, it seems relevant to mention that my phone used to require I enter a PIN in order to use it, and I had to enter that same PIN in TWRP before I made the backup. The temporary OxygenOS I installed to just have a working phone number for work does not have a pin.
I have never had any success restoring TWRP backups so I eventually gave up relying on them after the 4th failed attempt.
But I distinctly remember reading this piece of advice:
0. Copy the TWRP backups onto a separate storage (I assume you have already done that)
1. Install the original ROM that is present in the backup; don't restore the System partition
2. Once installation has completed, restore only the Data partition and ignore all the rest such as cache, system, boot, etc.
3. Reboot
Personally, I have never tried it. But just from reading it, it seems like it may just work. Or it might not.
adeklipse said:
I have never had any success restoring TWRP backups so I eventually gave up relying on them after the 4th failed attempt.
But I distinctly remember reading this piece of advice:
0. Copy the TWRP backups onto a separate storage (I assume you have already done that)
1. Install the original ROM that is present in the backup; don't restore the System partition
2. Once installation has completed, restore only the Data partition and ignore all the rest such as cache, system, boot, etc.
3. Reboot
Personally, I have never tried it. But just from reading it, it seems like it may just work. Or it might not.
Click to expand...
Click to collapse
I appreciate the reply.
It's the data partition that's throwing this 255 error, which it seems to have something to do with it being encrypted i'd guess? In the future, is it possible to just dd the whole thing somehow?
karenmcd said:
I appreciate the reply.
It's the data partition that's throwing this 255 error, which it seems to have something to do with it being encrypted i'd guess? In the future, is it possible to just dd the whole thing somehow?
Click to expand...
Click to collapse
Have you tried wiping the /data partition from TWRP's Advance Wipe?
karenmcd said:
Greetings,
I had lineageos 17 on my one+6 and after making a twrp backup and making sure i had all my files that i wanted i took the plunge and upgraded to lineage 18.
This would have been great except that I didnt actually have all the files I wanted. I critically forgot to make a manual separate backup of signal messenger. I need to get the history of signal messenger back. The only way i can think to do this, is to restore the twrp backup i made before upgrading and then making a backup with signal messenger app and then restoring the signal backup in lineage 18.
I attempted to restore my TWRP backup. When I made the TWRP backup I had checked ALL the boxes and saw no errors on the screen. When i attempted to restore i checked all the boxes on the screen and got what appears to be a fairly common error (255) when attempting to restore data (not sd/usb).
After, when i went to reboot twrp notified me that there was no OS installed. I rebooted anyway. I ended up stuck in a bootloader loop. I then downloaded
Then i unzipped that file and typed in the linux terminal:
I now have a working phone again.
I would like to know how do i restore the TWRP recovery image that I made at the beginning of the whole process. I'm pretty sure if I can do that I can then make a new Signal backup and be fine.
While doing lots of trouble shooting for the last 36 hours or so, it seems relevant to mention that my phone used to require I enter a PIN in order to use it, and I had to enter that same PIN in TWRP before I made the backup. The temporary OxygenOS I installed to just have a working phone number for work does not have a pin.
Click to expand...
Click to collapse
For what I know you need your device to be decrypted to restore from custom recovery.
I've had some luck in similar situations using Titanium Backup to extract an app and data from TWRP backup.
Your mileage may vary.