I haven’t found out whether a Oneplus3T is one-side or double-side. I am though contemplating following a fresh install procedure with full data wipe like here : https://doc.e.foundation/devices/oneplus3/install
I am not seeing why this abnormal behaviour appeared and why the dirty flash bettered anything
Hi, thanks for the following up !
I’m afraid that I no longer know which version was I using… I installed first the 0.13 but now the 0.16 is downloadable and I recall a major update I did a couple of onths ago…
I am now roaming forums in order to be sure to what extent data are backed up with a TWRP backup : namely concerning data associated with apps, contacts, sms etc…
Happy you’ve kinda brought your device back to /e/
But I can’t understand why your backup leads to boot-looping
About partial restore from TWRP : yes, but it’s not easy …
Anyway I’m afraid that your apps are gone for now
I’ll try to :
reinstall some apps with their defaults
take a TWRP backup of “working” Data partition
with TWRP restore “bad” Data
tar some directories (the list is to be established), store tar file outside of Data
restore back “working” Data
untar backups
cross everything, reboot to system …
For tar files storage you could use /data/media (mount it first), as this is a different filesystem .
For example (assuming you created the directory) /data/media/0/Backups/
I think we may also extract files directly from TWRP backup files using Windows + WinRAR …
One could also try to escape the painful owner & permissions steps, having them set while restoring the directory
Let’s try with tar !
First, extract data.ext4 file within Windows, using WinRAR (if splitted archive, choose the right one).
Note about splitted archive : search recovery.log file for “data.ext4”
What happened here ?
We could extract our directory, however TWRP archive has been made with leading / and a relocation path (/data instead of /data/data), and ToyBox tar doesn’t support relocation using -C option (at least on my TWRP, may vary).
So files get extracted using the path stored in archive, and we had to move the directory to it’s correct place.
Note that owners & permissions have been restored !
Don’t forget to delete archive file, once all restores done
Thank you so much for your didactic reply ! It’s on point as I was orienting myself more towards the Win10 + Winrar solution than Linux+cmd lines (Im having trouble with my Ubuntu partitions also haha)
An idea came to my mind : the battery died while I was using the NewPipe app (Youtube client). What if a corrupted file on the app directory created the bug ? Could deleting the directory virtually solve at once this bug ?
About your idea : I feel really sorry, I should come first with a fsck of Data partition
I’ve never seen a Data partition filesystem getting corrupted, but of course that can happen.
A delete might not have solved the problem, but a check would definitively have worth a try !
get mounted devices path : /data is /dev/block/dm-0 (also mounted on /sdcard)
unmounted twice (/data and /sdcard)
check : ok ! Let’s run e2fsck :
a. -c stands for “check for bad blocks”
b. -f to use the Force
c. -v to get some info
d. -z is useless, no e2undo provided by my TWRP …
why not ?
bullhead mode
Rebooted into System after that, everything ok
You can also use something like e2fsck -n -f /dev/... to dry run (help with e2fsck --help).
Sure thing ! I did not manage to find the DM feature in this forum though, if there is one…
I can edit this post adding temporarily my personal email if you want ?