New to rooting and all that stuff, have some basic knowledge, and successfully rooted my A20e with a stock rom and Magisk.
Now I'm trying to boost the performance, as I can't play anything that's more resource consuming for more then 1h without many lagspikes, and wanted to try the Eureka kernel, but I can't use the recovery mode as that was changed by Magisk, and I'm not sure if it even works properly since whenever I start in recovery the touchscreen doesn't work, yet the root work in normal mode except that I can't modify anything in the system folders within apps like Root Browser, i. e. can't change the permissions.
So is it possible to install the kernel though Odin or something else external?
And do any custom ROMs improve performance?
Related
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Duncan1982 said:
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Click to expand...
Click to collapse
Maybe install busybox from Ericsson
Thanks I have busy box installed, this is very odd it is like there is a security file blocking everything despite root.
Xblast works as I have the clock centred and circle battery.
I am Experienced in root, and haven't stumbled upon this before.
Was thinking it was 4.4.4 but others are having success.
Hmmmm baffled.
Maybe has something to do with the security settings?
Install if you like the Wanam module and check if Disable Secure storage is disabled.
Thats all i can think about for now.
Nope nothing, even tried changing secure storage value to false and upon hitting save it reboots and nowt.
I give up can't think of anything oh it could be AEA Kernel that perhaps is causing the problem?
The only way to find out if its the kernel you flashed. Re-flash the stock-kernel
Thanks for getting back, Yeh back to stock and same problem. Maybe for some reason only have partial root, can't see that as supersu is there and functional and I have twrp custom recovery. Hmmmmm the mind boggles lol.
Reasonably experienced root user and for the life of me I can't sus what's up.
Tried refreshing the AEA Kernel and it won't even do that now.
Not that it's important, was just after a sound mod & changing the Dpi down to 560. Tried both it won't change.
Some security thing is preventing this but what could it be?
With some 4.4.4 ROMs on the note 2, there were problems with getting "full" root using twrp. I don't know if this is relatedn but the symptoms sound similar. Solution there was to use philz recovery (which isn't an option here), or for some Roms to flash an older version of supersu in twrp and then update after starting. Could be worth a shot.
Did you make sure to open the SuperSU app after rooting and update the binary? Are you SELinux permissive?
If you are having issues, download the recovery version of SuperSU, install it, then make sure to open the app so it updates.
You could also disable SELinux through the build.prop. Having a kernel that is SELinux permissive doesn't matter if you still have everything enabled in the build.prop
Code:
(SELinux disable)
ro.build.selinux=0
(KNOX disable)
ro.config.tima=0
ro.config.knox=0
If none of that has helped, it is recommended you restore to stock and root again, making sure that reactivation lock is disabled before attempting to perform the root portion.
Hi,
I would like to gain some information. Is there any (or is it even possible), custom rom without root?
Simply saying I would like to have a rom, doesn't matter if custom or stock, but I would like to keep TWRP recovery intact.
{NOT INTERESTED IN XPOSED MODULE CLOAKROOT etc. because it doesn't work for apps that restrict use of root access, that I'm using}
Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??
Hello everyone.
I made some test in installing some custom roms in some old devices always avoiding to install TWRP permanently on the drive (i used it in boot mode and then adb listen in TWRP and adb command from PC).
I've done this in order to preserve the stock recovery mode.
I decided to install pixel experience as my default rom in my redmi note 7 and i noticed that this rom will use OTA updates so i'm asking you if i should install TWRP (or other recovery images) permenently in order to make it work properly.
Another question that i have revolves around Magisk, is this tool needed in order to make pixel experience work fine?
BTW i don't understand why TWRP does not officially support RN7 lol (eventually i'll use a porting or another recovery )
Thank you everyone
First, sorry for not answering your main question but I'm more intrigued as to how you can flash a custom rom without using a custom recovery like TWRP. Also, is it possible to permanently install TWRP? How you do this?
Second, Magisk is not needed for the rom but allows some other customizations, fixes and root access.
you need some kind of custom recovery that supports your phone, its what allows you to install roms. There are a few out there such as TWRP, organge fox, etc. Chose whatever you like that has good support for your device.
Perhaps, someone knows what problem can be caused by the connective, mentioned in the thread name and how to fix it...
So, what I have experienced myself: I flashed a modified kernel, magisk from twrp and used the phone happily..
After some time I got a system message about that my phone was ready for security patch updating. I deleted update files from Ota-packages folder, but after an occasional reboot I found that the phone had already been updated, I had no root, twrp and the custom kernel anymore.
Does anyone know the reason of such behaviour? What exactly cause it? How to reflash the custom kernel correctly? How to avoid subsequent system updates, which can rebuild the ROM with the stock kerner instead of the custom one?
Does it matter when to obtain root via magisk providing I use a custom kernel?