Develop Bugs

[ROM][UNOFFICIAL][6.0.1] crDroid [12/21]

OFFICIAL VERSION HERE : http://forum.xda-developers.com/xperia-z1/orig-development/rom-crdroid-android-t3280304
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
DOWNLOADS
12/25/2015
Not Working
Camera
Test and report back
SOURCE CODE
Kernel
Device Tree
Rhine Board Tree
crDroid
CREDIT
davidteri91
erikcas
jerpelea
crDroid Dev team
FXP Dev team
etc
XDA:DevDB Information
crDroid, ROM for the Sony Xperia Z1
Contributors
zhuoyang
Source Code: https://github.com/crdroidandroid
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2015-12-20
Last Updated 2015-12-29

Recovery
NOTE: For build after 12/25 only (build before 12/25 untested)
CyanogenMod Recovery - Download
How to flash (using fastboot):
Code:
fastboot flash recovery recovery.img
How to boot into recovery :
Press power button once (don't hold) when LED lights up on the Sony screen.

Should google gapps? Does have root? Internal and external memory work?
Sorry for bad Englisch!

I install rom from TWRP and phone not turn on... In .zip in build prop I read: ro.build.description=C6903-user 5.0.2 14.5.A.0.270 3750474323 release-keys
This is not Android 6.

opengapps doesn't work , used those instead
http://www.devfiles.co/download/m4Er5IlQ/gapps-600-base-20151016-1-signed.zip
had to set permission on my own , but playstore keeps on fc

aleksandar9999a said:
I install rom from TWRP and phone not turn on... In .zip in build prop I read: ro.build.description=C6903-user 5.0.2 14.5.A.0.270 3750474323 release-keys
This is not Android 6.
Click to expand...
Click to collapse
Here's a prove

solved said:
opengapps doesn't work , used those instead
http://www.devfiles.co/download/m4Er5IlQ/gapps-600-base-20151016-1-signed.zip
had to set permission on my own , but playstore keeps on fc
Click to expand...
Click to collapse
Hmm strange ... I do use opengapps myself , it works perfectly
Did you wipe everything (including /system) before you flash to this ROM ?

aleksandar9999a said:
Should google gapps? Does have root? Internal and external memory work?
Sorry for bad Englisch!
Click to expand...
Click to collapse
Yes , you should install gapps, Root can be enabled in development settings.
Both Internal and external storage works !

Okay, this ROM is really good. Just a few things and it will be perfect:
- no built-in recovery (I know I should use new bootloader but I don't know if there's any way how can I "downgrade" it back if I want to)
- Mi Pistons headphones are still buggy - you have to press all buttons to get it recognized
- in YouTube app when you use you phone in landscape and minimize some video (browsing other videos when the previous one is still playing) you see some graphical artefacts in right upper corner. Above multitasking button.
- and of course camera but that's known bug
edit : there are more glitches - see screenshot in attachments

I try again to install rom and it is work. I don't know why first time not work. I install from philz recovery. I have some questions. If you port camera from other rom, it will work? Before I was install cm12.1 and view that on first and second boot camera was work, but after this it isn't work. This is similar problem. The problem may be in framework.jar.

SuperLamic said:
Okay, this ROM is really good. Just a few things and it will be perfect:
- no built-in recovery (I know I should use new bootloader but I don't know if there's any way how can I "downgrade" it back if I want to)
- Mi Pistons headphones are still buggy - you have to press all buttons to get it recognized
- in YouTube app when you use you phone in landscape and minimize some video (browsing other videos when the previous one is still playing) you see some graphical artefacts in right upper corner. Above multitasking button.
- and of course camera but that's known bug
edit : there are more glitches - see screenshot in attachments
Click to expand...
Click to collapse
There's actually boot to recovery implementation in kernel but it seems to be not working. Will have to investigate that later on.
The graphical glitches seems to be cyanogenmod bug (crDroid is based on cm).

aleksandar9999a said:
I try again to install rom and it is work. I don't know why first time not work. I install from philz recovery. I have some questions. If you port camera from other rom, it will work? Before I was install cm12.1 and view that on first and second boot camera was work, but after this it isn't work. This is similar problem. The problem may be in framework.jar.
Click to expand...
Click to collapse
Unfortunately the problem is not that simple.
Camera just doesn't work yet in marshmallow.
We'll have to wait for Sony to release camera for marshmallow or someone else to get it working.

I try to merge memory, but it not work. It is possible that I'm wrong thing.

New build released.
https://www.androidfilehost.com/?fid=24338798368260209
In this build , proximity sensor is fixed.
Complete changelog available at Settings > About Phone > About crDroid > Changelog

Pls dear developer if possible can twrp be implemented in the kernel please??

gauravbhakuni90 said:
Pls dear developer if possible can twrp be implemented in the kernel please??
Click to expand...
Click to collapse
Unfortunately this would take some time. I just can't figure out yet what's wrong with the boot to recovery implementation.
For now , your best bet is updating TA with recovery mode and flash TWRP
or you can hotboot any kernel with recovery using "fastboot boot boot.img"

When phone is turn off and you plug charger, screen is light and then charger screen will restart and screen remaints lit. After 2 or 3 restarts the charger screen, phone will turn on and after this it will turn off (or not turn off someone) and situation will repeat.
Sorry for bad Englisch. I hope you understand me.

zhuoyang said:
Unfortunately this would take some time. I just can't figure out yet what's wrong with the boot to recovery implementation.
For now , your best bet is updating TA with recovery mode and flash TWRP
or you can hotboot any kernel with recovery using "fastboot boot boot.img"
Click to expand...
Click to collapse
Hi,
I tried to update my ta, but there are only generic softwares (I flashed .368) and no ta update - in emma. Do you know what am I doing wrong? because it's really wierd to boot another kernel everytime I want to go to recovery.

SuperLamic said:
Hi,
I tried to update my ta, but there are only generic softwares (I flashed .368) and no ta update - in emma. Do you know what am I doing wrong? because it's really wierd to boot another kernel everytime I want to go to recovery.
Click to expand...
Click to collapse
did you copy customization.ini to emma installation folder ?

zhuoyang said:
did you copy customization.ini to emma installation folder ?
Click to expand...
Click to collapse
yes, I wouldn't be able to run it if I didn't
edit: can I use the recovery you posted before like fota recovery? because fota recovery works, you only must have recovery built with 3.10 kernel otherwise you have no display.

[ROM][6.0.1][LUX] Stock Debloated VoLTE 2.0.0 [MPD24.107-70-1]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About Stock Debloated VoLTE
Information
Installation
Downloads
This is a fully Stock Debloated ROM (Android 6.0.1) of the MPD24.107-70-1 firmware, with support for VoLTE. This version supports XT1562 and XT1563, single-sim and dual-sim devices.
It is debloated, removing as much intrusive apps and services without losing the features of the Moto Display, Moto Voice and Miracast present in Stock MPD24.107-70-1.
Includes the stock bootlogo with the unlocked bootloader warning disabled.
-INFORMATION-
-Indian Firmware MPD24.107-71-1 (Android 6.0.1 )
-Security Patch Level of October 1, 2016
-Stock bootlogo
-Stock kernel
-Debloated
-Zipaligned
-INSTALLATION INSTRUCTIONS-
- Place ROM in your internal memory
- Wipe data and factory reset
- Wipe cache and dalvik-cache
- Flash ROM using TWRP
- Flash the modem (Only if VoLTE doesn't work)
- Reboot
-INSTALLATION FILES-
ROM
MIRROR [Android File Host]
MODEM MPD24.107-70-1
(DON'T USE RECOVERY, USE FASTBOOT METHOD)
MIRROR [Android File Host]​
Installing The Modem Via Fastboot
Step 1. Once the bootloader is unlocked, enable the USB debugging mode on your phone.
Go to Settings > About phone, and then tap "Build number" 7 times to become a developer.
Now go back to Settings, then choose "Developer options".
Find the "USB debugging" option and use its toggle button to enable it.
Accept warning by tapping on the OK button.
Step 2. Now install the USB drivers on your Windows from here.
Step 3. Extract the modem (ZIP or RAR file), if the file INSTALL.CMD does not exist, rename the INSTALL.TXT to INSTALL.CMD.
Step 4. Connect your phone to the computer, wait for the installation of the drivers and run the file INSTALL.CMD.
Step 5. Phone will automatically reboot in fastboot mode, wait for the procedure is completed. After installing the phone will restart in the system again.
Debloat List
/system/app
/system/app/Drive
/system/app/Translate
/system/app/talkback
/system/app/Hangouts
/system/app/HTMLViewer
/system/app/colorservice
/system/app/Bug2GoStub
/system/app/YouTube
/system/app/com.motorola.android.nativedropboxagent
/system/app/MotorolaConnect_Basic
/system/app/PartnerBookmarksProvider
/system/app/Videos
/system/app/GoogleHindiIME
/system/app/BookmarkProvider
/system/app/KoreanIME
/system/app/ZhuyinIME
/system/app/NoiseField
/system/app/EditorsDocs
/system/app/Maps
/system/app/EditorsSheets
/system/app/LauncherConfig
/system/app/EditorsSlides
/system/app/BasicDreams
/system/app/CloudPrint
/system/app/ColorProfiles
/system/app/GooglePinyinIME
/system/app/UserDictionaryProvider
/system/app/com.motorola.android.settings.modemdebug
/system/app/JapaneseIME
/system/app/Photos
/system/app/PhaseBeam
/system/app/MediaShortcuts
/system/app/Music2
/system/app/HoloSpiralWallpaper
/system/priv-app
/system/priv-app/MotoCareInt
/system/priv-app/DemoMode
/system/priv-app/Moodles
/system/priv-app/GuideMe
/system/priv-app/TagGoogle
/system/priv-app/LMIRescueSecurity
/system/priv-app/BodyGuardApp
/system/priv-app/3c_ota
/system/priv-app/DigitalPersonalization
/system/priv-app/CellBroadcastReceiver
/system/priv-app/PreloadContacts
/system/priv-app/MotoCare
/system/etc
/system/etc/motorola/MotoDemo
ROM Firmware Required: Unlocked Bootloader and Custom Recovery (TWRP 3.0.2-r3 Recommended)
Credits
Thanks to @effingbadluck for providing the TWRP backup for the first version of ROM (the second version is based on the complete firmware file).
Thanks to @SuperR. for SuperR's Kitchen and other instructions in the deodex process.
Thanks to @minimale_ldz for the XDRom and your best work in debloat process.
Thanks to you for always providing feedback.

really thanks for this.finally stock flashable rom.can i flash this without wipe?and then reroot etc..i am on stock rom with May security patch.thanks.

Uploading...

kos25k said:
really thanks for this.finally stock flashable rom.can i flash this without wipe?and then reroot etc..i am on stock rom with May security patch.thanks.
Click to expand...
Click to collapse
Hi! If you have the firmware MPD24.107-70, wipe cache and dalvik-cache only.

ok thanks.and then i imagine i have to reflash xposed.zip and generally the flashable zips i have flashed till now..right?

link wrong

problem here also.maybe till uploading..

spowl said:
link wrong
Click to expand...
Click to collapse
kos25k said:
problem here also.maybe till uploading..
Click to expand...
Click to collapse
Sorry, I went to sleep and gave an error in uploading. I am uploading again.

Upload OK.

THANKS. Your roms are fantastic!

did anyone try installing without f.reset?all ok?

Working my simcard again finally, thanks.
Sorry but what is the best way to root here?
Greetings

i successfully rooted the same stable way.supersu 2.62-3 systemless version after f.reset.and also successfully only wiped cache and dalvic from previous version with May security patches.Thanks again the dev for this rom.It is a must rom to have that was missing maaany time now.

Use version 2.79 of SuperSU edited by me for MXP Stock:
https://www.androidfilehost.com/?fid=529152257862692595
Sent from my XT1562 using XDA-Developers Legacy app

is systemless?

Can I add the sound mods as it was in your previous versions? This is the type of ROM I wanted for myself without root and my Pokemon go also works haha! I will definitely root the phone again but want to make sure if I can add sound mods to this?
Sent from my XT1562 using Tapatalk

Flashed over stock 24.107.70 (really stock, not a debloat) using TWRP r5. Wiped Cache and Dalvik. Re-flashed SuperSU from post #14, a kernel, and the latest Xposed. Everything seems to work, all apps and their state/options were kept.

Bluetooth an wifi not work simultaneously
Bluetooth an wifi not work simultaneously

Magiks Systemless SuperSU and Xposed work flawlessly

VOLTE not working for me. Any suggestions?

[MOD] FCS Xperia X OREO

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Main advantages
- Best performance at all temperatures (50 ~ 70% faster than stock)
- Less heat (especially during moderate / intense use -5 ~ 10 ° C)
- Maintains very good performance for long periods of time
- Faster cooling
- Overheating has been deactivated
- Do not heat device while in sleep mode
- System improvements and Soc qualcomm
- Optimized CPU and gpu for Soc qualcomm control
- No overheating when used and device charged
- System and kernel functions were fixed
- Add support init.d stock
Requirements
- Xperia X F5121 & F5122
- Compilation 34.4.A.2.70
- Firmware 8.0
- Install busybox
- Twrp
- Magisk 16
- it is unknown if it works for SuperSU
Installation
Attention: it is not authorized under any circumstance to lodge the files of this mod in another cloud of storage, you can add this thread to your post
- Turn off your device
- Enter twrp
- Install - Xperia_X_Thermal_Oreo_Compilation_70.zip
- Before restarting, perform the following steps
- Twrp
- Wipe
- Slide to factory reset
- Advanced cleaning
- Option:
- Dalvik / ART Cache
- Cahe
- Data
- Slide to clean
- Reailize the installation of - initd_magisk.zip
- ready restart and configure your device
- Once the configuration is finished, turn off your device
- and restart the first few times when your device starts, leave it for 2 to 3 minutes and unlock it and go
Now to enjoy your device without worrying that hot :laugh:
credits: @korom42 or its magisk module although it is adapted for the Xperia X

Faq
- will work in another compilation
you can try but it is based on the compilation 34.4.A.2.70 that you probably bootloop
- It is necessary to perform the cleanup with twrp and reestablish my device
if it is necessary for the changes to be applied correctly
- I can upload it to my personal storage cloud
no, but you can place the thread on this topic without any problems
- Works for Android Nougat
Do not

Reserved

It doesn't need Magisk and some suspicious module, I think. Any app which can emulate init.d (like Kernel Adiutor) will work just fine.

How do I know it works?
I installed it in a clean rom, but the phone heats up normally as expected, as data: install the magisk file and I throw error, followed the steps to the letter

winsters said:
I installed it in a clean rom, but the phone heats up normally as expected, as data: install the magisk file and I throw error, followed the steps to the letter
Click to expand...
Click to collapse
the device does not heat up if you follow the steps as you re-check the installation and it will last for 2 weeks

Bootloop wheb used on xgen rom 1.07. . Did I do something wrong

Does this mod also work with Omni Rom Oreo?

Hmm, I found only the 1st thing I'm unable to install, I can install the main FCS thing but it's a no go on the initd magisk thing.. it doesn't install....

lilbrat said:
Hmm, I found only the 1st thing I'm unable to install, I can install the main FCS thing but it's a no go on the initd magisk thing.. it doesn't install....
Click to expand...
Click to collapse
The same here

PNIGGE said:
The same here
Click to expand...
Click to collapse
Copy to internal sd (crucial). Install the zip. Enable init.d using kernel adiutor. Restart phone. Profit.

I was having some weird issues with the mod where the init.d scripts wouldn't run neither with the module suggested in OP nor through Kernel Adiutor and was also tired of having to reflash the mod every time a new security update was released, so I went in and made a pure Magisk version of the mod (attached on this post).
This Magisk version is exactly the same as the OP, the only difference is that it's now a Magisk Module (so it applies systemlessly) and that you don't need busybox nor any kind of init.d support for it to work (the init.d scripts from the mod are executed directly through Magisk late_start hook instead). Download the ZIP, install through Magisk Manager, reboot and done.

mbc07 said:
I was having some weird issues with the mod where the init.d scripts wouldn't run neither with the module suggested in OP nor through Kernel Adiutor and was also tired of having to reflash the mod every time a new security update was released, so I went in and made a pure Magisk version of the mod (attached on this post).
This Magisk version is exactly the same as the OP, the only difference is that it's now a Magisk Module (so it applies systemlessly) and that you don't need busybox nor any kind of init.d support for it to work (the init.d scripts from the mod are executed directly through Magisk late_start hook instead). Download the ZIP, install through Magisk Manager, reboot and done.
Click to expand...
Click to collapse
How would the installation process differ from OPs instructions with this Magisk module?

CntrlAltDel45 said:
How would the installation process differ from OPs instructions with this Magisk module?
Click to expand...
Click to collapse
You have two options:
1) Boot into TWRP and flash the attachment from my previous post (works only if you already have Magisk installed and working!), then reboot when done.
2) Open Magisk Manager, go to Modules, click the + button, locate the attachment from previous post, then reboot when done.
That's it. You don't need to flash/install anything else.

mbc07 said:
You have two options:
1) Boot into TWRP and flash the attachment from my previous post (works only if you already have Magisk installed and working!), then reboot when done.
2) Open Magisk Manager, go to Modules, click the + button, locate the attachment from previous post, then reboot when done.
That's it. You don't need to flash/install anything else.
Click to expand...
Click to collapse
Thank you. I used the second method you mentioned. Everything went by seamlessly.

mbc07 said:
You have two options:
1) Boot into TWRP and flash the attachment from my previous post (works only if you already have Magisk installed and working!), then reboot when done.
2) Open Magisk Manager, go to Modules, click the + button, locate the attachment from previous post, then reboot when done.
That's it. You don't need to flash/install anything else.
Click to expand...
Click to collapse
Used the 2nd method, but there's a problem: after 2 minutes in stand by from the restart of the phone, it restarted by itself...
What's the problem? Need a dalvik/cache wipe after the installation with Magisk? Is it incompatible with Xposed framework (installed on my phone)? Or maybe the compilation base (I'm on fw .118) is different and cause bootloop...
Thanks in advance.
Edit: I used the first method, I had an installation without restart, but it doesn't work!

will it work with .118 rom?

AlexUnder2010 said:
will it work with .118 rom?
Click to expand...
Click to collapse
No! But you can get the right file at this link: https://mega.nz/#F!DZAGDY6B!d6CeWtv-tqD0RHtsOHS02w
When you open the folder, find and download fcs thermal v. 1.3. Then install through twrp.
I've installed on stock rom .118 and works great

Niquillo said:
No! But you can get the right file at this link: https://mega.nz/#F!DZAGDY6B!d6CeWtv-tqD0RHtsOHS02w
When you open the folder, find and download fcs thermal v. 1.3. Then install through twrp.
I've installed on stock rom .118 and works great
Click to expand...
Click to collapse
It's for Nougat only ??*

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10e/S10/S10+

Team Win Recovery Project 3.3.1​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
Download: S10(Exynos variants - G970/973/975/F/N)
Download
Sources:
TWRP Tree and kernel source
Changelog:
15.12.2019
- Updated TWRP for Android 10.0
- From now on no more Magisk Prepatched images (if you need it patch it byself or flash my kernel where patched recovery is not needed)
07.10.2019
-Updated TWRP Kernel to Full ASIG Base
-Dex On PC will now work
23.09.2019
-Updated TWRP for boot on ASIG Bootloader and for not Break Camera on ASIG
-Dex On PC will not work for the moment but i will fix that soon
-Use ASIG TWRP Builds only when you are on a ASIG rom
22.09.2019
-Reverted MTP Changes from last build since for some mtp dont worked in system
21.09.2019
- Fixed the bug that mtp dont worked anymore on TWRP when usb cable got disconnected and reconnected
- Modded Kernel for have MTP in TWRP, Samsung Roms and GSI roms (for GSI Roms flash GSI_MTP_ENABLER.zip)
- Reverted FFS MTP changes since new way is more stable
- Fixed format data issue (was my fault)
14.09.2019
- Rebased Kernel to ASH6 base
- Added Busybox to twrp because enought devs asked me that since toybox is too limited
- Fixed all Bugs from initial release
- Fixed MTP using FFS_MTP in recovery (Thx to @bigbiff for add FFS MTP support on TWRP 3.3.0. FFS_MTP dont corrupts large files like the mtp used by samsung in the roms)
14.04.2019
- Initial Release
Bugs:
-No one
Telegram Group
https://t.me/twrp_n10
Note that after flashing this twrp other build not made by me will have lockscreen unlock issues
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][ASIG] TWRP for Galaxy S10e/S10/S10+, Kernel for the Samsung Galaxy S10
Contributors
geiti94
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 4.0
Stable Release Date: 2019-09-23
Created 2019-04-07
Last Updated 2019-12-15

Installation Guide
Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with power + vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field (if you want to patch twrp byself patch the downloaded tar in magisk manager. patched tar is in downloads folder after patch)
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp
flash the disabler that is on TWRP download link
flash my kernel avaiable here
press reboot to system in twrp.

Thank you!

Thank you!Thank you!

If I'm already rooted with Magisk do I still need to perform factory reset and so after installing the tar file?

jimbo77 said:
If I'm already rooted with Magisk do I still need to perform factory reset and so after installing the tar file?
Click to expand...
Click to collapse
yes because you have data encryption enabled and twrp dont have support for it

geiti94 said:
yes because you have data encryption enabled and twrp dont have support for it
Click to expand...
Click to collapse
Alright will give it a go. I'm just gonna backup my stuff

jimbo77 said:
Alright will give it a go. I'm just gonna backup my stuff
Click to expand...
Click to collapse
Anyone know if you could just decript it then flash?

Is it working?

reboot system...bootlop logo.

Does this include the ATT US galaxy s10???
---------- Post added at 07:57 AM ---------- Previous post was at 07:46 AM ----------
3dLyric said:
Does this include the SM-G973U
Click to expand...
Click to collapse

3dLyric said:
Does this include the ATT US galaxy s10???
---------- Post added at 07:57 AM ---------- Previous post was at 07:46 AM ----------
3dLyric said:
Does this include the SM-G973U
Click to expand...
Click to collapse
Only exynos will work for now, us snapdragon have locker bootloader, maybe never will have twrp.
Click to expand...
Click to collapse

help cannot bootphone into twrp or downlodmode tried three button combination no sucssees only phone blinks in coution messege

saxena1 said:
help cannot bootphone into twrp or downlodmode tried three button combination no sucssees only phone blinks in coution messege
Click to expand...
Click to collapse
Attach your phone to a computer and retry, it's a known issue

delete

bon0123456789 said:
reboot system...bootlop logo.
Click to expand...
Click to collapse
Have you tried doing reboot recovery from TWRP?

In the OP, it says ASC firmware base. Does that mean it only works on devices with ASC firmware base? If so how do I check that?

geiti94 said:
yes because you have data encryption enabled and twrp dont have support for it
Click to expand...
Click to collapse
I disabled encryption when installed Magisk.
Still need factory reset?

Ndaoud360 said:
In the OP, it says ASC firmware base. Does that mean it only works on devices with ASC firmware base? If so how do I check that?
Click to expand...
Click to collapse
Hi
I think he's talking about the last
First was ASBA and last is ASCA ^^

Step 9. hold vol up+ bixby+power until you are twrp, doesnt work for me. I have tried holding the buttons for more than 1 minute, holding vol up + bixby plugging usb, holding vol up and bixby only, it just stays on download mode. I can only press vol down + power to reboot, and I cant boot to system or recovery after that, I have to flash stock with odin and start over.
Any ideas?

[KERNEL][03.01.2020][10.0]NEMESIS KERNEL N10 S10 V3

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NEMESIS Kernel is the world first N10 and S10 Kernel with Magisk inside! So no patched recovery and no button combo is needed!
You are NOT allowed to use any part of the tweaks files, scripts, propriate Apps or what ever of this Rom without my permission!
Kernel Feature:
- Kernel can be installed only with my TWRP and not with other one since busybox support in twrp its needed!
- All Samsung Security are disabled
- Moro Sound module
- Wakeblocker by boeffla with a base blacklist inside (thx to @corsicanu for the list)
- Build in Magisk (no patched recovery and no button combo is needed!)
1) Put the zip file in your SD Card
2) Reboot in Recovery Mode (TWRP)
3) Install the Kernel
4) Press Reboot System and enjoy
V2.0
-Magisk update dont works! so dont try to update it in magisk manager. i will update it all time on new official magisk releases
V2.0
-Kernel works only on N10, N10+, N10 5G, N10+ 5G, S10e, S10, and S10+!
3.0 (03.01.2020)
- Updated Magisk to V20.2
2.0 (21.10.2019)
- Updated to N10/S10 BSKO/BSL7 source code
- Updated Magisk to 20.1
1.0 (21.10.2019) (Never Released on xda)
-First Build for telegram group for test the kernel
V2.0
My Synology NAS:NEMESIS KERNEL 2.0 DOWNLOAD​
Credits:
Samsung for the S10 BSKO kernel source......
@corsicanu for wakeblocker blacklist
@boeffla for wackeblocker
@morogoku for morosound module
Kernel Source
XDA:DevDB Information
[KERNEL]NEMESIS KERNEL N10 S10, Kernel for the Samsung Galaxy S10
Contributors
geiti94
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2019-12-15
Created 2019-12-15
Last Updated 2020-01-03

great job!

@geiti94
Do you know of any showstoppers running this on LOS17 on S10? Don't got it with me, so cannot try ATM.

Keule-T said:
@geiti94
Do you know of any showstoppers running this on LOS17 on S10? Don't got it with me, so cannot try ATM.
Click to expand...
Click to collapse
i dont use los so i dont know if he works on it.

geiti94 said:
i dont use los so i dont know if he works on it.
Click to expand...
Click to collapse
All right, will try it later & report.

What rom can I use with this kernel?

Yan.M said:
What rom can I use with this kernel?
Click to expand...
Click to collapse
all android Q roms. but when they patched services.jar on reboot he will boot in recovery. for use the phone again normal like it was on n9 s9 etc you need a unpatched services.jar

oh my god thanks man big man thanks

carhd mod android 10 not work kernel flash kernel complate no kernel

@geiti94 Could you add battlery idle mode (it allows the device to draw power directly from the external power supply when charging is paused) support in the next release? It would be a great feature to have.

Has_anDroid said:
carhd mod android 10 not work kernel flash kernel complate no kernel
Click to expand...
Click to collapse
read what is here. the kernel flash only with my twrp. when you have an other twrp he will not work

oh my god reboot system kernel works reboot recovery kernel not work thanks

I can't get it to boot for some reason. What I do is:
1. Flash G975FXXU3BSKO,
2. Flash TWRP,
3. Format /data,
4. Flash kernel (tried with and without multidisabler),
5. Reboot system.
Can't get past Samsung logo.

Vatt`ghern said:
I can't get it to boot for some reason. What I do is:
1. Flash G975FXXU3BSKO,
2. Flash TWRP,
3. Format /data,
4. Flash kernel (tried with and without multidisabler),
5. Reboot system.
Can't get past Samsung logo.
Click to expand...
Click to collapse
you need to flash the disabler that is in twrp download folder too

my device is 975F, me too. tried several times
Stock pure
Stock patched
Beyond rom
Always stuck at samsung logo i couldnt pas the logo secreen

geiti94 said:
you need to flash the disabler that is in twrp download folder too
Click to expand...
Click to collapse
Unfortunately this solution doesn't work. I'm definitely not flashing newbie, I tried every possible combination including the one you provided but I'm still stuck on Samsung logo.

I don't normally use XDA, but I just wanted to create an account to point out I had the same issues as well. Couldn't boot past the Samsung logo, the device was constantly stuck in a bootloop. I've since given up and reverted back to stock.

No SIM Card detected on S10e
Hi,
I've installed TWRP and the then kernel. The initial bootup was stuck at the Samsung logo. Subsequent bootups work fine.
After installing Magisk Manager, I could install AdAway and enable it. Also Titanium Backup detects 'root'. So far, so good.
Good job. Thanks !
But, my SIM card is not detected. SIM Card Manager says 'No SIM Card'. I tried reinserting it, but that did not help.
Any help / hints are appreciated.

Can't connect to 5G Wifi on beyondrom and magisk is throwing a sqlite error so nothing is detecting root

Vatt`ghern said:
Unfortunately this solution doesn't work. I'm definitely not flashing newbie, I tried every possible combination including the one you provided but I'm still stuck on Samsung logo.
Click to expand...
Click to collapse
ne0__ said:
my device is 975F, me too. tried several times
Stock pure
Stock patched
Beyond rom
Always stuck at samsung logo i couldnt pas the logo secreen
Click to expand...
Click to collapse
dokkanest said:
I don't normally use XDA, but I just wanted to create an account to point out I had the same issues as well. Couldn't boot past the Samsung logo, the device was constantly stuck in a bootloop. I've since given up and reverted back to stock.
Click to expand...
Click to collapse
and i say that again. first of all for flash the kernel my twrp is needed. second thing the disabler in my download link of twrp is needed to be used since the multidisabler by ian creates only problems on s10 etc with custom kernel and @ambasadii can confirm that too. ians multidisabler = bootloop on custom kernels