I have searched the forums here and couldn't find a direct solution to my problem.
My problem is after flashing a custom rom, I get the seandroid kernel enforcing error along with the boot loop. I understand this is kernel related, as when I restored my stock backup, then tried just flashing the custom kernel to that stock firmware, i got the same thing.
My question: is there a way to install custom roms/custom kernels without this damn seandroid boot loop annoyance?
I tried:
TWRP 2.8.5.0
Firekat N4ANK4V11X ROM
I was able to root successfully using auto root via odin, so root isn't a problem. I want a custom rom.
My KNOX version is:
Standard SDK 5.2.0
Premium SDK 2.2.0
Customization SDK 2.0.0
IM 2.0.0
CEP 2.0.0
Enterprise Billing 1.0.0
SE for Android 2.2.0
SSO 2.2.0
TIMA 3.0
VPN 2.2.0
Okay I solved my own problem. I downgraded twrp to 0.8.2.1 as this was the recommended Canadian version from the twrp site. I then realized I was trying to flash the wrong rom and firmware versions. All works great now on firekat v11x rom and 3.10.5-AELKernel-v7.2. This thread can be closed now
Related
Hi,
I'm in a bit of a pickle.
I'm rooted, have CWM regular recovery installed, and on Franco's r72 kernel.
My phone says it has downloaded the 4.2.2 update.
so now if I want to update, what should I do?
I have found a "stock recovery enabler" from here: http://forum.xda-developers.com/showthread.php?t=1995440
Questions:
- Do I need to flash a stock kernel BEFORE I install the above revert zip to stock recovery? Or is it ok to be on Franco kernel throughout the update process and stock recovery?
- Would I lost root if I update?
- Because of my current configuration, would I lose any data if Install an OTA update?
TIA.
ap1618 said:
Hi,
I'm in a bit of a pickle.
I'm rooted, have CWM regular recovery installed, and on Franco's r72 kernel.
My phone says it has downloaded the 4.2.2 update.
so now if I want to update, what should I do?
I have found a "stock recovery enabler" from here: http://forum.xda-developers.com/showthread.php?t=1995440
Questions:
- Do I need to flash a stock kernel BEFORE I install the above revert zip to stock recovery? Or is it ok to be on Franco kernel throughout the update process and stock recovery?
- Would I lost root if I update?
- Because of my current configuration, would I lose any data if Install an OTA update?
TIA.
Click to expand...
Click to collapse
Read this thread about OTA installlations http://forum.xda-developers.com/showthread.php?t=2145848.
Installation will abort, just flash a custom rom..
I'll give you a nickel for your pickle
hello,
first of all (as i cant update signature)
Phone: GT-i9505
TouchWiz: LP 5.0.1
Software number:
MDF v1.0 R4
VPN v1.4 R3
Kernel version: 3.4.0-4760392
Baseband version: I9505XXUHOD7
Build number: I9505XXUHOD7
so i rooted my phone using kingroot and then my phone would crash if i tried to use any root app (freeze then black screen then reboot)
i managed to flash TWRP 2.8.7.0 and void my warranty at the same time (LOL )
after trying to unroot my phone went into reboot loop so i used twrp to wipe cache nope still rebootloop
then i wiped data / factory rest and it now boots up but still has the kingroot files (and busybox files) in /sytem/xbin but the only kingroot files are krdem and ku.sud no more su binary normally just su
so what i was wandering was :
1:
is the crash a problem with SELINUX as on my phone it is ENFORCING
2:
How can i change se linux and root with supersu via twrp
3:
anything else that might help me
It is not a selinux problem. As any stock tw rom has selinux enabled and many people have rooted without much problems.
The problem is kingo root.
I'd recommend starting from 0. Meaning you have to reflash stock rom with odin and then use cf-autoroot to root the phone. It's way better and offers less problems.
Just installed Nougat stock ROM for my S7 Edge with ODIN, and trying to root.
I installed TWRP latest version 3.01 and immediately after installed supersu 2.79 SR3 from TWRP.
At first I could not boot the phone because it kept saying I used the wrong PIN code for boot. I reflashed stock rom and was able to boot again (same PIN) - disabled PIN on boot, and reflashed TWRP and supersu, but it keeps hanging at the Samsung Logo.
Flashing stock rom solves it, but I still want to root it..
What am I doing wrong?
currently there is no reliable root for nouget roms. It is being worked on.
Cosmic Blue said:
currently there is no reliable root for nouget roms. It is being worked on.
Click to expand...
Click to collapse
Thanks for replying.
In this case - even if the goal is to root - it seems the problem is with TWRP.. Even if I do not root, but just install TWRP, the neverending bootlogo shows up..
Nougat OS has been changed that all the old rooting and twrp need to be updated.
It will be a while till developers can modify the os to allow changes.
Have posted the same question in the TWRP S7 thread that I did not see before posting this one - sorry
I flashed magMa ux 8.5 rom for my n900t and i saw the Magisk systemless root and i got intrested! So i installed Magisk v12 with SuperSU but i found there was conflict with it so i wanted Magisk v12 with MagiskSU!
I tried dirty flashing the Magisk v12 + MagiskSU over the Magisk V12 + SuperSU! Which caused (im guessing here) caused my boot.img to get corrupted or damaged because it installs into ramdisk!
I tried a nandroid back to my old rom which, worked, wiped in twrp to reflash the rom, which also worked, but installing the magisk to the ramdisk and what it does ends up failing!
I can still boot into my system with root but it causes some conflicts with apps, such as snapchat as it thinks i have magisk still but i only have supersu! And i cannot full unroot from SuperSU app because, i think the boot.img is corrupted!
Would flashing a stock boot.img fix my problems, then reflashing rom again? Or would i have to reflash the whole stock samsung rom and things?
Im on Note 3 N900T! If reflashing the boot.img would work could someone provide a link to download the N900T!!! boot.img?
Thanks
What you call boot.img is the kernel.
Stock kernel won't work with a MM port like magma.
I advise you to do a full wipe from twrp then flash magma.
Before that, refer to the rom's thread for extensive informations about Magisk and systemless root.
Hi
I have an issue with my s7 edge. I am unable to flash any kernel, even if it succeeds in twrp, the kernel remains stock regardless. Also, i think supersu has caused the issue as I am unable to root with magisk, it says that the boot image is already patched by an unsupported program. I literally have no idea how to get rid of this kernel. I have flashed to stock with odin and also tried a full unroot with supersu. Is anyone able to help?
Thanks
Just curious, can you flahlsh to stock, root with magisk and then flash a custom kernel in Twrp? Have you also tried a custom ROM? Good luck
In twrp , go to advance wipe and check all boxes except sd card. Wipe.
Flash whatever rom you want. Boot it up. Then go back into recovery flash a new kernel and it should work.
Sent from my SM-G935FD using Tapatalk