[UTILITY][STABLE][6.0.1][14.10.2016][SM-G93X/SM-N930] Debloater 4.2 Terminal or TWRP - Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri

[UTILITY][STABLE][6.0.1][14.10.2016][SM-G93X/SM-N930] Debloater 4.2 Terminal or TWRP - Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri

Introduction:
Have you ever want an interactive way to debloat your Samsung Galaxy S7 or Note 7? Are you looking for best speed, less battery consumption and more system space ?
Yes, with its backup strategy, this binary allows you to debloat your device and push the bloatwares to a backup folder under your internal storage and known as DebloatedFOLDER which will include all the categorized bloatwares. :highfive:
It runs on : Marshmallow 6.0.1 and tested on Galaxy S7 Flat/Edge and Note 7 whether normal or ported.
Environment : Terminal system mode or Terminal TWRP mode
Click on my xda thread here to move forward.
Note: POST your reply on the linked thread.
Thank you !

Related

[TOOL] [MultiSystem] MultiROM and Recovery Replacement for Android

XDA:DevDB Information
MultiSystem, Tool/Utility for the Verizon Samsung Galaxy Note 3
Contributors
hsbadr
Source Code: https://github.com/hsbadr/MultiSystem
Version Information
Status: Testing
Current Stable Version: 1.3.1
Stable Release Date: 2015-05-09
Current Beta Version: 1.1.1
Beta Release Date: 2015-05-02
Created 2015-05-03
Last Updated 2015-05-10

Supported Devices
Samsung Devices
Samsung Galaxy Note 3
Samsung Galaxy Note 3 - Verizon Variant [Retail Edition]
Samsung Galaxy Note 3 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 3 - AT&T Variant
Samsung Galaxy Note 3 - T-Mobile Variant
Samsung Galaxy Note 3 - Sprint Variant
Samsung Galaxy Note 3 - International Variant
Samsung Galaxy Note 4
Samsung Galaxy Note 4 - Verizon Variant [Retail Edition] (ROOT Required!)
Samsung Galaxy Note 4 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 4 - Verizon Varian [Retail Edition] (ROOT Required!)
Samsung Galaxy Note 4 - AT&T Variant (ROOT Required!)
Samsung Galaxy Note 4 - T-Mobile Variant
Samsung Galaxy Note 4 - Sprint Variant
Samsung Galaxy Note 4 - International Variant
Samsung Galaxy S4
Samsung Galaxy S4 - Verizon Variant
Samsung Galaxy S4 - AT&T Variant
Samsung Galaxy S4 - T-Mobile Variant
Samsung Galaxy S4 - Sprint Variant
Samsung Galaxy S4 - International Variant
Samsung Galaxy S5
Samsung Galaxy S5 - Verizon Variant
Samsung Galaxy S5 - AT&T Variant
Samsung Galaxy S5 - T-Mobile Variant
Samsung Galaxy S5 - Sprint Variant
Samsung Galaxy S5 - International Variant
Click to expand...
Click to collapse
LG Devices
LG G3
LG G3 VS985 - Verizon Variant (Under Testing + more features utilizing Bump!)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+++

Reserved #2

Reserved #3

Reserved #4

Reserved #5

Awesome!

Better news than unanimous decision

Will keep my eye on this thread for sure.

Thank you; I'm excited to see what this means for the Verizon and AT&T S4's/S5's.

Incredible. I can't wait to check this out.
[emoji106]

MultiSystem is released! Go go go!

Oh man, I really want to try out lollipop... But I'm not sure I could live without xposed. I recall a week back you said you could successfully downgrade to 4.4.4 KitKat. Thank you for the amazing work, you are awesome.
Sent from my SM-N900V using XDA Free mobile app

Parker Iverson said:
Oh man, I really want to try out lollipop... But I'm not sure I could live without xposed. I recall a week back you said you could successfully downgrade to 4.4.4 KitKat. Thank you for the amazing work, you are awesome.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
If you go to LP, you will loss xposed no matter what. There is no way to root 4.4.4 or 5.0 sadly.

I dont think that the binaries have installed. Nothing happens. And I can't create a virtual copy of the rom. It's like its not doing anything
Sent from my SM-N900V using XDA Free mobile app

On a VZW S4 I can install MultiSystem, but I must make a symbolic link for it to function correctly. Also, using the verbose option as you suggest results in an error, but it works fine without it.
I can reboot to a virtual slot from the app, and I've confirmed with "MultiSystem status" that I am running on a virtual system. Switching between Stock and virtual works fine from within the app, however, when I am booting normally, I see no green LED, thus no indication of when to press vol.up/vol.down/home.
I am going to install FlashFire and attempt flashing a rom in the virtual slot now.
UPDATE:
From the virtual system, I flashed Empty Galaxy rom with FlashFire. This resulted in an error message at boot saying unofficial software was installed, and it would not boot. I flashed the nc5 kernel back with Odin and it booted successfully to the new rom. I checked, and it certainly was running on the virtual system. I had to remake the symbolic link to MultiSystem. I tried several different ways to get back to the Stock system, but was unsuccessful until I disabled the virtual systems. Then it booted into the Stock slot but android.process.acore and android.process.media relentlessly FC; eventually resulting in a reboot. I am going to attempt again starting from rooted NK1 as stock.

G.moe said:
On a VZW S4 I can install MultiSystem, but I must make a symbolic link for it to function correctly. Also, using the verbose option as you suggest results in an error, but it works fine without it.
I can reboot to a virtual slot from the app, and I've confirmed with "MultiSystem status" that I am running on a virtual system. Switching between Stock and virtual works fine from within the app, however, when I am booting normally, I see no green LED, thus no indication of when to press vol.up/vol.down/home.
I am going to install FlashFire and attempt flashing a rom in the virtual slot now.
UPDATE:
From the virtual system, I flashed Empty Galaxy rom with FlashFire. This resulted in an error message at boot saying unofficial software was installed, and it would not boot. I flashed the nc5 kernel back with Odin and it booted successfully to the new rom. I checked, and it certainly was running on the virtual system. I had to remake the symbolic link to MultiSystem. I tried several different ways to get back to the Stock system, but was unsuccessful until I disabled the virtual systems. Then it booted into the Stock slot but android.process.acore and android.process.media relentlessly FC; eventually resulting in a reboot. I am going to attempt again starting from rooted NK1 as stock.
Click to expand...
Click to collapse
That's great! Could you please post more info: Device, OS version, kernel version, ... etc
It seems that it works for you, but you should install compatible ROMs without installing unauthorized kernels & the updater-script in the ROM .ZIP should mount /system correctly as mentions in the Q&A section (don't mount the phyical system partition; remount the current system!). The LED indicator might need some debugging, but you can boot the stock system if you removed the microSD, for now.

hsbadr said:
That's great! Could you please post more info: Device, OS version, kernel version, ... etc
It seems that it works for you, but you should install compatible ROMs without installing unauthorized kernels & the updater-script in the ROM .ZIP should mount /system correctly as mentions in the Q&A section (don't mount the phyical system partition; remount the current system!). The LED indicator might need some debugging, but you can boot the stock system if you removed the microSD, for now.
Click to expand...
Click to collapse
The rom I was starting from and trying to go to were both debloated Stock NK1 across-the-board on an VZW S4. I made sure /system was mounted correctly in updater-script. I also eventually figured out I could remove the SD card after various different attempts. Shortly I will try from Lollipop, and see if that solves anything, like the LED indicator or the binary getting linked appropriately.
EDIT: NK1 is 4.4.2.
Have you heard anything from @muniz_ri about the VZW S4 that could be useful?

G.moe said:
The rom I was starting from and trying to go to were both debloated Stock NK1 across-the-board on an VZW S4. I made sure /system was mounted correctly in updater-script. I also eventually figured out I could remove the SD card after various different attempts. Shortly I will try from Lollipop, and see if that solves anything, like the LED indicator or the binary getting linked appropriately.
EDIT: NK1 is 4.4.2.
Have you heard anything from @muniz_ri about the VZW S4 that could be useful?
Click to expand...
Click to collapse
I'm working on a newer "generic" version that'd support multiple devices. I'll also add diffrent installation options including a flashable .ZIP file, to avoid irregular script installation issues.

How to repartition microSD card for MultiSystem
@carl1961 has created a PDF tutorial for microSD card partitioning. You can download it from here.
Thanks to: @carl1961

[TOOL] [MultiSystem] MultiROM and Recovery Replacement for Android

MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices.
★ Disclaimer:
This service is FREE of charge, use it at your own risk, take it or leave it !
Click to expand...
Click to collapse
THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. USE AT YOUR OWN RISK!
Click to expand...
Click to collapse
MultiSystem is a powerful tool and can perform potentially dangerous and/or destructive operations on your device and data that may affect your life. While it is unlikely to do irreversable damage to your device, it is not impossible, and you should proceed with caution. Loss of data and/or the need to re-flash a full stock (manufacturer-supplied) firmware IMGs (usually requiring a computer) is always a possibility, and is increasingly likely if you do not know what you are doing. It is possible to lose root access when using MultiSystem on locked-bootloader devices running unexpoitable (bu rooted) Android firmware, without careful reading of documentation or following the instructions. Please consult with expert users before performing actions you do not comprehend.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Notes:
To devs: Please do not use/port MultiSystem to any other device. If you'd like to add support for your device, please contact me!
Click to expand...
Click to collapse
To users: This thread is only for DEVELOPMENT. If you need a place for general discussions, go to MultiSystem Q&A thread.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Features:
Keeps stock system partition safe/rooted
Permenant root survival with proper use
MultiROM support via virtual ROMs
Unlimited number of virtual ROMs
Booting options to choose stock, primary, or secondary virtual ROM
Any of the virtual ROMs can work as a recovery replacement
Flashing multiple ROMs at the same time without a reboot
Ability to create/install ROMs on Linux to microSD card
Great performance & battery life on virtual ROMs
Recovery solution to install ROMs or Mods
Easy upgrade to newer versions of Android
Ability to safely apply OTA updates to virtual system
Permissive SELinux and other kernel tweaks
Safe flashing that doesn't trip KNOX flag on Samsung devices
Wrapper script runs via ADB or a Terminal Emulator on device
APK to manage all MultiSystem functions with a nice UI and extra options
Management for the best performance & user experience
Support for all Android devices with microSD card
Portability to almost all devices
Compatibility with all Android versions
Click to expand...
Click to collapse
★ ChangeLog:
07.05.2015 - v1.3:
Option to mount stock system on boot
Option to mount virtual system on boot
Minor fixes & updates
05.05.2015 - v1.2.1:
Flashable ZIP installation
Fixed installation issues
Fixed mounting issues
Fixed LED indicator for S4/S5
Supported Note 3/4, S4/5, & other device
03.05.2015 - v1.1.2:
Initial public release
Minor bug fixes
02.05.2015 - v1.1.1:
Minor bug fixes
01.05.2015 - v1.1:
Public testing release
Updated all binaries
Added Boot Options to switch ROMs
Added primary & secondary virtual ROMs
Added Sleep Time option on boot
Added create IMG from system partition
Added copy IMG from another virtual ROM
Added option to mount system partition
Added option to mount any virtual IMG
Added option to clear log files
Minor bug fixes
24.04.2015 - v1.0:
Internal testing release
Click to expand...
Click to collapse
★ Instructions:
READ everything about MultiSystem here & Q&A thread
BACKUP all your data to an external storage or computer
INSTALL a stable stock ROM for your stock system
PARTITION your microSD card into two (FAT32/ExFAT & EXT4) partitions
DOWNLOAD the latest version of MultiSystem APK
INSTALL MultiSystem APK & open it
INSTALL MultiSystem binaries by pressing Install button
FLASH the associated .ZIP file to add MultiSystem support/hijack
REBOOT to check GREEN LED for boot options & check permissive SELinux
Now, you should be able to create a virtual ROM & boot into it...
If you're upgrading from previous version of MultiSystem
Open MultiSystem app & uninstall MultiSytem using Uninstall button
Uninstall the installed version of MultiSystem app
Follow the above instructions to install the new version.
Click to expand...
Click to collapse
If the instructions are not clear enough, check the step-by-step translations by @Thepooch
Click to expand...
Click to collapse
It's time to re-read everything about MultiSystem including the directions in the Q&A thread. MultiSystem app already includes instructions for each function & you may post your question(s) to the Q&A thread if you couldn't find an answer after careful reading/search!!
Click to expand...
Click to collapse
in Settings >> Display >> set "Screen timeout" to "10 minutes" for testing, creating/copying a virtual IMG, or flashing.
Click to expand...
Click to collapse
DO NOT USE ANY FUNCTION BEFORE UNDERSTANDING THE PROCESS !
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Downloads:
Please read carefully the instructions above before proceeding at you own risk!
Download the latest version from the main development thread!
Click to expand...
Click to collapse
★ Credits:
@ChainFire - for SuperSU & FlashFire
@Hashcode - for Safestrap Recovery
@[NUT] - for XZDualRecovery
@Androguide.fr - for APKreator & various libraries/apps
Jack Palevich - for Terminal Emulator for Android
@osm0sis - for Android Image Kitchen
All authors of binaries/libraries, source codes, or tutorials...
Please PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I'd like to thank everyone who made a donation just to show appreciation.
It's fine to just click Thanks! or enjoy my work without saying anything.
A donation is to show appreciation of the work I have done already.
A donation is not by any means in expectation of future work.
A donation doesn't entitle for preferred/private support/requests.
A donation is meant as a gift - always appreciated, never required.
Click to expand...
Click to collapse
Verizon Samsung Galaxy Note 4 (N910V), Note 3 (N900V) & LG G3 (VS985)
Hit thanks, follow thread & add 5-star rating/review... Donations are always appreciated!

XDA:DevDB Information
Multiystem, Tool/Utility for the T-Mobile Samsung Galaxy S 4
Contributors
hsbadr
Source Code: https://github.com/hsbadr/MultiSystem
Version Information
Status: Testing
Current Stable Version: 1.3.1
Stable Release Date: 2015-05-09
Current Beta Version: 1.1.1
Beta Release Date: 2015-05-02
Created 2015-05-06
Last Updated 2015-05-10

Supported Devices
Samsung Devices
Samsung Galaxy Note 3
Samsung Galaxy Note 3 - Verizon Variant [Retail Edition]
Samsung Galaxy Note 3 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 3 - AT&T Variant
Samsung Galaxy Note 3 - T-Mobile Variant
Samsung Galaxy Note 3 - Sprint Variant
Samsung Galaxy Note 3 - International Variant
Samsung Galaxy Note 4
Samsung Galaxy Note 4 - Verizon Variant [Retail Edition] (ROOT Required!)
Samsung Galaxy Note 4 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 4 - Verizon Varian [Retail Edition] (ROOT Required!)
Samsung Galaxy Note 4 - AT&T Variant (ROOT Required!)
Samsung Galaxy Note 4 - T-Mobile Variant
Samsung Galaxy Note 4 - Sprint Variant
Samsung Galaxy Note 4 - International Variant
Samsung Galaxy S4
Samsung Galaxy S4 - Verizon Variant
Samsung Galaxy S4 - AT&T Variant
Samsung Galaxy S4 - T-Mobile Variant
Samsung Galaxy S4 - Sprint Variant
Samsung Galaxy S4 - International Variant
Samsung Galaxy S5
Samsung Galaxy S5 - Verizon Variant
Samsung Galaxy S5 - AT&T Variant
Samsung Galaxy S5 - T-Mobile Variant
Samsung Galaxy S5 - Sprint Variant
Samsung Galaxy S5 - International Variant
Click to expand...
Click to collapse
LG Devices
LG G3
LG G3 VS985 - Verizon Variant (Under Testing + more features utilizing Bump!)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+++

Reserved #2

Reserved #3

Reserved #4

Reserved #5

MultiSystem v1.3
Download the latest version from the main development thread!

Simple One-Click Installation
I've fixed the installation script by setting the required symlinks (this makes it a very simple one-click installation for future versions), but I'll keep it a bit complicated for everyone to go through the Q&A thread (posts #1-6) to learn more before being able to use it.
On a side Note, I'd recommend to backup your data via TitaniumBackup & only wipe system data before rebooting to a completely different ROM.
Good luck!

MultiSystem v1.3.1 [May 9, 2015]
★ ChangeLog:
Simple one-click installation
Added log for installallation
Fixed LED indicator for Note 4
Click to expand...
Click to collapse

MultiSystem Video Tutorial
Thanks To: @Tomsgt , aka RootJunky
Don't forget to subscribe & like the video to show appreciation of his great effort & time spent in making the video :highfive::good:

Frequently Asked Questions: Samsung Galaxy Note 2

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Samsung Galaxy Note 2
[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.
[/SIZE][SIZE=+1]Q1: Which versions are available from Samsung Galaxy Note 2
[/SIZE][SIZE=+1][/SIZE]Without LTE: N7100
With LTE: N7105
[SIZE=+1]
[/SIZE][SIZE=+1]Q1: Is there a list for all ROMs, Kernels, Apps and Guides?
[/SIZE]For N7100: [INDEX] Note 2 - ROMs, Kernels, MODs, GUIDES
For N7105: [INDEX] Note 2 4G LTE/t0lte/N7105[SIZE=+1]Q3: What does "flashing" my phone mean?
[/SIZE][SIZE=+1][/SIZE]You are overriding the currect firmware with another ROM and Kernel. There are some AOSP or CyanogenMod based ROMs available, which are upgraded to Android Marshmallow, but you can also install a Samsung Stock based ROM, which is based on Android 4.3 or Android 4.4. You can flash your Note 2 with TWRP or ClockWorkMod. [SIZE=+1]Q4: Download Mode... What is this?[/SIZE]
In Download Mode you can flash ROMs or Recovery to your phone. If you want to flash the Stock-ROM back, you are forced to use Odin to flash the firmware. For flashing via Odin, you need to boot into Download Mode. To get into the download-mode, you must shut down your Note 2 and start it, while pressing Power, Volume Down and the home button.[SIZE=+1]
[/SIZE][SIZE=+1]Q5: How can I flash the Stock-ROM?[/SIZE]
[SIZE=+1][/SIZE]For flashing the Stock-ROM, you can visit this guide by @dr.ketan[SIZE=+1]Q6: How do I root my device?[/SIZE]
Another great guide by @dr.ketan:
[Root]How to Root Note2 [N7100] & keep flash counter 0[SIZE=+1]
[/SIZE][SIZE=+1]Q7: Can I install an OTA if I'm rooted/unencrypted?
[/SIZE][SIZE=+1][/SIZE]If you installed a Custom Recovery or rooted your phone, you are not able to install updates via OTA. You are forced to flash the upgrade via Odin then.[SIZE=+1]Q8: I'm trying to search for something specific but I'm having trouble. How do I use XDA Search?[/SIZE]
XDA Forum Moderator The_Merovingian has done a nice guide, how to use the search-feature: HERE[SIZE=+1]Q9: How can I install Android Marshmallow on Galaxy Note 2?[/SIZE]
You can have a look at this Thread by me. You will learn, how to install Android Marshmallow coming from Stock:
[GUIDE] How to install Android Marshmallow on Galaxy Note 2[SIZE=+1]Q10: How can I get out of a Bootloop?[/SIZE]
Doing a FactoryReset should solve this issue. You can do this by booting into Recovery.[SIZE=+1]Q11: Will Knox triggered, if I flash a Custom ROM or Custom Recovery?[/SIZE]
Yes, Knox counter will go to 0x1 and you will lost your warranty.[SIZE=+1]Q12: How can I enable MTP on CyanogenMod ROMs?
[/SIZE]You need to pull down the status-bar and enable MTP there. If there is not button, you need to go to the developer settings and enable it there.Some other helpful words:
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free.
APK - "Android Package" an Android application
Bloatware - Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted. Usually, these are apps are sponsored by a company and included by a carrier for profit
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
Custom recovery - A modified version of stock recoveries that allow you to do more things in the recovery mode.
Cyanogenmod (CM) - A free open-source project based on the AOSP. It is a modded version of the Android firmware
Dalvik-Cache - Holds all of the pre-compiled .dex files created from installed apps. These files are static and do not change unless the app is updated.
Deodexed - Where ODEX files are moved into the actual applications modded) version of the Android firmware.
Developer - A man or woman who has created (developed) software.
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM.
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop below the minimum frequency.
KANG - The process of creating a code based of someone else's code.
Kernel - An important part of all operating systems that handles the CPU and other vital components. A modded kernel may be used for overclocking.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Open-source - (not to be confussed with free) A peice of software that is free to edit, use, distribute and share with no charge.
Overclock - To exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Radio Firmware - A type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
ROM -
1. A modified version of the Android operating system operating system.
2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
Stock - An unchanged version of something. Example: I just flashed stock sense.
Underclock - To change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WIP - "Work In Progress"
Zipalligned - An archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
INTL - International
Odex - Files that are collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application.
Recovery Mode - A special environment that you can boot into for troubleshooting and upgrading purposes
Thanks to @benjamingwynn for the glossary of terms
Forum Rules | New Users Guide | XDA Tour | Report PostsThis FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
This thread is an ongoing process. This will be a WIP for a period of time
http://forum.xda-developers.com/wiki/Bootloader

This is not a Q&A Thread
This is not a Q&A Thread This is not intended to be a Q&A help thread. Please only post suggestions for content that should be added to the OP. Post the relevant links to accompany your request.
If you need help or have a general question, consider using these links:
Question's please here: http://forum.xda-developers.com/shield-tablet/help
Or here: [NOOB FRIENDLY] Ask the question! [N7100 and other variants]

Trafalgar Square said:
This is not a Q&A Thread This is not intended to be a Q&A help thread. Please only post suggestions for content that should be added to the OP. Post the relevant links to accompany your request.
If you need help or have a general question, consider using these links:
Question's please here:http://forum.xda-developers.com/shield-tablet/help
Or here:[NOOB FRIENDLY] Ask the question! [N7100 and other variants]
Click to expand...
Click to collapse
I need your help pls help me

Sid76 said:
I need your help pls help me
Click to expand...
Click to collapse
Pls help me when I disconnect my phone from charger it stuck in boot image like icon of galaxy note 2 after that when I connect again it starts normally and I do disconnect this happen again pls help me our bootloop and I tried many ROMs but not able to fix help me

Hello PLZ someone help me. I searched for more than two weeks to solve my problem and did not find any results
I'm sorry in advance that I could not write English well.
I have a Samsung Galaxy Note 2 (N7100) phone with Android 9 custom ROM, which I charged quickly when it finished charging, but it doesn't turn on now.
The mobile stops on the Samsung logo or lineage logo or mobile Battery animation when I charge it and I can only go into recovery mode and download mode
After this incident, I wanted to factory reset it with the custom recovery twrp that I installed on my mobile phone or wipe all the memory, but I got the error "Unable to mount storage".
Even when I wanted to install the official ROM with micro sd memory, twrp displays zero for mobile memory, sd memory and otg.
I also wanted to flash it with Odin with four official files and a pit file, which was unsuccessful and show erorr at the end the message "re-partition operation failed" was announced.
I tried to flash files again with the Miracle tool without a box. Some partitions were burned, but due to the inability to burn some partitions, I received a wrong reply error (0).
Also, after flashing the recovery file with the official recovery and new version of twrp, Miracle displayed a successful message, but in practice, there was no change in my custom recovery.
So I'm looking for a way to repair emmc with just a usb cable and no box or any other way to repair my mobile

[Custom-Roms] Huawei Mate 8 - NXT- EMUI 5.x-Android 7

[Custom Rom]
[K-Rom M8-V5] [Magisk](all regions) Huawei Mate 8 -
NXT- B592 - EMUI 5.01 - Android 7 -
Based on Huawei Firmware
B592 (China) and KankVip B592 V3
On TWRP backup basis.
Developed and tested on this device:
Huawei Mate 8 (NEXT)
Model number: Huawei NXT-L29
Build Number: NXT-L29C432B581
-OTA updated
without branding, with root and root access.
TWRP recovery
Mods:
- Call Recorder
- KangVip Advanced Settings
- Autostart administration in the
telephone manager
- Viper 4 Android FX 2.5
- Ad Block Plus
- Immersive Mode
(hide Navbar e. t. c.)
For topicality:
The Google Patch is from 2017-10-05 and the firmware is
Version B592 (Asia)
The deviating specifications in the device information,
have been taken over by the B581 and
guarantee the OTA eligibility for subsequent updates."
Please make a backup of your data with Huawei Backup and TWRP.
The Rom will be installed as if you were trying to restore a TWRP backup.
All your apps remain intact.
Prerequisites:
Firmware B581
TWRP Recovery (from download)
Root is not necessary.
OEM and FRP unlocked
USB Debugging on.
You are familiar with the matter? Then let's go!
Preparation/ Installation:
Download:
Please do not download the MEGA 2017-11-09-M8-K-Rom-V5.rar as "ZIP".
The backup is already compressed.
Unpack and the backup directory:
2017-11-09-M8-K-Rom-V5
to the TWRP Backup folder on the ExtSd.
Installation:
Uninstall these apps, if available:
SuperSu and Busybox.
Restore and reboot the backup in TWRP.
Please do not perform any wipes immediately before and after the event.
In the future, never do a factoryreset.
Depending on the configuration of your existing B581,
the following may still have to be done:
install ************* v5.3.0.apk,
flash in TWRP BusyBox-Magisk-1.25.zip,
flash in TWRP Magisk-permissive-script_v1.0.zip,
for the Kangvip advanced settings.
For Ad Block Plus first install the app and
then the zip's flash.
If the flashing fails, please add the modules in the Magisk Manager App.
Don't experiment with Xposed!
The SafetyNet is lost."
The Rom is partially debloated. Some Google and Huawei apps have been removed.
They can be installed by you if necessary.
That's what you can do with the HiApp.
In the Kangvip Advanced Settings do not use the Addblocker and
"hideNavbar". Both works only on China Roms.
I recommend to fully charge the battery after installation and carry out a calibration.
Since the rom runs with the stock kernel, you can only take a few options
in the k-advanced settings / tune cpu.
With the app in the attachment, you can check it out.
See also the screenshots.
....... and remember: A custom ROM is never as perfect as a stock Rom.
You have to teach him something in between.
Depending on the configuration of your devices, it can of course also be "stuck" somewhere.
I give full support for this, because there is a lot of support between rooted nougat devices and the EMUI
there's no real wedding.

Good luck!
Subsequent rooting with SuperSu is possible with the V5:
Restore the stock boot partition (kernel) from a TWRP backup.
SuperSU.EMUI5-K-Rom.zip flashing.
finished.
Threadupdate: 2017-11-17:
Increase battery life:
I have tested some settings on cpu performance.
By turning off individual cores, the others have to do the work.
It is difficult to predict whether this will cause permanent damage.
Lowering the frequency distributes the load evenly balanced.
The performance loss is only 6% and not noticeable
and the battery life is considerably longer.
You can easily see this on the graph in the appendix.
Test environment:
V. 5 with SuperSu Root
Ex kernel tuner app (beta).
My configuaration is: max power big cores= 1306 / little cores= 807 MHz.
You can create individual profiles and put a widget on the home screen.
I recommend a calibration with "Battery Calibration" from NéMa. It also optimizes the consumption of all available apps.
Thanks to:
[KangVIP]
Chainfire, Stephen (Stericson) + Jmz Software, Lineage OS Team,Team Win RecoveryProject, JRummy and Huawei Technologies Co., Ltd. Greetings to China Mobile Com.
[Custom Rom] Huawei Mate 8 - NXT-L29C432B582 - Custom System Update ("V.6")
- EMUI 5.01 - Android 7 -Tested by @apat26. Quote:
"I tested your ROM on L29C185B582 for a couple of
days and this is working perfect."
On TWRP backup basis.
This update replaces the [K-Rom-M8-V5].
Developed and tested on this device:
Huawei Mate 8 (NEXT)
Model number: Huawei NXT-L29
Build number: NXT-L29C432B582
- OTA updated.
- Without branding, with root and root access.
- TWRP recovery[/SIZE]
Mods:
- Call Recorder
- KangVip Advanced settings
- Autostart administration in the phone manager (PM+)
- Viper 4 Android FX
- Obtaining OTA authorization
I couldn't test if this runs on Firmwares other regions.
I think the v6 is going on all regions on B582.
Quick guide for experienced users:
Please make a backup of your data with Huawei Backup and TWRP.
The Rom will be installed as if you wanted to restore a TWRP backup.
All your apps remain intact.
Conditions required:
- Firmware B582,
- TWRP recovery, (from download, or available from v5 )
- root is not necessary,
- OEM and FRP unlocked,
- USB Debugging on.
All required files are in the download folder.
You are familiar with the matter? Then let's go!
If available, uninstall these apps: SuperSu and Magisk.
A unroot is not necessary. Please do not download the downloads as "ZIP".
Installation:
1. Replace existing boot partition:
"2017-12-M8.B582.stock.kernel.boot"
copy in the TWRP backup directory to the ExtSd and restore.
2. Install update:
"2017-12-M8_B582_AdvS_Xposed_SystemUpdate"
also copy to the TWRP backup directory and restore."
3. Rooting:
- In TWRP mount Internal storage/ system,
- go to: Install, system/ k-rom/ set and install the SuperSU.zip.
- Reboot.
- After starting, take the BusyBox App from the download.
Then please use it to install its binaries.
- Install the PM+ app and bring the autostart administration to the phonemanager.
Iggnore the incompatibility warning.
Do not reboot between steps 1 to 3. Do not wipes before and after.
That's all. The installation is complete.
If Viper or Xposed have not been installed with it, this can be found in the
Advanced settings can be made up for.
Xposed is already active. In case the framework gets disabled,
in the Advanced settings. There's no way use other Xposed versions.
This also applies to SuperSU. They are not compatible with this system.
Both are optimized for this system.
Of course, you can also use Magisk to root later with the instructions
in the v5 thread. (loss of ota authorization)
Xposed does not run under magisk rooting together with the Advanced settings.
It must be used for a successful SafetyNet test, must be completely removed before rooting.
In the Kangvip Advanced settings do not use the Addblocker and "hide Activate NavBar".
Both works only on China Roms.
Hiding the NavBar can be done comfortably with the App "Tiles" from the playstore. (See v5)
In the K-Advanced Settings /tune cpu, some of the following are available.
Modifications of the computer performance possible. Those who need more power can do so.
Testing out the "Power save" options is useless. Did a lot of it.
The Huawei's own energy saving settings cannot be topped.
Good luck!
Thank you very much:
[KangVIP] (Advanced settings),
@Tecalote (SuperSU)
and Chainfire, Stephen (Stericson) + Jmz Software, Team Win RecoveryProject,
JRummy and Huawei Technologies Co., Ltd.
NEW[Custom Rom] [KangVip Rom M8-B592-V4]Huawei Mate 8 - NXT-L29C432B592 - Custom System Update
- EMUI 5.01 - Android 7 -
On TWRP backup basis.
This turns the B582 into a B592.
Developed and tested on this device:
Huawei Mate 8 (NEXT)
Model number: Huawei NXT-L29
Build number: NXT-L29C432B582
- OTA updated.
- Without branding, with root and root access.
- TWRP recovery[/SIZE]
Mods:
- Call Recorder
- KangVip Advanced settings
- Autostart administration in the phone manager (PM+)
- Viper 4 Android FX
- Obtaining OTA authorization
I couldn't test if this runs on Firmwares other regions.
Quick guide for experienced users:
Please make a backup of your data with Huawei Backup and TWRP.
The Rom will be installed as if you wanted to restore a TWRP backup.
All your apps remain intact.
Conditions required:
- Firmware B582,
- TWRP recovery
- root is not necessary,
- OEM and FRP unlocked,
- USB Debugging on.
Downloads: https://www.mediafire.com/folder/2ppn9ewownun5/NXT
You are familiar with the matter? Then let's go!
If available, uninstall these apps: SuperSu and Magisk.
A unroot is not necessary. The download is compressed in zip with Huawei file manager.
Installation:
Extract
"2017-12-18--K_E5_B592_V4.zip,"
copy it in the TWRP backup directory to the ExtSd and restore.
Immediately afterwards, rooting starts with the installation of SuperSuV4 and reboot.
Install the PM+ app and bring the autostart administration to the phonemanager.
Iggnore the incompatibility warning.
Do not reboot between restoring and rooting.
That's all. The installation is complete.
If Viper or Xposed have not been installed with it, this can be found in the
Advanced settings can be made up for.
Xposed is active and stable.
There's no way use other Xposed versions.
This also applies to SuperSU. They are not compatible with this system. Do not change the busybox binaries.
Both are optimized for this system.
In the Kangvip Advanced settings do not use the Addblocker and "hide Activate NavBar".
Both works only on China Roms.
Hiding the NavBar can be done comfortably with the App "Tiles" from the playstore. (See v5)
In the K-Advanced Settings /tune cpu, some of the following are available.
Modifications of the computer performance possible. Those who need more power can do so.
Testing out the "Power save" options is useless. Did a lot of it.
The Huawei's own energy saving settings cannot be topped.
Good luck!
Thank you very much:
[KangVIP], Chainfire, Stephen (Stericson) + Jmz Software, Wraithdu, Team Win RecoveryProject,
JRummy and Huawei Technologies Co., Ltd.
The roms I offer are original Huawei firmware. Only the system was modified by kangvip and me. The kernel are 100% stock. If you like this work you could give a donation to kangvip.
https://www.paypal.me/KangVIP
Please not for me, because I don't take money for it. I created this TWRP backup roms for my use. I love it when these things work. And it does. Now I'll share it with you.
Downloads:
https://mega.nz/#F!1g8QDZqa!F9wV-6oWYUsx70n96Xb3dQ
Disclaimer:
Despite careful elaboration, I cannot guarantee that the execution of this manual will not cause any damage to the device or operating system and therefore I do not assume any liability for any damage or malfunction of the hardware and software! If you are still unsure, follow these steps: Follow the instructions only if you or your device is subject to any conditions (model number, Android version, etc.). Read the instructions carefully and completely, look up unknown terms. Check downloaded files for viruses. Make a backup of important settings and data. Do not follow the instructions if you do not know what you are doing.
These warnings must be logical. Please process my comments correctly.

Discussions, exchange of experiences, tips and tricks
around the topic "KangVip Roms"
are welcome here.
:good:

ChinHon said:
Discussions, exchange of experiences, tips and tricks
around the topic "KangVip Roms"
are welcome here.
:good:
Click to expand...
Click to collapse
Nice to see you here
Waiting for your work with kang b592,,,

Link ? nvm. found will test it soon.

hamadazh said:
Nice to see you here
Waiting for your work with kang b592,,,
Click to expand...
Click to collapse
Comes in about 2 hours.

danterape said:
Link ? nvm. found will test it soon.
Click to expand...
Click to collapse
Open the txt file in the attachments.

w00t w00000t, good job there buddy
Sent from my HUAWEI NXT-AL10 using Tapatalk

ChinHon said:
Comes in about 2 hours.
Click to expand...
Click to collapse
Ok bro, take your time we can waiting more than 2 hours

hamadazh said:
Ok bro, take your time we can waiting more than 2 hours
Click to expand...
Click to collapse
Check out the thread update !!

ChinHon said:
Check out the thread update !!
Click to expand...
Click to collapse
Yeah thank you :good:

I saw this rom abit ago on the euro net, all kang roms will work on any mate 8 version b580 and up all models , all it takes is the custom multi version kernel , I found a few online , but I run dl0017 because I feel its the best and all the diferance is with google framework is install thegoogle apps package. There r multiple ones available , just be sure to remove autonavi location services from the phone too to get proper gps and remove hi suite.

c|nder said:
I saw this rom abit ago on the euro net, all kang roms will work on any mate 8 version b580 and up all models , all it takes is the custom multi version kernel , I found a few online , but I run dl0017 because I feel its the best and all the diferance is with google framework is install thegoogle apps package. There r multiple ones available , just be sure to remove autonavi location services from the phone too to get proper gps and remove hi suite.
Click to expand...
Click to collapse
My rom is a pure system update. It's tuned to the stock kernel. All other partitions remain unaffected during installation. It's not just Kangvip Rom. There are no problems with the Gapps. They do not need to be reinstalled. Many Devs adapt the kernel to the rom, I do it the other way around.

Well the kernel is what differentiates the phone from the OS LOL. U do know u can take the newest b592 kernel and just patch a few lines for it to be accepted and not trip any security features , eg: fingerprint dev opt.

@ChinHon
One question
Do you can overwrite a normal B560 with this backup (v2 or v3)? I saw nothing about of which firmware we can have to install your custom rom.
B.R

franzyroy said:
@ChinHon
One question
Do you can overwrite a normal B560 with this backup (v2 or v3)? I saw nothing about of which firmware we can have to install your custom rom.
B.R
Click to expand...
Click to collapse
The B581 is required, but it does not work with the B560.

I have now successfully rooted the V3 with magisk and stock kernel. Substratum no longer works. We can do without it, too. There are no EMUI themes for this. I didn't keep Xposed with magisk, but the previous installation with K-Settings. Stable here too. Antutu's good at 95,850.

Would this work on asia/ Pacific l29 b585??

i have a mate 8 with b581 can i flash v3? and do i need to wipe?

nikolas60 said:
i have a mate 8 with b581 can i flash v3? and do i need to wipe?
Click to expand...
Click to collapse
Yes you can. Not flash, but as TWRP backup restoring. No wipe, please. It's all in the manual.

c|nder said:
Would this work on asia/ Pacific l29 b585??
Click to expand...
Click to collapse
If you mean the ROM, Pacific definitely. Maybe the 585.
Make a TWRP backup and then test it. If it doesn't work, you just have to restore "boot and system" of your backup.

[DISCONTINUED][TWRP BACKUP-ROM][10] Lightheart 1.0 Galaxy S10 [24.10.2020]

Lightheart 1.0 - Efficiency is key.
Hi everyone. My name is Skulldron and for those of you who do recognise me, know me as the creator of Project Pixel, another one of the greatest ways to emulate the Pixel Experience, whilst keeping all the benefits of using OneUI and its stock optimized drivers as its base. Today I'm going to be introducing something, different. Over the years of working on Touchwiz based ROMs, I've learnt the description of every little apk, every little permission, what it accepts and what it rejects, its pros and its cons. As a result of this experience, I have one of the best debloat lists out there, with each item on the debloat list, being tested, literally through trial and error for over 4 years, and it goes over every file and every partition known in the OneUI OS. This exact same debloat script was used in Project Pixel, which has recieved positive review after positive review for how efficient and how lightweight OneUI became after the debloat. Today however, I present to you Lightheart OS, a new project that I will be building myself and updating monthly (as I do own an actual Galaxy S10). Lightheart, is essentially built equal to Project Pixel, except that instead of Pixelifying and adding another gigabyte worth of apks, permissions and modules, just stops after the debloating and optimization bit. I have done something similar with the Galaxy Tab S2, and it was called Performante, but it was even more stripped on features than I would have liked myself, so today I showcase Lionheart, the Lineage OS to my Cyanogenmod.
Features:
1. Heavily Debloated System Size - The overall size of the system partition has dropped from 5.2 GB to 3.2 GB, along with RAM consumption dropping from 4.2 GB on stock, to 3.1 GB on Lightheart.
2. Heavily Debloated Product Partition - All bloat has been removed/deprecated from the Product Partition dropping its size from 592 MB to 78 MB
3. Better Battery Performance due to Efficiency - With the removal of an incredible amount of bloat, along with better performance and lesser services, you should be looking at better SOTs and better standby times.
4. Better Performance due to the Cruel Custom Kernel - The Cruel Kernel Team have been kind enough to give me permission and access to their kernel, which in itself has many optimizations, along with the allowance to achieve higher system speeds and overclockabilty via Mtweaks (Needs to be installed seperately, I will provide a link)
5. Preloaded Magisk with Cruel - Cruel Kernel comes preloaded with Magisk, all you have to do is install the Magisk Manager
6. October Patch with the promise of updates every month - As I use this rom as my own daily driver, i will update it every month to keep up with optimizations by Samsung and security patches.
7. Restored some stock Google Permissions - Some stock google framework was restored, such as the default setup wizard.
8. All Essential Samsung Features have been kept - All essential OneUI features have been kept alive, for the sole purpose of necessity.
9. Completely Deknoxed - It is covered under the debloat
Changelog:
1.0 - Initial Release
TWRP Install Instructions:
1. Download the latest available TWRP Image from Ianmcd's thread (the current supported version is 3.4.0.3 and will be linked at the bottom of the thread)
2. Download the custom VBmeta file and install 7Zip.
3. Rename the downloaded TWRP Image as recovery.img.
4. Highlight both the vbmeta.img and recovery.img, then right click while selected, 7Zip and then add to archive.
5. Once your in the 7zip interface, choose .tar and do not change any of the configurations and build the .tar file.
6. For this next bit, you'll need to download Odin 14.4 (links will be provided)
7. Open Odin, and then connect your device via USB.
8. Select AP, and then select the newly made recovery.tar.
9. Once it is loaded, press start, and when it reboots, hold the recovery combination (Power + Volume Up + Bixby) to boot into TWRP.
You have now successfully installed the latest TWRP for your S10 and can now proceed to actual install. Remember that if you are coming from stock you will need to flash the MultiDisabler, linked at the end of the thread.
Install Instructions (THIS ROM IS NOT FLASHABLE!):
1. Download Lightheart 1.0.
2. Open the zip and extract the folder.
3. Switch off your phone, and go into twrp via the button combination.
4. Make a backup of your cache (This will make the directory to TWRP's recovery system)
5. Boot back into the OS and head to where you stored Lightheart 1.0.
6. Cut the entire Lightheart Folder and move it to TWRP/BACKUPS/Random Number/
7. Now boot back into TWRP and wipe system, data, dalvik, cache.
8. Go to the restore option, and you should see Lightheart as a restorable ROM.
9. Restore Lightheart and once your done, boot into system
And thats about it for the install process. It is a bit unconventional, but I have been unable to procure or manufacture a working installer script as of this moment, so please bear with me for now.
Download Links:
1. TWRP Galaxy S10 Series:
https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
2. TWRP 3.4.-03 (Ianmcd):
https://androidfilehost.com/?fid=8889791610682934970
3. Custom vbmeta:
https://drive.google.com/file/d/1MBQ1iIei6a-RoURS6k6q_xwQOjG4jR-a/view?usp=sharing
4. Lightheart 1.0:
https://drive.google.com/file/d/1U3WcjUSZh3jWCjfoq8vLex83E8D1r8zA/view?usp=sharing
5. Odin 14.4:
https://odindownload.com/download/Odin3_v3.14.1.zip
6. Magisk Manager:
https://github.com/topjohnwu/Magisk/releases
7. MTweaks 17.3:
https://androidfilehost.com/?fid=8889791610682894841
Credits and kernel source:
1. @evdenis for their remarkable Cruel Kernel
2. Kernel Source: https://github.com/CruelKernel/samsung-exynos9820
XDA:DevDB Information
Lightheart 1.0, ROM for the Samsung Galaxy S10
Contributors
Skulldron
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP 3.4.0.3 Ianmcd
Based On: OneUI
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-10-24
Created 2020-10-23
Last Updated 2020-10-31

Reserved

Reserved

Hi first thnx for your work but if this rom are make for S10 only why the tread is on cross device development ?

thanks for the rom is there the recording call

Random-Tester said:
Hi first thnx for your work but if this rom are make for S10 only why the tread is on cross device development ?
Click to expand...
Click to collapse
Hi. The plan is to slowly extend the ROM to the Galaxy s10+ and s10e, hence why the thread is in cross development

Skulldron said:
Hi. The plan is to slowly extend the ROM to the Galaxy s10+ and s10e, hence why the thread is in cross development
Click to expand...
Click to collapse
When you have done the above please feel free to report this thread and request it to be moved. For now it will be moved to the appropriate S10 only section.

Negan said:
When you have done the above please feel free to report this thread and request it to be moved. For now it will be moved to the appropriate S10 only section.
Click to expand...
Click to collapse
Noted. Thread has been updated with corrections and a link to a telegram group I have made, in case ya'll need further support. Thankyou ^_^

Skulldron said:
Noted. Thread has been updated with corrections and a link to a telegram group I have made, in case ya'll need further support. Thankyou ^_^
Click to expand...
Click to collapse
I encourage you to ensure to provide sufficient support on XDA. Please check the telegram sticky for more info. Also since this is essentially a TWRP backup I've edited your thread title to indicate this as this should be clear from the get go. Do not re-edit that again unless you're able to have the rom be flashable. Thank you and all the best of luck with your project.

Awesome !! Love it so far. Nice performance, genshin impact is not dropping frames like on other oneui ROMs.
Keep up the good work

Waiting for the s10e
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
Waiting for the S10e
Sent from my [device_name] using XDA-Developers Legacy app

Hi,
I would like to use your rom if it means longer battery life. However I have no knowledge of rooting or flashing a galaxy S10 phone. I'm not afraid of the terminal but I'm afraid of loosing access to KBC mobile or Google Pay or any other app that is financially or government involved.
Is it because you say deknoxed that it will have problems with such apps or quite the opposite ?
Another question is, Can Jodin3 be used as well? I only have access to MacOS.
Forgive my English, it's not my mother language.
Kr,

Don't do anything with your phone then if you don't want to loose Google pay etc...

hi ,thx 4 ur hard work,sorry 4 a NOOB question: i have an s10 which is G973N, can i flash this rom?

HannibalHu said:
hi ,thx 4 ur hard work,sorry 4 a NOOB question: i have an s10 which is G973N, can i flash this rom?
Click to expand...
Click to collapse
As long as its not G973U, it should work but I advise caution when flashing a ROM which is not the same model

So far this Rom ist great, the lack of the samsung account makes setting up some apps a bit difficult, but other than that this is awesome!

How are temperatures on this debloated rom?

Pro

Skulldron said:
Hi. The plan is to slowly extend the ROM to the Galaxy s10+ and s10e, hence why the thread is in cross development
Click to expand...
Click to collapse
does it mean it would work for s10e or we need to wait a while?

Hi, this rom works with the latest bootloader?

Develop Bugs

welcome