Aliendalvik: root access?

[stiray]

I am desperately trying to get root access on aliendalvik (I want to integrate xposed framework to get control over what information applications are gathering and fake them using xprivacylua).

Is someone aware of some simple method how to do it? I have unpacked squoshfs, added su to the image and created new image but the apks started dont run (lxc-info says the aliendalvik container is started). On the other side, without the su binary the image is working fine. Selinux?

Can the image be built from sources?

[Levone1]

I believe Aliendalvik is closed-source …

[stiray]

Ok, I think i have figured it out, I have probably messed up some permissions while mounting.

For help to the others.

Backup /opt/aliendalvik/system.img if something goes wrong.

unsquashfs /opt/alien/system.img to some directory, lets say ~/aliendalvik

Change whatever you feel appropriate.

Run:

sudo mksquashfs ~/aliendalvik system.img -comp lz4 -Xhc -b 131072 -no-exports -no-fragments -no-duplicates -all-root

You should get squashfs image matching the original one (except the changes).

Copy it back to /opt/alien (stop the android subsytem first), take care that ownership and permissions are the same as original system.img.

I wonder if jolla would have something against doing some community image (normally, still for paying users) with integrated microg, xposed and root? I would rather integrate magisk, but the problem is that magisk is using boot or recovery to start, while they are not needed here. But it would be great if someone knows how to adapt magisk to start from system image.

[remote]

We should pressure Jolla into integrating and supporting all those privacy features into theirs aliendalvik system.img.
It should have integrated switches to limit access to data and internet access per android app.
Wasn’t Jolla about privacy?

[stiray]

Quite frankly, I think they should do it sooner or later, no pressure needed.

As I have stated here:

Feedback: initial impressions

7of9, this is actually wrong, check xprivacy lua. The question should not be “allow or it doesnt work” but rather “would you like to fake this information”. Android actually did it wrong here from google wish for a huge payoff, but based on GDPR: EDPS Opinion 4/2017 on the Proposal for a Directive on certain aspects concerning contracts for the supply of digital content, 14 March 2017, p. 7. “There might well be a market for personal data, just like there is, tragically, a market for live huma…

Privacy market is becoming a huge opportunity and at the end of the day, people are becoming sick of google and fb. Projects like librem5, /e/,… are grabbing the attention, and I think that sailfish has the best story of them all. There are some rough edges to be polished but I am very satisfied with 4.0.1 on xperia 10 plus (and I have moved to it from my own rom that had all that I need or want. Now they have to scale up and support as many devices as possible. If they will fail to do it, someone else will lead the market.

[Levone1]

Or, maybe some other old root that works through /system, like SuperSU or something… If your method to mod system img works, you might be able to hack it. (unless you tried already)

[remote]

@stiray

no pressure needed

I’ve been using SFOS since 2017 and I can clearly see that they have lost focus on privacy aspect lately. Sadly.

[stiray]

Well this would really be stupid as I think that right now is the time for privacy selling point.

[Inte]

Isn’t AD rooted by default? At least I have a couple of apps that do not run since they detect a rooted system?

[remote]

Indeed. But lately end-users and their wishes are not a priority.

[Sword11]

I certainly appreciate the insights, I was able to unsquash and rework based on your post.

Which SU binary were you using and which manager? I havent had much luck with the ones I have tried in /system/bin. I would love to be able to install xprivacylua to mask the unlocked bootloader. Sadly SFOS’s browser is too old to access a website, and the app detects the unlocked bootloader and closes.

[Levone1]

Been messing around with this a bit, and got SuperSU as far as screenshots, but it’s ultimately an issue if system r/w access. Even su app can’t get that of itself. Somehow tje access is restricted - not sure where. I’m guessing it’s either at the kernel level, or it’s in closed-source Aliendalvik code… I’ve asked about it, but no response, Any Way to Get r/w Access in Android?. I’ve tried various things with mount, system props, etc., on Android and on SF side. May not be possible, (however, I’m certainly no expert).

[stiray]

No, you wont be able to obtain rw access on squashfs, by definition it is a read-only file system. You will need to use some rooting method that doesn’t require updating (this “needs to be updated” is a nonsense imposed by developers). Go to xda-developers and ask there.

[Levone1]

Right, but the issue isn’t just that the root app would behave properly - the issue is the rw access itself. Without that, there’s no use in ‘rooting’, since you still won’t be able to do anything that you would want root for…

[bundyo]

There is a theoretical possibility to mount squashfs pseudo read-write with overlayfs. Dunno if this can be done transparently with AD.

[fabio.87]

Any news about root support of App Support on Sailfish OS 4.5.0.21 (and Android 11)? Backup/restore processes would be much easier with root access (like with the good AlienDalvik su, control, etc. made by @coderus). Unfortunately, Shizuku is not enough to obtain the right privileges to do so.