Related
I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Pro4TLZZ said:
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Click to expand...
Click to collapse
What was corrupt? How did you fix it?
keeganjk said:
What was corrupt? How did you fix it?
Click to expand...
Click to collapse
Something in the partition, so I didn't restore that
Pro4TLZZ said:
Something in the partition, so I didn't restore that
Click to expand...
Click to collapse
Which partition? I just wiped my device and reinstalled FreedomOS.
keeganjk said:
Which partition? I just wiped my device and reinstalled FreedomOS.
Click to expand...
Click to collapse
Userdata partition
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
OK.
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
keeganjk said:
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
Click to expand...
Click to collapse
I'm sorry I can't help you more
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
I just wiped and reinstalled OxygenOS http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.10/. Once I reconfigure all my settings, files, etc, I'm going to see if it works.
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
What's the difference between TWRP and bluspark TWRP?
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
I can't restore; I deleted all my backups in an attempt to free up space.
I think I found the solution!
1. Go to Wipe in TWRP, swipe to factory reset
2. Download:
OnePlus Recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
OxygenOS: http://oxygenos.oneplus.net.s3.amaz...3_OTA_015_all_1708252353_e6d7756780064352.zip
3. Rename recovery image as recovery.img, boot phone into fastboot, plug into computer, run these commands on the computer:
fastboot devices
fastboot flash recovery recovery.img
fastboot boot recovery.img
4. Open recovery on phone
5. Select Forgot Password, will wipe all leftover files in SD Card.
6. Boot back into recovery, select reload, select Install over ADB or Install Over USB or something similar and plug phone into computer.
7. Run 'adb sideload oxygen-os-filename' without quotes on computer.
8. Let it install OxygenOS, it may appear to be frozen at some points; it probobaly isn't, so don't shut it off or unplus USB.
9. Download Bluspark TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=26601&task=get
9. Reboot into fastboot, plug into computer and run these commands on the computer:
fastboot devices
fastboot flash recovery bluspark-twrp-filename-location.img
fastboot boot bluspark-twrp-filename-location.img
10. Success (hopefully)
Oh. Wait. Now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?
the solution to this was to boot to your previous rom that u have made nandroid backup with and then setting up the same password/pin in settings > security. When you then boot into twrp it will ask you for the pin/password to decrypt your data partition and then you can flash the nandroid backup(you have to have the same password there). here it is obvious that you are trying to flash data partition that uses different encryption password (in case of stock rom there is non) and this obviously wont happen.
maybe another solution would be to connect externally usb and unmounting data partition and then restoring from usb...
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Need4Sneed said:
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Click to expand...
Click to collapse
For me flashing normal oxygenos with magisk 16 and formatting data and trying to make it boot with the new flash and then rebooting into recovery and restoring made it work. I guess it has to do with the right filesystem having to be made first.
hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.?
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.
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
First things first:
1. This is not a thread about how to flash ROMs, recoveries or use Android SDK and ABD or fastboot commands. If you have questions about the basics, please keep them in @Funk Wizard's excellent thread created for that purpose:
OnePlus 5T: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup & More !!
2. This thread is not the place to discuss the merits of encryption or decryption.
3. I'm not responsible for what you do to your own device. Read, think, read more, re-think, wipe, flash in that order.
4. This OP and the following posts will be updated as the discussion develops, so please check back here from time to time.
Now on to the discussion
There has been a lot of talk lately about encryption, decryption and the benefits and liabilities of each. Obviously having your device encrypted is a gain for security, something we should try to keep if possible. But encryption methods can vary, which is a problem for flashaholics like myself. When you flash a new ROM that cannot read the encryption of the previous ROM, /data must be formatted, causing the loss of /sdcard - pictures, music, files, etc.
Understanding the Problem
The issue seems to revolve around Qualcomm's "KeyMaster" encryption keys. While both Nougat and Oreo use FBE (File Based Encryption), by default they use different encryption keys, as pointed out by dev @codeworkx -- Nougat and Oreo 8.0 use KeyMaster 1 while Oreo 8.1 uses KeyMaster 3. So when an Oreo 8.1 ROM is flashed, it either can't access /data (requires decryption or formatting /data) or the ROM reformats /data itself, like early beta Lineage 15.1 builds. Likewise, reverting to a Nougat or Oreo 8.0 build will cause the same problem. Apparently, moving to KeyMaster 1 to 3 works (ie, flashing from OOS to Omni/Lineage) but reverting from Keymaster 3 back to 1 doesn't. When this happens, OOS can still decrypt with your PIN/password but TWRP can't.
One solution is to run unencyrpted, for which you may find threads in the How-To section. This discussion is about how to stay encrypted and flash back & forth between ROMs without loosing all of your data.
Links on the subject:
https://source.android.com/security/encryption/file-based
I look forward to your contribution to this discussion! :good:
Reserved
Just dropping this here:
mad-murdock said:
If only someone would be advanced in linux FBE, used tools and libraries. There surely is a way to remove encryption with a flashable .zip. _IF_ current TWRP has the needed tools onboard.
I hope one day we get encrypt/decrypt options in TWRP - where it belongs.
Click to expand...
Click to collapse
Yes, NOW I have seen this thread. Thanks for mentioning.
Seems useful.
After a bit of google kicking, I found this: https://source.android.com/security/encryption/file-based
Seems a good start on the topic. Maybe add it to a list of (hopefully growing) links?
Wow. Seems like this didn't work out that well.
mad-murdock said:
Wow. Seems like this didn't work out that well.
Click to expand...
Click to collapse
1. Rather than understand and deal with it, lots of people decrypt.
2. The issue hasn't gone away. Give it time.
Great information to those who recently owned an OP even if they have knowledge how to flash ROMs. (Including me)
Thanks!
I've stumbled across another issue for investigation. While experimenting yesterday, I discovered that @codeworkx TWRP 3.2.1-0 for Oreo (8.0 and 8.1) is able to read stock OOS/OOS B1 encryption until it is backed up in TWRP, an Oreo 8.1 ROM is flashed (eg, Omni, Lineage), and OOS is restored. After that, TWRP cannot decrypt /data with the correct PIN/password of the restored OOS ROM or "default_password". It doesn't matter if the nandroid was taken with or without a PIN/password, if the PIN/password is removed from the Oreo 8.1 ROM before restoring the nandroid, etc. Codeworkx suspects it has to do with how the passwords are being stored between 8.0 and 8.1.
And before you ask, I never formatted /data or decrypted & re-encrypted. The contents of /sdcard survived every flash and nandroid restore. Every ROM flashed was able to access /data with the correct PIN/password including the restored OOS. Only TWRP can't read /data with the correct password.
Also, I've left recovery systemless. That means my nandroid backups are only of data, and I restore by flashing the stock OOS ROM and only restoring the data nandroid. So zero changes have been made to system.
the Doctor said:
I've stumbled across another issue for investigation. While experimenting yesterday, I discovered that @codeworkx TWRP 3.2.1-0 for Oreo (8.0 and 8.1) is able to read stock OOS/OOS B1 encryption until it is backed up in TWRP, an Oreo 8.1 ROM is flashed (eg, Omni, Lineage), and OOS is restored. After that, TWRP cannot decrypt /data with the correct PIN/password of the restored OOS ROM or "default_password". It doesn't matter if the nandroid was taken with or without a PIN/password, if the PIN/password is removed from the Oreo 8.1 ROM before restoring the nandroid, etc. Codeworkx suspects it has to do with how the passwords are being stored between 8.0 and 8.1.
And before you ask, I never formatted /data or decrypted & re-encrypted. The contents of /sdcard survived every flash and nandroid restore. Every ROM flashed was able to access /data with the correct PIN/password including the restored OOS. Only TWRP can't read /data with the correct password.
Also, I've left recovery systemless. That means my nandroid backups are only of data, and I restore by flashing the stock OOS ROM and only restoring the data nandroid. So zero changes have been made to system.
Click to expand...
Click to collapse
""And before you ask, I never formatted /data or decrypted & re-encrypted. The contents of /sdcard survived every flash and nandroid restore. Every ROM flashed was able to access /data with the correct PIN/password including the restored OOS. Only TWRP can't read /data with the correct password""
So Do you mean to say I can revert back to OOS OB-1 by flashing it over Omni/LOS/etc via TWRP without formatting Data, and later on restoring Nandroid data of OOS OB-1.
shail139 said:
""And before you ask, I never formatted /data or decrypted & re-encrypted. The contents of /sdcard survived every flash and nandroid restore. Every ROM flashed was able to access /data with the correct PIN/password including the restored OOS. Only TWRP can't read /data with the correct password""
So Do you mean to say I can revert back to OOS OB-1 by flashing it over Omni/LOS/etc via TWRP without formatting Data, and later on restoring Nandroid data of OOS OB-1.
Click to expand...
Click to collapse
Yes, but obviously TWRP would not be able to decrypt with a PIN/password set by OOS. That just means you would have to disable lockscreen protection in the ROM before going into TWRP.
the Doctor said:
Yes, but obviously TWRP would not be able to decrypt with a PIN/password set by OOS. That just means you would have to disable lockscreen protection in the ROM before going into TWRP.
Click to expand...
Click to collapse
By that way the steps to restore should be...
1. Backup of OOS OB-1 in TWRP should be taken post removal all securities PIN/PASSWORD/etc (On external drive/OTG)
2. Flash OOS OB-1 normally, clean flash, boot to system, no security should be set
3. Boot to TWRP, restore OOS OB-1 Backup Only "Data" should be checked via OTG drive
4. Reboot to system
"twrp-3.2.1-0-universal-codeworkx-dumpling" will be the TWRP to be used
Correct me if I am wrong in steps
so in this case, am i right to say that, so long i dont do nandroid restore, i wouldnt have problem with encryption/decryption regardless of what rom i'm flashing using codeworkx's universal TWRP?
usually i always clean flash new roms and i'm ok to go through the 'hassle' of reinstalling stuffs. if i want to go back to the previous rom, i'll just do a clean flash of the previous rom instead of reverting back via nandroid.
so technically so long i'm on the right TWRP, i'm fine with switching roms am i right?
thanks for sharing the findings as well!
gorillaCF said:
so in this case, am i right to say that, so long i dont do nandroid restore, i wouldnt have problem with encryption/decryption regardless of what rom i'm flashing using codeworkx's universal TWRP?
usually i always clean flash new roms and i'm ok to go through the 'hassle' of reinstalling stuffs. if i want to go back to the previous rom, i'll just do a clean flash of the previous rom instead of reverting back via nandroid.
so technically so long i'm on the right TWRP, i'm fine with switching roms am i right?
thanks for sharing the findings as well!
Click to expand...
Click to collapse
I tried a clean flash of OOS from TWRP as well, but even that didn't work. I think you'd have to restore factory encryption per this guide to get TWRP to be able to decrypt OOS again:
[How To] Revert to 100% stock OOS from Oreo 8.1 | Restore factory encryption
Again, you can flash, backup and restore in TWRP even if you don't. It just won't be able to decrypt /data with your OOS PIN/password, so you'd have to remove lockscreen security first.
the Doctor said:
I tried a clean flash of OOS from TWRP as well, but even that didn't work. I think you'd have to restore factory encryption per this guide to get TWRP to be able to decrypt OOS again:
[How To] Revert to 100% stock OOS from Oreo 8.1 | Restore factory encryption
Again, you can flash, backup and restore in TWRP even if you don't. It just won't be able to decrypt /data with your OOS PIN/password, so you'd have to remove lockscreen security first.
Click to expand...
Click to collapse
Formating /data is the only way to go back to 8.0 crypto (after booting fully stock) and then you can use you Nandroids from OOS to restore /data with PIN, face unlock all ON.
Been there, done that from 8.1 custom to OOS N.
Didn't use stock recovery, didn't use revert builds, there actually were none at the time, but I think they are unneeded anyway.
It's a cumbersome process because backing up internal storage and restoring it is a pain when you have a lot of data to carry around.
But it's pretty straight forward.
All this done on blu_spark TWRP.
The problem I noted above wasn't that OOS couldn't read or encrypt /data properly after the nandroid backup--TWRP couldn't read OOS's PIN/password. I had no problems restoring and running OOS after running Omni/Lineage. After I restored OOS, on first boot I entered the PIN and found that my fingerprints and face unlock still worked. But when I booted back into Codeworkx TWRP neither the PIN or "default_password" worked. I didn't try Blu_Spark.
IMO, what we ultimately want is an official TWRP that can decrypt without workarounds so we can avoid the cumbersome process or formatting /data and moving everything back to /sdcard.
Edit: Here is the exact sequence of what happened:
I came from OOS OB1 with /data formatted by the stock recovery, encrypted, with PIN/fingerprints/face unlock.
I booted Codeworkx recovery, entered the PIN, it decrypted properly, I did a nandroid backup of the Data partition.
Still in recovery, I wiped Dalvik-Art/Cache/System/Data, then flashed Omni, gapps, Magisk.
I ran Omni for a while, moved to Lineage using the same process as above. I never removed the PIN, and Codeworkx TWRP had no problems decrypting with it in Omni or Lineage.
After running Lineage for a while, I went back into Codeworkx TWRP, decrypted with my PIN (it worked), wiped as above, flashed OOS OB1 with the factory zip, wiped the Data partition, restored Data from nandroid, flashed Magisk, rebooted.
On first boot OOS asked for a PIN. I entered my PIN and found my fingerprints & face unlock still working.
VVV HERE IS THE PROBLEM STARTED VVV
When I booted back into Codeworkx TWRP it could not decrypt with my PIN. I booted back into OOS and removed my PIN, set lockscreen protection to "None". TWRP still could not decrypt /data. I tried "default_password" but no dice.
Revert back to Omni, remove PIN, reboot TWRP, still can't decrypt.
So something changed between when I restored OOS OB1 (TWRP could decrypt with the PIN) and after first boot (TWRP couldn't decrypt with the PIN). Also, why could TWRP decrypt with OOS OB1's PIN to do the nandroid backup from a clean flash and to restore the same backup after being on Omni/Lineage, but couldn't decrypt with it after the first boot of the OOS nandroid backup?
Again, formatting /data again is not an acceptable workaround. I think we want to understand what changed and solve the problem.
the Doctor said:
Again, formatting /data again is not an acceptable workaround. I think we want to understand what changed and solve the problem.
Click to expand...
Click to collapse
The mentioned /data format is not a workaround per se, it's the only working workflow to get things going once you find the need to get back to OOS for the time being.
Accepting that is part of the process!
Users should know this upfront so they don't find out the hard way.
I'm currently running OxygenOS 5.0.3 and my understanding is that it uses Keymaster1. If I'm now upgrading to LineageOS 15.1 it'd change to Keymaster3 but without the need of formatting.
However, if I'd want to revert to OxygenOS 5.0.3 with Keymaster1 I would have to format /data. Is my understanding correct?
Macusercom said:
I'm currently running OxygenOS 5.0.3 and my understanding is that it uses Keymaster1. If I'm now upgrading to LineageOS 15.1 it'd change to Keymaster3 but without the need of formatting.
However, if I'd want to revert to OxygenOS 5.0.3 with Keymaster1 I would have to format /data. Is my understanding correct?
Click to expand...
Click to collapse
My experience has been that the ROM can decrypt without any issues, but TWRP can't decrypt without formatting /data with the stock recovery.
the Doctor said:
My experience has been that the ROM can decrypt without any issues, but TWRP can't decrypt without formatting /data with the stock recovery.
Click to expand...
Click to collapse
As previous posters have alluded to, use "twrp-3.2.1-0-universal-codeworkx-dumpling.img". This is able to decrypt 5.0.3.
wunderdrug said:
As previous posters have alluded to, use "twrp-3.2.1-0-universal-codeworkx-dumpling.img". This is able to decrypt 5.0.3.
Click to expand...
Click to collapse
Right. Flash Omni or Lineage, then go back OOS and try it again as Macusercom says in the post I quoted.
[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?
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
I got the same problem... I did't find the solution. Can someone help ?
k1n9n0th1n9 said:
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
Click to expand...
Click to collapse
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Pupet_Master said:
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Click to expand...
Click to collapse
hi, I had this, try doing the partitions separate, I did data afterwards following a reboot.
Try OrangeFox-R10.0_8-Stable-davinci recovery.
flamedrops said:
Try OrangeFox-R10.0_8-Stable-davinci recovery.
Click to expand...
Click to collapse
Orange fox atm is the worse and most buggy recovery for K20
Pupet_Master said:
Orange fox atm is the worse and most buggy recovery for K20
Click to expand...
Click to collapse
even the latest one?
flamedrops said:
even the latest one?
Click to expand...
Click to collapse
Yeap, it is still in it's infancy, where other TWRPs solved some issues that even the latest OF still has
I have just made a new backup after restore from Titanium Backup, but after flash new firmware and test some new roms, some of apps were crushing after restore and must be installed and configured one again.