Because it’s not officially endorsed by twrp, but “only” some version. FP would have to go through some steps to have it declared official
A question - probably a stupid one. I backed up with TWRP for the first time today - never know when it might come in useful. I found the backup folder with Amaze afterwards, and copied it to my SD card (which involved choosing root directory to grand write access - I followed the instructions the phone gave me - hope it wasn’t a mistake). Does this make any sense? Would it make sense to save a copy to my computer (in case I lose or break my phone)? How is this usually done (I suppose there is a simpler solution than copying stuff several times)?
It does make sense to store the backup to the SD card and to the computer also.
Before you make a backup with TWRP you can choose the backup location (internal/externalSD).
If you move the backup afterwards you could run into troubles when you want to restore again.
Got it - I hadn’t realized that I could change the destination for the backup. Thank you!
PS Can I delete the first backup and its copy now? By simply deleting the “backup” folder?
Does anyone else have problems using ADB in TWRP?
I just stumbled over this today. ADB works fine when running FPOOS. Then I went into TWRP. ADB devices finds the phone, but the computer suddenly does not have authorization to use ADB. After booting again into the OS, ADB works again as just fine.
So apparently I have no authorization to use ADB in TWRP, while it works fine in the OS.
Is it necessary to give an extra ADB authorization within TWRP?
The same here a few days ago:
No possibility to use e.g. ADB shell with TWRP. I wanted to modify some system files to gain write access on my external sd card (I finally tried it on the running OS and it fortunately worked).
I also got the message that an authorization is required. I wasn’t sure, but thought, that this should have been working some months ago.
My phone is encrypted and with FP Open OS 16.08 on it in comparison to the status a few months ago, where it wasn’t encrypted and ran an older version of the OS. Maybe one of this changes is the cause for it.
I then played around with some options and after activation of ADB sideload in TWRP at least this seemed to work. But I haven’t done more testing on it.
I also noticed that TWRP seems to forget settings everytime. It e.g. always asks if I want write access to the system partition and even if I choose “never ask again” it asks on every start of TWRP. And there is more: It also forgets other settings like vibration when typing, timezone, etc.
In the meantime I would also assume that the authorization problem is related to the encryption of /data, maybe also your other problems.
@Johannes pointed out this possibility. Looking at another post from him, where he describes the location of the authorization file, this also makes sense: The file is apparently stored somewhere in /data:
Unfortunately the version or the modification of TWRP which Fairphone uses cannot handle encrypted /data partitions (see also @lklaus’ post above) , which is very very annoying and significantly reduces the usefulness of TWRP. Actually it renders it rather pointless. Particularly that you can’t use ADB, as usually using ADB in recovery is an important way for troubleshooting.
Edit: @paulakreuzer, maybe this info can be added to the first post: The Fairphone port of TWRP that ships with Open OS is not able to deal with encrypted devices, which makes it impossible to make system backpups, and apparently also to use ADB in recovery.
3 Likes
Quite some time ago I also said, that TWRP needs working support for decryption ot /data in order to be better than e.g. my current ks01lte device, which also suffers from a working decryption of /data :-/.
I have a problem with TWRP which has to do with encryption. I’m using the exposed framework on my phone (especially for Xprivacy). Now, after every update I need to flash the framework again. Since the last update, however, I encrypted my phone and as you probably will expect (I hadn’t thought about that) I cannot flash any files on my phone anymore. Do you know if there is any other possibility to flash the framework (maybe outside TWRP)?
It should still be possible to install it via TWRP, but you need to have the files on a SD-card, and not on the internal memory.
I am actually considering to try installing stock recovery, since with TWRP on an encrypted device you can’t even ADB sideload. As sad as is sounds, but currently the stock recovery has more advantages on an encrypted device than TWRP (can’t believe I have to say that).
I already moved the files to my SD, yet it still doesn’t work (I can start the installation/flashing process this way, but it fails). I guess it’s because the data directory where the files have to be moved to is encrypted.
It basically should work, because the files are written to the /system partition, and not /data partition (which is the encrypted one). I have installed these files (openGAPPS, xposed) several times on an encrypted Open OS, so basically, it should work.
I tried again and now it worked! Maybe because I unchecked the box with “verify zip” or something along these lines in the window where you confirm flashing by wiping the screen? Never had to do this before, but maybe this is what was needed. Thanks for your help!
For all those people who don’t have a SD-card: You can also push the XPosed zip to e.g. /system and then flash it from there. Though you then have to mount the system partition in TWRP before.
The procedure to push to the system partition is a bit more complicated. Connect your phone to the PC via USB and allow root access for adb. Then execute the following commands in a terminal:
$ adb push xposed-v86-sdk22-arm.zip /sdcard/
$ adb shell
$ su
# mount -o remount,rw /system
# mv /sdcard/xposed-v86-sdk22-arm.zip /system/
# mount -o remount,ro /system
# exit
$ exit
1 Like
yes, you can delete the old backup folder if you made a new backup on the sd card
Adding to that:
On an encrypted device it is not even possible to make a hard reset for the same reason: the recovery cannot access /data.
In the meantime I came to the conclusion that TWRP with the current port/version is completely useless on an encrypted device and more a pain in the ass than anything useful!
- no ADB access
- no hard reset possible
- no backups possible
As sad as it is, but the Android stock recovery offers more functionality in particular in regard to troubleshooting.
2 Likes
That’s indeed pretty bad, let’s hope during the CM-port progress there will also be some work in the future on TWRP and decryption support for /data.
Unfortunately I did not take a look into the forum before encrypt my FP2 device.
Can someone shortly explain (or post a link if it is already described somewhere) the options I have now? (e.g. how to switch to stock recovery)
Especially before updating the phone I like to have a full current backup … I normally
create it via TWRP. In addition I used a USB stick (/USB-OTG) as backup target in
the past (Nexus 5 - CM 12 - TWRP). It looks like that this is not possible with
the FP TWRP version as well. :-/
Thanks for any recommendation in advance.
There are some apps (like nandroid backup), which can create those backups from the running ROM. So you could restore that on an unencrypted (new) phone. At least in theory,i didn’t test it…