Develop Bugs

Custom kernel Z3+ E6553 - Nuke Verity / Sony RIC and allow SELinux permissive

Introduction
The stock Sony kernels use SONY RIC, SELinux and CONFIG_DM_VERITY that together make it exceptionally hard to root. With the stock kernel, it's impossible to run a modified ROM of any form (incorporating changes to the system partition). Attempting to boot with the stock kernel off a modified system partition results in a kernel stop or panic, manifested either by getting stuck on the Sony screen or a bootloop.
This kernel removes the Sony RIC and CONFIG_DM_VERITY and sets boot and runtime parameters that allow SELinux to be disabled or to be set into permissive mode. Once this kernel is flashed, you can download SuperSU flashable zip and flash it to your phone using the TWRP recovery image I posted in this forum in order to get root on your stock ROM.
This kernel contains no source patches. It's a completely stock kernel from the Sony github repository.
Click to expand...
Click to collapse
Features
SELinux configurable at boot and runtime
Sony RIC disabled
CONFIG_DM_VERITY disabled
Click to expand...
Click to collapse
Installation instructions
This boot 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.
Unzip the boot.zip file to extract the boot.img file
Code:
C:\>adb reboot bootloader
C:\>fastboot flash boot boot.img
C:\>fastboot boot recovery.img
C:\>adb push UPDATE-SuperSU-v2.46.zip /sdcard/supersu.zip
Then switch to the TWRP interface, go to the Install menu and flash /sdcard/supersu.zip. Reboot and you're rooted. You can then modify your system partition as you please.
Click to expand...
Click to collapse
NOTE: if you install Xposed you MUST wipe cache/dalvik after installation otherwise you will get an error message telling you that you are running out of storage space and any apps you install with Play store will fail the installation with a 504 error. This is NOT related to the kernel, but is caused by failing to wipe cache after installing Xposed.
Download
Binary
28.0.A.8.251 custom kernel for Z3+ E6553
TWRP Recovery Image V0.1 for Z3+ E6553
Sources @ github
Kernel config
Sony kernel-copyleft repository
Click to expand...
Click to collapse
Changelog
Code:
[B]Changelog[/B]
[new] 12 September 2015- Update to 28.0.A.8.251
[old] 10 September 2015 - Initial release
Thanks To
Code:
[url="http://forum.xda-developers.com/member.php?u=631273"]@Chainfire[/url]. What would we do without SuperSU.....
Click to expand...
Click to collapse

Awesome work, works without any issues.

I must be being really stupid....
Unable to boot into recovery without reflashing recovery.img. I must be missing something!
Otherwise no other issues to speak of. Amazing Thanks!

elladroid said:
I must be being really stupid....
Unable to boot into recovery without reflashing recovery.img. I must be missing something!
Otherwise no other issues to speak of. Amazing Thanks!
Click to expand...
Click to collapse
"Until Sony releases an open bootloader you need to use this image via fastboot boot mode."

really 28.0.A.8.251?
@dl12345
searching for 28.0.A on GitHub gave me:
28.0.A.7.xxx Updated 2 months ago by jerpelea
28.0.A.6.xxx Updated 3 months ago by jerpelea
28.0.A.4.xxx Updated 4 months ago by jerpelea
Did you try the source posted on SONY Developer?
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-28-0-a-8-251/
Does your boot.img work as a replacement for the boot.img flashed with 28.0.A.8.251 FTF?
I ask because I failed booting a boot image compiled from the SONY Developer source and an older kernel from 28.0A.7.24/31 as replacement for the image in the latest 8.251 FTF for my SGP712/karin_windy

DHGE said:
@dl12345
searching for 28.0.A on GitHub gave me:
28.0.A.7.xxx Updated 2 months ago by jerpelea
28.0.A.6.xxx Updated 3 months ago by jerpelea
28.0.A.4.xxx Updated 4 months ago by jerpelea
Did you try the source posted on SONY Developer?
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-28-0-a-8-251/
Does your boot.img work as a replacement for the boot.img flashed with 28.0.A.8.251 FTF?
I ask because I failed booting a boot image compiled from the SONY Developer source and an older kernel from 28.0A.7.24/31 as replacement for the image in the latest 8.251 FTF for my SGP712/karin_windy
Click to expand...
Click to collapse
Correct. The sources on github are old. I dowloaded the archive from the Sony website and compiled it. Yes the boot.img I compiled works perfectly as a replacement. I'm currently running it on my phone.

How to modify system partition
Hi all,
Nob question but need help urgently. After installing the kernel I'm now getting storage space almost full and error 504 due I think to some modifications to the kernel to get root. I'm aware OP did say to modify system partition but don't have a clue how to do so in order to get storage space back and also install apps. Urgent help needed pls.
Cheers and thanks for your assistance.

yawo76 said:
Hi all,
Nob question but need help urgently. After installing the kernel I'm now getting storage space almost full and error 504 due I think to some modifications to the kernel to get root. I'm aware OP did say to modify system partition but don't have a clue how to do so in order to get storage space back and also install apps. Urgent help needed pls.
Cheers and thanks for your assistance.
Click to expand...
Click to collapse
The kernel makes no modifications to the system partition and is unrooted. You need to flash SuperSU to get root.
This error you're getting is caused by the Xposed framework. You've installed the Xposed framework but you forgot to do a wipe dalvik and cache after installing. This is exactly what happens when you forget to wipe cache after installing xposed.
You can try to use the xposed uninstaller which may fix it. If not, you need to do a full wipe and reflash a ROM.

dl12345 said:
The kernel makes no modifications to the system partition and is unrooted. You need to flash SuperSU to get root.
This error you're getting is caused by the Xposed framework. You've installed the Xposed framework but you forgot to do a wipe dalvik and cache after installing. This is exactly what happens when you forget to wipe cache after installing xposed.
You can try to use the xposed uninstaller which may fix it. If not, you need to do a full wipe and reflash a ROM.
Click to expand...
Click to collapse
Thanks very much. It's true I installed Xposed Framework and didn't wipe cache. I have already reinstalled the Rom so will remember this time not to repeat the same mistake.

dl12345 said:
Introduction
NOTE: if you install Xposed you MUST wipe cache/dalvik after installation otherwise you will get an error message telling you that you are running out of storage space and any apps you install with Play store will fail the installation with a 504 error. This is NOT related to the kernel, but is caused by failing to wipe cache after installing Xposed.
Download
[B
Click to expand...
Click to collapse
I'm on .251 (modified system partition) without XPOSED installed. Using the kernel just causes boot loops (Sony Logo then 3 red flashes from the LED) the same way the stock kernel does. Is there something special I need to get SONY RIC / Verity to not run at boot?

This looks like a bad flash. Can you fastboot this kernel?

dl12345 said:
This looks like a bad flash. Can you fastboot this kernel?
Click to expand...
Click to collapse
No luck doing fastboot boot, or fastboot flash boot (both have the same issue of red led 3x then rebooting)
I re-downloaded it and the md5sum matched between the downloads:
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img (2)
EDIT:
Also just in case it matters, the exact build I'm on is
28.0.A.8.251
Edit2: Went back to complete stock from FTF flash and the kernel boots. Need to modify system partition and recheck
Edit3: Flashes SuperSU.zip and it is booting with SU installed. Unsure why my old rom was incompatible with it

ChrisJ951 said:
No luck doing fastboot boot, or fastboot flash boot (both have the same issue of red led 3x then rebooting)
I re-downloaded it and the md5sum matched between the downloads:
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img (2)
EDIT:
Also just in case it matters, the exact build I'm on is
28.0.A.8.251
Edit2: Went back to complete stock from FTF flash and the kernel boots. Need to modify system partition and recheck
Edit3: Flashes SuperSU.zip and it is booting with SU installed. Unsure why my old rom was incompatible with it
Click to expand...
Click to collapse
Me neither - this bootimage has very few modifications: only CONFIG_DM_VERITY and RIC removed, some options for runtime control of SELinux added and the verity keys removed from the ramdisk. It boots fine on a stock 251 ROM for me. The kernel source is .251 source too...
I have noticed that I occasionally get bad flashes and odd behaviour when flashing ROMs (with everything from fastboot to flashtool to TWRP). I think the platform itself isn't totally stable and bug free. Usually I fix it by just wiping and reflashing

Hi @dl12345, can you make the same kernel for Z3 (D6603) or at least point me in direction to know what I need to change by compiling own kernel from sources? Or modifying the original ramdisk..
The issue is that the new Concept M firmware from Sony uses the same security features. Guys (@Gustavo RD78) made successfully kernel for previous Concept L (5.1.1) based firmware, however the same approach seems to fail in case of Marshmallow. Your help will be very appreciated.
EDIT - removed full OP quoted by mistake.

ondrejvaroscak said:
Hi, can you make the same kernel for Z3 (D6603) or at least point me in direction to know what I need to change by compiling own kernel from sources? Or modifying the original ramdisk..
The issue is that the new Concept M firmware from Sony uses the same security features. Guys (@Gustavo RD78) made successfully kernel for previous Concept L (5.1.1) based firmware, however the same approach seems to fail in case of Marshmallow. Your help will be very appreciated.
Click to expand...
Click to collapse
You need kernel source (Sony won't upload it since it's closed beta test).
Also do not quote full OP.
[UPDATE]
AOSP and copyleft source are different things. You need kernel source for concept rom's kernel, and it won't be published so it's impossible to build custom kernel for concept rom.

AndroPlus said:
You need kernel source (Sony won't upload it since it's closed beta test).
Also do not quote full OP.
Click to expand...
Click to collapse
Do I get it right, that I can't justo compile kernel for use with this firmware from AOSP / Sony Copy-left sources?

[kernel][E6533][Z3+ dual][32.2.A.0.224](RIC disable, TWRP, root,dm-verity)

Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:

Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!

youngcube said:
Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!
Click to expand...
Click to collapse
no need to flash superSU i think, it's already included in the kernel.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.

bruno$0 said:
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.
Click to expand...
Click to collapse
Working wonderful with SuperSU 2.68 I have a doubt do you have a DRM Restore that works with this Android Version?

Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks

[/COLOR]
creepyvillager said:
Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks
Click to expand...
Click to collapse
No flashing a kernel doesn't wipe anything, if you're having a dilemma then take a backup of everything like apps, contacts etc using titanium backup, copy the backup folder to your external memory or computer then flash.
Hope it helps.
P. S ONLY INSTALLING A RECOVERY WIPES EVERYTHING.
---------- Post added at 09:41 AM ---------- Previous post was at 09:25 AM ----------
bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?

njaya95 said:
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?
Click to expand...
Click to collapse
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.

creepyvillager said:
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.
Click to expand...
Click to collapse
I just found out to use this kernel i should have .244 firmware i bet you're at .185 so update it to .244 then try this kernel. I'm just downloading the firmware now using Xperifirm(https://www.google.com/url?sa=t&rct...9Q4Ht-00R24lisYcw&sig2=ac8ImW1ZY7AvFSZpG9I9mA) and i'll post what i did to the phone after the update.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
It's not, need to flash SuperSU I flashed 2.66 Beta

bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Hey can you help me, how to make this kernel SELinux status permissive.

njaya95 said:
Hey can you help me, how to make this kernel SELinux status permissive.
Click to expand...
Click to collapse
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.

bruno$0 said:
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.
Click to expand...
Click to collapse
Okay ?

Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?

SugnaB said:
Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?
Click to expand...
Click to collapse
It's for 6.0.1 so don't flash it for 5.0.1, update the firmware then flash it cause Sony would have updated somethings in the kernel which won't work with old firmwares. The reason for boot working is maybe because of the phone rebooting from fastboot mode.
Hope it helped. [emoji4]
Sent from my E6533 using XDA-Developers mobile app

Did it need a Unlocked Boot-loader device?

sani007 said:
Did it need a Unlocked Boot-loader device?
Click to expand...
Click to collapse
offcourse.

Sorry for the noob question but I need to know the prerequisites,
Can I flash the Kernel right after flashing stock file OR....
Do I need to first unlock my bootloader
Do I need to have backed up my TA partition

hi there, i wanna update form .185 to .224. is it possible to update without wipe the data? and if it can, if i wanna root it, i just flash this kernel after fw upgrade, then flash supersu via twrp, am i right? thanks

If Xperia Z3+ Dual can't be bootloader unlocked, what's the point in this kernel?!

New Paranoid Android just getting stuck in bootloop on Nexus 6

I have rooted, TWRPd, and flashed the latest Shamu AOSPA, along with franco.kernel. Every time I do it it just goes into bootloop. If I reflash everything it basically says no root, and offers me SuperSU flash. When I flash, it goes to bootloop, when I don't flash, it works (most of the time), but no SuperSU.
Help?!

Flash SuperSU separately. If you actually need root access

Pirateghost said:
Flash SuperSU separately. If you actually need root access
Click to expand...
Click to collapse
What do you mean separately ?do you mean after I get it to boot up I thought I had to do a full wipe ,flash ROM,gapps,SuperSU .?I also am stuck on boot for 30 min powered down tried again no luck

I installed new PA on shamu yesterday without errors:
1. Flash latest factory image from Google
2. Then, flash latest TWRP
3. Flash PA + Gapps
4. Reboot
5. Flash Franco
6. Flash Supersu
7. Reboot
If you want, you can flash Franco kernel and then reboot before flashing Supersu to ensure success.
Good luck!!!
Enviado desde mi Nexus 6 mediante Tapatalk

1981greg said:
What do you mean separately ?do you mean after I get it to boot up I thought I had to do a full wipe ,flash ROM,gapps,SuperSU .?I also am stuck on boot for 30 min powered down tried again no luck
Click to expand...
Click to collapse
I literally mean don't use root method built into twrp. Use the SuperSU zip and flash it separately

Pirateghost said:
I literally mean don't use root method built into twrp. Use the SuperSU zip and flash it separately
Click to expand...
Click to collapse
Just to add.. Same thing is happening here..
Steps:
Installed PA and Banks Gapps And ElementalX kernel(because of the encryption issue referenced in the thread).. Rebooted. All was well.
Rebooted to recovery and made a backup. Installed 'UPDATE-SuperSU2.46.zip' obtained from Chainfire's site and upon rebooting you see the boot animation indefinitely. Reboot into recovery and restore only system in TWRP and it boots fine again.

mostyle said:
Just to add.. Same thing is happening here..
Steps:
Installed PA and Banks Gapps And ElementalX kernel(because of the encryption issue referenced in the thread).. Rebooted. All was well.
Rebooted to recovery and made a backup. Installed 'UPDATE-SuperSU2.46.zip' obtained from Chainfire's site and upon rebooting you see the boot animation indefinitely. Reboot into recovery and restore only system in TWRP and it boots fine again.
Click to expand...
Click to collapse
2.46 is outdated, use newer version.
http://forum.xda-developers.com/showthread.php?t=1538053
I use the stable branch. Version 2.65

mostyle said:
Just to add.. Same thing is happening here..
Steps:
Installed PA and Banks Gapps And ElementalX kernel(because of the encryption issue referenced in the thread).. Rebooted. All was well.
Rebooted to recovery and made a backup. Installed 'UPDATE-SuperSU2.46.zip' obtained from Chainfire's site and upon rebooting you see the boot animation indefinitely. Reboot into recovery and restore only system in TWRP and it boots fine again.
Click to expand...
Click to collapse
That version is ridiculously old.

Pirateghost said:
That version is ridiculously old.
Click to expand...
Click to collapse
githyanki said:
2.46 is outdated, use newer version.
http://forum.xda-developers.com/showthread.php?t=1538053
I use the stable branch. Version 2.65
Click to expand...
Click to collapse
Agreed. I looked again and was not even sure how I got to 2.46 via google search.. Only guess was it was 4am. Apologies for the time waste.

[RECOVERY LOCKED/Nougat/7.0][G955U/W] Safestrap Recovery v4.09 B01 [Apr 19, 2019]

Samsung Galaxy S8+ (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.09-B01 [Nougat:7.0]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.2.1 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8+ (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.09-B01-DREAM2QLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-DREAM2QLTE.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.

CHANGELOG:
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up
4.07-B01 [2018-07-16]
- Fix CHARGER_BOOT detection.
- TWRP updated to 3.2.2.
- Update safestrap portrait theme.
- Update safestrap app to use topjohnwu's libsu & internal busybox (busybox app not needed anymore).
4.06-B02 [2018-04-10]
- Fix taskset cpus to 8 cores (thanks to Hashcode).
- Add exfat support for recovery (ext-sdcard fix).
- Fix MTP (thanks to me2151).
4.06-B01 [2018-04-03]
- Initial release.
BUGS:
- ROM-slots not working for now.

Mine

Yessssss finally a solution. But I can't do it lol I'm running Oreo
Sent from my SM-G955U using Tapatalk

Could you boot an AOSP rom off of it?

Slypnslyde said:
Yessssss finally a solution. But I can't do it lol I'm running Oreo
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
So downgrade - flash PartCyborg's rom, I think it's doable while on Oreo. Don't quote me on this though. I'll just be very sad if it's not possible.

psych0r3bel said:
So downgrade - flash PartCyborg's rom, I think it's doable while on Oreo. Don't quote me on this though. I'll just be very sad if it's not possible.
Click to expand...
Click to collapse
Totally possible

ParisInLove said:
Totally possible
Click to expand...
Click to collapse
Cool I hope it do it right
Sent from my SM-G955U using Tapatalk

ParisInLove said:
Totally possible
Click to expand...
Click to collapse
Just to clarify, when I downgrade from 8.0 to 7.0 to obtain root, boot the rooted ROM then
install busybox and safestrap.apk before reflashing Oreo and that will run alongside Rooted QL1 in a second ROM slot under safestrap?? I apologise if I misread instructions, it's been a while as I haven't used safestrap since my s3 years ago
Edit: just saw the ROM slots not working, and the new Oreo modified thread. Lol

gerryl432 said:
Just to clarify, when I downgrade from 8.0 to 7.0 to obtain root, boot the rooted ROM then
install busybox and safestrap.apk before reflashing Oreo and that will run alongside Rooted QL1 in a second ROM slot under safestrap?? I apologise if I misread instructions, it's been a while as I haven't used safestrap since my s3 years ago
Edit: just saw the ROM slots not working, and the new Oreo modified thread. Lol
Click to expand...
Click to collapse
Were is this oreo thread you mention? iv been searching for it, but i cant find it.

siulmagic said:
Were is this oreo thread you mention? iv been searching for it, but i cant find it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206

gerryl432 said:
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
Click to expand...
Click to collapse
thank you.

@afaneh92 Do you have sources for this recovery? As in how did you get it to work with android 7 when safestrap support ended in KK. I'd like to boot it on LP+.

kirito9 said:
@afaneh92 Do you have sources for this recovery? As in how did you get it to work with android 7 when safestrap support ended in KK. I'd like to boot it on LP+.
Click to expand...
Click to collapse
Here its
https://github.com/mohammad92/android_bootable_recovery-safestrap
We have permissive root on S8, S8+ and Note 8 thats why its working on 7.0+

Would this allow us to flash magisk? Or a custom kernel?

afaneh92 said:
Here its
https://github.com/mohammad92/android_bootable_recovery-safestrap
We have permissive root on S8, S8+ and Note 8 thats why its working on 7.0+
Click to expand...
Click to collapse
Thank you. So as long as you can get root and make the selinux permissive it should work?

TacoTuco said:
Would this allow us to flash magisk? Or a custom kernel?
Click to expand...
Click to collapse
No.
kirito9 said:
Thank you. So as long as you can get root and make the selinux permissive it should work?
Click to expand...
Click to collapse
I think yes.

afaneh92 said:
No.
I think yes.
Click to expand...
Click to collapse
Could a Dev make a DT and possibly build a rom with this new freedom to flash things? Cause as far as I know all you need is a DT and a way to compile and you should be fine right? Or will the whole no custom kernel thing prevent that.

Would I be able to install this on Nougat, and then update to Oreo and keep it installed?
Then from there add a Nougat ROM with root so that I could update it and use my root stuff.

This is awesome! Recovery is working great so far! Pls let me know of any roms working with this method I can't wait to try it out!

[ROM][Alpha-3][UNOFFICIAL] LineageOS-16.0 For dragon (6/19/2020) 4.9 kernel.

[UNOFFICIAL] LineageOS-16.0 For Dragon 4.9 kernel.
The system is built on the basis of the 4.9 kernel and drivers from Nvidia Shield TV.
Of the pluses I noticed, Play 2 / 4k video on YouTube and from files.
To install this firmware you need your own version of TWRP. You can download TWRP here.
Android 9.
Known issues:
- There is no LP0 sleep (standby) mode.
- There is no Camera.
- SELinux - permissive !
Works:
- Wi-Fi and BT
- Sound speakers, headphones, via BT.
system-as-root (SAR)
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. Wipe CACHE and DAVLIK
6. Reboot into system
Download ROM Alpha1
Download TWRP
LOS-16 based on kernel 4.9 nvidia Alpha 3.
Changes
-Added sound through headphones.
Installing images from the archive via fastboot or twrp.
Download ROM Alpha3
- The ROM does contain it's own vendor.img !
Links to the sources
kernel 4.9
platform/dtb
Kernel 4.9 drivers
Kernel 4.9 nvgpu
Vendor
Device nvidia dragon
Thanks @webgeek1234 and CM-Shield team, for the source.
Thanks @michie for testing rom.
If someone wants to help finish the sound support in the kernel and the system, write, I will help you how to start the assembly yourself.

Thank you very much.
This is really an important refresh for the software base.
I think that this new kernel can do wonders on our device.

LOS-16 based on kernel 4.9 nvidia Alpha 2.
Changes
-Added sound through speakers, microphone.
-Blocked sleep mode in the kernel. Now the tablet does not freeze after turning off the screen.
Installing images from the archive via fastboot or twrp.
Download ROM

if sound is working can you make it work on linux with 4.9?

mi_guel said:
if sound is working can you make it work on linux with 4.9?
Click to expand...
Click to collapse
If you mean the mainline kernel, then the answer is no.
If you are about Linux for Tegra at 4.9 then this is possible.

Vartom said:
LOS-16 based on kernel 4.9 nvidia Alpha 2.
Changes
-Added sound through speakers, microphone.
-Blocked sleep mode in the kernel. Now the tablet does not freeze after turning off the screen.
Installing images from the archive via fastboot or twrp.
Download ROM
Click to expand...
Click to collapse
Good work
Gesendet von meinem Pixel 2 XL mit Tapatalk

Vartom said:
LOS-16 based on kernel 4.9 nvidia Alpha 2.
Changes
-Added sound through speakers, microphone.
-Blocked sleep mode in the kernel. Now the tablet does not freeze after turning off the screen.
Installing images from the archive via fastboot or twrp.
Download ROM
Click to expand...
Click to collapse
Glad to see most function works!good job!

The recovery here doesn't seem to work.

almightysiman said:
The recovery here doesn't seem to work.
Click to expand...
Click to collapse
What exactly does not work?
Encryption does not work. I checked the firmware installation.

Vartom said:
What exactly does not work?
Encryption does not work. I checked the firmware installation.
Click to expand...
Click to collapse
I try fastboot Flash recovery and can't boot into recovery,I am not sure what I did wrong.
Edit:I also tried to flash recovery in 3.3.1.2 recovery,then when I tried boot into your recovery,It get black screen and go back to bootloader.

almightysiman said:
I try fastboot Flash recovery and can't boot into recovery,I am not sure what I did wrong.
Edit:I also tried to flash recovery in 3.3.1.2 recovery,then when I tried boot into your recovery,It get black screen and go back to bootloader.
Click to expand...
Click to collapse
Try downloading the recovery again, sounds like it's corrupt. It should work both ways.

michie said:
Try downloading the recovery again, sounds like it's corrupt. It should work both ways.
Click to expand...
Click to collapse
Tried so many time,still no luck,maybe I should keep trying.

Vartom said:
What exactly does not work?
Encryption does not work. I checked the firmware installation.
Click to expand...
Click to collapse
Finally get alpha2 working,one question,Can I flash magisk to root It?

almightysiman said:
Finally get alpha2 working,one question,Can I flash magisk to root It?
Click to expand...
Click to collapse
You can, but magisk will not work. This is a real SaR.

Vartom said:
You can, but magisk will not work. This is a real SaR.
Click to expand...
Click to collapse
So root is not possible at the moment?

almightysiman said:
So root is not possible at the moment?
Click to expand...
Click to collapse
Yes. To be able to get root, I have to make a special version of the firmware.

Vartom said:
Yes. To be able to get root, I have to make a special version of the firmware.
Click to expand...
Click to collapse
Thanks for making such effort!It's truly a good kernel,I already feel much smooth than other rom.

almightysiman said:
I try fastboot Flash recovery and can't boot into recovery,I am not sure what I did wrong.
Edit:I also tried to flash recovery in 3.3.1.2 recovery,then when I tried boot into your recovery,It get black screen and go back to bootloader.
Click to expand...
Click to collapse
i used it with fastboot boot command, not flash, worked fine, and the rom it's quite snappy

LOS-16 based on kernel 4.9 nvidia Alpha 3.
Changes
-Added sound through headphones.
Installing images from the archive via fastboot or twrp.
Download ROM

Hello friends, can you please take notice of the following thread for the future of development of our device?
https://forum.xda-developers.com/pix...xel-c-t4123463
Thank you in advance!