So I'm running lineage 14.1 as they finally released a copy for the A5(2017) and I can't seem to install SU, it said binary is full. I would use magisk but alot of stuff still does not support it. How would I hide root from apps with SU? I have tried a few ways and it failed. Second the audio tweak lenage has is terrible, how would I remove it and go to a better one? And finally what are some good custom kernels that are compatable with Lineage and the Samsung galaxy A5(2017)
LOS come with pre installed root. U have to flash a zip to enable it.
https://download.lineageos.org/extras
Flash appropriate zip from above link (arm64)
Use ViperForAndroid for better audio
Use alphabet kernel for more tweeks
Pls do some research before posting.
jfk999 said:
LOS come with pre installed root. U have to flash a zip to enable it.
https://download.lineageos.org/extras
Flash appropriate zip from above link (arm64)
Use ViperForAndroid for better audio
Use alphabet kernel for more tweeks
Pls do some research before posting.
Click to expand...
Click to collapse
I have done research and flashed it but I absolutely hate the built in root. Viper last time I tried won't work and I can't set SE Linux to permissive and alphabet kernel does not specify what OS's it supports and have had it where it kept rebooting my phone on stock kernel settings.
So alphabet kernel caused lineage OS to go into an infinite boot loop and viper needs permissive SElinux which I have not been able to do. Can anyone help me? I know alphabet you can set it to permissive but caused lineage to infinitely boot
Related
Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.
Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?
Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
Good evening guys
I have a Xiaomi 5s stock rom MIUI9 with TWRP 3.2 (capricorn)
I was using the old supersu.apk to have root privilegs. I remove it completly to install the Magisk but I'm getting error 1
Follow the pictures...
As you can see I have the unlock boot, twrp, stock rom and not rooted... Tried others topics and tips to install the Magisk but It wont work...
What should I do?
(Xiaomi forum I saw a guy he installed the stock rom and full restored and he continues with error:1)
Resolution:
Change TWRP 3.2.1-1 to TWRP ZCX
Download stock rom (same as you're using)
Open the .iso with winrar or other software
Get the boot.img and put it in smartphone sdcard
Reboot in the recovery mod
Select install and change to install a IMG
Select boot.img and the partition BOOT
Install the magisk (feel free to put any version, I used v14)
Reboot and enjoy! :laugh:
PS: You dont need to unistall first your root because it'll be replaced when you install the stock boot.
Use magisk 15.2, make sure zip file not corrupt.
Even better use TWRP 3.2.1.1 and flash Magisk 16. That combination has some serious bugs ironed out.
BajinganTengik said:
Use magisk 15.2, make sure zip file not corrupt.
Click to expand...
Click to collapse
I tried with Magisk 15.3 and failed, same error. (ERROR:1)
8166uy said:
Even better use TWRP 3.2.1.1 and flash Magisk 16. That combination has some serious bugs ironed out.
Click to expand...
Click to collapse
I'm using the TWRP 3.2.1-1 is the same thing, I saw in Xiaomi Forum about the TWRP ZCX but I dont know what is the difference...
Does anyone have a fix to it?
Resolved, tip in the first post.
You could try the Xiaomi.eu ROM which has better support for rooting and adds some polish to MIUI (and also implements every weekly beta release of the official repo). Does require a clean install though.
8166uy said:
You could try the Xiaomi.eu ROM which has better support for rooting and adds some polish to MIUI (and also implements every weekly beta release of the official repo). Does require a clean install though.
Click to expand...
Click to collapse
Thank you for your advise, but I prefer the stock rom, btw I already fixed it too xD
Hi , i'm a little lost about installing a custom . I know i have to root my phone and install TWRP to flash the custom ROM but what about the custom kernel ?
Thanks
well u must know that if u just backed up drm keys and unlocked bootloader, after installing twrp and reading the log u can see that it says "Kernel does not have support for reading SELinux context" this means that kernel does not support selinux so u must change the kernel i recommend to get the kernel from this thread: https://forum.xda-developers.com/z5-premium/development/safetynet-stock-kernel-twrp-magisk-t3621404
then u must choose the google drive link then depending on ur model choose single or dual then flash the kernel via fastboot then boot into recovery and install the ROM and Open GApps (ARM64) u like in my case i installed Mokee because it is the only one with official support and always updated with latest security patches the only problem is that it include xposed and u wont be able to bypass SafetyNet and if u open online games the phone crashes and reboots
if u want to install mokee go this link (even if it says dual it supports all Z5P models): https://download.mokeedev.com/?device=satsuki
LastDarkWarlord said:
well u must know that if u just backed up drm keys and unlocked bootloader, after installing twrp and reading the log u can see that it says "Kernel does not have support for reading SELinux context" this means that kernel does not support selinux so u must change the kernel i recommend to get the kernel from this thread: https://forum.xda-developers.com/z5-premium/development/safetynet-stock-kernel-twrp-magisk-t3621404
then u must choose the google drive link then depending on ur model choose single or dual then flash the kernel via fastboot then boot into recovery and install the ROM and Open GApps (ARM64) u like in my case i installed Mokee because it is the only one with official support and always updated with latest security patches the only problem is that it include xposed and u wont be able to bypass SafetyNet and if u open online games the phone crashes and reboots
if u want to install mokee go this link (even if it says dual it supports all Z5P models): https://download.mokeedev.com/?device=satsuki
Click to expand...
Click to collapse
I installed successfully Mokee thanks.
Did you manage to install Sony apps or restore drm functionality like x-reality ? Thanks
typhon0 said:
I installed successfully Mokee thanks.
Did you manage to install Sony apps or restore drm functionality like x-reality ? Thanks
Click to expand...
Click to collapse
well u can install sony apps with a Magisk module called "Sony Apps Enabler" install the module, reboot phone and delete Playstore data
about the DRM functionality u can flash Zach's kernel but its only available for Unlocked Stock 32.3.A.0.376 even tho in the post it says the dev is making this kernel to work with custom ROMS comming soon: https://forum.xda-developers.com/xp...ernel-zachs-kernel-playground-z5-wip-t3340725
but u can recover good audio functions by installing this mod: https://www.mediafire.com/file/1jwsked0y4853td/Z5-6.0.1-ALL+In+One+Mod+V3.0.zip
and Viper4Android: http://www.mediafire.com/file/xonl4jha2e4vez1/ViPER4Android_FX_v2505.zip
flash the mod via recovery then reboot phone and install Viper4Android apk once u open it a window of installing the driver will appear, press Yes, the app will freeze but dont close it beacuse the installation is in progress, once driver is installed reboot phone and configure in the app, i recommend to enable everything except reverberation and speaker optimization (this one is bc if u enable speaker optimization audio loses some volume power)
LastDarkWarlord said:
well u can install sony apps with a Magisk module called "Sony Apps Enabler" install the module, reboot phone and delete Playstore data
about the DRM functionality u can flash Zach's kernel but its only available for Unlocked Stock 32.3.A.0.376 even tho in the post it says the dev is making this kernel to work with custom ROMS comming soon: https://forum.xda-developers.com/xp...ernel-zachs-kernel-playground-z5-wip-t3340725
but u can recover good audio functions by installing this mod: https://www.mediafire.com/file/1jwsked0y4853td/Z5-6.0.1-ALL+In+One+Mod+V3.0.zip
and Viper4Android: http://www.mediafire.com/file/xonl4jha2e4vez1/ViPER4Android_FX_v2505.zip
flash the mod via recovery then reboot phone and install Viper4Android apk once u open it a window of installing the driver will appear, press Yes, the app will freeze but dont close it beacuse the installation is in progress, once driver is installed reboot phone and configure in the app, i recommend to enable everything except reverberation and speaker optimization (this one is bc if u enable speaker optimization audio loses some volume power)
Click to expand...
Click to collapse
To restore audio processing I found this if your are interested : https://forum.xda-developers.com/cr...t-sony-xperia-xz2-sound-enhancements-t3772758
And for the camera are you using something specific or the base one from mokee.?
typhon0 said:
To restore audio processing I found this if your are interested : https://forum.xda-developers.com/cr...t-sony-xperia-xz2-sound-enhancements-t3772758
And for the camera are you using something specific or the base one from mokee.?
Click to expand...
Click to collapse
for the camera im using mokee one, i tried using google camera but when i tried to record vids i couldnt while in base camera u can record vids with no problems however an alternative u can use is to use OpenCamera: https://play.google.com/store/apps/details?id=net.sourceforge.opencamera
btw the XZ2 audio is good but there is a problem and its when u put music on, it doesnt let u to lower the volume and audio its at max volume even if u mute it so im staying with my current audio mod since its ore stable
Hello guys.
Unfortunately the today Magsik Update doesn't run very well on my Device. I did update to the available slot then reboot but the bootsplash now runs since 1H without being able to land on OOS. I'm on 11.2.5.5.LE15 BA + Omega Kernel latest build
Fastboot mode doesn't report any bootloader version nor baseband version.
What's the best way to repair that ? What was the mistake I did to prevent further error while I'm updating magisk or the Kernel ?
Ty @avid_droid but that's what I tried first. It leads me to the exact same type of Boot where nothing happens for 30 minutes excepts the bootsplash logo animation.
I did try to boot from the vanilla boot.img ... but that sent me directly to crashdump mode.
I then boot one last time to magisk_boot.img and .... it worked.
For some reasons everything was wiped on the device even if I never wipe anything from fastboot but no matter ... I'm now back in OOs and try to set it up completly
It's not Magisk, I updated to version 23 with no issues at all.
Also flashed the new Omega kernel afterward, no issues with that either, Magisk was still retained.
I would see if you can get into recovery, if you can then do a system reset and see if the phone will let you set it up again.
For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^
Fre$h said:
For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^
Click to expand...
Click to collapse
I did it the other way round, updated Magisk app, then Magisk itself, rebooted the phone. Installed the latest kernel using EX Kernel manager, it noted that Magisk was there so re-applied it on the new kernel, then rebooted and it was fine after that.
I'm not using any Magisk modules though, not going to risk that until we have a good recovery.
avid_droid said:
Same here. I keep magisk modules to a minimum. I am however playing with substratum and we know how that usually ends up haha. Giving it a go. Trying to remember the signal icons I used to use
Click to expand...
Click to collapse
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either
djsubterrain said:
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either
Click to expand...
Click to collapse
Liv dark works now on op9pro OS11.. I'm using several different themes from livDark now
All I need to do here just hit "install"?
Ive never done it before so I just don't want to screw up.
First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update
Fre$h said:
First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update
Click to expand...
Click to collapse
Thx bro...all good
This is particularly here we miss TWRP to flash magisk uninstaller properly. I like the way we can temporary boot from rooted boot.img but the disadventage is that we need a computer just near us to do that.
Hope everything is now fixed
Hello.
I have the Samsung A22 4G (SM-a225m) And want to custom rom it, but how? I am hating one ui and really want to change to a custom rom, I know how to install custom recoveries like TWRP but I dont really know the custom rom installation. If someone could help me do it and send me the link of the file and how to install it. Thanks anyway.
if you follow this guide https://forum.xda-developers.com/t/...axy-a22-sm-a225f-a225m-android-11-12.4333305/ after installing twrp, there should be a gsi installing method and follow that, but be warned, bluetooth headphones dont output audio from my knowledge and you have to go into phh setttings, samsung features and alternative audio policy, speakers will work but you cant control audio, thats why you follow this guide https://forum.xda-developers.com/t/...stem-that-wont-let-you-change-volume.4550239/ for a workaround to control audio. Hope it helps!
It does not work, I had to reflash stock rom again, I would prefer someone having the a225m with a custom rom to tell me how to do it, the guide doesnt work
cervigil said:
It does not work, I had to reflash stock rom again, I would prefer someone having the a225m with a custom rom to tell me how to do it, the guide doesnt work
Click to expand...
Click to collapse
I have the A225M, some custom roms do not boot, for example project elixer does not boot but spark os 13 gsi is working and boots fine, just go into twrp and click restart restart fastboot then you type fastboot devices to check if the device is detected, then you type fastboot flash system pathtogsi.img then type fastboot reboot, if the device keeps rebooting, the gsi is not bootable, hope it helps!
what version do you used? bvn or bgn?
cervigil said:
what version do you used? bvn or bgn?
Click to expand...
Click to collapse
I believe you should try to go with BgN whenever you can
I installed it and wifi and bluetooth doesnt work
go to this guide https://forum.xda-developers.com/t/fusion-kernel-for-a225f-a225m-android-11-12.4337511/ and flash the kernel via twrp, has wifi drivers but bluetooth should work by default