Hi, I was wondering if any build of the SuperSU is compatible with P8 Lite. Currently I have (as most of us) SuperSU pro v2.67.
Is there something that I should be aware of?
What makes a build compatible with this phone?
Thanks in advance.
You can put the latest, 2.76 ....
Thanks, I downloaded 2.78 and it seems to be working. At least it didn't give me a bootloop. But does anyone knows of, what makes any superSU build compatible with any phone? Or every build is compatible with every phone?
Thanks
spirto82 said:
Thanks, I downloaded 2.78 and it seems to be working. At least it didn't give me a bootloop. But does anyone knows of, what makes any superSU build compatible with any phone? Or every build is compatible with every phone?
Thanks
Click to expand...
Click to collapse
Every build should be compatible whit any phone, but maybe OLD versions aren't compatible whit NEW phones .... and sorry, I wanted to write 2.78 not 2.76 Press Thanks if I helped you
It did help. Just two more questions for anyone that can help:
Is the installed superSU version related somehow to the custom recovery build? Or the only restriction, is that the recovery should be adapted to the phone?
(meaning: OK I can flash any superSU version, does it have to be through TWRP 3.02 or it need a specific version, cause there could be compatibility problem?)
And secondly, I would like to ask if there is a guide for a systme-less superSU installation...
Thanks again.
Related
Hi everyone.
I have a Huawei Honor 4x (Che2-L11) and today i flashed TWRP succesfully on it after so many soft bricks. But now i cant flash any file with it. I tried flashing super SU and xposed framework, both installed fine but the phone failed to boot (I was stuck at the Honor logo) so i had to uninstall xposed (When i installed superSU i had to reflash system.img)
How can i root my damn phone?
Update: I have now rooted my phone with BETA-SuperSU-v2.74-2-20160519174328-forced-systemless.zip
You have bootloop now?! After you rooted
Um nope its all good, cant install xposed though.
Try another xposed version
I have the Kirin 620 version and there is only version for that (Android 6)
HaxOrHF said:
I have the Kirin 620 version and there is only version for that (Android 6)
Click to expand...
Click to collapse
Someone posted in honor 7 thread that v85 worked fine compared to v86 which had problems.
May be you can give that a try.
Okay, i'll give it a shot
Ok i managed to install the older version but now i get "xposed framework version 85 is installed, but not active, please check logs for details"
HaxOrHF said:
Ok i managed to install the older version but now i get "Its installed but not activated"
Click to expand...
Click to collapse
May be it has something to do with the systemless root. I am not sure. Sorry buddy...:crying:
Root works perfectly idk i guess i'll just leave it
HaxOrHF said:
Root works perfectly idk i guess i'll just leave it
Click to expand...
Click to collapse
I myself had to leave Xposed alone coz emui does behave weirdly when I install Xposed on my honor 7.
Sometimes random reboots, sometimes settings not working and sometimes dialer.
It's probably due to some not properly built libs, like touchwiz or on xperia devices.
deleted
If it doesn't work try another version
Fixed it??
Hi,
SuperSU is not very clear to me.
Is the version of supersu important for each device or can we just get the last available version and install it, I have a Galaxy S4, is there a "best" supersu version for that?
And then if yes, is the version linked to the ROM version or the device? I mean, given a Custom ROM, should it have his own specific supersu version? or is it a matter of hardware?
Thx.
ferdossi said:
Hi,
SuperSU is not very clear to me.
Is the version of supersu important for each device or can we just get the last available version and install it, I have a Galaxy S4, is there a "best" supersu version for that?
And then if yes, is the version linked to the ROM version or the device? I mean, given a Custom ROM, should it have his own specific supersu version? or is it a matter of hardware?
Thx.
Click to expand...
Click to collapse
Simply put, no SuperSU is not tied to a specific device or ROM. There were instances where it did matter like when systemless root was being developed and people needed systemless over regular system root. But I believe at this point the newest version of SuperSU decides whether you need system less or not for you. Custom roms generally come with whatever the latest version of SuperSU is available when it is built. In those instances if you want systemless root you just uninstall root and reinstall it systemless. I use the S4 for a few years and have had both system root and systemless.
Hi all when flashing any version above v12 on to my phone it gets stuck at the boot logo I am using Lineageos latest version of typing this but if I use v12 its fine but dont pass the CTS and stuff
I have tried to fully uninstall the magisk and reinstall it on the newer version and nothing can anyone help please
I have also fully reinstalled the ROM with formatting everything and it still don't boot
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
ldeveraux said:
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
Click to expand...
Click to collapse
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on the first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Jet45 said:
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on thé first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Click to expand...
Click to collapse
So glad someone eles has the same problem and I'm not on my own it just seems weird how the v12 works it don't pass but all loads fine. Let hope they find why and fix it.
Flash your stock bootloader then try flashing magisk
I'm using the stock bootload not changed my bootloader
If it was the bootloader why foes v12 work fine?
No request to have any information about this ?
What do the devs need (other than time of course) to try a troubleshooting ?
How to get this logs/boot image and logs ?
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Recycool said:
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Click to expand...
Click to collapse
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Recycool said:
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Click to expand...
Click to collapse
So I'll try to reproduce it at my side with that you've said, it may be a walktrough . Two brains to work on it may succeed
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I posted a logging of the problem on the main support thread, let's see what happens
https://forum.xda-developers.com/ap...sal-systemless-t3432382/page1765#post73249492
cross the fingers (I hope that you say like that in English)
Fingers crossed they sort it. Would love yo be able to use magisk again
Does anyone here have this issue on a stock ROM or is it just Lineage OS? From the log that was posted in the main support thread it looks like the Magisk installation was successful, but the system hangs on this one line before it can fully boot. I'm not qualified to read more than that out of the log though...
There's been some code added to GitHub in the last few days. Have anyone tried the latest unofficial snapshot? There was a new one built yesterday: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
Hi we got anymore news on this I have tried the latest beta one and it still gets stuck at booting.
It seems there is nothing to expect from nor magisk team neither lineage team. Nobody seem want to work on this really specific problem.
i've been trying to find one xposed that works with 7.1.1 but nope nothing if anyone can help lemme know
mister_propa said:
i've been trying to find one xposed that works with 7.1.1 but nope nothing if anyone can help lemme know
Click to expand...
Click to collapse
This will work for European exynos. If the framework is not compatible it shouldn't make any changes to the system. Only an error appeared.
Maybe someone can tell it's not possible or compatible to Snapdragon. I don't know for sure! It is recommended to backup device before you install Xposed.
Get latest Xposed installer. Choose version 88.2. If you have root and BusyBox installed, the installer will possibly install the framework by itself. Then reboot.
Else you need a custom recovery TWRP and flash in recovery. When no problems the system will boot up normally. Maybe it takes some extra time to boot first time.
Click to expand...
Click to collapse
toineh said:
This will work for European exynos. If the framework is not compatible it shouldn't make any changes to the system. Only an error appeared.
Maybe someone can tell it's not possible or compatible to Snapdragon. I don't know for sure! It is recommended to backup device before you install Xposed.
Click to expand...
Click to collapse
it doesnt work for snapdragon it give me bootloops just stays at the samsung sign ugh it's really frustrating that all of these phones having xposed n not the sd note8 smh i used the early ones first then the 88.2 i flashed it i installed it thru xposed n still the same frozen results
I have successfully installed Magisk on my device Root works but when I try to install a magisk module I get an error about not being able to mount magisk.img. When I try to install through recovery the module is flashes without any errors but once you open the app It displays "no modules installed". Before the G5s plus that I have a had the Moto G5 Plus. It had the same problem I just had to install another kernel over stock one and Magisk would work as expected. Is there a kernel for stock room that would support Magisk. Anyone else had this problem or is it just me?
ive no issue installing modules through magisk. Theres a lot of factors here. You didnt mention but id presume you installed magisk through recovery. Also, I presume you installed xposed. Maybe the modules your using require xposed to work. I forgot the exact steps to install xposed through magisk, but its not hard, and Id assume anyways you tried all of that. Have to flask xposed through recovery if I remember, then you can install xposed app apk too through recovery, then open magisk and install the latest xposed there. Im not using a stock rom, however Im fully confident if you properly rooted, and unlocked your phone of course, (I assume you did, just saying) its not a kernel issue. Sorry if I wasnt any help, its all i can think of right now.
When I got the phone I unlocked the bootloader and installed TWRP. When I set up my device I went back to recovery to install Magisk 14.3. It installed correctly and I got root using Magisk but when I try to install any module through the Magisk app I get an error. If I got you right should I try to install Xposed too? I was planning to install Xposed, Magisk version. But when I try that I get an error. I have attached a screenshot of when I try to install Xposed by topjohnwu and Greenify for Magisk. I get the same error.
well, xposed may not be your issue if you cant install any module with magisk manager. The modules, majority of them, if not all of them, i dont know, do not require xposed. Some do, most do not. Now please keep in mind, i could be wrong. I would say this, no harm in installing xposed, its basically a must get anyways for many awesome apps/modules. How you install, first install the xposed manager, youll have to look around for it, its not on the play store. Then downkoad magisk xposed through magisk. Once you download that zip file boot into twrp and install xposed through twrp.
This is a youtube on it: https://www.youtube.com/watch?v=MCcvsOp83A4 Now thing is, this may not fix any of your problems. But theres a chance it may. Like i said either way you want xposed on rooted phones anyways.
Patched kernel for stock. I have no problem running modules on Magisk. Flash in recovery.
https://forum.xda-developers.com/showthread.php?p=73930507
Sent by way of magic
if youre using stock rom, try this kernel. i just compiled it today from geneticengineers git. last updated hours ago.
Ae3NerdGod said:
if youre using stock rom, try this kernel. i just compiled it today from geneticengineers git. last updated hours ago.
Click to expand...
Click to collapse
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
Ae3NerdGod said:
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
Click to expand...
Click to collapse
Is there a thread for these kernels or any for G5S Plus?
THERAJ12 said:
Is there a thread for these kernels or any for G5S Plus?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g5s-plus/development/kernel-t3707143/post74562730#post74562730
wifi fixed btw