Related
I found these lines on the AOSP website regarding the Lollipop encryption system:
Created fast encryption, which only encrypts used blocks on the data partition to avoid first boot taking a long time.
Click to expand...
Click to collapse
And this:
To enable inplace encryption, vold starts a loop to read each sector of the real block device and then write it to the crypto block device. vold checks to see if a sector is in use before reading and writing it, which makes encryption much faster on a new device that has little to no data.
Click to expand...
Click to collapse
To me, it seems like Google has made a disturbing choice to force encryption users on Lollipop to use "fast encryption", which only encrypts new data added to the phone, but not the free space, which on a previously unencrypted phone would contain recoverable private information. I see a lot of websites recommending an "encrypt and wipe" procedure before selling an old phone; Google's new policy regarding fast encryption has apparently made this procedure nothing more than placebo. I believe Kitkat and earlier had the option to disable Fast Encryption, but it seems like Google has made it impossible to encrypt previously deleted unencrypted information, which seems like a massive security risk to me.
I tried encrypting a factory-resetted Lollipop device, which took all of roughly 20 seconds, which really shows how little of the storage space Lollipop is encrypting. Everything on the previously wiped OS is completely unencrypted and freely available to anyone who can get their hands on the phone. Is there a way to mitigate this security risk (a reliable tool to zero-fill the free space, but none of the options on Google Play seem legitimate), or maybe force full-disk encryption instead of fast encryption?
Hey folks,
I use the latest unofficial CM13 build for onyx with running exposed modules, working gravityBox etc. –
I wanted to tweak onyx's way oversaturated display-colors via blu_spark kernel.
But unfortunately I can't find it in the twrp-filebrowser. Almost everything is empty.
Installing from TWRP-Manager also doesn't work, since I get the message after rebooting "can't find the file".
I am using a SD card with Marshmallows Merging feature (although still wondering how I can control what goes where)
I don't remember since when I cannot see find my "Downloads" folder in TWRP. But I guess since then another problem occured:
GMail says "unknown issue with google play services".
Maybe these two are corralated.
Please help me, fellow Android lovers
Thx,
Louis
The "adopted storage" feature fully encrypts your SD card. TWRP cannot access encrypted storage devices.
Thx for the info!
Is there any way I can decrypt the adopted SD for TWRP? Or how can I control where my data is stored, so I can find the files in TWRP and install st uff? I mean, there must be a way to influence where apps are installed and files stored.
Thx so much! ?
Hello,
I recently acquired a Sony Z5C, planning on switching to LineageOS sooner or later, but the android tweking world is way more complex than I initially imagined. I am mostly concerned about privacy and control but there is so much to go through I am completely lost. I thought it was all about running either Sony's rom or the lineageos rom but there seems to be a lot more to take into account.
What I am looking for:
getting rid of Sony's annoying bloatware
getting rid of Google Play Services
automatic or semi automatic security updates
fine tuning of application permissions (including ability to deny specific apps access to, say, my location, contact list, camera, internet, sms, without the apps noticing they have been denied access in the first place)
ads and trackers blocking (for instance global or per-application blacklisting of known "evil" domains)
being able to restore everything as it was when I purchased the phone
f-droid begin able to download and install updates without manual intervention
as little side effects as possible resulting from the deletion of the Google Play Services
Icing on the cake:
no loss in camera quality (I read somewhere it is sometimes possible to use image-enhancing algorithms despite having deleted the required DRM keys)
no loss in gps accuracy
same battery life (or better)
encompassing all data traffic of specific apps through tor or another technology preserving distant services from identifying me and my mobile network operator from knowing I access said services
Questions:
What is the difference between opengapps and microg? How does it relate with lineage? At which point in the installation process is it involved?
What are the consequences of rooting the device?
What is the purpose of so called "Magisk"? I read it "changes everything" but I have no idea what "everythin" was. As far as I understand, it is useful to fake a genuine configuration that have not been tempered with in order to use Google Pay or some games. I do not seem to care about that: should I? Is there more to know?
Most important question: in your opinion, considering the above points, the phone I have, current trends and hindsight, and your experience, what would be the best way to go? Should I follow the installation steps on the official lineageos page for the Z5C or do you think another option would suit me better?
To illustrate my technical knowledge: I have been a gnu/linux user for almost a decade but I am completely ignorant of the Android world and feel lost. In particular the concept of "root" and how user and system data is organized on the filesystem(s) (especially on Sony devices) seem different. I am willing to learn and get technical, but there is too much information and I do not know where to start with zero experience.
Thank you very much for your help.
I am in same situation. Did things like that for Moto and Samsung already, but I am new to Sony.
Key is to install TWRP. This is some kind of recovery where you can
- make a backup
- install LOS
- recall backups.
Once this is done:
- install root/su
- tingle the framework (to get microG running)
- install microG
- install afwall (firewall)
- install adaware
only than plugin a SIM and/or enable Wifi.
So: first thing is to install TWRP
unlock Bootloader:
To be able to unlock your Xperia Z5 Compact, prepare it by following these steps:
Go into Settings > About phone and tap seven times on Build number to enable developer options.
From Settings, go into Developer options and enable OEM unlocking.
Warning: Device protection features will not work on this device while this setting is turned on.Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialer and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
TWRP
https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952
A few words to your queston:
opengapps are not open source, they just add normal google apps to Custom Roms. With all pros and cons.
MicroG is offering some kind of api, so that most features can be used (notification, google maps, access to playstore).
They are installed after the custom rom. Some people don't install any of them, use FDroid as a store.
root gives you the chance to change settings, for a few advanced configurations it is required (or makes it easier): firewall, ad remove ...
No experience with magisk. It is another way of "rooting" it, gives more features (hide the root status) which is required for some games. Not needed it til now.
What seems to be missing from previous post is to backup your DRM keys since unlocking your bootloader means losing them FOREVER.
Regards,
Aeny
Aeny said:
What seems to be missing from previous post is to backup your DRM keys since unlocking your bootloader means losing them FOREVER.
Regards,
Aeny
Click to expand...
Click to collapse
Right, but didn't you need TWRP to make a backup. And that is on my list, first point. Or is it a special step to do?
Thank you for your help and valuable information which now raises even more questions
If I get things right TWRP is low level stuff that would allow me to backup and restore the system whenever I need to. Say for instance I just installed LOS and configured it as desired so I use TWRP to get a backup and if I later mess things up I can restore this backup without having to go through the whole installation and configuration process? How does the official LineageOS installation guide fit in all this, sould I follow it? Do I need to follow a completely different procedure? I am not planning to tinker anympre once everything has been set up, is TWRP only recommended for people who often experiment and change things or is it recommended for everyone?
The DRM keys are removed when unlocking the bootloader but since TWRP requires an unlocked bootloader they have to be backed up beforehand, am I right? Does it mean I can restore them afterwards once the bootloader has been unlocked without locking it up again? How can I back them up in the first place?
I cannot seem to picture how all the pieces fit together, which is low level stuff, which is high level. When you say "install microg", "install afwall", "install adaware", what are microg, afwall, adaware? Are they regular applications? Regular applications with root access? Low level modules? How is root managed in comparison with a gnu/linux system where I can either directly log as root, change user to root with "su", or get temporary privileges with "sudo"? When you say "install root/su", are we simply talking about installing the equivalent of "su" or "sudo" on a linux distribution? Is there a root password I shall input each time it is required or provide some applications root privileges through a configuration app? Is such an application to be installed separately?
Thank you for the clarification about opengapps/microg. I am interested in microg although I can give a try without in the beginning as long as it is still possible to install microg later.
fetchaspade said:
WRP only recommended for people who often experiment and change things or is it recommended for everyone?
Click to expand...
Click to collapse
Yes, highly recommended if not even required. All my LOS setups run via TWRP.
fetchaspade said:
The DRM keys are removed when unlocking the bootloader but since TWRP requires an unlocked bootloader they have to be backed up beforehand, am I right? Does it mean I can restore them afterwards once the bootloader has been unlocked without locking it up again? How can I back them up in the first place?
Click to expand...
Click to collapse
Good point. Don't know where do I need this DRM keys for, as I did't faced off this with other mobiles.
I think you have to make a backup of the TA partition:
https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597/
fetchaspade said:
I cannot seem to picture how all the pieces fit together, which is low level stuff, which is high level. When you say "install microg", "install afwall", "install adaware", what are microg, afwall, adaware? Are they regular applications? Regular applications with root access? Low level modules? How is root managed in comparison with a gnu/linux system where I can either directly log as root, change user to root with "su", or get temporary privileges with "sudo"? When you say "install root/su", are we simply talking about installing the equivalent of "su" or "sudo" on a linux distribution? Is there a root password I shall input each time it is required or provide some applications root privileges through a configuration app? Is such an application to be installed separately?
Click to expand...
Click to collapse
addsu is to flash via TWRP in same manner like LOS itself - as a zip. Others are regualar applications (installed like that) but required root privileges to work. No root password required. Once an app needs it it will ask you, and if you like it remembers you allowed it (so it will ask just once usually). Recommend to try this. You can't do much wrong if you create a backup
fetchaspade said:
Thank you for the clarification about opengapps/microg. I am interested in microg although I can give a try without in the beginning as long as it is still possible to install microg later.
Click to expand...
Click to collapse
MicroG is a bit more fiddling to install than gapps and seems to has limitations. There are separate threads for just this.
Just start, you will get a feeling for that all.
Edit: But
there is already a lineagos with microG built-in:
https://download.lineage.microg.org/suzuran/
Thank you starbright_
To recap, I am to unlock the bootloader, install TWRP, flash addsu via TWRP, flash lineage enhanced with microg, and I'm good to go.
I'm still stuck on the very first step: backing up the TA partition. If I'm not mistaken I need the TA backup tool which requires root access. Root access requires an unlocked bootloader (which would remove the TA partition and the DRM keys) or is achieved for a limited amount of time thanks to exploits. According to both https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597/ and https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388, it won't work on recent versions (7.1.1) so I need to downgrade. How can I do that? I imagine I need a tool to flash an old official rom: where am I to find an old official rom? How can I flash it without having an unlocked bootloader?
Backing up the TA partition really seems cumbersome. Is the loss of quality really noticeable on photos and videos? I find photos quite disappointing already and I fear it would get even worse.
On an unrelated topic, do you now of any way to backup SMS conversations as a simple file to import later on the same or different device? All I can find are applications that back up messages on a GMail account (no thanks) or any IMAP server (in what world is it simpler than an xml or simple text file ?).
Maybe you can translate this:
https://reraise.eu/2016/09/05/xperia-z5c-so-sicherst-du-die-ta-partition-teil-1
On an unrelated topic, do you now of any way to backup SMS conversations as a simple file to import later on the same or different device? All I can find are applications that back up messages on a GMail account (no thanks) or any IMAP server (in what world is it simpler than an xml or simple text file ?).
Click to expand...
Click to collapse
I'm using titanium backup for that.
(menu / backup data to xml)
@fetchaspade
Did you start your project? I would appreciate to take notes of your step. That's not only helping others, but also yourself once you have to do the steps again once.
After losing all the data of my internal storage twice, I am searching for a final solution of this disaster.
If I let the phone encrypt everything, am I facing the problem of accessing it through twrp again?
Sometimes I just forget to install the decryption patch after each update.
Often I saw twrp asking me for a pattern, after an unwanted encryption. I couldn't enter a code like 6363 by swiping. --> data lost!
Any advice would be really appreciated.
SilentEYE said:
After losing all the data of my internal storage twice, I am searching for a final solution of this disaster.
If I let the phone encrypt everything, am I facing the problem of accessing it through twrp again?
Sometimes I just forget to install the decryption patch after each update.
Often I saw twrp asking me for a pattern, after an unwanted encryption. I couldn't enter a code like 6363 by swiping. --> data lost!
Any advice would be really appreciated.
Click to expand...
Click to collapse
Fastboot and install the twrp with decryption support
Just rename it to recovery.zip before install
No need for passwords in twrp
FDE is optional when using this
https://www.androidfilehost.com/?w=files&flid=283470
pingufanpoy said:
Fastboot and install the twrp with decryption support
Just rename it to recovery.zip before install
No need for passwords in twrp
FDE is optional when using this
https://www.androidfilehost.com/?w=files&flid=283470
Click to expand...
Click to collapse
I already had installed twrp with encryption support.
After flashing havoc rom the system started encrypting my internal storage.
TWRP was asking for encryption password, but there was none, because it was a clean flash.
The first time my system got encrypted ( maybe even deleted) was after upgrading to vendor / firmware v10.
Gesendet von meinem Redmi Note 4 mit Tapatalk
You need to flash Force encryption disabler zip every time you upgrade ROMs because on Pie encryption gets enabled on boot. Even if you decrypt using TWRP, if you flash another ROM it will still encrypt on boot if you don't flash FED.zip. I learned this the hard way too
AntwnhsAnt said:
You need to flash Force encryption disabler zip every time you upgrade ROMs because on Pie encryption gets enabled on boot. Even if you decrypt using TWRP, if you flash another ROM it will still encrypt on boot if you don't flash FED.zip. I learned this the hard way too
Click to expand...
Click to collapse
Sorry, but I don't get it.
At its very first boot, LOS encrypted my unencrypted phone without asking me for the key.
So I think it just chose a key at random (or maybe even an hardcoded one: who knows?).
How can this even work with (any) update?
What if I need to reboot my device? Will it reboot? (I don't dare to even test it).
I also run LOS on another phone (OP3T) which has asked me the encryption key when I chose to encrypt it.
So I see two main oddities with this phone:
LOS is encrypting MY OWN phone without asking me permission to do so and
LOS is failing to tell me which encryption key it's using, thus acting more like a bitlocker than as a security feature.
And I need a way to chose my very own encryption key, anyway. How to?
Uqbar said:
Sorry, but I don't get it.
At its very first boot, LOS encrypted my unencrypted phone without asking me for the key.
So I think it just chose a key at random (or maybe even an hardcoded one: who knows?).
How can this even work with (any) update?
What if I need to reboot my device? Will it reboot? (I don't dare to even test it).
I also run LOS on another phone (OP3T) which has asked me the encryption key when I chose to encrypt it.
So I see two main oddities with this phone:
LOS is encrypting MY OWN phone without asking me permission to do so and
LOS is failing to tell me which encryption key it's using, thus acting more like a bitlocker than as a security feature.
And I need a way to chose my very own encryption key, anyway. How to?
Click to expand...
Click to collapse
Its not LOS its the vendor/firmware flashed, everytime you put a new/vendor firmwar it "force encrypts" your phone on first boot. So used "disable force encryption" if you dont want it. Its just how it is so stop whining about "final solutions" for a disaster. Theres no disaster spen 10$ on an sd card and move your pictures or whatever there even while encrypted you can (keep it portable) then theres no problem.
Mooatreides said:
Its not LOS its the vendor/firmware flashed, everytime you put a new/vendor firmwar it "force encrypts" your phone on first boot. So used "disable force encryption" if you dont want it. Its just how it is so stop whining about "final solutions" for a disaster. Theres no disaster spen 10$ on an sd card and move your pictures or whatever there even while encrypted you can (keep it portable) then theres no problem.
Click to expand...
Click to collapse
I surely haven't fully understood this encryption thing.
Mainly because on one phone, the OP3T, it was done by the OS itself upon my request with my encryption key.
While on another one, the POCO F1, is being done by something else, the so called "vendor software".
I was willing to have encryption on the POCO F1, it looks like I cannot have it. Bare truth.
With LOS v16 on an OP3T, if I reboot to TWRP recovery (or system) and don't provide the key I defined myself, I won't get access to the storage.
With LOS v16 on a POCO, I can reboot to TWRP recovery (or system) and have the storage decrypted by the " vendor software" without providing any key.
So, to my very limited understanding at least, POCO F1 doesn't have encryption unless you are trying to access the storage from the bootloader or from a device which has been turned off!
Or am I missing something very important?
P.S.
I don't see how a uSD card would save me. Can I enable user controlled encryption on an uSD?
LOS 17.1 is now available and developers say that LOS's own recovery is going to be the preferred recovery.
Last year Google announced that adb is very likely to be removed soon.
Those two statements brings up an important question: how can users create a full backup of their devices **without** having to root them in order to make backup apps work?
I am not talking about backing up pictures, media, calendars or address books, there are plenty of ways to do this without root access. I am talking about a full backup, including the whole system partition and user data. TWRP was an excellent tool for this job: a backup could be created any time, any where, completely independent whether a PC was near or not. You could even write the backup directly onto a USB storage, and the phone could always be restored as well any where and any time.
That is a feature that I miss very much in LOS's own recovery and to my opinion this is an issue that needs to be solved.
Will this feature be added to LOS recovery in the (near) future? Or are there any other solutions to do a full backup without the need for root access?
dvdram said:
LOS 17.1 is now available and developers say that LOS's own recovery is going to be the preferred recovery.
Last year Google announced that adb is very likely to be removed soon.
Those two statements brings up an important question: how can users create a full backup of their devices **without** having to root them in order to make backup apps work?
I am not talking about backing up pictures, media, calendars or address books, there are plenty of ways to do this without root access. I am talking about a full backup, including the whole system partition and user data. TWRP was an excellent tool for this job: a backup could be created any time, any where, completely independent whether a PC was near or not. You could even write the backup directly onto a USB storage, and the phone could always be restored as well any where and any time.
That is a feature that I miss very much in LOS's own recovery and to my opinion this is an issue that needs to be solved.
Will this feature be added to LOS recovery in the (near) future? Or are there any other solutions to do a full backup without the need for root access?
Click to expand...
Click to collapse
Making a complete system backup requires root and/or custom recovery, period.
That is he way it is, you can't change that. There are no alternatives.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Making a complete system backup requires root and/or custom recovery, period.
Click to expand...
Click to collapse
Pardon me, but that is a very harsh answer to a seriously asked question of common interest.
"We take security very seriously"...
Do you know where these words are written?
Maybe you'd like to try looking at this issue this way:
Many users who install LOS, are doing this because of security reasons. Imagine some of these users having bad luck and their phones get compromised by some bogus apps. And then they read an answer like this, telling them nothing different than: sorry, we can't and we won't help you!
And know imagine this:
Users can create snapshots or images of their running systems, with all of their apps included, as well as all necessary accounts, logins and passwords. When the "impossible thing" happens to a device running LOS, they have the option to restore the complete system without having to do a factory reset and without having to reinstall each and every app and the corresponding accounts.
What do you think, which one would please the users of your product more: an answer with an attitude like that one above, or the second possibility?
Furthermore: I was not bagging you to include this possibility. I was asking how this kind of back up could be made in the future, when TWRP won't work with Android 10, and when Google will remove adb. And frankly, I don't see why a recovery made by LOS should not be able to do a task that a third party recovery is capable of. If TWRP developers can put together such a piece of code, I am sure LOS developers should be able to do so as well.
Another possibility would be to reverse Google's decision and to keep adb.
So, from my perspective, there are at least two possible ways of dealing with this. But I am a user, not a developer, and I don't know if or why any one of these possibilities is a bad idea, or if there are really serious arguments against it, or whatever pro or con there might be. I simply don't know about these things and that's why I was asking about it. I am a user who doesn't like having to do a complete re-installation after a crash. And I am pretty sure that I am not the only user with this kind of antipathy.
A polite answer to the question would have included at least a glimpse of explanation why this and why not that.. And an open minded developer would have even cared to discuss about this.
dvdram said:
Pardon me, but that is a very harsh answer to a seriously asked question of common interest.
"We take security very seriously"...
Do you know where these words are written?
Maybe you'd like to try looking at this issue this way:
Many users who install LOS, are doing this because of security reasons. Imagine some of these users having bad luck and their phones get compromised by some bogus apps. And then they read an answer like this, telling them nothing different than: sorry, we can't and we won't help you!
And know imagine this:
Users can create snapshots or images of their running systems, with all of their apps included, as well as all necessary accounts, logins and passwords. When the "impossible thing" happens to a device running LOS, they have the option to restore the complete system without having to do a factory reset and without having to reinstall each and every app and the corresponding accounts.
What do you think, which one would please the users of your product more: an answer with an attitude like that one above, or the second possibility?
Furthermore: I was not bagging you to include this possibility. I was asking how this kind of back up could be made in the future, when TWRP won't work with Android 10, and when Google will remove adb. And frankly, I don't see why a recovery made by LOS should not be able to do a task that a third party recovery is capable of. If TWRP developers can put together such a piece of code, I am sure LOS developers should be able to do so as well.
Another possibility would be to reverse Google's decision and to keep adb.
So, from my perspective, there are at least two possible ways of dealing with this. But I am a user, not a developer, and I don't know if or why any one of these possibilities is a bad idea, or if there are really serious arguments against it, or whatever pro or con there might be. I simply don't know about these things and that's why I was asking about it. I am a user who doesn't like having to do a complete re-installation after a crash. And I am pretty sure that I am not the only user with this kind of antipathy.
A polite answer to the question would have included at least a glimpse of explanation why this and why not that.. And an open minded developer would have even cared to discuss about this.
Click to expand...
Click to collapse
Your reaction is a very butt-hurt reaction for a question that has been asked AND has been answered many times on this website and could have easily been found by you if you had searched.
Unless, of course, you did search and you did read where it has been answered before and, for whatever reason, you mistakenly thought that you would get a different answer just because you needed it to.
My point was, there is no way to access system partition or data partition without root. This forum is full of posts from other users asking the same thing, they all got the same answer, it can't be done without root or TWRP. Android just does not work that way, it has a linux kernel, which means, everything requires specific permissions and it is not in the best interests of OEM/carriers to allow access to /system and /data that easily and there is no way to give you "limited" access that only allows you to backup the /system and /data. There is only full permissions or none and they will not allow full permissions to the user.
That is entirely the whole point of people like us that find ways of rooting devices and installing custom recovery in the first place, because it is the ONLY way we can access /system and /data to make backups or modifications.
As for your thoughts of whether there will be a "new" way of making backups if adb and TWRP are no longer viable options....
Who knows? None of us will know until that time comes. We will all just have to wait and see if any takes the time to develop a new method.
Sent from my SM-S767VL using Tapatalk
dvdram said:
...
Last year Google announced that adb is very likely to be removed soon.
...
Click to expand...
Click to collapse
Android Debug Bridge (ADB) is a Server - Client pair software
ADB Server runs in the Android device
ADB Client runs in Windows / Linux / Mac iOS
ADB completely is open source. Hence everyone can grab the source code and compile it matching the target Android OS / computer OS. Manufacturers like Samsung & ZTE actually already provide their build of ADB Client suitable to their Android devices: they don't recommend to make use of universal ADB Client that floats around the WEB.
AFAIK Google announced to remove backup / restore feature from ADB Client, not ADB at whole.
jwoegerbauer said:
Android Debug Bridge (ADB) is a Server - Client pair software
ADB Server runs in the Android device
ADB Client runs in Windows / Linux / Mac iOS
ADB completely is open source. Hence everyone can grab the source code and compile it matching the target Android OS / computer OS. Manufacturers like Samsung & ZTE actually already provide their build of ADB Client suitable to their Android devices: they don't recommend to make use of universal ADB Client that floats around the WEB.
AFAIK Google announced to remove backup / restore feature from ADB Client, not ADB at whole.
Click to expand...
Click to collapse
Yeah, I can't see Google completely removing adb, it is too valuable of a tool for development even for the stuff the carriers and their developers do on their end. Removing it would be like building cars and engines but completely disallowing the production or use of tools to assemble/disassemble the cars or engines.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
My point was, there is no way to access system partition or data partition without root.
Click to expand...
Click to collapse
I know that and I understand that. I've been using Linux on my private and on my working machines for at least 30 years now, and I know about permissions. And I also understand that there are good reasons for not rooting an Android device.
But that is not the point here.
I am and I always was talking about the recovery here, not the running LOS system, that you run every day to make any use of your phone at all. From my point of view, as a Linux user, booting into recovery is like taking a secondary boot device, eg a USB memory, and starting another Linux system that is completely independent of the one that my PC is running in normal cases. Using this secondary Linux I can do anything to the system and the hard drive that I want, regardless of permissions. I can re-install the boot manager, I can copy or delete files, I can repair the file system, and, most important: I can create images and snapshots of the system that will serve as an lifeline, a certain point in time that I can return to if it should become necessary.
My question was and still is, why a custom recovery like TWRP can include this function, but the recovery made by LOS can or will not do so, or if there is a chance that the LOS recovery will include this function in the future.
Again: I am not talking (and I never was) about making root available in LOS.
@dvdram
...
My question was and still is, why a custom recovery like TWRP can include this function, but the recovery made by LOS can or will not do so, or if there is a chance that the LOS recovery will include this function in the future.
....
Click to expand...
Click to collapse
Wondering why you don't ask this question to the developers of LineageOS?
jwoegerbauer said:
@dvdram
Wondering why you don't ask this question to the developers of LineageOS?
Click to expand...
Click to collapse
Silly me! I actually believed there would be developers reading this forum. How could I mistaken this statement on the starting page:
"XDA Developers was founded by developers, for developers."
I guess the word "developers" must have another meaning than I have always believed. Thank you for showing me my wrong!