I'm unable to install franco kernel with magisk on stock marshmallow... I haven't tried this combination,does it actually work or I'm wasting my time?
If i install magisk first and then franco kernel then the rom boots but magisk manager doesn't open so can't get access to root,i tried supersu also but it gives me bootloop
Also if you can suggest other kernels that can be flashed on stock that Will be much helpful to me...
Thanks
Related
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Nocturnal86 said:
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Click to expand...
Click to collapse
You need to flash a kernel that is permissive and then flash SuperSU there are a few in the forums if you search you shall find them
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
aalaap said:
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
Click to expand...
Click to collapse
So I flash this in ADB? Is the secure kernel the same as stock? and if I were to flash a customer kernel like FK would I lose root? Sorry for all the questions just trying to clarify some stuff so I'm not completely ignorant to what I'm doing lol
There's a batch file that does it. You run it in the bootloader, not ADB.
FK has a Lollipop compatible kernel, but try and root stock first. Then flash FK's Lollipop version (it's different) and run CF AutoRoot again. Just to be sure things are working. Personally, I'm going to use stock for a while, understand the performance and then try FK or EX or whatever, so I'll be able to tell the difference.
Spend whole day browsing XDA, still can't get the thing done.
Running stock Nougat 39.2.A.0.361 with unlocked bootloaders and TWRP 3.0.2.0. Downloaded SuperSU 2.79, booted into recovery and flashed SuperSU. No errors, just a success message. However, after rebooting the phone, no sign of SuperSU exists. Flashtool also indicates root access is denied.
When installing custom ROM with SuperSU integrated ( http://forum.xda-developers.com/xperia-xz/development/rom-romaur-v1-0-fast-stable-t3486874 ) root works perfectly. Once custom ROM is installed, SuperSu icon is displayed and root access is OK.
I read that this problem might be because of incompatible kernel? I installed custom kernel (which was attached to RomAur - Stock_Kernel_f8331_fw.327-DRM FIX) before installing custom ROM, but I guess that re-flashing stock ROM later (using Flashtool) restored original kernel as well? If so, what exactly do I need to do in order to have rooted stock Nougat? Just flash some custom kernel (which one exactly?) and try flashing SuperSU again? Really don't want to brick anything.
P.S. Current kernel - 3.18.31-perf-g6af3ae9
if you are on stock nougat,
flash androplus kernel v18 from here:
https://kernel.andro.plus/tone2.html
after that,
flash supersu 2.78.
Thanks, will try. Is there any reason why using SuperSU 2.78 is needed? I see the latest one is 2.79?
manxp85 said:
Is there any reason why using SuperSU 2.78 is needed?
Click to expand...
Click to collapse
No - mine is running fine on 2.79SR1
BTW:
With stock kernel DM_Verity is ON
That detects any modification (e.g. installing SuperSU) in the non-USERDATA partitions via comparing signed checksums and if there is any modification found refuses to boot the device.
Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?
manxp85 said:
Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?
Click to expand...
Click to collapse
Welcome to the quirks of RomAur
It lasted less than a day on my device. I find the claims a bit overblown (did not notice them) and there were minor quirks/annoyances.
It needs time I suppose. But without the SONY sources auras76 can't do magic.
On my SAMSUNG G S5 I am on ResurrectionRom. THAT is an improvement over stock for me with LOTS of stuff I use and appreciate.
My Xperia XZ runs on stock ROM with AndroPlus Kernel v18 now. Do not forget to flash the Recovery too.
I am not sure if the SuperSU app is within the zip-file (80% positive it is). If not install it via Appstore.
Replaced RomAur with stock - works so much better. For some reason, root access on RomAur was lost every time after device was encrypted. No such problem with stock ROM.
I'm trying use android pay on my rooted sm-n920t 6.0.1. I've successfully installed Magisk and phh SU. The feature within Magisk that hides root from safetynet isn't compatible with stock Samsung kernel. So what are some recommendations on which kernel would be best suited for a stock rom rooted with Magisk?
Sent from my SM-N920T 6.0.1 using Tapatalk
biggdevon said:
I'm trying use android pay on my rooted sm-n920t 6.0.1. I've successfully installed Magisk and phh SU. The feature within Magisk that hides root from safetynet isn't compatible with stock Samsung kernel. So what are some recommendations on which kernel would be best suited for a stock rom rooted with Magisk?
Sent from my SM-N920T 6.0.1 using Tapatalk
Click to expand...
Click to collapse
Hi, could you tell me how did you installed magisk on your n920t? which version of magisk did you use ? I'm trying to install magisk on my sm-n9200 6.0.1 with stock rom unrooted , but failed . I installed magisk manager and flashed Magisk-v11.1.zip on my n9200 with stock 6.0.1 rom ( unmodified) , but when I opened magisk manager , it said " magisk is not installed ", while the root function showed and worked correctly . I followed the instructions in magisk manager to download and install magisk . After installation, magisk manager said that magisk was installed , but after I rebooted my note5, it showed " magisk is not installed " again.
woyaojizhu8 said:
Hi, could you tell me how did you installed magisk on your n920t? which version of magisk did you use ? I'm trying to install magisk on my sm-n9200 6.0.1 with stock rom unrooted , but failed . I installed magisk manager and flashed Magisk-v11.1.zip on my n9200 with stock 6.0.1 rom ( unmodified) , but when I opened magisk manager , it said " magisk is not installed ", while the root function showed and worked correctly . I followed the instructions in magisk manager to download and install magisk . After installation, magisk manager said that magisk was installed , but after I rebooted my note5, it showed " magisk is not installed " again.
Click to expand...
Click to collapse
You said you're not rooted, how are you flashing the files? Custom recovery, Flashify, FlashFire?
I started from compete stock, fresh.
Flashed TWRP via Odin, booted to recovery
Flashed arter97's v22 kernel via TWRP, booted system
Waited for system to settle (10 min), rebooted to recovery
Flashed osm0sis unSU.zip (Google is your friend), stay in recovery
Wipe dalvik and cache, flash Magisk-v11.1.zip
Boot system.
Forgot to mention the post you quoted was from when I used v10.2. Now using v11.1 so there's no need to install anything from phh. And you'll need the Magisk Manager app from the Play store
biggdevon said:
You said you're not rooted, how are you flashing the files? Custom recovery, Flashify, FlashFire?
I started from compete stock, fresh.
Flashed TWRP via Odin, booted to recovery
Flashed arter97's v22 kernel via TWRP, booted system
Waited for system to settle (10 min), rebooted to recovery
Flashed osm0sis unSU.zip (Google is your friend), stay in recovery
Wipe dalvik and cache, flash Magisk-v11.1.zip
Boot system.
Forgot to mention the post you quoted was from when I used v10.2. Now using v11.1 so there's no need to install anything from phh. And you'll need the Magisk Manager app from the Play store
Click to expand...
Click to collapse
I started from compete stock, fresh too. I flashed twrp, installed magisk manager app , and then flashed Magisk-v11.1.zip using twrp.
woyaojizhu8 said:
I started from compete stock, fresh too. I flashed twrp, installed magisk manager app , and then flashed Magisk-v11.1.zip using twrp.
Click to expand...
Click to collapse
Not sure then. I know the stock Samsung kernel doesn't play well with Magisk so maybe try a custom kernel. Otherwise try reaching out and posting your logs on the main Magisk troubleshooting thread: https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
im on poco f1
custom rom google
kernel sphinx 1.8.7
before update the kernel i can delete or uninstall any magisk module and reboot without problem. but after update the latest sphinx kernel ver 1.9 then i remove some module and reboot i goes to bootloop. so i flash the older version of sphinx my phone turn out okay no more bootloop after removing or adding any modules. i have try to find the sphinx kernel thread but cause im new here i just open new thread. sorry mods. Just for heads up of the problem that had occured to my device. thanks.
Hey all,
I am rooted with Magisk 17.3 on global hardware and global ROM stock MIUI 10.2.2.0, but I cannot install any Magisk modules or flash Magisk ZIPs in TWRP. I know root works because I've edited system files and allowed a few apps root permissions. But when I try to install something with Magisk Manager (6.1.0 since 7.0.0 doesn't work < v18) I get this error: /data/adb/magisk_merge.img mount failed... abort or it tells me Magisk 17.x+ isn't installed. (I've tried the Magisk Mod Uninstaller, Youtube Vanced, and LKT). When I try to flash a Magisk ZIP in TWRP it gives me Error: 1
I did some searching and some people were getting this due to their filesystem being formatted as f2fs in the past, but I verified that the Mi Mix 3 uses EXT4 using DiskInfo.
Did I miss something during the rooting process? I unlocked the bootloader, flashed TWRP in fastboot, flashed Magisk 17.3 in TWRP, and verified root was achieved with Rootchecker. The Magisk Manager app also says it's installed and passes SafetyNet. Anyone have any ideas?
Do you use a custom kernel?
Try the latest Magisk canary build and see if that works
JetzNicht said:
Do you use a custom kernel?
Try the latest Magisk canary build and see if that works
Click to expand...
Click to collapse
No it is the stock kernel that came with the MIUI 10.2.2.0 global build. Should I be using one?
Quick update: I am able to install some modules now by downloading them in Magisk, then booting to TWRP and flashing the ZIP there. I was able to get Magisk Mod Uninstaller (mm) and LKT to run for example using this method. YouTube Vanced still gives me the Error: 1 when I do this however.
The try a custom kernel, had the same problems with any modifications to the system with stock kernel.
As far as I know there are only two kernels atm, friendly fire and androplus.