Develop Bugs

[Recovery][FOTA]CWM and TWRP recoveries for custom ROMs

Now we have official TWRP support, so this thread will not be updated anymore. For more info about official TWRP visit this thread.
Tired waiting for someone to repack kernel with your favorite version of recovery? Or tired to run recovery script every time you update your ROM or kernel? Now you don't need any repacked kernels or recovery-scripts. Use your FOTAKernel as recovery partition!
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure) by @Dees_Troy. And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Installation:
Download zip and flash it via your current recovery. If your current recovery is unusable, you can flash it via terminal emulator:
- Extract FOTAKernel.img and place it to the root of your external SD-card
- Type su and grant root access
- Type
Code:
dd if=/ext_card/FOTAKernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.7.0
TWRP 2.8.6.0 (this and next versions are compiled for Xperia M by me)
Older versions and CWM:
TWRP 2.8.5.0 (port from Xperia L)
TWRP 2.8.4.0 (thanks to @Rohan purohit for bringimg it for Xperia L, I just ported and modded it)
TWRP 2.8.0.0/CWM (or scroll down, it's right below this post)
You can restore original FOTAKernel image by following instructions in this post (or just scroll down, it is 3rd post, lol).
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader this partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery! Here is some info from Dees_Troy.

Download
TWRP 2.8.6.0>>>
TWRP 2.8.5.0>>>
TWRP 2.8.4.0>>>

Restoring original image
- You can restore original FOTAKernel flashing it via Flashtool by flashing any firmware (just uncheck everything in "wipe" section and uncheck everything in "exclude" section excluding "FOTA" like in attached screenshot).
- Or install attached zip via recovery or flash FOTAKernel.img from archive as it is written in OP.

cucumber09 said:
TWRP version is 2.8.0.0, because I could not boot 2.8.3.0 this way (maybe due to ramdisk size limitations), I'll look for this later and will try to fix it
Click to expand...
Click to collapse
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea

kh34d said:
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea
Click to expand...
Click to collapse
I don't know for sure. Download both recoveries, try to flash one that differs from yours and reboot recovery. If it changes, that means it works on CM11 kernel. BTW, even if it doesn't work on CM11, it will work when you will flash CM12 kernel. So you can flash it to be prepared.

Some one please uploade original fota kernel, i'm forgot to backup them .. thanks

itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Okay, I will upload original FOTAKernel.

itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Everything about restoring is in 3rd post.

cucumber09 said:
Everything about restoring is in 3rd post.
Click to expand...
Click to collapse
Thangs, now all problem will be fixed ..

@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?

KHM90 said:
@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?
Click to expand...
Click to collapse
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.

cucumber09 said:
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.
Click to expand...
Click to collapse
Ok thx, Not needed just wanna know whether it will work or not
btw, FOTA kernel awesome idea:good:

I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...

ndrancs said:
I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...
Click to expand...
Click to collapse
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.

I'm confused, does it work for locked bootloader?

pincheraro said:
I'm confused, does it work for locked bootloader?
Click to expand...
Click to collapse
No way. It even won't work on stock kernel with unlocked BL.

@cucumber09 Which build is the attached FOTA restore zip from? .9?

elmkzgirxp said:
@cucumber09 Which build is the attached FOTA restore zip from? .9?
Click to expand...
Click to collapse
No, it is from earlier build, but also from 4.3. From first 4.3 build, as I remember.

cucumber09 said:
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.
Click to expand...
Click to collapse
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?

ndrancs said:
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?
Click to expand...
Click to collapse
I read these sources. And 49th line defines size of uncompressed ramdisk. But now I am not sure, which one is used in our kernel. I suppose, that newer one.

Flashable TWRP v2.8.7.0 for Sony Z3+ E6553 Ivy_Kitakami

Introduction
Disclaimer: While this TWRP has been tested by myself on my own device to flash, wipe and backup, I make no warranties as to it's performance. Use at your own risk.
WARNING: flashable version contains a kernel boot image which will be flashed to your device along with the recovery image.
Click to expand...
Click to collapse
Installation instructions
This recovery image is for the E6553 single SIM Z3+. Do not use it on another model.
This recovery image requires an unlocked bootloader. You will lose some functionality on your phone if you unlock your bootloader
Do your research and make sure you're using the latest version of the relevant tools if you do decide to unlock.
DO NOT enable MyXperia functionality if you've unlocked your bootloader. You will brick your device.
This first download of this recovery image CANNOT be flashed to your phone and must be used in fastboot mode only
The second download is a flashable recovery
Use the first version to flash the second dual-boot.zip version
Unzip the recovery.zip file to extract the recovery.img file to use in fastboot mode
Code:
C:\>adb reboot bootloader
C:\>fastboot boot recovery.img
C:\>adb push dual-boot.zip /sdcard/dual-boot.zip
C:\>adb push dual-boot.zip.md5 /sdcard/dual-boot.zip.md5
Click to expand...
Click to collapse
Now use the TWRP install feature to install dual-boot.zip. Follow the prompts of the Aroma graphical installer.
CAVEAT: this extends the boot time by about 5 - 10 seconds as ramdisk images need to be unpacked and there's a wait on a keypress to determine whether to enter recovery mode. In order to boot into recovery, press power on. When you see the yellow LED come on then press the down volume button once or twice. You will then boot into TWRP.
NOTE: the dual-boot.zip installs a new 28.0.A.8.251 kernel. If you're using the autoroot kernel from Devries you will need to flash SuperSU to re-root your device
This dual boot/recovery works by flashing the recovery image to the FOTAkernel partition. A custom ramdisk image contains the normal boot image. If the down volume keypress is detected, then the recovery ramdisk is automatically extracted from the FOTAKernel partition and flow of control switches to recovery. If no keypress is detected then the normal ramdisk is extracted and normal android boot ensues.
Those of you who installed version 1.0 please download and install this version 1.1 to fix the error with the startup of the trim area daemon
Download
Binary
Fastboot TWRP Recovery Image v2.8.7.0-e6553-1.0 for Z3+ E6553
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 (MD5: 52d4b7d406308dbd457e8b94210b7c87)
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 - MD5
Sources @ github
device_sony_kitakami
device_sony_ivy
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: -- 29 September 2015
[new] v1.1 fix up problem in combined ramdisk preventing trim area daemon from starting correctly
[new] Flashable recovery - 28 September 2015
[new] Fixed various sys/class issues so that CPU temperature and LED / backlight control work correctly
[new] Updated to use 28.0.A.8.251 kernel (as opposed to the AOSP kernel)
[old] Initial release - 10 September 2015
Click to expand...
Click to collapse
Thanks To
The regular contributors to the Z3+ forum, among others @[NUT], @ChrisJ951, @DHGE, @Devries, @zxz0O0, @Venkat Kamesh, @AndroPlus, @Sacktreter who pass on knowledge and who make the forum a lively and cooperative place
Click to expand...
Click to collapse

People who installed version 1.0 of the Flashable TWRP must please update to version 1.1 to correct a bug.

Awesome work.
Glad you were able to get the screen working for it! Boots up fine w/o issue for me

This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+

AMoosa said:
This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+
Click to expand...
Click to collapse
I'd venture to suggest that it's highly unlikely that locked bootloader recovery could work. The DM_VERITY is almost a guarantor of that. Just search for CONFIG_DM_VERITY or Verity in the Z3+ forums for more info.
Even if an exploit works, the second it modifies the system partition, the kernel panics and refuses to boot. The only way of preventing that is to flash a new kernel or edit the ramdisk to remove the verity key. And the only way to flash a new kernel / edit the ramdisk is to unlock the bootloader.

Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
This is correct behaviour. You're not actually flashing the recovery image, just temporarily booting a recovery kernel and associated ramdisk. Sony Xperia devices don't have a recovery partition, or more accurately, they don't have a bootloader than can check and load a boot image from a recovery partition.
Technically it's possible to make the boot image check for a ramdisk on another partition and use this instead of the normal ramdisk, but this is step two. Sony should be releasing an open recovery bootloader fairly soon for the Z3+ which will allow this recovery image to be flashed. It's already been released for other devices.
Until Sony releases open recovery for Z3+ or I spend the time trying to implement a feature that probably only has days or weeks of utility (until Sony releases the open recovery for Z3+) , you're stuck with a TWRP that you need to launch every time in fastboot mode.

On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
New version now flashable so that you can boot into recovery...read top post carefully before using.

serrin85 said:
On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot
Click to expand...
Click to collapse
Fixed in latest version

http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..

deecept said:
http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..
Click to expand...
Click to collapse
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.

dl12345 said:
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.
Click to expand...
Click to collapse
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!

deecept said:
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!
Click to expand...
Click to collapse
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks

dl12345 said:
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks
Click to expand...
Click to collapse
HI dl12345,
this recovery support Dual model? E6533

hi.question...i get remote: dtb not found error when trying to boot the recovery..any ideas?

didnt get a thing... how do i install?

please, release TWRP for 6533 too
we need custom recovery so bad

Dathrex said:
please, release TWRP for 6533 too
we need custom recovery so bad
Click to expand...
Click to collapse
Pleaseee ????

Brother, please, help us with twrp to E6533, please.
Enviado de meu E6533 usando Tapatalk

[CBUMP][BOOT] Bump Your Current Boot Image

BUMP Your Current Boot Partition
Supports all of G2​
Will work for other devices that use BUMP, so long as boot is located at:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Uses:
1) Fix boot partition after flashing SuperSU.
2) Flash any boot.img you want without BUMPing it first. Flash this zip after flashing the non-BUMPed boot.img.
3) Fix boot cert error.**
**This will fix boot cert error as long as you are on JB/KK bootloader. If you broke your phone and got boot cert error by upgrading your bootloader to LP, this won't help.
4) For Dev: The cbump binary in the zip is built static. Feel free to yank it out and use it for your own purposes.
Use: Simply flash in TWRP.
Download:
https://www.gregtwallace.com/
Download is under Miscellaneous.
Credits:
BUMP Team
Open BUMP Team
CBump Dev (who deleted his account, not sure who it was)
--Dev's Source: https://github.com/blastagator/cbump
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal

res 1

Wow! Awesome thing for our G2.
Gonna test it, im impressed, thank you buddy!
Wysłane z mojego LG-D802 przy użyciu Tapatalka

@InsideMuz
ok i tried it again on two different ROMS (AiCP-MM.11.0[030516] and crDroid[030616])
Variant: D802
flash in this order:
Code:
1. ROM
2. GAPPS
3. SuperSU.v2.68
4. CBUMP
@blastagator
thanks for this CBUMP Tool.

fLipz said:
@InsideMuz
ok i tried it again on two different ROMS (AiCP-MM.11.0[030516] and crDroid[030616])
Variant: D802
flash in this order:
Code:
1. ROM
2. GAPPS
3. SuperSU.v2.68
4. CBUMP
@blastagator
thanks for this CBUMP Tool.
Click to expand...
Click to collapse
You're saying that I should install it after clean install?

InsideMuz said:
You're saying that I should install it after clean install?
Click to expand...
Click to collapse
yes sir, 'coz i always do a Clean iNstall everytime i flashed a ROM and that is my routine 1 2 3 4
or try to boot to recovery on your current ROM and try to flash SuperSU.v2.68 1st then followed by CBUMP.

@blastagator thanks for your perfect tool working awesome

fLipz said:
yes sir, 'coz i always do a Clean iNstall everytime i flashed a ROM and that is my routine 1 2 3 4
or try to boot to recovery on your current ROM and try to flash SuperSU.v2.68 1st then followed by CBUMP.
Click to expand...
Click to collapse
Don't work anyway.

Finally worked with SuperSU 2.70!

Did not work with superuser.zip from jan 31 2016. Still get a cert error.

Ummm... Hello @blastagator
I'll try to explain this swiftly...
I made a LG Framework Installer for LG G2 (and finally it installed), also the thread is here
It works by installing all required files to system and then modifies the ramdisk so that LG Framework will be added to BOOTCLASSPATH. The installer is working and changes are verified by re-extracting ramdisk to a connected computer and checking BOOTCLASSPATH on init.environ.rc.
And here is the problem, I know that cert will be broken so I used your CBUMP but booting still gives me secure boot errors... Please help us

xxoscarxx28 said:
Ummm... Hello @blastagator
I'll try to explain this swiftly...
I made a LG Framework Installer for LG G2 (and finally it installed), also the thread is here
It works by installing all required files to system and then modifies the ramdisk so that LG Framework will be added to BOOTCLASSPATH. The installer is working and changes are verified by re-extracting ramdisk to a connected computer and checking BOOTCLASSPATH on init.environ.rc.
And here is the problem, I know that cert will be broken so I used your CBUMP but booting still gives me secure boot errors... Please help us
Click to expand...
Click to collapse
Have you tried saving the new boot.img, using the normal python bump, and then reflashing the python bump version? That will at least tell you if it is CBUMP or some other issue.

blastagator said:
Have you tried saving the new boot.img, using the normal python bump, and then reflashing the python bump version? That will at least tell you if it is CBUMP or some other issue.
Click to expand...
Click to collapse
I tried, and python worked. Maybe it is CBUMP, but well... I looked through the source code of both and then just appended the 6 bytes of lg_magic to the boot.img and it works! Hahahahha
Anyway, thanks for your response
LG Framework is now ready
One down, two to go
Hooks to framework.jar (xposed?)
Upgrade API lvl of lp apps (permission handling rework to make mm happy)

I tried to make a porting of miui 8 from n5 and after flash rom i flashed this script for bumping boot image. In the reboot anyway i got boot security error. Why? (for doing porting i must decompile and recompile kernel)

Hi there guys!
Well it seems there's a lot of stuff around Bump and LG and devs that I do not know.. I read something but I really didn't get the basic stuff, I saw a few bump threads closed but then I find this one..
I have a few question for whom who may know, if you please..
I have an LG G Pad 7 where the latest stock is Lollipop; to root and install TWRP I got to downgrade to KK, as many of LG owers got to; then I can flash ROMs. But what if I need a rooted STOCK? The only Stock available for me are kdz, which completely erase any stuff. If I try to root the Lollipop stock I cannot boot anymore because of boot error!
So I would like to know if I took the boot.img from a rooted KK rom and then bump it, could I flash it back to Lollipop stock so that I'll be able to root it? Also, if it is possible, do I need a "special" version of Bump tool or can I use the G2 one, for example?
Well, I think it's all..
Thanks a lot for paying attention, see you!

Thanks so much!
I tried to install Magisk on my vs985 (G3 verizon) and of course got slammed by the flashing red and blue lights secure boot error.
Little bit of googling led me here, and this fixed it right up.

does any one know if this can be made to work for lg devices such as vs425pp and k120 ?

Hi. Apologies for asking this here. I'm a bit desperate, and I've been searching for ways to get magisk installed on my g3 (f460k - the korean cat.6 variant with snapdragon 805). My search brought me here. Unfortunately, my device is dead dev-wise. I'm wondering if this would work on Nougat? I'd like to flash Magisk then this to avoid secure boot error. Thanks.
Edit:
Flash it after flashing magisk on f460k running Nougat and it works!!! Thank you op for this!

I edited boot.img (came out at 11 mb instead of 16 but contents seems as the original).
Entered TWRP and installed edited img. (Cannot enter fastboot)
Installed your zip. Script seemed to execute correctly.
Reboot (withot wipe cache/dalvik)
Got this error on the top left corner of the screen with LG logo
secure booting error boot certification verify
Had to re-enter recovery and install back original boot.img
Any ideas? Thanks

http://k.japko.eu/boot-img-manipulation.html
used above procedure, just unpacked and repacked, got 16 mb boot.img, installed tru twrp, installed cbump, got into fastboot

[KERNEL][STOCKMM]Radium Kernel R1[OC/UC][UBER]

RADIUM KERNEL FOR THE MOTO G 2014!
This is my first kernel! This is primarily a companion to my Radium Redefined M rom, but I'm also putting it up here for people who don't like to flash roms (Well, they're missing out, aren't they ). It'll start off as close to stock, I'll add features slowly (Keep those requests comin' in!)
NOTE- THIS KERNEL IS ONLY FOR STOCK/STOCK BASED ROMS. DO NOT FLASH IT ON CM/AOSP ROMS. ANYWAYS, I'M NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE
So here we go!-
Features-
OC/UC (1.5GHz/96MHz)
Compiled with UBERTC 4.9
That's it for now
How to flash-
1. Download the latest version
2. Reboot to recovery
3. Flash (You need not wipe anything)
4. Reboot and enjoy!
I know, the features are very less. But it starts off this way. I'm still learning. I'll be adding more governors/hotplugs slowly
Downloads-
LATEST VERSION (R1)
Mirror
ALL BUILDS (FOLDER)
Credits-
1. @zakee94 - For help with OC and ramdisk changes
2. @attack11 - For help with source code
XDA:DevDB Information
Radium Kernel , Kernel for the Moto G 2014
Contributors
Vidhanth
Source Code: https://github.com/Vidhanth/Radium-Kernel
Kernel Special Features: Overclocked and Underclocked to 1.5 GHz and 96 MHz. Optimized with Uber toolchain.
Version Information
Status: Stable
Created 2016-05-15
Last Updated 2016-05-15

RECOMMENDED SETTINGS-
As of now, the kernel is pretty much stock. So it's perfect out of the box.
You can do one thing tho- Change read ahead of Internal Storage to 1024 KB and externel to 4096 KB (If you have a 32 GB card. If other, set a lesser value).
I'll be updating this when we have more features

Reserved
Mine

@Vidhanth
The kernel flashes properly. However, after rebooting, root access breaks. So no root access, after booting. Wiping dalvik and cache doesn't help either. And here are the relevant screenshots.

VirenLuke said:
@Vidhanth
The kernel flashes properly. However, after rebooting, root access breaks. So no root access, after booting. Wiping dalvik and cache doesn't help either. And here are the relevant screenshots.
Click to expand...
Click to collapse
Of course that's normal. SuperSU is systemless, so it patches the boot.img. This kernel replaces your previously patched boot.img so you lose root access. To fix this, you need to flash SuperSU again

Vidhanth said:
Of course that's normal. SuperSU is systemless, so it patches the boot.img. This kernel replaces your previously patched boot.img so you lose root access. To fix this, you need to flash SuperSU again
Click to expand...
Click to collapse
Okay, I reflashed SuperSU, got systemless root working again
Everything works perfectly.

Viren said:
Okay, I reflashed SuperSU, got systemless root working again
Everything works perfectly.
Click to expand...
Click to collapse
Could you please tell me what version of supersu you used and if possible provide the link?
For already I used two versions and does not leave the bootloop

dougluna said:
Could you please tell me what version of supersu you used and if possible provide the link?
For already I used two versions and does not leave the bootloop
Click to expand...
Click to collapse
SuperSU version 2.62 :
https://download.chainfire.eu/748/SuperSU/?
The problem is that beyond 2.62, the method of rooting changed from patching the boot image for a systemless root, to the old fashioned method of /system rooting. While the newer method works on all custom ROMs, it so happens that the stock Motorola ROM requires you to perform a systemless root. So go ahead and install the version in that link. After that, you can boot up, go to the play store, and update from there to version 2.65, which is the current stable build.

For already I used two versions and does not leave the loop boot
Sent from my Moto G 2014 using XDA-Developers mobile app

Viren said:
SuperSU version 2.62 :
https://download.chainfire.eu/748/SuperSU/?
The problem is that beyond 2.62, the method of rooting changed from patching the boot image for a systemless root, to the old fashioned method of /system rooting. While the newer method works on all custom ROMs, it so happens that the stock Motorola ROM requires you to perform a systemless root. So go ahead and install the version in that link. After that, you can boot up, go to the play store, and update from there to version 2.65, which is the current stable build.
Click to expand...
Click to collapse
Thank you very much

stuck on boot screen

ditoparlo said:
stuck on boot screen
Click to expand...
Click to collapse
Please answer two questions:
1. Are you using a stock ROM?
In other words, are you using Radium Redefined?
Or are you using any other ROM out there?
2. Did you flash SuperSU 2.62?
Or did you flash any other version than this?
If the answer to either is yes, please go read the OP and all the posts that follow, thoroughly. That will solve your problems If not, then please provide more information. "Bootloop" isn't enough information to help.

Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Sent from my Moto G 2014 using XDA-Developers mobile app

sonrics1993 said:
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Click to expand...
Click to collapse
Correct me if I'm wrong, but I'm pretty sure this kernel is already built-in in the Radium's rom, so you don't need to re-flash it from this thread.

sonrics1993 said:
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
I think you can open the Radium Rom zip, the radium kernel zip and copy the system folder and the boot.img from the zip kernel to the rom kernel, replace and i think it will boot fine with radium kernel by default
AcTSkull said:
Correct me if I'm wrong, but I'm pretty sure this kernel is already built-in in the Radium's rom, so you don't need to re-flash it from this thread.
Click to expand...
Click to collapse
Its not yet i think.

sonrics1993 said:
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Try this -
Flash radium + gapps + kernel
Reboot
Flash supersu
Reboot
And are you sure it's a bootloop? The first boot takes a while. If you think it's taking too long, just force restart from the bootanimation
AcTSkull said:
Correct me if I'm wrong, but I'm pretty sure this kernel is already built-in in the Radium's rom, so you don't need to re-flash it from this thread.
Click to expand...
Click to collapse
No, Radium doesn't have it yet. It will be added in the next update
Sent from my Moto G 2014 using Tapatalk

Its a great kernel, thanks! It could be possible to add usb keyboard function? That would make it even better!
Thanks in advance

kurtxcobain said:
Its a great kernel, thanks! It could be possible to add usb keyboard function? That would make it even better!
Thanks in advance
Click to expand...
Click to collapse
Okay I'll look into it
Sent from my Moto G 2014 using XDA-Developers mobile app

Thanks for your hard work.
Maybe you want to add double tap to sleep and double tap to wake feature for the next version.

Aciong.Aksaya said:
Thanks for your hard work.
Maybe you want to add double tap to wake and double tap to wake for the next version.
Click to expand...
Click to collapse
I won't be adding that because it isn't stable, causes battery drain and doesn't work on all devices.
Sent from my Moto G 2014 using XDA-Developers mobile app

modified boot image (No DM-Verity + Disabled auto stock recovery flash on boot)

Hey there,
The reasons I modified the stock boot image was to:
*Be able to keep TWRP even with a non-rooted device.
*Disable DM-Verity checks to be able to modify the system partition to add an anti theft app that doesn't get removed if a performs a factory reset. (from phone settings or stock recovery)(ofcourse he could flash TWRP etc. but he would need some knowledge to do that, I doubt most thieves have this).
The only stuff I changed:
*Removed DM-Verity setting from DTB tree on kernel
*Commented out this part from init.rc in the ramdisk:
HTML:
service flash_recovery /system/bin/install-recovery.sh
class main
oneshot
This is the part that reflashes the stock recovery on every boot.
I'm running latest OTA (5.0.3) on my Oneplus 5T.
So if anybody minds testing and confirming this works? (it does on my device)
You can download the image here:
http://www.mediafire.com/file/5eexidj8rxddx9x/boot_NoVerity_NoAutoFlash.img
Oh and on a side note, I did this to learn so if you don't trust this you don't have to download it.
But I'd still love to hear what you think about the idea?
Greetings,
Down...

What about this anti theft app? How It works?

Deltalfa said:
What about this anti theft app? How It works?
Click to expand...
Click to collapse
It's called Cerberus.
I wanted to be able to install it as a system app without it getting wiped because of DM-Verity.
So I would install Cerberus, move to system/priv-app (as root). Then remove root and TWRP to return back to Stock recovery.
This way the thief will notice nothing when resetting the phone (either trough system settings or trough stock recovery).
The only way he can get rid of Cerberus if by flashing TWRP but I doubt he would do that.

how to modified the stock boot image in miui to Disable DM-Verity ?

Hi, is this zip still valid for latest 8.1 releases with Project Treble?
Thank you!

mom4751 said:
Hi, is this zip still valid for latest 8.1 releases with Project Treble?
Thank you!
Click to expand...
Click to collapse
I reply to myself.
No, this mod is old and likely is not good for Project Treble ROMs.
Flash this mod instead: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
This one has worked perfectly on my OP5T but i had to change recovery.
I started with official TWRP 3.2.3.0 but after flashing universal-dm-verity-forceencrypt it started to bootloop into recovery.
I had to flash Codeworkx TWRP instead. You can take it from here:
https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673