I used magiskI currently struggle with this ROM and Magisk super user permission. For some apps (Amaze, OandBackupX and Titanium backup) I can't give them root rights, as there is no dialog to ask for permission. If I configure Magisk to automatically allow apps to use root permission, it also doesn't work. @MartinX3 : did you made any special configuration that could interfere with Magisk su permission mechanism ?
---------- Post added at 01:24 PM ---------- Previous post was at 01:24 PM ----------
I currently struggle with this ROM and Magisk super user permission. For some apps (Amaze, OandBackupX and Titanium backup) I can't give them root rights, as there is no dialog to ask for permission. If I configure Magisk to automatically allow apps to use root permission, it also doesn't work.
@MartinX3 : did you made any special configuration that could interfere with Magisk su permission mechanism ?
Please use the uninstaller on it's github page
Perfect and nice to hear!No update did work on my phone since 18.1 (I talked about it here, somewhere in the 99 pages… ^^).
But I didn't try the latest one (20.4). I'll try before uninstalling.
edit: updating to 20.4 did work !
And root permissions are fixed !
Thanks for your help ))
Ok I found the script: https://github.com/topjohnwu/Magisk/blob/master/scripts/magisk_uninstaller.sh
I suppose I'll have to run in from TWRP*?
You have to extract it with dumper payload -goNot used to flashing this rom so forgive me if I dont know what Im doing.. You mention that you need to flash all of these .imgs but the download folder only has a Zip...
so where do I get the imgs needed for:
- fastboot flash boot boot.img
- fastboot flash dtbo dtbo.img
- fastboot flash vbmeta vbmeta.img
- fastboot flash system system.img
- fastboot flash vendor vendor.img
#include <std_disclaimer.h> /* * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
jerpelea said:for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
i thought pushing a maintenance update would be a good idea.
Sadly it wasn't achievable.
I tried to simply rebuild the old sodp sync with the newest omnirom, also synced the newest sodp stuff wit the newest omnirom.
But that every time resulted into
1. Installing gapps on a fresh system let the device crash into twrp with the message "set_policy_failed:/data/cache/"
2. Upgrading from the previous version resulted into "no web views detected". The webview is needed for some apps to render their content. Without that they would simply crash.
Regardless if the gapps, aosp or bromite webview was installed, none was listed and the logcat throws errors.
3. The audio doesn't route anymore to a connected usb audio 3.5mm adapter.
4. There may be more bugs, but i am too frustrated to with the already occurring bugs and invested hours/days.
Lets look optimistically into the future of android 10.0, kernel 4.14 and which custom roms can be build on it.
omnirom 9 may be deprecated, but it seems that they backport security fixes.
Soooo, we get still security updates.
On the other side i got insulted (called a stupid idiot), warned, kicked and banned at once for asking about the security commits and saying that the insulter has a low emphatic intelligence.
I look if i will continue distributing stuff for this toxic community administration.
dear xz2 compact owners with not working touch.
It seems that we fixed the problem
the code needs to to get refactored and merged into sodp, before i can release new builds.
But anyway, i'm on vacation & studying for exams, so don't expect builds earlier than end of september/october.
To test it
fastboot flash boot boot.img fastboot flash vendor vendor.img fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
someone may have seen that in september comes a sodp switch to
1. Android 10 (queen cake)
2. Kernel 4.14 (using 4.9 at the moment)
i won't switch asap to the new stuff and wait until it proofs enough stability to act as a daily driver.
Maybe it is stable directly right release (i don't think it) or it may take ~1-5 months.
(and i don't know how fast omnirom switches to q.)
omnirom with may 2019 security patch level.
Newer, faster, more stable, oemv9 support.
Also i'll only push files to the single sim device section.
The dual sim device section will get a file with a hint to look into the single sim section.
There is also the twrp dual sim patcher. Without it the single sim firmware won't work on a dual sim phone.
That'll save bandwith and server storage.
I linked the patcher on the first page, but use my uploaded v4alpha patcher instead.
It contains my complete overhaul of the patcher and the current v3 in the xda thread doesn't work on tama.
I already made a pull request and the author just needs to merge my changes.
attached oemv8 images at the post
it is only a current snapshot of the camera development.
Expect further improvements with the upcoming oem blobs.
Ps: Oemv8 compatible builds are getting compiled after i released the oemv8 sonyaosp builds.
bug & feature tracker