Related
I'm trying to get a flash-able zip to use in recovery. I can flash and root android 5.0 but as soon as I install a different kernel I lose root. I mostly want to use fast charging . Do i just need to wait longer for there to be a kernel that supports fast charging with android 5.0?
raven.warsong said:
I'm trying to get a flash-able zip to use in recovery. I can flash and root android 5.0 but as soon as I install a different kernel I lose root. I mostly want to use fast charging . Do i just need to wait longer for there to be a kernel that supports fast charging with android 5.0?
Click to expand...
Click to collapse
I believe you are supposed to flash supersu after kernel install, i did it that way and I still had root after installing elementalx
chapelfreak said:
I believe you are supposed to flash supersu after kernel install, i did it that way and I still had root after installing elementalx
Click to expand...
Click to collapse
nope titanium back up tells me no root
raven.warsong said:
nope titanium back up tells me no root
Click to expand...
Click to collapse
Is that that only app you tested? Are you using play version or the Lollipop compatible beta from Twitter?
raven.warsong said:
nope titanium back up tells me no root
Click to expand...
Click to collapse
have you tried flashing the pie patch from http://forum.xda-developers.com/showpost.php?p=56533296&postcount=7169
Stock Nexus 5X Kernel + SafetyNet Patch
Current version: android-msm-bullhead-3.10-nougat-mr1.1
Suitable for build: N4F26T
I compiled the stock kernel for the Nexus 5X and applied the SafetyNet patch by sultanxda.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is for Android 7.1.1, build N4F26T!!!! This will not work on any prior build.
- All stock features that came with the N4F26T build will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the kernel included in the N4F26T build, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Extract <boot_image>.img from zip file
- Test it with: fastboot boot <boot_image>.img
- Once you know it works, flash with command: fastboot flash boot <boot_image>.img
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
And otherwise, I'm not a professional developer, just a hobbyist. Please don't ask me for a ton of help, I only created this kernel because I want to run completely stock, but still use Android Pay while having an unlocked bootloader in case I ever decide to root my device in the future. I will try to maintain this kernel with each new release until I lose interest
(shamelessly copied from Sakete's kernel for the Pixel/Pixel XL. Thanks for the inspiration, Sakete!)
It will work on Rooted Android 7.1.1 NMF26F ?
AFK269 said:
It will work on Rooted Android 7.1.1 NMF26F ?
Click to expand...
Click to collapse
You'll have to test it and let me know as I'm not using it on a rooted phone
If your root method trips SafetyNet then this kernel is useless to you, as it will only bypass the unlocked bootloader check and not the root check.
Well I tried to install your kernel and it is missing files and will not install. I wish there was a way to just flash the bypass of safety net with any kernel that you wanted to use.
weaselskhs said:
Well I tried to install your kernel and it is missing files and will not install. I wish there was a way to just flash the bypass of safety net with any kernel that you wanted to use.
Click to expand...
Click to collapse
Can you clarify? Did you flash with fastboot? What steps did you use?
Bootloop while installing unpacked .img file using TWRP. PixelROM 7.1.1, SuperSU v2.78 SR2
doggie13_ said:
Bootloop while installing unpacked .img file using TWRP. PixelROM 7.1.1, SuperSU v2.78 SR2
Click to expand...
Click to collapse
I wouldn't expect this kernel to work with custom ROMs.
Well that makes sense as I am also running Pixel Rom 7.1.1 and super su
It'd be super cool if this patch worked with PixelRom
Is there a specific reason this doesn't work with custom ROMs?
19lmyers said:
Is there a specific reason this doesn't work with custom ROMs?
Click to expand...
Click to collapse
Well for starters there is code missing from the stock kernel to work properly with the pixel rom. Which begs the question why you would want to flash the stock kernel on a pixel rom when you can use other custom kernels. I believe that Franco's kernel has the safetynet patch included.
Thanks to share
Hi,
Will this work for 6p?
Thanks
turbo81 said:
Hi,
Will this work for 6p?
Thanks
Click to expand...
Click to collapse
No. It's only for Nexus 5X (Bullhead).
Subbed. I'll be waiting for the N4F26I build. I miss using Android Pay.
Does anyone know if there is or will be a patch for the nexus 6p?
drew_t said:
Does anyone know if there is or will be a patch for the nexus 6p?
Click to expand...
Click to collapse
If you want use Franco.Kernel ... He has already did this. Find it at N6P thread, not here.
apatal said:
Subbed. I'll be waiting for the N4F26I build. I miss using Android Pay.
Click to expand...
Click to collapse
+1
I am waiting for N4F26I build.
Updated OP for N4F26I. Unfortunately, my 5X started bootlooping (hardware issue) so I don't have the device to test it with anymore
Updated for N4F26O.
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.
Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.
I believe It's because it requires new magisk template. Give developers some time to update.
working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.
MarcTremonti said:
working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.
Click to expand...
Click to collapse
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.
theduke7 said:
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.
Click to expand...
Click to collapse
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.
MarcTremonti said:
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.
Click to expand...
Click to collapse
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!
theduke7 said:
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!
Click to expand...
Click to collapse
Yea bluspark is enforcing. I guess they are on gitlab from freedomOS.(check FOS thread for gitlab link)
But i guess easiest way would be just to flash freedomOS. Its nothing else anyway, than debloated stock ROM with a few tweaks. Everything selectable in aroma to your needs.
Try this...
kokesh said:
Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.
Click to expand...
Click to collapse
You can try this:
Update to the latest Magisk version and get everything set. for example, Snapchat and other apps that you might need to pass safety.
After that, you can downgrade to the V.12.0. And V4A it should work fine.
The only bad thing here is that you can't use Android pay or pass safetynet.
This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342
I use the one from ahrion, too. Works fine.
I am 6
Sent from my ONEPLUS A3000 using Tapatalk
siwan05 said:
This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342
Click to expand...
Click to collapse
I've tried both. It installs, but once I launch Viper, it asks either for driver install, or shows the driver state as abnormal. Never has any effect on the audio.
For example, I can't install this ROM. https://androidfilehost.com/?fid=529141701856461698
When I install this ROM, the system doesn't boot
But I can install this ROM. https://androidfilehost.com/?fid=95916177934523996
So what's the problem?
dogukans3131 said:
For example, I can't install this ROM. https://androidfilehost.com/?fid=529141701856461698
When I install this ROM, the system doesn't boot
But I can install this ROM. https://androidfilehost.com/?fid=95916177934523996
So what's the problem?
Click to expand...
Click to collapse
which version of twrp are you running?
smart-t78 said:
which version of twrp are you running?
Click to expand...
Click to collapse
I don't use twrp.I'm using PhilZ Touch Recovery 6.59.2
dogukans3131 said:
I don't use twrp.I'm using PhilZ Touch Recovery 6.59.2
Click to expand...
Click to collapse
and thats the cause of your problem. philz touch recovery is out of date and cant handle unified espressowifi builds. if you want to use the latest roms, update to the latest common twrp by android-andi
smart-t78 said:
and thats the cause of your problem. philz touch recovery is out of date and cant handle unified espressowifi builds. if you want to use the latest roms, update to the latest common twrp by android-andi
Click to expand...
Click to collapse
the same problem was repeated for recovery.When I flash this recovery,it doesn't boot https://androidfilehost.com/?fid=673368273298980762
( I flash it using TWRP 3.0.0-0)
But when ı flash TWRP 3.0.0-0 for P5110( https://androidfilehost.com/?fid=24407100847293583 )It works perfectly
dogukans3131 said:
the same problem was repeated for recovery.When I flash this recovery,it doesn't boot https://androidfilehost.com/?fid=673368273298980762
( I flash it using TWRP 3.0.0-0)
But when ı flash TWRP 3.0.0-0 for P5110( https://androidfilehost.com/?fid=24407100847293583 )It works perfectly
Click to expand...
Click to collapse
which rom do you want to install?
when you run a unified common twrp, you cant install older device specific roms. if you run an older device specific twrp, you cant install newer unified roms.
smart-t78 said:
which rom do you want to install?
when you run a unified common twrp, you cant install older device specific roms. if you run an older device specific twrp, you cant install newer unified roms.
Click to expand...
Click to collapse
I want to install newer unified ROMs, but I can't install anything for Unified , I can only install device specific ROM and TWRP
If I install anything for "Unified espresso" (ROM, TWRP, Kernel etc.), the system will not boot, but if I install anything for device specific, the system will boot successfully
dogukans3131 said:
I want to install newer unified ROMs, but I can't install anything for Unified , I can only install device specific ROM and TWRP
If I install anything for "Unified espresso" (ROM, TWRP, Kernel etc.), the system will not boot, but if I install anything for device specific, the system will boot successfully
Click to expand...
Click to collapse
so what was the last installed samsung stock rom? 4.2.2 or 4.0.4?
smart-t78 said:
so what was the last installed samsung stock rom? 4.2.2 or 4.0.4?
Click to expand...
Click to collapse
4.2.2
dogukans3131 said:
4.2.2
Click to expand...
Click to collapse
ok.
next case is there replaced hardware in your tab (e.g mainboard, display)? you need a special kernel then. look here https://forum.xda-developers.com/ga...nified/kernel-anykernel-t3484739/post74352635
smart-t78 said:
ok.
next case is there replaced hardware in your tab (e.g mainboard, display)? you need a special kernel then. look here https://forum.xda-developers.com/ga...nified/kernel-anykernel-t3484739/post74352635
Click to expand...
Click to collapse
No
dogukans3131 said:
No
Click to expand...
Click to collapse
are you sure. maybe its a refurbished tab. try it out. install common twrp + unified rom + special kernel for your device
smart-t78 said:
are you sure. maybe its a refurbished tab. try it out. install common twrp + rom + special kernel for your device
Click to expand...
Click to collapse
Is this the kernel I need to install?
anykernel-2017-11-04-17-13-p5110-only.zip
And is this kernel compatible with Kitkat?(I'm using cm11)
dogukans3131 said:
Is this the kernel I need to install?
anykernel-2017-11-04-17-13-p5110-only.zip
And is this kernel compatible with Kitkat?(I'm using cm11)
Click to expand...
Click to collapse
backup your current system. after that try a marshmallow rom (e.g lineage 13). only to be sure
dogukans3131 said:
Is this the kernel I need to install?
anykernel-2017-11-04-17-13-p5110-only.zip
And is this kernel compatible with Kitkat?(I'm using cm11)
Click to expand...
Click to collapse
no, this kernel isnt compatible with kitkat.
smart-t78 said:
no, this kernel isnt compatible with kitkat.
Click to expand...
Click to collapse
I just downloaded Cyanogenmod 13 (device specific). Does this kernel work with device-specific ROMs? If it works, I'll try to flash the latest Unified TWRP first. If it works, I'll install the Unified ROMs.
The second question is, can I install cm 13 without factory reset(on CM 11)
dogukans3131 said:
I just downloaded Cyanogenmod 13 (device specific). Does this kernel work with device-specific ROMs? If it works, I'll try to flash the latest Unified TWRP first. If it works, I'll install the Unified ROMs.
The second question is, can I install cm 13 without factory reset(on CM 11)
Click to expand...
Click to collapse
1. i think there is no need for the special kernel on device specific roms. keep in mind that device specific builds wont be supported and wont get updates amymore.
2. no, you cant upgrade from cm11 to cm13 without factory reset. clean install is needed
smart-t78 said:
1. i think there is no need for the special kernel on device specific roms. keep in mind that device specific builds wont be supported and wont get updates amymore.
2. no, you cant upgrade from cm11 to cm13 without factory reset. clean install is needed
Click to expand...
Click to collapse
No, I want to install this kernel because I want to install Unified TWRP. If it works, then install Unified ROM
dogukans3131 said:
No, I want to install this kernel because I want to install Unified TWRP. If it works, then install Unified ROM
Click to expand...
Click to collapse
You can install unified twrp (or any other version of twrp) without installing the kernel. The rom and the kernel you have installed are completely independent of the twrp recovery. If you want to install a unified rom with a custom kernel you must first install unified twrp, then clean flash the rom and after that flash the kernel.
john99ap said:
You can install unified twrp (or any other version of twrp) without installing the kernel. The rom and the kernel you have installed are completely independent of the twrp recovery. If you want to install a unified rom with a custom kernel you must first install unified twrp, then clean flash the rom and after that flash the kernel.
Click to expand...
Click to collapse
Unfortunately, I can't enter the recovery mode when I flash Unified TWRP (after the Samsung Galaxy Tab 2 logo, the screen goes black and remains until I restart the system). I can only enter the recovery mode when I flash device specific TWRP