Database Users

Cm12.1 optimized

Hi.
I am not quite sure how to proceed even after going through some threads.
I've got Antares CM12.1 (12.1-20150428-NIGHTLY-jfltexx) on my S4 GT-I9505 plus
CWM v6.0.4.4
Does it make sense to upgrade to CM12.1 optimized or wait for the final version?
It is recommended to use TWRP Recovery v2.8.6.0 instead of CWM.
Can I just flash the TWRP zip via CWM and It'll be fine? (TWRP replaces CWM?)
I don't want to do a clean install, just upgrade.
Thanks!

PePeMoke said:
Hi.
I am not quite sure how to proceed even after going through some threads.
I've got Antares CM12.1 (12.1-20150428-NIGHTLY-jfltexx) on my S4 GT-I9505 plus
CWM v6.0.4.4
Does it make sense to upgrade to CM12.1 optimized or wait for the final version?
It is recommended to use TWRP Recovery v2.8.6.0 instead of CWM.
Can I just flash the TWRP zip via CWM and It'll be fine? (TWRP replaces CWM?)
I don't want to do a clean install, just upgrade.
Thanks!
Click to expand...
Click to collapse
It's not really an upgrade. They are different roms. Sure, they are both by the same developer. But on is stock AOSP and one has Optimizations to make it faster and smoother, I guess.
Doing a clean installation is recommended to avoid issues and bugs. You can, of course, dirty flash, but don't complain about problems
I would recommend you TWRP. It's easier to use and I haven't had any problems with it so far. I use version 2.8.3.0.
Flashing it using the zip should be fine.

GDReaper said:
It's not really an upgrade. They are different roms. Sure, they are both by the same developer. But on is stock AOSP and one has Optimizations to make it faster and smoother, I guess.
Doing a clean installation is recommended to avoid issues and bugs. You can, of course, dirty flash, but don't complain about problems
I would recommend you TWRP. It's easier to use and I haven't had any problems with it so far. I use version 2.8.3.0.
Flashing it using the zip should be fine.
Click to expand...
Click to collapse
Thanks mate!
The TWRP Recovery v2.8.6.0 I've got installed will convert to F2FS automatically?
Because in the instructions it says "To convert cache and data partitions to F2FS look in post above post."
But in the next line it says "System partition is automatically converted to F2FS at ROM's installation"
So I just flash the ROM via TWRP and it will do so?

PePeMoke said:
Thanks mate!
The TWRP Recovery v2.8.6.0 I've got installed will convert to F2FS automatically?
Because in the instructions it says "To convert cache and data partitions to F2FS look in post above post."
But in the next line it says "System partition is automatically converted to F2FS at ROM's installation"
So I just flash the ROM via TWRP and it will do so?
Click to expand...
Click to collapse
F2FS is optional. You don't have to convert. You can just flash it with your default file system (ext4).
But you if do want to convert and flash that rom, then use the recovery provided by the rom developer. There is a link in the thread that takes you to a modified version of TWRP I think
Note: Converting will wipe the internal memory..

GDReaper said:
F2FS is optional. You don't have to convert. You can just flash it with your default file system (ext4).
But you if do want to convert and flash that rom, then use the recovery provided by the rom developer. There is a link in the thread that takes you to a modified version of TWRP I think
Note: Converting will wipe the internal memory..
Click to expand...
Click to collapse
Ok got that.
I flashed the suggested TWRP for that ROM.
But it says in red "System partition is automatically converted to F2FS at ROM's installation"
So doesn't that mean that it will do the converting anyway?
It's the Antares cm12.1 optimized build by the way.

PePeMoke said:
Ok got that.
I flashed the suggested TWRP for that ROM.
But it says in red "System partition is automatically converted to F2FS at ROM's installation"
So doesn't that mean that it will do the converting anyway?
It's the Antares cm12.1 optimized build by the way.
Click to expand...
Click to collapse
As I said, using the TWRP recovery suggested by the developer will convert your file system to F2FS.
IF you WANT to convert, use that one.
IF you DO NOT WANT to convert, then download TWRP from their site or somewhere else. One that is not modified

GDReaper said:
As I said, using the TWRP recovery suggested by the developer will convert your file system to F2FS.
IF you WANT to convert, use that one.
IF you DO NOT WANT to convert, then download TWRP from their site or somewhere else. One that is not modified
Click to expand...
Click to collapse
The OP is right, my 12.1 Optimized automatically converts /system to F2FS at ROM's installation. I will soon revert this to let the user choose between ext4 and F2FS and to fix installation issues on recoveries that don't have mkfs.f2fs binary inside ramdisk
TWRP 2.8.6.0 is suggested because it has the maximum compatibility with Android 5.1
Differences between official TWRP and my F2FS-compatible? Just a plus: management support for this file system, the other things are identical
Inviato dal mio GT-I9505

AntaresOne said:
The OP is right, my 12.1 Optimized automatically converts /system to F2FS at ROM's installation. I will soon revert this to let the user choose between ext4 and F2FS and to fix installation issues on recoveries that don't have mkfs.f2fs binary inside ramdisk
TWRP 2.8.6.0 is suggested because it has the maximum compatibility with Android 5.1
Differences between official TWRP and my F2FS-compatible? Just a plus: management support for this file system, the other things are identical
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
I know he's right.
I was just trying to figure out if he really wants to convert or not.
To me it seemed as if he thought F2FS is obligatory in order to run your rom. So I made sure he gets the point that it isn't

AntaresOne said:
The OP is right, my 12.1 Optimized automatically converts /system to F2FS at ROM's installation. I will soon revert this to let the user choose between ext4 and F2FS and to fix installation issues on recoveries that don't have mkfs.f2fs binary inside ramdisk
TWRP 2.8.6.0 is suggested because it has the maximum compatibility with Android 5.1
Differences between official TWRP and my F2FS-compatible? Just a plus: management support for this file system, the other things are identical
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Thank you for the answer first of all.
I wanted to root my device again after the 12.1 optimized build installed,
but when I flash the matching tar file (cf-autoroot bye chainfire) via Odin SuperSU is not installed and
when I download it from the playstore it cannot update the binary..
you know why is that?

Ok I've got root access by installing the SUperSU update via TWRP.
But why doesn't it work the other way?
I had no problems with doing so in your 12.1 nightly..
Bye the way, great ROMs!!

PePeMoke said:
Ok I've got root access by installing the SUperSU update via TWRP.
But why doesn't it work the other way?
I had no problems with doing so in your 12.1 nightly..
Bye the way, great ROMs!!
Click to expand...
Click to collapse
The rom is already rooted. But you have to enable root first. The rom developer (AntaresOne in this case) posted instructions in the rom thread on how to do that.
But installing SuperSU from the market or via a flashable zip is also good. I've had problems with the CM Superuser app.

PePeMoke said:
Thank you for the answer first of all.
I wanted to root my device again after the 12.1 optimized build installed,
but when I flash the matching tar file (cf-autoroot bye chainfire) via Odin SuperSU is not installed and
when I download it from the playstore it cannot update the binary..
you know why is that?
Click to expand...
Click to collapse
CF auto-root is only for stock rom. It's NOT for CM 12.1. I would reflash CM 12.1 without wiping just to make sure CF auto-root is gone.
Every CM rom contains root. You just have to enable it like GDReaper told you.

Thanks guys!
Runs smooth and I have root access via cm.

recover the kernel from rom

hi folks,
im not shure if i am right with my request here.
how or generally is it possible to save the kernel from my current rom? is a software out there (found no way with TWRP or CWM) or a special recovery or a way with a terminal script or, or, or...?
slimrom is running on my n9005 but they don't provide a kernel download and i want to test others like lean-kernel but not without a kernel backup....
thx in advance

Open the rom zip and extract the kernel .

The other option is to take a backup of the /boot partition, which is the kernel + initial ramdisk.

sorry for the delay, thx 4 all

How to Root Honor 8 FRD-L09 (NOUGAT 7.0 EMUI 5.0 With Bluetooth, NFC, system apps)

I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
I have only tested this with the device: (Honor 8 FRD-L09)
If anyone got this working on other devices please leave a comment so I can add it to this list for other people to see.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this with OldDroids TWRP or with surdu_petrus TWRP: Link(36.2MB) and Link(24,2MB)
1- Flash OldDroids or surdu_petrus TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid, surdu_petrus and phhusson

thierrybla said:
I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this only with OldDroids TWRP: Link(36.2MB)
1- Flash OldDroids TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid and phhusson
Click to expand...
Click to collapse
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM

omartins said:
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
Click to expand...
Click to collapse
I have only tested it on the FRD-L09
I can't say for sure if it works on the others, I'm sorry.
If you got this working on a different device please let me know.

Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?

david320te said:
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
Click to expand...
Click to collapse
Yes SuperSU doesn't work as far as I know you need Phh Superuser.
But if you already have nougat 7.0 B380 you can just begin at the boot.img installing step and it should work for you too.
Good luck!

Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP

david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The difference is that the TWRP that I linked can flash .img 's
wich you need to flash the boot.img
Try to get back in TWRP and start at step 1 just do the whole guide then your phone should boot again

david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Q: Why does booting take so long?
A: Because of the decryption process which need to finish
its work before twrp tries to access /data partition.
Click to expand...
Click to collapse
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.

N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.

N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
You are right it is for P9 but it worked for me regardless though :fingers-crossed:

david320te said:
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
Click to expand...
Click to collapse
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot bootloader),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.

N01tra said:
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot fastboot),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
Click to expand...
Click to collapse
I had the same as you describe here but I fixed it by flashing the 2 files I posted up here (a and b)

After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/

david320te said:
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
Click to expand...
Click to collapse
I'm glad to hear it works! :highfive:
TWRP backups never worked for me I always just flash it clean and then have titanium backup do the rest
Have a nice day

Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.

fourcc said:
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
Click to expand...
Click to collapse
Hey,
Your question is not stupid I can see why you are confused but everytime I tried to root or preroot something it didn't work for me I also run 380 and once I tried the prerooted 378 made by atariii it worked so there is no reason te be skeptical because I was in the same situation as you and this worked for me just give it a try you won't be disappointed

Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!

fourcc said:
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
Click to expand...
Click to collapse
Tell me how it went !
Goodluck!

Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!

fourcc said:
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
Click to expand...
Click to collapse
that's fine too I'm glad it worked good for you!
Have a nice day!

Bootloop for WAS-LX2 ElementalV2

SuperSUv2.82-EMUI5-noverity-Permissive.zip
from: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP recovery
from: https://forum.xda-developers.com/p10-lite/development/beta-t3619496
Elemental V2
from: https://forum.xda-developers.com/p10-lite/development/rom-emui-5-1-huawei-p10-lite-dual-sim-t3733095
(unchanged for first screen, picked stock music and WAS-LX1 patch, unchanged for third screen)
Installed the above
Now I'm stuck in a bootloop(?)
It boots but after like 1 - 2 minutes it restarts itself
I tried let it restart itself a bunch of times and it just ends in Huawei's eRecovery
I only know the model for my phone: WAS-LX2 (no exact roms for LX2)
Hopefully someone can help <3

CheesyBen said:
SuperSUv2.82-EMUI5-noverity-Permissive.zip
from: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP recovery
from: https://forum.xda-developers.com/p10-lite/development/beta-t3619496
Elemental V2
from: https://forum.xda-developers.com/p10-lite/development/rom-emui-5-1-huawei-p10-lite-dual-sim-t3733095
(unchanged for first screen, picked stock music and WAS-LX1 patch, unchanged for third screen)
Installed the above
Now I'm stuck in a bootloop(?)
It boots but after like 1 - 2 minutes it restarts itself
I tried let it restart itself a bunch of times and it just ends in Huawei's eRecovery
I only know the model for my phone: WAS-LX2 (no exact roms for LX2)
Hopefully someone can help <3
Click to expand...
Click to collapse
Elemental V2 already have preinstalled SuperSu. So if You try to root again your device will enter in bootloop. Those are parched stock roms and not compatibile with standard SuperSu or Magisk installers.
Regards

Alexxxx1 said:
Elemental V2 already have preinstalled SuperSu. So if You try to root again your device will enter in bootloop. Those are parched stock roms and not compatibile with standard SuperSu or Magisk installers.
Regards
Click to expand...
Click to collapse
I wiped data and did a factory reset and only installed the rom
Still does the same thing

CheesyBen said:
I wiped data and did a factory reset and only installed the rom
Still does the same thing
Click to expand...
Click to collapse
Than, u probably have Ext4 formated Data partition from some reason.... . You need to change from Ext4 in F2FS using Twrp..
Or use service rom to rollback to stock.
Edit. I ve just saw, dude....... use Twrp Elemental. You didnt followed basic instructions for flashing Elemental rom. You can not flash Elemental with other twrp.
All the best.

Alexxxx1 said:
Than, u probably have Ext4 formated Data partition from some reason.... . You need to change from Ext4 in F2FS using Twrp..
Or use service rom to rollback to stock.
Edit. I ve just saw, dude....... use Twrp Elemental. You didnt followed basic instructions for flashing Elemental rom. You can not flash Elemental with other twrp.
All the best.
Click to expand...
Click to collapse
I like did every combination I had at my disposal
I guess elemental v2 doesn't support lx2? I'll wait for v3 but it has been UPLOADING for like a week now

NEW KERNEL /FIX FOR BOOTLOOP/Magisk installation in nougat z3+/z4

NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootlooped​credits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
in cmd window :fastboot flash boot new_kernel.img
IMP:steps 1 & 2 are can also be used when u have met with an unexpected bootloop/restart problem at any time( if u don't want to flash the complete stock ftf,this boot image will help u in letting ur device come out of bootloop.
3.proceeding to our main thread....now boot into recovery & flash "magisk.zip"
4.wipe cache & dalvik.and reboot.
PROPERTIES OF THE KERNEL (new_kernel.img:---
Build 32.4.A.1.54
1. Sony RIC- disabled.
2. DM-Verity- disabled.
3. TWRP- disabled.
4. DRM Fix- enabled.
5. Superuser / root- Not present. ( flash magisk its better)
6. Busybox- Not present
7.many more tweaks to reduce heat & increase battery backup
LINK TO THE CONTENT
https://drive.google.com/drive/folders/1ic9zsMi576s1P9H6s1z4_g0ofSJJktIs?usp=sharing

I just want stock rooted rom with magiks
doctorsworld99 said:
NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootlooped​credits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
Click to expand...
Click to collapse
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp

Sumantomar1709 said:
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp
Click to expand...
Click to collapse
u can try flashing magisk over stock.but whenever i did that my device used to go into bootloop.thats why i've to experiment with different twrps,kernels to detect the culprit.
finally i got this awesome kernel which helped me to come out of bootloops everytime.so i will suggest to use this [near to stock ] kernel .
but u can try flashing magisk over stock.....if anything goes wrong ,,,just flash the new_kernel,,and ua fine to go with magisk.

Thnx. I will try & let u know.

thank u sirThis kernel help me from bootloop .how did u make this kernel

Champsingh909 said:
thank u sirThis kernel help me from bootloop .how did u make this kernel
Click to expand...
Click to collapse
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime

This kernel really working in bootloop.thnx

doctorsworld99 said:
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime
Click to expand...
Click to collapse
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot

Champsingh909 said:
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot
Click to expand...
Click to collapse
creating a separate thread isn't a good idea ,i'll update the details of the kernel in this thread itself,plz give me some time.

Kernel properties added.

Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.

LoaderFabi said:
Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.
Click to expand...
Click to collapse
i got frequent bootloops on installing it over stock kernel and also over m-rom .i think the kernel was the culprit.

Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?

chrnodroid said:
Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?
Click to expand...
Click to collapse
Hopefully yes,flash it as instructed.best of luck:good:

Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.

MrHands0m3 said:
Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.
Click to expand...
Click to collapse
confirmed!! this kernel is the ****!.. try it... (don't blame me if you brick your device)

The link to download the kernel won't work anymore, is there a mirror?