Database Info

[MOD] MultiROM v33x [20/05/2016]

{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to TheMultiROM Menu (3 bars in the top right corner) to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
Your device must not be encrypted.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on a Rom compatible with one of these kernels and flash it or use the non-kexec workaround. (See important Notices)
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to TheMultiROM Menu (3 bars in the top right corner) to start flashing other ROMs.
Adding ROMs
Go to recovery, select TheMultiROM Menu (3 bars in the top right corner) -> Add ROM. Select the ROM's zip file and confirm.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to TheMultiROM Menu (3 bars in the top right corner) in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to TheMultiROM Menu (3 bars in the top right corner) -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/multirom-htc/Team-Win-Recovery-Project (branch android-6.0)
Kernel w/ kexec-hardboot patch - https://github.com/olivieer/android_kernel_sony_msm8994 (branch 32.1.A.0.xxx)​
FAQs can be found here.
CREDITs
Tasssadar
Myself5
nkk71
Garcia98
XDA:DevDB Information
MultiROM for Sony Xperia Z4/Z3+, Tool/Utility for the Sony Xperia Z4
Contributors
Olivier
Version Information
Status: Beta
Created 2016-05-20
Last Updated 2016-05-20

Reserved
DOWNLOADs
MultiROM
Kernel with kexec-hardboot:
- For use with the 32.1.A.1.185 only
- Works on both variants (Single SIM + Dual SIM)
- MultiROM TWRP is already built-in

Reserved

Gonna test it today and will provide a feedback. Thx for work ?

Ok, so can't root it - Systemless method with patching doesn't work anymore. Also can't flash any zip to main ROM - neither by main menu (flashing, but where - no idea), nor by ROM list (main ROM is hidden and cannot make it visible via settings, resets every time to hidden status).

MotexT said:
Ok, so can't root it - Systemless method with patching doesn't work anymore. Also can't flash any zip to main ROM - neither by main menu (flashing, but where - no idea), nor by ROM list (main ROM is hidden and cannot make it visible via settings, resets every time to hidden status).
Click to expand...
Click to collapse
You need to use my kernel; it can be found in the second post.
EDIT: I can reproduce your problem and will check it once I get home (~ 1-2 days).

Olivier said:
You need to use my kernel; it can be found in the second post.
EDIT: I can reproduce your problem and will check it once I get home (~ 1-2 days).
Click to expand...
Click to collapse
Actually I'm using your kernel. Systemless Root in recovery says like it's already patched and terminal returns "abort operation". Looks like you already patched it by Systemless SU, so I can't repatch it again. If you did so, revert this change. By other side, MultiROM along with TWRP works good, except zip flashing from main TWRP menu - it flashes, everything seems to be good, but actually changes did not appear to be applied on main ROM, even when I inject everything, like described in guide (tried both Systemless SU and DRM fix - neither works :/). Also there is bug with main ROM - can't uncheck "Hide internal ROM", so main ROM couldn't be shown in ROM list. If any ideas - I'm up for testing.

MotexT said:
Actually I'm using your kernel. Systemless Root in recovery says like it's already patched and terminal returns "abort operation". Looks like you already patched it by Systemless SU, so I can't repatch it again. If you did so, revert this change.
Click to expand...
Click to collapse
Alright - systemless root doesn't work because my kernel uses a combined ramdisk, meaning the actual ramdisk of the ROM is in /sbin/ramdisk.cpio. SuperSU doesn't know that, tries to treat the main ramdisk as a normal one and fails (hence the abort). I'll try to find a solution...

I remember using this on the original XZ! So great it's being worked on. Will do some testing tomorrow. Thanks a ton, dev.

Olivier said:
Alright - systemless root doesn't work because my kernel uses a combined ramdisk, meaning the actual ramdisk of the ROM is in /sbin/ramdisk.cpio. SuperSU doesn't know that, tries to treat the main ramdisk as a normal one and fails (hence the abort). I'll try to find a solution...
Click to expand...
Click to collapse
We need either edit Systemless SU zip to patch proper boot image or make regular SU zip working (aka system mode) - for now, with .185 kernel it gives bootloops due to SELinux changes

but the z3+/z4 dont have any rom and dont have any romer ╮(︶︿︶)╭

windowgame98 said:
but the z3+/z4 dont have any rom and dont have any romer ╮(︶︿︶)╭
Click to expand...
Click to collapse
Make one.

MotexT said:
We need either edit Systemless SU zip to patch proper boot image or make regular SU zip working (aka system mode) - for now, with .185 kernel it gives bootloops due to SELinux changes
Click to expand...
Click to collapse
Fixed, please re-downloaded the boot image (from the same link), I have updated it. You can now also use the MultiROM Manager to install MultiROM. It can download TWRP, MultiROM and my kernel.

Useless till we dont have at least 2 roms... BUT HEY Thx for making it for the future maybe?
Sent from my E6553 using XDA-Developers mobile app

KOALAaufPILLEN said:
Useless till we dont have at least 2 roms... BUT HEY Thx for making it for the future maybe?
Sent from my E6553 using XDA-Developers mobile app
Click to expand...
Click to collapse
We have some unstable CM builds for now.

So, tested it for a while. Bugs: second ROM doesn't booting properly - just rebooting to black screen, then red LED blinks 3 times and reboots to that state again and then just after second reboot boots to multirom ROM menu.

@MotexT, yes, for me same behavior. Even stock kernel sometimes reboot device on bootanimation.

MotexT said:
So, tested it for a while. Bugs: second ROM doesn't booting properly - just rebooting to black screen, then red LED blinks 3 times and reboots to that state again and then just after second reboot boots to multirom ROM menu.
Click to expand...
Click to collapse
Quarx said:
@MotexT, yes, for me same behavior. Even stock kernel sometimes reboot device on bootanimation.
Click to expand...
Click to collapse
Try now; use the MultiROM Manager to upgrade.

ia this compatible with .253 stock and CM build by Quarx?

I've just ordered a 16GB microSD to test this
You said you haven't tested it with stock ROM well that's precisely what I plan on doing... I'm running CM13 and after a couple of days of research there doesn't seem to be any solution in sight for the camera bugs. However after seeing your thread, I figured if all goes well I could be running CM13 daily and just reboot to the stock ROM when I need to shoot a video (necessary for my professional activity... I'd rather do this than always have my old phone with me).
I'll keep you updated once I get the microSD.
Edit: looks like your server is offline, I can't download your APK... I'll try to download it again tomorrow.

[ROM][SiriuZ V3.0][GT] EMUI 8.0 P20 Lite by Catuva21

{
"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"
}
V 3.0 - EMUI 8.0​DONOT COPY MY WORK, Ask for Permissions
Code:
- I am not responsible for the damage of your cell phone if you do not correctly perform the steps
- loser warranty
- if you are not sure better not to touch and leave this page
COMPATIBLE WITH
with all versions, P20 lite, remember to know your original compilation if at any time you want to return to stock for example ANE-LX3C25 with this data you can return to stock.
This version is based on the official modification of EMUI, activating functions that are in the high-end versions, adding some modifications for their better performance.
REQUIREMENTS:
- EMUI 8.0.0
- Activate the OEM unlocking, which is in adjustment / developer options and leave it so forever to avoid conflict.
- unlock the bootloader.
- install the recovery that I will leave, automated from windows-linux
Guard the rom in an external memory.
Turn off the cell phone press the plus and power buttons until you have the TWRP window
Press WIPE
Press FORMAT DATA
Write the word "yes" without quotes and accept, just do the work
Press BACK to go back several times to the main window.
Press WIPE, then ADVANCE WIPE
Verify that the partition DATA this in the f2fs extension
Mark: Dalvik, cache, data, internal storage, system
IMPORTANT !: do not mark "micro sdcard".
Once you have marked, slide the "swipe to wipe" arrow to clear it.
Go back to the main sale, press INSTALL
Press SELECT STORAGE
Switch to Micro SDCard to find the rom.
Look for the MORFUZ rom and flash
At the end of the installation press "wipe davilk-cache", wait for it to finish.
Reboot system.
Congratulations now will start the rom MORFUZ
It seems that Huawei modified the modem partition in the September-October patch and the MORFUZ kernel does not work incoming and outgoing calls.
-IMPORTANTonly install this module from the root Magisk options if incoming and outgoing calls do not work.
https://mega.nz/#!F7oXzSRZ!8uuSCIx4UTbuWkTEYoFmTXTCwvIr6Reuc1vyq6OIhw0
Rom Siriuz
https://mega.nz/#!tYBjTQhC!yPbPXkazpQUy7bzLdm33rEapihBB8iVmSGlGxy1RweI
TWRP Mod by catuva21 - VERSION 2
unzip, the file is automatic
https://mega.nz/#!uD4FlCqL!ERBzP4ZWa2sR8f_wnn15F_cOFCdYVKgfYETjiehQkkQ
TELEGRAM GROUP
https://t.me/joinchat/ERAhfQ8kyF6_iH5nMun5dg
Contributors:
CATUVA21
Credits:
- Openkirin Recovery TWRP
- Alexxx1
- Chisetdel31260
ROM OS Version: ANE-L
ROM Kernel: Stock
ROM Firmware Required: EMUI 8.0.0
Version Information:
Status: Stable
Created on: 2018-06-30
Last Updated on: 2018-09-10

DESCRIPTION ROM SIRIUZ​DETAILS OF THE ROM
SIRIUZ 3.0
- Base firmware P20 lite (security patch for September).
- Custom kernel MorfuZ now works wifi and bluetooth.
- Huawei ID integrated and running.
- New bootanimation.
- New bootlogo.
- Percentage activated from start, for other models.
- Activated the font change in themes.
- New topics.
- 7 themes to change the font customization.
- Yorreciones de camara.
- Youtube advance updated.
- Adaway ad blocker.
- VolTe Activated.
- Magisk 17.1
SIRIUZ 2.6
- P20 lite base firmware (August security patch).
- MorfuzKernel 2.1 selinux Permissive.
- Turbo GPU.
- Added support init.d.
- Added busybox.
- Huawei ID back.
- Boot profile for the Darknnes-Blu_Active kernel within init.d improves performance.
- Change of the MTweaks auditor kernel application.
- Added Lent AR fun camera function.
- Magisk 16.7.
- Increase bitrate of photos and video, improve quality.
- Application of return mail.
- Youtube Mod Updated.
- New Gboard keyboard.
SIRIUZ 2.4
-Base firmware P20 lite(security patch jun).
-Activated Dual Speaker.
-Added DolbyAtmos in Music.
-New Boot logo.
-Added custom watermark for the P20 lite.
-Now without patches.
-Installation mode AROMA-INSTALLER.
-Music: stock or crack.
-Camera: stock, Mate10Pro or P20Pro.
-Root: Magisk or Supersu.
-Navbar, Use the fingerprint sensor as a navigation bar.
-Solid explorer, Kernel Auditor, Quick Reboot.
-MxPlayer.
-Sony Music.
-Eliminated the data space.
-Deodexed (improves optimization).
-Improvements in the quality of photos, video and sound..
-It eliminated unnecessary google applications.
-Added Call Recorder.
-Added Youtube Mod (function in the background).
-Activated multi-user X5.
-Keyboard change, google.
-Reduction of size of icons.
-Activated glove mode.
-Mtu 1500.
-Explored files improved.
-Added main screen design 5x5,5x6,6x5.
-Added more applications of social networks of Twin cloning.
. * facebook, faceboot lite
. * messenger, messenger lite
. * whatsapp, whatsapp mod
. * instagram
. * snapchat
. * telegram
. * twitter
. * mega
. * creativefrends
. * microsoft office

r2

when i go to security options settings app crashes
cant setup fingerprint id
oh now it works after playing with the instalation settings

I got an error during installation and start bootlooping, latter with more time I'll try again.
Thanks to share your work with us.

Error finishing the installation:
set_perm: some changes failed
Other problems:
-Does not detect micro sd
-You can not configure a screen lock method (settings close when you try to enter that section)
-Developer options can not be activated (the settings are closed when you press compile)
Those problems are what happened to me, I followed the installation instructions exactly as it says in the post

same problem with me

brandox0 said:
Error finishing the installation:
set_perm: some changes failed
Other problems:
-Does not detect micro sd
-You can not configure a screen lock method (settings close when you try to enter that section)
-Developer options can not be activated (the settings are closed when you press compile)
Those problems are what happened to me, I followed the installation instructions exactly as it says in the post
Click to expand...
Click to collapse
The rom is working or not?

thanks for the rom!
followed the install instructions except i didn't install the TWRP321_OREO_P20LITE.rar because i previously installed it following these instructions.
chose to install the custom kernel and SuperSU. not sure right now what else. i will write it down when i try the next build.
i encountered the following issues:
-error finishing the installation: set_perm: some changes failed during flashing (could this be because i didn't install your modded TWRP?)
-unable to set the lockscreen options
-unable to set up fingerprintid
-settings crashes when attempting to enable dev options
-sd card isn't detected within the fw
once i saw the sdcard isn't detected, i tried to recover from my latest backup but TWRP wasn't able because /system was only mounted as read-only (could this be as well because i didn't install your modded TWRP?).
ended up having to reflash stock from erecovery, rerooting and reinstalling TWRP in order to restore from my last backup (maybe i did something wrong?).
after reading the features list, i personally would use it as my main rom. i'd love to see it with viper4android included and with an all dark theme though but that's just me.
thanks for your work! looking forward to more!

luigi997 said:
The rom is working or not?
Click to expand...
Click to collapse
Well, if you eliminate the fact that the fingerprint reader or any other screen lock method does not work, you can not use the micro sd and the developer options are not available. So yes, the rom works.
You can try to urge it, maybe you're lucky and do not have mistakes.

brandox0 said:
Well, if you eliminate the fact that the fingerprint reader or any other screen lock method does not work, you can not use the micro sd and the developer options are not available. So yes, the rom works.
You can try to urge it, maybe you're lucky and do not have mistakes.
Click to expand...
Click to collapse
If i try to uninstall an app, the system reboot.
I've installed the modded kernel

Anyone with no issues? Can be used as a daily driver?
Please report back testers ^_^

[email protected] said:
Anyone with no issues? Can be used as a daily driver?
Please report back testers ^_^
Click to expand...
Click to collapse
Nope, so far I haven't seen anyone reporting positively. No fingerprintid and no security features makes the rom pretty much unusable as far as I've tested and seen on the thread. I'm awaiting to see how this develops..

Success
This rom is working prefectly.. i have keep on trying to re install the rom.I always follow the exact instruction, and i have found out. You will have a set_perm: some changes failed. IF you mark check the navbar, and status bar while in aroma installer.. I have able to use everything. Ill try to make a screenshot of it.

riorabel12 said:
This rom is working prefectly.. i have keep on trying to re install the rom.I always follow the exact instruction, and i have found out. You will have a set_perm: some changes failed. IF you mark check the navbar, and status bar while in aroma installer.. I have able to use everything. Ill try to make a screenshot of it.
Click to expand...
Click to collapse
Awesome! I'll try again!
Did you flash the recovery included in the post?
What do you mean with "If you mark check the navbar, and status bar while in aroma installer"?
Thanks for the feedback!

madalone said:
Awesome! I'll try again!
Did you flash the recovery included in the post?
What do you mean with "If you mark check the navbar, and status bar while in aroma installer"?
Thanks for the feedback!
Click to expand...
Click to collapse
YES. I HAVE FLASH THE RECOVERY. AND WHEN YOU FIRST DO THAT... AND YOU SHOULD PUT THE ROM INTO YOUR SD CARD..
YES, IF YOU MARK CHECK THE NAVBAR ANF STATSBAR. WHILE CHOOSING YOUR DESIRED APPS. YOU WILL SEE THAT IN THE VERY LAST PAGE OF THE AROMA INSTALLER. WHERE YOU HAVE THE OPTIONS. NAVBAR STATSBAR, SOLID EXPLORER, KERNEL AUDIATOR, AND the QUICK REBOOT. SO JUST MARK CHECK THE SOLID EXPLORER,KERNELAUDITOR,AND QUICK REBOOT..
SO TRY IT NOW. AND GIVE ME SOME FEEDBACK IF IT WORKS IN YOU. ALSO KINDLY TRY TO DO A SCREENSHOT. I DONT HAVE OTHER PHONE TO TAKE A SHOT ON IT. KUDOS THANKS

ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting).
edit1: after a cache wipe, i rebooted the phone. the phone boots but no root.
tried to flash SuperSU through TWRP but failed.
wiped data/cache/dalvik/system & reflashed rom with Stock kernel & Magisk no bootimage patcher errors. after a cache wipe, rebooted & phone has root :victory:
brandox0 said:
I also want to try again, but I'm still not sure.
So far, how is the rom working? Is there a fault signal mentioned above?
Click to expand...
Click to collapse
so far i'm still getting all my apps installed. i'll letcha know how i get on with it.
edit2: as i am stubborn, i reflashed the rom with the custom kernel and Magisk. root is on and the phone seems to run smoothly.

madalone said:
ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting). is that the kernel failing to install?
after a cache wipe, i rebooted the phone. the phone boots as expected.
Click to expand...
Click to collapse
I also want to try again, but I'm still not sure.
So far, how is the rom working? Is there a fault signal mentioned above?

madalone said:
ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting).
edit1: after a cache wipe, i rebooted the phone. the phone boots but no root.
tried to flash SuperSU through TWRP but failed.
wiped data/cache/dalvik/system & reflashed rom with Stock kernel & Magisk no bootimage patcher errors. after a cache wipe, rebooted & phone has root :victory:
so far i'm still getting all my apps installed. i'll letcha know how i get on with it.
Click to expand...
Click to collapse
I worked perfectly, the only problem is that mobile became very slow.

rapza4 said:
I worked perfectly, the only problem is that mobile became very slow.
Click to expand...
Click to collapse
i had that plus overheating but after what i did in edit2 it was gone and the phone runs smoothly.
on another note: is it possible to make this rom have init.d support somehow? it'd be cool for stuff like Liveboot..

Update Rooted Tab S6 SM-T860 without wiping data using Odin

Normal disclaimers, I take no responsibility if things go sideways. While this worked for me you should probably backup anything you care about.
My tablet was only rooted with no TWRP. I haven't needed TWRP installed permanently for quite a while now.
Have working adb tools
Download the current/updated firmware with frija or other tool
Extract the firmware
Adb push the AP_XXXX.tar.md5 file to your device sdcard
adb push AP_XXXX.tar.md5 /sdcard/Download/
Open Magisk (I'm using the canary version, may not be needed but I know it works for A11)
Select Install
Select and Patch a File
Choose the file you just copied to the device
Magisk will patch the file and return a file name and location
adb pull this file back to your computer
adb pull /sdcard/Download/magisk_patched_xxxxxxx.tar ./
Turn off all your magisk modules. (If your modules are all compatible with the version you're going to this is ok but mine were not which sent my tablet into a bootloop after the update)
Turn tablet off
Open Odin
Hold both volume buttons and plug in the usb cable to your computer
Push the volume up button to continue to download mode
Add the AP, BL, and HOME_CSC files to Odin.
NOTE: If you use the CSC file instead of HOME_CSC you will wipe the device/factory reset. This can be used on a fresh device to gain root as well.
Cilck start and wait for the process to complete
If you forget to turn off the magisk modules and end up in a bootloop like me, hold the volume up button. Eventually the the tablet should go into safe mode which will cause magisk to disable all the modules. Mine finally booted after this.
Passing SafetyNet:
Turn on Magisk Hide
Get the safetynet fix test 2 module from kdrag0n
SafetyNet should pass with basic attestation
Fix Bluetooth with the BluetoothLibraryPatcher module. If you don't you will need to re-pair bluetooth devices after each reboot.

Thanks. I have been hoping the this was possible. I guess a kernel install needs a wipe then? SELinux is really getting on my nerves.

quasiperfect said:
Thanks. I have been hoping the this was possible. I guess a kernel install needs a wipe then? SELinux is really getting on my nerves.
Click to expand...
Click to collapse
Can't say. I primarily root to block ads and route my hotspot traffic though my VPN. The stock firmware with root gives me that.
Using my steps you would end up with a stock rooted kernel. If your existing setup plays nice with that you should be ok. You could always try and see, worst case you have to wipe anyway.

I'm using successfully this method: https://forum.xda-developers.com/t/...unencrypted-and-retain-all-your-data.3798256/ to update the s8. The tab isn't rooted (yet) so haven't use it here.
m.

meduza said:
I'm using successfully this method: https://forum.xda-developers.com/t/...unencrypted-and-retain-all-your-data.3798256/ to update the s8. The tab isn't rooted (yet) so haven't use it here.
m.
Click to expand...
Click to collapse
I'm afraid very little of that will apply to the Tab S6.

... well, when I'll be rooted, I'll definitely try it Maybe someone will try it earlier and report it ... .
m.

Thanks OP. This worked easily for me and I'm now updated. The S6 is working far better - less lag, more battery. I'm a happy camper.

Did you have the boot loader unlocked and Dm-veity disabled when you did this?
i used this meathod and it checked my file system booted into download mode and gave me this error: there is a root hash in your system.
I have managed to fix this issue with no data loss though

BaigGam3rss said:
Did you have the boot loader unlocked and Dm-veity disabled when you did this?
i used this meathod and it checked my file system booted into download mode and gave me this error: there is a root hash in your system.
I have managed to fix this issue with no data loss though
Click to expand...
Click to collapse
BL unlock and root is all I use. Encryption and dm-verity are still enabled.

Hi, I have a short question.
I tried to update my Samsung Tab S6. I downloaded the latest firmware file from November and copied the AP*.tar.md5 file over to the tablet. I started Magisk (v23) and tried to patch the file, but every-time I select the file nothing happened. Where is my mistake, please?

Hello, and thank you for your work. Would there be any updates/changes to this procedure, for the android 12 update?

Arobase40 said:
If you also have TWRP, look at here :
SM T865 - T860 One UI 4.1.1 Android 12 - updates - general discussion
Hi, this is a general thread about our stock Android firmware with One UI 4.1 now and it's later updates. We can exchange our experiences and discuss software changes etc. here. April 2020: Android Q. finally arrived :) Changes...
forum.xda-developers.com
Post #585
I have done it many times and all is working fine and no issue with Android 12.
No need to keep your hand on the buttons as it will reboot on TWRP anyway...
Click to expand...
Click to collapse
Well I had some issues, I'm sure by some error on my part. Perhaps instead of just turning off my modules in Magisk, I should have uninstalled them. I couldn't get out of the bootloup, holding the volume up button did not work. I was able to get into recovery, and factory reset it. Then it booted up no problem, with Magisk installed. Was able to root no problem. Luckily I predicted there would be problems, and I used an app on Fdroid called Neo Backup, which successfully restored all apps and data, and cache. Samsung cloud was used to restore all settings, WiFi passwords, wallpaper, etc.

Arobase40 said:
You said nothing about your configuration and if you have TWRP or not, if you used normal CSC or HOME_CSC.
If you used normal CSC, this should be the problem as it needs to factory reset your tab !
Finally, is your tab updated now and running and with which version and from which initial version ?
Finally, if you have Magisk up and running, you can also download and install "Magisk Bootloop Protector" module...
Click to expand...
Click to collapse
I did have TWRP installed, and was careful to use HOME_CSC, as I did not want my device wiped. Tablet is fully updated to 12, and rooted and running well. I updated from latest build of 11 stock firmware. I had Riru and LSPosed modules and Busybox modules. I'll probably put Busybox back on, but I only put LSPosed on, for Gravitybox, which I don't think I will use anymore anyway.
Didn't not know about the Bootloop protector module, good tip.

T860 Android 12 One UI 4.1
Used this method and it required a factory reset from recovery
{
"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"
}

Arobase40 said:
That's not the truth and there is no reason to do that !!!!
Click to expand...
Click to collapse
I don't understand your statement

Arobase40 said:
Once again when you said "Used this method and it required a factory reset from recovery" is NOT the truth specially when you use the HOME_CSC and thus you should keep all your data safe !
Click to expand...
Click to collapse
You can say it's not the truth, but it wouldn't boot so I booted into recovery and it told me /data was corrupted and offered a factory reset

I need to delete this post from my favorites. It keeps screwing me over every time I follow this post to update.

correct me if i am wrong, i am outdated
1 with home_csc, it won't wipe if you are rooted with encryption disabled (in the past). is it true that if i am on stock firmware and root it, twrp can handle the data partiition properly without wiping my data now?
2 i havent set any password. this was required for decryption in twrp for reading the data partition partition. so without any password set, will twrp able to keep my data, ie without wipe?
and,
3 as @l7777 mentioned "I have managed to fix this issue with no data loss though", how did you do that?

xxjoe08 said:
correct me if i am wrong, i am outdated
1 with home_csc, it won't wipe if you are rooted with encryption disabled (in the past). is it true that if i am on stock firmware and root it, twrp can handle the data partiition properly without wiping my data now?
2 i havent set any password. this was required for decryption in twrp for reading the data partition partition. so without any password set, will twrp able to keep my data, ie without wipe?
and,
3 as @l7777 mentioned "I have managed to fix this issue with no data loss though", how did you do that?
Click to expand...
Click to collapse
It's been a long time since I did this. My only issue was Magisk module compatibility. I don't use TWRP anymore so I can't speak to that. I have to imagine with the changes to Magisk and Android 12 things will be different.

[ROM][OFFICIAL][hotdogg][11.0] crDroidAndroid v7.x

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
crDroid Recovery (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
You must have crDroid recovery installed in both slots
Boot crDroid recovery
Format Data
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_crdroid_zip_here>
Install gapps (Optional)
Reboot recovery again (from advanced menu)
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_gapps_zip_here>
Reboot
Update installation:
You must have crDroid recovery installed in both slots
Boot crDroid recovery
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_crdroid_zip_here>
Install gapps (Optional)
Reboot recovery again (from advanced menu)
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_gapps_zip_here>
Reboot
NOTE: If all the flashing process succeeds the terminal output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error which is also fine.
Sources:
ROM: https://github.com/crdroidandroid
Device sources: https://github.com/hotdogg-dev
Download:
ROM https://crdroid.net/hotdogg
Changelog: https://raw.githubusercontent.com/c..._vendor_crDroidOTA/11.0/changelog_hotdogg.txt
Known issues:
* You tell me
NOTE: Default camera and gallery are from OxygenOS to have all features and cameras working. Video section of the camera will force close the app, you can take videos but doing a long press on camera shutter button.
Visit official website @ crDroid.net
DarkJoker360 Telegram Updates
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

Reserved

Thank You for adding this rom. Been a long time since I've ran crDroid. Really looking forward to it.

so i have looked, but what do you mean with having "crDroid REcovery installed on both slots?"
so in fastboot i would set current slot a.. flash recovery, then set slot b.. flash recovery?
been out of the flashing thing since the LG v20 so this has changed a bit.

Good day all. I just flashed my onplus 7t McLaren to crDroid Rom. And I love it. Just a quick question. When the screen is off I have to press the power button for it to wake up. How can I do it so I tapped on the screen instead for it to come up? Thank you

Northern Lights said:
Good day all. I just flashed my onplus 7t McLaren to crDroid Rom. And I love it. Just a quick question. When the screen is off I have to press the power button for it to wake up. How can I do it so I tapped on the screen instead for it to come up? Thank you
Click to expand...
Click to collapse
Under Display setting if you scroll all the way down you can turn on tap to wake

Superxer said:
Under Display setting if you scroll all the way down you can turn on tap to wake
Click to expand...
Click to collapse
Thank you very much that did it..

So far, super impressed with this ROM and the overall experience! I like the little "ditties" under the Welcome to crDroid at the top!
So question, the Preinstallation section says, "Magisk 20.0 or newer for root (after first boot) - (Download from here)". I have installed the Magisk APK from the Github repo, and it confirms "Ramdisk Yes" which, from what I am reading on Magisk's install page, means I need to patch the boot.img file. Magisk says, "You should be able to extract the file you need from the official firmware packages or your custom ROM zip (if using one)." I think that means I need to somehow extract this .img file from crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip. However, when I look into that zip, I'm not seeing it. Forgive me if I am just misinformed or overlooking something!

Super happy to see some development on hotdogg again, and one of my favorite ROMs no less. I just hope to get regular updates unlike everything else (besides Carbon 8.0, not even 9.0), but am super happy to find everything working, unlike some of the one off ROM builds on here. So far, no problem (other than not realizing Gapps weren't included and Magisk causing softbricks if installed before setup). Everything tested so far is working and has the battery life I expect from crDroid.
TitaniumCoder477 said:
So far, super impressed with this ROM and the overall experience! I like the little "ditties" under the Welcome to crDroid at the top!
So question, the Preinstallation section says, "Magisk 20.0 or newer for root (after first boot) - (Download from here)". I have installed the Magisk APK from the Github repo, and it confirms "Ramdisk Yes" which, from what I am reading on Magisk's install page, means I need to patch the boot.img file. Magisk says, "You should be able to extract the file you need from the official firmware packages or your custom ROM zip (if using one)." I think that means I need to somehow extract this .img file from crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip. However, when I look into that zip, I'm not seeing it. Forgive me if I am just misinformed or overlooking something!
Click to expand...
Click to collapse
So the easiest way to install magisk and (I did it on this ROM) is to rename magisk.apk to magisk.zip and install that through TWRP. On this ROM, you MUST do it after setup or risk a potential soft-brick.

Found my first issues. Cannot install Magisk modules through the Magisk app, and TWRP decryption doesn't seem to work. I'm not sure if the issues are related, but the Magisk issue seems related to the kernel and it's ability to process different file formats. Interesting enough, Substratum module installed automatically fine and Systemless hosts also works fine, but modules from the repo fall with a simple "Installation Failed" message. Tried turning off passcode but that didn't allow TWRP to see any folders inside /sdcard still so couldn't try installing modules in TWRP how I normally would either.

I have been using with this rom and i wanted to see if anyone had this issue, lets say you are on a call and I have the speaker on, I hear crackling noises. ?? cant figure out

thats_the_guy said:
Super happy to see some development on hotdogg again, and one of my favorite ROMs no less. I just hope to get regular updates unlike everything else (besides Carbon 8.0, not even 9.0), but am super happy to find everything working, unlike some of the one off ROM builds on here. So far, no problem (other than not realizing Gapps weren't included and Magisk causing softbricks if installed before setup). Everything tested so far is working and has the battery life I expect from crDroid.
So the easiest way to install magisk and (I did it on this ROM) is to rename magisk.apk to magisk.zip and install that through TWRP. On this ROM, you MUST do it after setup or risk a potential soft-brick.
Click to expand...
Click to collapse
I was looking for a method that didn't involve TWRP since I too came across the same issues you encountered. I actually just finished rooting crDroid a few minutes ago. Here were my steps:
Grab a copy of payload-dumper-go (I used payload-dumper-go_1.2.0_linux_amd64.tar.gz)
Make it executable and install golang if you haven't already
Unzip crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip
Type: ./payload-dumper-go crDroidAndroid-11.0-20210927-hotdogg-v7.10/payload.bin
Copy the boot.img file from new folder to your phone
Also copy Magisk-v23.0.apk to your phone and install it
Open the Magisk app and and tap Magisk > Install
Choose Select and Patch a File (should be the only option you can choose at the moment)
Browse to and choose the boot.img file
Once patched, copy the resulting magisk patched .img file back to your computer
Restart your phone into fastboot mode
Then flash with: fastboot flash boot /path/to/your/magisk_patched.img file
You may also want to flash the other boot; for example, in my case boot_a was flashed, so I then typed: sudo ./fastboot flash boot_b ~/Downloads/magisk_patched-23000_dCYIE.img
Then restart your phone!
These are the steps I performed, gleaned from the Magisk github's install.html#magisk-in-recovery page and also @gwolfu at https://forum.xda-developers.com/t/...droid-v7-10-13-sep-2021.4292267/post-85192599

Northern Lights said:
I have been using with this rom and i wanted to see if anyone had this issue, lets say you are on a call and I have the speaker on, I hear crackling noises. ?? cant figure out
Click to expand...
Click to collapse
I have not experienced any issues so far. Are you talking about speaker phone when you're on a call? If so, I will try that on my next call and let you know.

TitaniumCoder477 said:
I have not experienced any issues so far. Are you talking about speaker phone when you're on a call? If so, I will try that on my next call and let you know.
Click to expand...
Click to collapse
Hi Titanium, yes when Im on a speaker phone. This doesnt happen always but often. Thanks

Northern Lights said:
Hi Titanium, yes when Im on a speaker phone. This doesnt happen always but often. Thanks
Click to expand...
Click to collapse
Well, I've had a few calls both on and off speaker phone with no issues. Very clear.

What are the fastboot commands to flash crDroid recovery to both A/B slots?

gnabtib8 said:
What are the fastboot commands to flash crDroid recovery to both A/B slots?
Click to expand...
Click to collapse
fastboot flash recovery_a <drag_recovery_img_here>
fastboot flash recovery_b <drag_recovery_img_here>

gnabtib8 said:
What are the fastboot commands to flash crDroid recovery to both A/B slots?
Click to expand...
Click to collapse
Nevermind, I see you asked about recovery and it's been answered!

So far so good, it's breath of fresh air to wipe away all the TMobile bloat. Is wireguard support and Dolby audio (OnePlus 7 pro build uses) planned features? Thank you for this build

This Dolby Atmos magisk module with audio modification library magisk module fixes the low volume issue.
GitHub - reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module
Contribute to reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module development by creating an account on GitHub.
github.com
Does anyone have L1 with this rom?

[ROM] Samsung Galaxy J8 Debloated+Rooted Stock Rom v7.1 - J810F/G/M/Y/GF - j8y18lte

{
"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"
}
YOU ARE THE SOLE RESPONSINLE FOR WHAT HAPPENS TO YOUR DEVICE. PROCEED WITH CAUTION!​
Hi all! I should have posted this years ago but anyways... This rom is made due to the fact that there is no bug-free rom for Galaxy J8, not even any development going on. So, I decided to de-bloat the latest stock firmware, polish it a bit, configure some settings and fix some of the issues.
Twrp and Root Guide: https://forum.xda-developers.com/t/...d-flash-twrp-j810f-g-m-y-gf-j8y18lte.4479201/
WORKING
Everything that works on stock rom, including VOLTE.​
NOT WORKING
Nothing.
CHANGELOG
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder.
BLOATWARE LIST
Read the "More Info About Bloatwares" pdf file inside the Google Drive folder.
INSTRUCTIONS​HOW TO MAKE A CLEAN INSTALLATION (WARNING! YOU WILL LOSE ALL YOUR DATA INCLUDING INTERNAL STORAGE -pictures, songs, downloads, files, apps etc.-)
1. Install/Update TWRP (use v3.5.0) (big thanks go to goldfish07)
2. Create backup, INCLUDING VENDOR (everything you need - including your files in internal storage - use an external storage if possible)
3. Reboot into TWRP. Navigate to Wipe/Format Data type yes and apply it. Then, go to Wipe-Advanced Wipe, select ONLY these "Dalvik/Art Cache - System - Vendor - Data - Cache" and format them.
4. Copy "J8_De-Bloated_Stock_Rom_v7.1.zip" to your internal or external storage and flash it.
5. Reboot and enjoy! (it might say "NO OS INSTALLED", it is normal when you format system from advanced wipe and then install the zip, just swipe and system will start) (first boot may take a couple of minutes, please be patient, YOU WILL ONLY SEE THE "SAMSUNG LOGO", NOT the animation and it is NORMAL)
HOW TO MAKE A DIRTY INSTALLATION (ONLY IF YOU ARE COMING FROM ANOTHER VERSION OF DEBLOATED ROM) (YOU WILL NOT LOSE ANY DATA)
1. Open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android.
2. Go inside the "data" folder and delete the 3 folders (adb, app, system). Do not delete the "local" folder.
3. Copy the "J8_De-Bloated_Stock_Rom_v7.1.zip" to your phone.
4. Reboot into TWRP.
5. Flash the "J8_De-Bloated_Stock_Rom_v7.1.zip".
6. When installation completes, select "Wipe cache/dalvik" and swipe.
7. Reboot and enjoy!
Contributors
goldfish07 (Ayush Bisht) for anykernel and TWRP
Kernel Source (thanks to goldfish07 (Ayush Bisht))
GitHub - goldfish07/android_kernel_samsung_j8y18lte: base: LA.UM.8.6.r1-04700-89xx.0
base: LA.UM.8.6.r1-04700-89xx.0. Contribute to goldfish07/android_kernel_samsung_j8y18lte development by creating an account on GitHub.
github.com
ROM INFO:
Security Patch Level2021-12-01OS VersionAndroid 10PDAJ810FJXU6CVA1
Download: https://tinyurl.com/J8-Debloated-Rom

Reserved

New Update v7.1!
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder for changelog details.

BNFCTR said:
New Update v7.1!
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder for changelog details.
Click to expand...
Click to collapse
Hi, thank you firstly.
I installed this rom everythink is ok but no internet connection.
Any solution?

sinanlenfom said:
Hi, thank you firstly.
I installed this rom everythink is ok but no internet connection.
Any solution?
Click to expand...
Click to collapse
Please follow the clean installation steps carefully.

Hi bro thank you so much this rom work perfectly everything work thanks a lot

Download link (https://tinyurl.com/J8-Debloated-Rom) is not working ((
Who can share it?

there is a way to make a ROM to make the touch work, I have a j810m and the touch stopped after updating to Android 10 binary 3 version, I had changed the display and I didn't know I couldn't update

Cheat said:
Download link (https://tinyurl.com/J8-Debloated-Rom) is not working ((
Who can share it?
Click to expand...
Click to collapse
The link is working. Please try using another browser or use vpn.

jabsjrm said:
there is a way to make a ROM to make the touch work, I have a j810m and the touch stopped after updating to Android 10 binary 3 version, I had changed the display and I didn't know I couldn't update
Click to expand...
Click to collapse
While system update check, it also verifies your display originality. If you change your display on untouched stock rom, it will be permanently disabled unfortunately. You should have upgraded to debloated rom or disabled system update apps so that you could keep using changed display. There is no luck fortunately. (you cannot downgrade to Android 9 to solve the issue because bootloader does not allow that)

This and the "More info about bloatwares" is great, thanks for all your efforts. The device is finally usable without stutter even when scrolling.
But there is a small thing -> I think you should remove default magisk so that it can be installed with app and be able to update.

erfto said:
This and the "More info about bloatwares" is great, thanks for all your efforts. The device is finally usable without stutter even when scrolling.
But there is a small thing -> I think you should remove default magisk so that it can be installed with app and be able to update.
Click to expand...
Click to collapse
You're welcome. I configured some of the Magisk settings so that you do not need to do anything so as to be able to successfully pass SafetyNet. Additionally, If I remove default installation of Magisk as an app, stub app will give you error while downloading the app unfortunately. Lastly, Magisk v24.3 is the latest working version for J8. Magisk v25.x versions will bootloop the device. Therefore, do not attempt to update Magisk. Considering these issues, I decided to include Magisk and its configurations. If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.

BNFCTR said:
You're welcome. I configured some of the Magisk settings so that you do not need to do anything so as to be able to successfully pass SafetyNet. Additionally, If I remove default installation of Magisk as an app, stub app will give you error while downloading the app unfortunately. Lastly, Magisk v24.3 is the latest working version for J8. Magisk v25.x versions will bootloop the device. Therefore, do not attempt to update Magisk. Considering these issues, I decided to include Magisk and its configurations. If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
Click to expand...
Click to collapse
I'm not knowledgable about this but i get it now, thanks for informing !

where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev

X - root said:
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
Click to expand...
Click to collapse
just do what was posted above?
BNFCTR said:
... SNIP ... If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
Click to expand...
Click to collapse

Where are people getting TWRP from? I can't see it listed for the J8 on their website: https://twrp.me/Devices/Samsung/
There's an unofficial one here:
[RECOVERY] TWRP 3.6.x.x for Samsung Galaxy J810G/GF/F/M/Y j8y18lte
TWRP 3.6.x.x for Samsung Galaxy J8 Note: I AM NOT RESPONSIBLE OF ANY DAMAGE WILL HAPPEN AFTER YOU FLASH THIS TWRP , ALWAYS DO BACKUP FIRST DOWNLOAD MODE 1. power off your Samsung J8/On8 2. press & hold both vol+ & vol- keys and insert USB driver...
forum.xda-developers.com

Bro i need galaxy theme is there any solution ?

X - root said:
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
Click to expand...
Click to collapse
You can uninstall it from Magisk homepage "Uninstall Magisk". The system may not boot without Magisk. Keep this in mind.

Canyoning.cat said:
Where are people getting TWRP from? I can't see it listed for the J8 on their website: https://twrp.me/Devices/Samsung/
There's an unofficial one here:
[RECOVERY] TWRP 3.6.x.x for Samsung Galaxy J810G/GF/F/M/Y j8y18lte
TWRP 3.6.x.x for Samsung Galaxy J8 Note: I AM NOT RESPONSIBLE OF ANY DAMAGE WILL HAPPEN AFTER YOU FLASH THIS TWRP , ALWAYS DO BACKUP FIRST DOWNLOAD MODE 1. power off your Samsung J8/On8 2. press & hold both vol+ & vol- keys and insert USB driver...
forum.xda-developers.com
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/t/...d-flash-twrp-j810f-g-m-y-gf-j8y18lte.4479201/

Kevin Ackerman said:
Bro i need galaxy theme is there any solution ?
Click to expand...
Click to collapse
Download the necessary apps from "Deleted Apps" folder inside the Google Drive folder and copy them to corresponding folder and reboot.