Related
I installed TWRP 2.8.6.2 from the link in the first post of the Lollipop thread (http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-1-photon-q-t3073781 ). I assume this is the latest/correct version for PQ?
I want to backup data so I can reformat data as f2fs and be able to use latest kernel.
I've tried backing up just data, or all four selections, with and without compression. Everything I've tried fails with error 255.
The log shows /data/data/com.skype.radier failed. So I deleted skype cache, data, then uninstalled. Retried backup again and still fail. Tried to manually delete folder, it won't delete nor will any of the subfolders (error 39 from es explorer). Tried to delete using TWRP's file manager, still won't delete (ERROR=1)/
a piece of TWRP log where it shows the errors.
I:addFile '/data/data/com.skype.raider/files/myskype.name/media_messaging/emo_cache/^80485FFBB32073DC42B65F944722AD423320F0EA974A6BF94F^pthumbnail_5b11e5f1-d716-4f57-842d-6ffdb8b257f3_distr' including root: 1
E:Error adding file '/data/data/com.skype.raider/files/myskype.name/media_messaging/emo_cache/^80485FFBB32073DC42B65F944722AD423320F0EA974A6BF94F^pthumbnail_5b11e5f1-d716-4f57-842d-6ffdb8b257f3_distr' to '/external_sd/TWRP/BACKUPS/T0695028XX/2015-12-15--15-40-38_cm_moto_msm8960_jbbl-userdebug_4.4.4_KTU84Q//data.f2fs.win000'
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/T0695028XX/2015-12-15--15-40-38_cm_moto_msm8960_jbbl-userdebug_4.4.4_KTU84Q/data.info'
E:createTarFork() process ended with ERROR=255
Backup Failed.
Well just great. I wanted to backup but instead deleted everything. After posting I kept searching and trying ways to be able to delete that. Finally came to something that suggested using fcsk to check/repair the filesystem. Said to boot to recovery, adb shell, unmount and then run it. That didnt work cuz there was no unmount command in adb shell that I could find. Then I found in the TWRP menu there was a repair filesystem command, thought that was great! Ran it. And it wiped my data folder completely.
Not very happy right now.
I had the same problem as you when trying to convert to F2FS, and lost many hours of work as well! In my case the backup actually worked when using compression, so I thought all was good even though I never could get it to restore. I was able to get some of the data back by untarring the backup files themselves though, so you could maybe even look at the unsuccessful backup files if you had something important to recover.
In post 161 of this thread http://forum.xda-developers.com/pho...anogenmod-12-1-photon-q-t3073781/post64064173 a developer has compiled TWRP 2.8.7.0 for the Photon Q and it appears backup works. I never have tried it myself though as I hadn't seen the post in time. I just ended up using titanium backup.
Well I'm in an even worse situation now. I tried restoring from the failed backup and now my phone crashes and reboots a minute or two after booting. So I figured I better reinstall gapps. However, I can't get into recovery anymore. Just sits forever of the TeamWin screen. Reloaded recovery thru adb fastboot and it still does the same thing. So I can't even get into recovery to try flashing gapps again or if it came to it wipe data and start clean. I'm phoneless.
RSD Lite back to stock...
Hello,
XT1032 CM 12 latest nightly (I think)
I flashed TWRP v2.8.6.0 using their manager app. I entered recovery mode and everything seemed to work fine. I made a NANDroid backup then rebooted. Unfortunately the device was then stuck at the bootlogo and kept looping. I can still access recovery and fastboot but for some reason adb doesn't see the device, nor can my device's data be access under Windows 7. I don't recall if I had USB debugging on or not. I would like to try to backup a few files to my computer (the backup for instance) but I am unable to since I can't use adb as the device is not recognized. MTP through TWRP doesn't seem to work either. I do have the Universal drive pack installed already on Windows.
Any help would be greatly appreciated. Thanks for your time.
To start with, let's make sure the files you want still exist.
1. Boot into TWRP recovery
2. Go to "Mount" and check that your "Data" partition is selected
3. Go back and then go to "Advanced" and then to "File Manager"
4. Navigate around (maybe /sdcard/ ? Depends what you're looking for) and find the files you need
If you can't find your file, you'll need some more help. Let's say you do see your file. Do you have a USB-OTG cable? You could plug a USB drive into your phone and mount that. Then you could copy your file to that drive. If you don't have the cable you do have some other options, but let us know how far you get.
EDIT: I know I haven't addressed the problem of the bootloop at all. Many of those solutions involve wiping so we need to make sure you've backed up all the files you need first.
First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:
frustratedwhiteman said:
First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:
Click to expand...
Click to collapse
I'm not really a Nandroid expert, but I can take a few shots in the dark. When you did your backup you got a TAR file for System and one for Data, etc., right? Then you convert those to IMGs? If you upgraded and then restored the system backup I can see why that would result in a boot loop. Restoring the data image shouldn't cause such problems though. Is this what you've tried so far? You're right, though. The safest method is to manually restore the data of just the apps where you need that data, and do it one at a time. This would allow you to pinpoint what is causing the issue. Of course, I may have no idea what I'm talking about. I've never actually needed to restore a Nandroid backup! Hopefully someone with more experience there will chime in.
I thought to hell with it I went and solved the issue by installing CM13
Thanks for taking the time to help and see you next time
UPDATE: I have since updated to official 5.1.6 via OTA flashed TWRP and Magisk. The backup finished successfully with no sign of 255 error and once rebooted the USER ID and all 999 folders were still gone after the update and switched slots.
Only tested on OnePlus 6 but file structure should be the same on any device running Android O. Must be rooted to grant Terminal Emulator root permission. You cannot remove a user without root.
If anyone has had the 255 error while trying to create a backup file or trying to restore with TWRP. This error pertains to the parallel apps or multi user ID. If you are not sure if you have parallel apps running on your OnePlus 6 or other devices you can do a quick check by go into your Root browser and look in these locations.
/storage/emulated
/data/system/
data/system_ce/
data/system_de/
data/misc/
data/misc_ce/
data/misc_de/
data/user/
data/user_ce/
data/user_de/
If you see any folder named 999 then you have parallel apps enabled on your device. TWRP in it's current form will not allow you to create a backup or restore a backup with parallel apps enabled.
Currently there is only one solution that I have found to be able to delete all of the 999 folders and that is to open a terminal emulator to each of these locations and remove the 999 folders individually. I have found a solution where you can delete the user ID and by doing so it removes all of the 999 folders and not only does it remove the folders they do not return once you reboot your device. The solution is simple so let's get to it.
Install Terminal Emulator from the play store
Open Terminal and type
su
Press enter and grant root permission
Next type
pm remove-user 999
Press enter
Close Terminal and reboot
Once rebooted go back to your Root browser and check the locations listed above to ensure the 999 folders are gone. That's all, Enjoy.
I searched the locations you mentioned and didn't find any 999 folders but I still get the error 255 when trying to flash 5.1.6 full zip. Any ideas what the issue could be?
I even tried running the commands on terminal anyways and got an error saying "couldn't remove user ID 999"
Any help is appreciated. Thanks
dracoboss said:
I searched the locations you mentioned and didn't find any 999 folders but I still get the error 255 when trying to flash 5.1.6 full zip. Any ideas what the issue could be?
I even tried running the commands on terminal anyways and got an error saying "couldn't remove user ID 999"
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Try to remove your security pin code first before install new firmware.
Thanks for sharing the info :good:
Stupid question about backup ,
I normally use root essentials to make a system backup but I think with op6 it will not backup al the required files anymore I think.
So I want to make the backup true twrp but can someone list the files to backup. As there are also vendor partition listed. So please let me know what to backup exactly to make the correct backup.
Thanks in advance.
Regards ysco..
dracoboss said:
I searched the locations you mentioned and didn't find any 999 folders but I still get the error 255 when trying to flash 5.1.6 full zip. Any ideas what the issue could be?
I even tried running the commands on terminal anyways and got an error saying "couldn't remove user ID 999"
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Make sure you're doing "su" then enter first and its getting root permissions
I'm on official TWRP.
I have a backup of Renovate 2.0, which worked without any errors, but after I ran into issues with the 2.1 flash (bootloop) I wanted to restore my backup, which fails with the 255 error at the Data partition, the rest restores fine.
Now I was in TWRP terminal to do the above, but I couldn't find / delete any of the 999 folders. I also didn't have any other IDs on 2.0, nor did I have any security features active at the time of my backup.
What will this operation do for me with a complete but unrestorable backup anyway, surely it won't delete folders out of my backup?
What triggers the error, the destination (ROM) or the backup file?
Is there a way to get into my backup from TWRP terminal?
Any other ideas?
Thanks for any input!
geenyous said:
I'm on official TWRP.
I have a backup of Renovate 2.0, which worked without any errors, but after I ran into issues with the 2.1 flash (bootloop) I wanted to restore my backup, which fails with the 255 error at the Data partition, the rest restores fine.
Now I was in TWRP terminal to do the above, but I couldn't find / delete any of the 999 folders. I also didn't have any other IDs on 2.0, nor did I have any security features active at the time of my backup.
What will this operation do for me with a complete but unrestorable backup anyway, surely it won't delete folders out of my backup?
What triggers the error, the destination (ROM) or the backup file?
Is there a way to get into my backup from TWRP terminal?
Any other ideas?
Thanks for any input!
Click to expand...
Click to collapse
The directions that are listed above are to be used inside terminal emulator once your phone is booted up and before you make the backup. I'm not sure if you can actually take files out of the backup especially from your device. That may be something you have to pull from the device and put onto your computer to accomplish
ysco said:
Thanks for sharing the info :good:
Stupid question about backup ,
I normally use root essentials to make a system backup but I think with op6 it will not backup al the required files anymore I think.
So I want to make the backup true twrp but can someone list the files to backup. As there are also vendor partition listed. So please let me know what to backup exactly to make the correct backup.
Thanks in advance.
Regards ysco..
Click to expand...
Click to collapse
If you want to make a full and complete backup of your entire system then you go into backup in TWRP and you check mark every box and then make your backup.
dracoboss said:
I searched the locations you mentioned and didn't find any 999 folders but I still get the error 255 when trying to flash 5.1.6 full zip. Any ideas what the issue could be?
I even tried running the commands on terminal anyways and got an error saying "couldn't remove user ID 999"
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Please if you could report back to us on this thread and let us know if the instructions you were given above help you or not
dgunn said:
If you want to make a full and complete backup of your entire system then you go into backup in TWRP and you check mark every box and then make your backup.
Click to expand...
Click to collapse
Thanks for the reply back to me.
I already did make a full backup and I know the procedure to make a backup in twrp but I wanted to know if all must be marked for a full backup. Some say that not all needs to be checked. If you mark all the backup is huge lol.
Thanks.
Regards ysco..
dgunn said:
Please if you could report back to us on this thread and let us know if the instructions you were given above help you or not
Click to expand...
Click to collapse
Oh sorry lol. Turns out I just had to use official twrp to flash the full zip instead of the unofficial one I was using. After that it was smooth sailing
ysco said:
Thanks for the reply back to me.
I already did make a full backup and I know the procedure to make a backup in twrp but I wanted to know if all must be marked for a full backup. Some say that not all needs to be checked. If you mark all the backup is huge lol.
Thanks.
Regards ysco..
Click to expand...
Click to collapse
boot, system image, vendor image, data.. and you are on the safe side.
Once I made a backup of boot, system, vendor, data (no images) I had to flash OOS afterwards. I don´t completely understand the difference between first and second way, finally both worked. But for sure it is not necessary to mark all partitions.
Flying Fox said:
boot, system image, vendor image, data.. and you are on the safe side.
Once I made a backup of boot, system, vendor, data (no images) I had to flash OOS afterwards. I don´t completely understand the difference between first and second way, finally both worked. But for sure it is not necessary to mark all partitions.
Click to expand...
Click to collapse
Thanks for pointing out the steps for a successful backup.
Regards ysco..
ysco said:
Thanks for the reply back to me.
I already did make a full backup and I know the procedure to make a backup in twrp but I wanted to know if all must be marked for a full backup. Some say that not all needs to be checked. If you mark all the backup is huge lol.
Thanks.
Regards ysco..
Click to expand...
Click to collapse
I backup everything to reduce the amount of steps for the restore process. If you check every box during the backup process you do not have to Flash the OS during restore. Yes it does take up more space but the restore process is simple if you do. By checking every box all you have to do is restore your backup and then Flash magisk and you're done no need to flash the OS
dgunn said:
I backup everything to reduce the amount of steps for the restore process. If you check every box during the backup process you do not have to Flash the OS during restore. Yes it does take up more space but the restore process is simple if you do. By checking every box all you have to do is restore your backup and then Flash magisk and you're done no need to flash the OS
Click to expand...
Click to collapse
Ahh good to know mate
Thanks.
Regards ysco..
dgunn said:
I backup everything to reduce the amount of steps for the restore process. If you check every box during the backup process you do not have to Flash the OS during restore. Yes it does take up more space but the restore process is simple if you do. By checking every box all you have to do is restore your backup and then Flash magisk and you're done no need to flash the OS
Click to expand...
Click to collapse
Actually you don't have to make a backup of system AND system image as well as you usually don't buy apples AND apples and pears. You just need the system image (and boot, vendor, data) to perform a complete and success backup.
dgunn said:
UPDATE: I have since updated to official 5.1.6 via OTA flashed TWRP and Magisk. The backup finished successfully with no sign of 255 error and once rebooted the USER ID and all 999 folders were still gone after the update and switched slots.
Only tested on OnePlus 6 but file structure should be the same on any device running Android O. Must be rooted to grant Terminal Emulator root permission. You cannot remove a user without root.
If anyone has had the 255 error while trying to create a backup file or trying to restore with TWRP. This error pertains to the parallel apps or multi user ID. If you are not sure if you have parallel apps running on your OnePlus 6 or other devices you can do a quick check by go into your Root browser and look in these locations.
/storage/emulated
/data/system/
data/system_ce/
data/system_de/
data/misc/
data/misc_ce/
data/misc_de/
data/user/
data/user_ce/
data/user_de/
If you see any folder named 999 then you have parallel apps enabled on your device. TWRP in it's current form will not allow you to create a backup or restore a backup with parallel apps enabled.
Currently there is only one solution that I have found to be able to delete all of the 999 folders and that is to open a terminal emulator to each of these locations and remove the 999 folders individually. I have found a solution where you can delete the user ID and by doing so it removes all of the 999 folders and not only does it remove the folders they do not return once you reboot your device. The solution is simple so let's get to it.
Install Terminal Emulator from the play store
Open Terminal and type
su
Press enter and grant root permission
Next type
pm remove-user 999
Press enter
Close Terminal and reboot
Once rebooted go back to your Root browser and check the locations listed above to ensure the 999 folders are gone. That's all, Enjoy.
Click to expand...
Click to collapse
I don't have parallel apps or multi-user. What I have is a "work profile" (latest feature by gsuite which is mandated by my organization). Work profiles isolate work/company account data into a separate encrypted/remote wipable silo. Android creates copies of the apps for the work profile. This is causing a folder called "/data/system_ce/10" which is failing to backup. Any solution for TWRP to work with work profiles? Ideally, can I "ignore" folders to not be backed up so that TWRP nandroid backups can work.
angadsingh said:
I don't have parallel apps or multi-user. What I have is a "work profile" (latest feature by gsuite which is mandated by my organization). Work profiles isolate work/company account data into a separate encrypted/remote wipable silo. Android creates copies of the apps for the work profile. This is causing a folder called "/data/system_ce/10" which is failing to backup. Any solution for TWRP to work with work profiles? Ideally, can I "ignore" folders to not be backed up so that TWRP nandroid backups can work.
Click to expand...
Click to collapse
You will have to remove those folders from the system before you can do a backup. Maybe cut and paste them onto an OTG drive, do the backup and then replace the folders. Twrp will not backup any multi-user accounts and that is exactly what gsuite has made.
See here for more info similar to your issue.
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page56
Hello. Can you tell me how to properly restore a backup on TWRP? Do I have to change slots oraz something?
Restore does not work ...
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
Thank you,
Peter
Hi, I'm restoring from a nandroid backup but once it starts restoring data it fails with error 255. I have no 999 files, and ran the steps here: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632 to remove 999 folders (it didn't work but I looked in those folders and saw no 999 folders) and have NEVER used Paralell Apps.
Is the backup salvageable?
NateDev said:
Hi, I'm restoring from a nandroid backup but once it starts restoring data it fails with error 255. I have no 999 files, and ran the steps here: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632 to remove 999 folders (it didn't work but I looked in those folders and saw no 999 folders) and have NEVER used Paralell Apps.
Is the backup salvageable?
Click to expand...
Click to collapse
Can you still boot into your OS?
mikex8593 said:
Can you still boot into your OS?
Click to expand...
Click to collapse
No, because I was on the P beta, but wiped everything including system. I tested a restore with everything else except data and it worked, just data failes, and recovery.log says "==> extracting: //data/reserve-lib/com.oneplus.soundrecorder/ (mode 40755, directory)
tar_extract_file(): failed to extract //data/reserve-lib/com.oneplus.soundrecorder/ !!!" so I'm assuming that's the issue, but I don't think there's any way to edit nandroid backup files like a filesystem, is there?
Edit: So I made the data backup into a .tar file and I can see the offending folder, but can't delete it from within WinRar, but I can make it a folder and delete it. Once I have that, how do I make it back into a .win000 file?
NateDev said:
No, because I was on the P beta, but wiped everything including system. I tested a restore with everything else except data and it worked, just data failes, and recovery.log says "==> extracting: //data/reserve-lib/com.oneplus.soundrecorder/ (mode 40755, directory)
tar_extract_file(): failed to extract //data/reserve-lib/com.oneplus.soundrecorder/ !!!" so I'm assuming that's the issue, but I don't think there's any way to edit nandroid backup files like a filesystem, is there?
Edit: So I made the data backup into a .tar file and I can see the offending folder, but can't delete it from within WinRar, but I can make it a folder and delete it. Once I have that, how do I make it back into a .win000 file?
Click to expand...
Click to collapse
I think you may be able to just rename .tar to .win000, try it and see.
JazzieBoi said:
I think you may be able to just rename .tar to .win000, try it and see.
Click to expand...
Click to collapse
Yea I editited it saying I did that, but can't figure out how to make it back into .win000. I guess I will just transfer it onto the phone, backup that and then restore (as just transfering will probably mess something up)
i'm having hte same problem , i never used parallel apps and i'm getting the same error on a restore for no freaking reason!
I need to restore so badly, i can get into OS just fine now but i didn't backup my apps prior to doing the wipe after the backup.. any ideas please?
NateDev said:
Yea I editited it saying I did that, but can't figure out how to make it back into .win000. I guess I will just transfer it onto the phone, backup that and then restore (as just transfering will probably mess something up)
Click to expand...
Click to collapse
Did you get this working? I'm not very good with TWRP yet so I don't know all the lingo, but I too made a backup and receive the error 255 when trying to restore using TWRP. When I restored the backup and unchecked data like you mentioned, it finishes without error but get this error "Your device is corrupt. It can’t be trusted and may not work properly" when I try to boot it. Restoring the backup without the data box checked still doesn't restore everything obviously. I'd like to restore the data too. Did you get it all working to where you can restore all?
R0ttenB4ndit said:
Did you get this working? I'm not very good with TWRP yet so I don't know all the lingo, but I too made a backup and receive the error 255 when trying to restore using TWRP. When I restored the backup and unchecked data like you mentioned, it finishes without error but get this error "Your device is corrupt. It can’t be trusted and may not work properly" when I try to boot it. Restoring the backup without the data box checked still doesn't restore everything obviously. I'd like to restore the data too. Did you get it all working to where you can restore all?
Click to expand...
Click to collapse
So I edited the backup and removed the offending files and then put the file back into the backup but that didn't work because I guess it broke the signature or something but it wouldn't restore data at all once I edited it. Idk.
I just don't bother with backups anymore, too much of a hassle haha, and it makes no sense why it fails, since I have no parallel apps or anything
Thanks very much for the response and info! No backup at all? Bummer. I've tried to backup several times using twrp and keep asking around. In the root directions it's said how to backup and restore. Surely it's been done in this os since instructions are there.
The second time I tried, I was able to backup and restore all partitions "successfully" using the newest bluespark twrp version from a couple days ago... But I get this boot issue saying the device can't be trusted and doesn't boot.
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.