Database Info

Software Development [CLOSED] [ROM] [CUSTOM] [INTEL JOYING] GTX joying ROM V9a3 2018-04-22

========================================ACHTUNG===================
=================WARNING==========================================
=====================================================PELIGRO=======
AS WITH ANY UNSUPPORTED SYSTEM MODIFICATIONS, USING THIS MAY LEAD TO A BRICK
IF YOU DON'T KNOW WHAT YOU ARE DOING ( HAVEN'T BRICKED MY SYSTEM YET! ) PLEASE
BE AWARE THAT NO ONE ON THE INTERNET IS RESPONSIBLE FOR ANY DAMAGE TO YOUR
UNIT. ANY PROBLEMS WILL BE CONSIDERED ACTS OF WHATEVER GOD YOU BELIEVE IN.
======PELIGRO=======================================================
================================WARNING============================
===ACHTUNG=========================================================
For FYT SoM (5009/6011/6021/6022/6023) based JOYING / Intel SoFIA units ONLY!
Hello, here is a custom rom based on the SYU Stock Build [sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.bsp.20180110.181524 release-keys]
Your Head Unit MUST ALREADY BE ROOTED! You must be able to obtain Super User access within Android!
Due to Bluetooth, WiFi, and as well as nvram patches in the ROM and bootloader, you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM.
Why this ROM? Simple answer: It's makes your Head Unit faster than running the stock ROM's, has updated Google Apps, and has the bloat removed! It's pre-rooted also!
INSTALLATION INSTRUCTIONS:
Step 1: Unzip the contents to the root of your USB flash drive on your computer, then plug the flash drive into the Joying unit via USB.
Step 2. Use the Android helper application "custom" to install. Download from link below, either on the Head Unit itself, OR on PC and transfer using ADB. Once installed, open the program, and grant superuser privileges when prompted, you'll be presented with screen as here:
{
"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"
}
Step 3: Click INSTALL CUSTOM. Wait for output to say recovery successfully installed!
If you wish to preserve your /data, AKA dirty-flash, click on "Do not wipe data" at this point to prevent your data partition from being wiped.
ALL EXISTING DATA ON UNIT WILL BE ERASED. THIS IS A CLEAN INSTALLATION!
Step 4: click REBOOT TO INSTALL GTX ROM - Your Joying unit will reboot, and installation will automatically proceed through TWRP.
(NOTE! The ROM automatically re-installs stock recovery during installation, so if something goes wrong, you can always restore to the original JOYING firmware.)
Recovery options:
RESTORE STOCK - Restores the original stock recovery
INSTALL CUSTOM - Installs superdave's custom recovery (needed to install this ROM)
VERIFY RECOVERY - tells you which recovery you have installed
Rom Utilities:
(all options on this menu work only if you have custom recovery installed)
"Do Not Wipe Data" Switch - enable this to prevent your /data partition from being wiped when installing the ROM. (Your results may vary. Works for me!)
REBOOT TO TWRP - Reboots to TWRP home screen allowing you to do things
INSTALL GTX ROM- installs joying_gtx stock rom from installation media
Exit - exit custom
Code:
====Includes====
xposed v87 x86
open gapps x86 Nano Feb 2018
ViPER4ANDROID FX
precompiled dalvik cache (first boot 2 minutes)
enabled eth0 at boot at 192.168.65.100 for debugging
ADB enabled
SeSuperuser built-in
Included [custom] app to manage superdavex's custom recovery for easy installation and maintenance
RightCamera (front cam app) modified APK
AOSP android boot animation
Interactive cpu governor:
go_highspeed_load set at 70% CPU load
titanium backup
nova launcher
GVC CallHandler 4 Joying
Amaze File Manager
Xposed modules:
boot manager
gravitybox
no overlay warning
immsersive mode forcer
app settings
fake wifi
GPSSpeedFix
======Removed======
[I]Debug Services:[/I]
usbactive
sqldebug
pekallfmrserver
watchdog
ap_logfs
apk_logfs
log-watch
crashlogd
adbusbmuxd
adbec
bootwatcher
shcmd
fmd
[I]Removed Apps:
[/I]
BasicDreams
BluetoothMidiService
Exchange2
Galaxy4
HoloSpiralWallpaper
LiveWallpapers
LiveWallpapersPicker
NoiseField
OpenWnn
PhaseBeam
PrintSpooler
GooglePinyinIME
RKUpdateService
CaptivePortalLogin
WAPPushManager
[I]removed from /system-priv-app
[/I]ManagedProvisioning
CallLogBackup
OemTelephonyApp
DeviceTest
StressTest
WallpaperCropper
GoogleFeedback
ProxyHandler
CellBroadcastReceiver
[I]Removed FYT APPS[/I] ( these slow the system down considerably, even when not in use )
SYU-1-C9-Calculator-V1.0
Sofia-1-C9-TV-V1.0
JY-1-C9-Video-V1.0
JY-1-C9-TimeWeather-V1.0
SYU-1-FileManager-V1.0
SYU-1-C9-Update-V1.0
Sofia-1-C9-ExDvr-V1.0
SYU-1-C5009-DVR-V1.0
Sofia-1-C9-Gallery-V1.0
JY-1-C9-MUSIC-V1.0
ZBox
note, this is a test release intended for developer users only. no support other than this post is offered. A final version will follow soon once initial testing has been completed.
Download Links
Installer ( unzip, this will help you install the ROM on a STOCK, un-rooted Head Unit ) :
xxxxx Mod Edit
custom V4_9
xxxxxxx Mod Edit
source code
Firmware Download:
V9 ALPHA 3
xxxxxx Mod Edit

Reserved for TWRP instructions.

Q / A:
Q: Do I need to worry about what MCU version I have before I use your rom?
A: Maybe, GTX ROM doesn't touch the MCU, which shouldn't be re-flashed with each install anyway as it usually doesn't change. Whatever MCU version you have, this ROM will work for you, as long as you have an FYT based SoM unit. If you encounter errors, you might need to change the "ro.build.fytmanufacturer" property in /system/app/fyt.prop to match whatever your unit ORIGINALLY came with.
Q: I have a RK3066/RK3188/PX3/PX5 based head unit. Will this ROM work for me?
A: NO! This ROM ONLY works on FYT based head units. This means all Joying Intel units, as well as some from other brands.
Q: I like Live Wallpapers. How do I enable them?
A: Use the built in terminal. type su and hit enter. You now have root. then type in:
Code:
cp -R /system/vendor/oem/LiveWall* /system/app
hit enter again, then reboot!
Q: I don't want to use this ROM anymore, what do i do?
A: Use the helper application, custom, open the program, and click RESTORE STOCK. This will restore the STOCK RECOVERY. Go on Joying's website [link], download the firmware of your choice, and follow their instructions.
Q: Can I use google voice to make hands free calls?
A: You sure can. Use the "Voice Search" app to dial a number using your voice, once at the Google App screen, click on the hamburger menu, and then select GV CallHandler 4 Joying. Make sure your unit is set to a DPI of at least 161dpi or greater, and then clear data on the google app. After you reboot, you should be able to make calls.
Q: How do I view my front camera?
A: If you are using the analog RCA video input, on the back of the unit, you can use the RIGHT CAMERA app to view. Note, than unlike the AUX program, this one will NOT mute the system audio.
Q: How can I fix my GPS speed to calculate 1/kmh or 1/mph steps instead of the default 4 steps?
A: Go to XPOSED INSTALLER, and enable the GPSSpeedFix module. Reboot, and the steps will be fixed.
Q: How can I enable different DPI settings for each application?
A: Go to XPOSED INSTALLER, and enable the App Settings module. Exit the installer, and open the App Settings to make your adjustments. Reboot, and your changes will be visible.
Q: This ROM is fast, but I want more speed, what do I do?
A: Add a fan to your unit, preferably a FAN + Heatsink. Then download an app like SetCPU to lock your CPU to MAX speed. Be careful.
Q: How do I re-assign the hard keys on my unit? Joying says that DVD and EJECT don't work! Is this a lie?
A: Yes! There is a way to re-assign keys, and the DVD and EJECT keys do actually work, the software that comes with the unit is not very good. Check @surfer63's XSofiaTweaker thread for more info on how this works.
Q: I want to send and receive my text messages on my Joying unit...is this possible?
A: Sure! Use third party app like Pulse, or Pushbullet. Works like a charm. I personally use Pulse, it's got the look and feel of a stock SMS app.
Q: Installing the Joying Factory Rom takes like an hour...multiple reboots, then it starts over, then it reboots, then it optimizes apps, then it starts over, again. jeez. How long does your ROM take to install?
A: Installation is less than 4 minutes. First boot is timed at one minute 53 seconds, and there are no crashes or reboots. It just works.
Q: Xposed says there is an update available! Is it safe to update Xposed?
A: NO! Do NOT update Xposed, it will make your unit non-functional! Just say NO!
Q: Am I able to "upgrade" from an earlier version of the ROM to a newer without loosing my data and apps?
A: Yes, read the first post on what option to select in custom. Many others and I have tested, and it works for almost all people, still there is a chance that it could not work.
Q: I need to download the stock Joying firmware so I may use your ROM! Where do I get the latest updates?
A: See here: https://drive.google.com/open?id=1nF5Pgn95_WWGk8S2byb8rR5ko0ss5F_S
Q: is there a video where I can see you install the ROM?
A:

Issues:
-Unable to send text message via google voice app using Pulse SMS, error is "Message couldn't be sent" // If anyone has a fix for this, please let us know
-Google Assistant doesn't work, launching activity manually results in "The Google Assistant doesn't work on this device" / You can fix this by changing the resolution to at least 720. use the command wm size to change the screen resolution or another tool that can change DPI
Release History:
custom helper:
V4_1: Fixed installation issue from micro sd cards.
V4_2: Check OS build fingerprint, will deny install unless you are on 20171215 or later.
V4_3: Updated text on installation screen for easier reading, Updated build detection logic
V4_4: Fixed bug in build detection logic
V4_5: Added no_data_wipe, translations included.
V4_6: fixed reboot to twrp not extracting recovery ota.
V4_7: lbug fixed
V4_8: script improvements
V4_9: prepare for re-write, added performance mode
ROM:
V4: Replaced opengapps with nano version
V5: Updated to 01-10 AOSP Base, Added bluetooth build property from @surfer63, more optimizations.
V6: Added Navi APK, more optimizations, CANBUS firmware included, various stability fixes, ability to "dirty flash", mcud included to prevent bootloops during app optimization, works with 800x600 units now, fixed overlay bug, faster first boot, added ViPER4ANDROID, added USB audio policy modifications.
V7: Fixed LED issues and AMP Options. Updated GAPPS base to 20180226, might need to optimize apps on first boot if you are dirty flashing. Added fyt.prop to /system/app fix various issues.
V8: Changes in the way the installer handles re-installation of stock recovery for disaster recovery situations in which the installation fails and custom recovery remains installed, changed installation logic to to compensate for faulty installation media, twrp bug fixes, fixed twrp restart loop, clear FYT flags on twrp start.
V9 alpha 1:
updated recovery busybox to 1.27
fixed SYU file manager not found in CM Settings
fixed right camera not displaying
updated MCUd build to co-exist with sofia server
eliminate audio pops during rebooting
updated gtx_installer
updated dalvik cache
fixed recovery_maintenance.sh in system and recovery envrionments
recovery maintenance.sh is now functional from recovery console
updated clean_rom.sh
permissions overlay fixed
fixed script logic in install-recovery on 6021 units
include terminal app APK
added nano x86 editor
added network_up.sh to ensure debug network access and SU daemon is always run
v9_alpha_2:
fixed drm video black screen issue
added rom version information to fyt_build.prop
sofiaserver runs audio through all channels during call
v9_alpha_3:
xposed module to prevent xposed from updating framework causing bootloops
added remount command to path
added display calibration app to launcher
include both 5_25 and 9_20 versions of McuUpdateAll.bin in /system/mcu/ (copy the corresponding version to /system/mcu)
keep JET and other apps as user to ease upgrade

V3 Rom link not working?

Just finished upload, Try now.

gtxaspec said:
Just finished upload, Try now.
Click to expand...
Click to collapse
Yes, works fine. Sorry for clicking the links too early
I can't do anything with it now, but a link is so easily clicked.

my joying head units have an internal amp, can I use this ROM?

usa911g said:
my joying head units have an internal amp, can I use this ROM?
Click to expand...
Click to collapse
Yes, no problem at all. If there are bugs we will share them all. Nothing specific for amp or no-amp models.

surfer63 said:
Yes, no problem at all. If there are bugs we will share them all. Nothing specific for amp or no-amp models.
Click to expand...
Click to collapse
because the EQ app for amp or non-amp models is different, so I concern that

usa911g said:
because the EQ app for amp or non-amp models is different, so I concern that
Click to expand...
Click to collapse
Actually it is one and the same app with different screen-layouts and functionality depending on the hardware.

The digital amp software is included.

Reserved.
As soon as I have time I will try this rom

the russian hackers at 4pda are using the following build.prop mods, anyone care to chime in? if they actually do something, I will include them.
Code:
ro.rk.install_non_market_apps=true
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
persist.telephony.support.ipv4=1
persist.telephony.support.ipv6=1
persist.sys.purgeable_assets=1
ro.wifi.channels=14
media.stagefright.enable-http=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false

I have no idea about the build props.
The custom V3 app did install the recovery image in one go. I do not know whether you improved something or the previous time was a glitch on my system when it gave that verification error.
I installed the V3 ROM. It works fine. It seems indeed faster than the original joying stock rom.
From what date are the GAPPS? The unit is trying to update all gapps. It is not really useful to have everything pre-odexed for a quick start (and it really is a quick start), when it immediately starts updating once you have finished the Google account setup.
(I myself also prefer the GAPPS micro package. I don't need and want google photos, youtube, google fit, etc. on my head unit.)
My JET apk is only partly working. At this moment I do not know why.
Replacing apps with mods (radio, BT, sofiaserver) works again now the apps are installed in /system/app
Copying the launcher.sh to /data does work. The launcher.sh works with the SofiaServer keymod as well as with the Xposed module sofiaservercustomkeymod (the one that uses the launcher.sh).
Installing a newer version ór installing one of the xposed modules currently doesn't work as it requires the package installer. The default package installer has been replaced by the googlepackageinstallers from the gapps. As such I can easily work around it by simply writing the apps to their folder in /system/apps. As soon as I upload my modules to the global xposed repository it is no problem anymore anyway as the Xposed installer can install it. I will still looking into why that one can install and my app not. I will also uninstall the google installer and replace it with the default package installer and see what happens.
And with regard to the customkeymod xposed module with settings screen: The settings screen itself works fine, but I still can't use the settings from my app. They stay empty.

Ok, if you think the microgapps is lighter I can cook that in.

gtxaspec said:
Ok, if you think the microgapps is lighter I can cook that in.
Click to expand...
Click to collapse
You might even consider nano or pico gapps and let users just install whatever else they need manually.

I'll do nano on v4 release which will be out tonight.

gtxaspec said:
I'll do nano on v4 release which will be out tonight.
Click to expand...
Click to collapse
Is Viper4Android working on this ROM?
Some time ago you said that you will investigate why is not working on the stock Joying but you never returned with an answer, can you please share your findings if you have any?
Thank you !
---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------
surfer63 said:
(I myself also prefer the GAPPS micro package. I don't need and want google photos, youtube, google fit, etc. on my head unit.)
Click to expand...
Click to collapse
I second this .... I also prefer things kept extremely simple !

haven't tested viper. I will install it tonight and test it tomorrow morning on my drive.

🗃️S4 Unified Collection & Guides📚

Welcome to S4 Unified Collection!
​STOCK ROM FIRMWARES
[Check my Guides for Installation]
Note: If you can't find the Firmware for your device from the link below, then it's not my fault. Android File Host informed me, they delete files with less population on downloads. I don't have these files anymore.
You can find the latest Stock ROM Firmware for your S4 variant below:
GT-I9295 (jactivelte): I9295XXSDQD6 / Build Date: 2017-04-20 / OS: Lollipop 5.0.1
GT-I9500 (ja3gxx): I9500XXUHQD1 / Build Date: 2017-04-25 / OS: Lollipop 5.0.1
GT-I9505 (jfltexx): I9505XXUHQK1 / Build Date: 2017-11-09 / OS: Lollipop 5.0.1
GT-I9505G (jgedlte): I9505GUEUDPF1 / Build Date: 2016-05-13 / OS: Lollipop 5.1.1
GT-I9506 (ks01lte): I9506XXUDRB1 / Build Date: 2018-02-15 / OS: Lollipop 5.0.1
GT-I9515 (jfvelte): I9515XXS1BQD2 / Build Date: 2017-04-17 / OS: Lollipop 5.0.1
GT-I9515L (jfvelte): I9515LUBU1BQF1 / Build Date: 2017-06-08 / OS: Lollipop 5.0.1
SCH-I545 (jfltevzw): VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra): I545LWWSGQA1 / Build Date: 2017-01-05 / OS: Lollipop 5.0.1
SCH-R970 (jflteusc): R970TYSGPL1 / Build Date: 2016-12-02 / OS: Lollipop 5.0.1
SCH-R970C (jfltecri): R970CVRUFND1 / Build Date: 2014-04-11 / OS: KitKat 4.4.2
SCH-R970X (jfltecsp): R970XWWSGQA1 / Build Date: 2017-01-05 / OS: Lollipop 5.0.1
SGH-I337 (jflteatt): AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan): I337MVLSGQB1 / Build Date: 2017-02-09 / OS: Lollipop 5.0.1
SGH-M919 (jfltemo): M919UVSFQA1 / Build Date: 2017-01-04 / OS: KitKat 4.4.4
SM-S975L (TracFone-StraightTalk): S975LUDUANB1 / Build Date: 2014-02-04 / OS: Jelly Bean 4.3
SPH-L720 (jfltespr): L720VPSGPL1 / Build Date: 2016-12-20 / OS: Lollipop 5.0.1
MODEMS & BOOTLOADERS
[Check my Guides for Installation]
Note: If you can't find the Modem/Bootloader for your device from the link below, then it's not my fault. Android File Host informed me, they delete files with less population on downloads. I don't have these files anymore.
You can find the latest Bootloader & Modem for your S4 variant below:
GT-I9295 (jactivelte): I9295XXSDQD6 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9500 (ja3gxx): I9500DXUHPB1 MODEM
GT-I9505 (jfltexx): I9505XXUHQK1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9505G (jgedlte): I9505GUEUDPF1 MODEM
GT-I9506 (ks01lte): I9506XXUDRB1_I9506XXUDRA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9515 (jfvelte): I9515XXU1BQD2 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9515L (jfvelte): I9515LUBU1BQF1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SCH-I545 (jfltevzw): VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra): I545LWWSGQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SCH-R970 (jflteusc): R970TYSGPL1 COMBINED BOOTLOADER & MODEM / BOOTLAODER - MODEM
SCH-R970C (jfltecri): R970CVRUFND1 COMBINED BOOTLAODER & MODEM / BOOTLOADER - MODEM
SCH-R970X (jfltecsp): R970XWWSGQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SGH-I337 (jflteatt): AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan): I337MVLSGQB1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SGH-M919 (jfltemo): M919UVSFQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SM-S975L (TracFone-StraightTalk): S975LUDUANB1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SPH-L720 (jfltespr): L720VPSGPL1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
RECOMMENDED ROMS
Recommend ROMs for the variants below, are:
Official LineageOS / LineageOS microG, Official crDroid, Official DivestOS or any of JDCTeam ROMs with tags [LIVE] [STABLE] [DAILY]
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-I9507 (jtfddxx)
GT-I9508 (jfltezm)
GT-I9515 (jfvelte)
GT-I9515L (jfvelte)
SCH-I545 (jfltevzw) VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra)
SCH-R970 - jflteusc
SCH-R970C (jfltecri)
SCH-R970X (jfltecsp)
SGH-I337 (jflteatt) AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan)
SGH-M919 (jfltemo)
SM-S975L (TracFone-StraightTalk)
SPH-L720 (jfltespr)
Recommened ROMs for the variants below are:
GT-I9295 (jactivelte): Official LineageOS / LineageOS microG
GT-I9500 (ja3gxx): -
GT-I9506 (ks01lte): Unofficial LineageOS 20.0 or Unofficial crDroid
TWRP RECOVERIES
[Check my Guides for Installation]
The list below contains the variants which can use the latest Official Unified TWRP Recovery or Unofficial TWRP Recovery or OrangeFox Recovery:
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-I9507 (jtfddxx)
GT-I9508 (jfltezm)
SCH-I545 (jfltevzw)
SCH-I545L (jfltelra)
SCH-R970 - jflteusc
SCH-R970C (jfltecri)DCTeam
SCH-R970X (jfltecsp)
SGH-I337M (jftlecan)
SGH-M919 (jfltemo)
SM-S975L (TracFone-StraightTalk)
SPH-L720 (jfltespr)
The list below contains the variants which need a specific TWRP Recovery version:
GT-I9295 (jactivelte): Official TWRP Recovery
GT-I9500 (ja3gxx): Official TWRP Recovery
GT-I9506 (ks01lte): Official TWRP Recovery / TWRP- 3.6.0_9-0 or OrangeFox Recovery Project
GT-I9515 (jfvelte): Official TWRP Recovery
GT-I9515L (jfvelte): Official TWRP Recovery
SGH-I337 (jflteatt): TWRP Recovery Locki Patched by mattgyver
GAPPS & microG
GApps
Note: You should always use the smallest package of GApps, be sure you have selected Platform: ARM and the proper Android version of the ROM you are going to flash. If the ROM you want to flash include GApps, no need to download and flash any GApps at all.
Most of the GApps have also a config. file which can be used to to configure your installation the way you like. You can skip any Package that you don't want to be part of your installation. For more infos about that, read the instructions of the GApps you chose or search in Google.
MindTheGapps
BiTGApps
NikGApps (Only Core version)
Open GApps / Open GApps Unofficial A12L
LiteGapps
microG
If you don't want to use Google Play Services and general move away from Google, microG and its variants is an open source alternative which replace these services.
NanoDroid
MinMicroG
BiTGApps microG
microG
MAGISK ROOT
You can check my Guides for installation.
Magisk (APK)
Magisk.zip (Flashable Zip)
Uninstall.zip (Flashable Zip)
Magisk Canary (APK)
Magisk Delta
FoxMagiskModuleManager (This app replace the official magisk module repository since no longer available)
Momo (You can use this app too check if any modifications related Magisk are detected or not)
Universal SafetyNet Fix by kdrag0n [Video Guide]
Shamiko (Hide Root from apps) [Guide]
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]. For Microsoft Intune and other microsoft apps, check this guide.
PIT FILES
Note: If you messed the partitions of your device, you can fix it by simply flashing the PIT FILE for your variant via Odin in the PIT TAB.
The list below contains PIT FILES for some variants:
GT-I9500 (ja3gxx) PIT FILE
GT-I9505 (jftlexx) PIT FILE
SAMSUNG USB DRIVER
Note: If you have a problem while you connect the device to your PC and PC can't recognize it, you may miss the Samsung USB DRIVER. To fix follow these steps:
1. Download SAMSUNG USB DRIVER.
2. Unzip it and install it to your PC.
3. Connect your device and done! Now should be ok.
ODIN
You can download ODIN HERE. Recommened version is Odin 3.12.3
ULTIMATE COLLECTIONS & GUIDES (APPS)
Check the Privacy & Security section in my Guides.
If for some reason you can't find/install an app on Google Play Store due country restrictions or anything, you can sideload the app from APKMirror.
Android Ultimate Collection & Guides
Windows Ultimate Collection & Guides
ReVanced & ReVanced Extended - Guides & Useful Links
UNIVERSAL ANDROID DEBLOATER
Universal Android Debloater
S4 UNIFIED COLLECTION MIRROR
S4 Unified Collection AFH Mirror
DISCORD SERVER
Please verify yourself at #welcome channel. Read #FAQ channel.
Discord Server
JDCTEAM UNIVERSE
Here you can find the work of JDCTeam over the years for our S4 device!
Scroll Down to check the Guides
​

Welcome to S4 Unfied Guides!
!DISCLAIMER!
Most people I know (including myself) who used my Guides and steps, did that with success many times. If you don't follow exactly the steps or you do a mistake during the process, I do not take any responsibility for any unexpected results or damage that may happen. However I am here to help if something goes wrong, just ask in the thread.​
INSTALL BOOTLOADER & MODEM
You can flash Bootloader & Modem with two methods:
Combined: [Recommended]
1. Download Odin and the COMBINED BOOTLOADER _MODEM.tar for your variant to your PC. [You can find everything in my Collection]
2. Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator.
3. Put the COMBINED BOOTLOADER_MODEM.tar to AP section, untick Auto-Reboot, flash!
4. When It's done, reboot your device by pressing Power Button for couple of seconds.
Seperate:
1. Download Odin, the BOOTLOADER.tar and MODEM .tar for your variant to your PC. [You can find everything in my Collection]
2. Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator
3. Put the BOOTLOADER to BL section and MODEM to CP section, untick Auto-Reboot and flash!
4. When It's done, reboot your device by pressing Power Button for couple of seconds.
Notes:
Check what version of Modem and Bootloader you have with apps like Device Info HW.
If Modem & Bootloader didn't changed to the version you wanted, do the same steps again with the method you have selected.
If for some reason Odin failed to flash, make sure your run Odin as adminstrator, try to change USB Port in your PC and don't move the cable during flash. Also if you have Odin and the files on an External hard drive, move Odin and all the files you want to flash, into one folder to your Main Drive for example C: drive.
For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have QK1 Stock ROM then you need to have QK1 Modem/Bootloader. On Custom ROMs doesn't matter. You can have any Modem/BL of your variant you want but recommend is always the latest.
INSTALL TWRP RECOVERY
ODIN Method (No TWRP Recovery currently installed)
1. Download Odin and the .tar file of the TWRP to your PC. [You can find everything in my Collection]
2. Reboot to Download Mode by pressing Power Button + Vol.Down + Home Button.
3. Run Odin as adminstrator > connect your device to PC > put the .tar file of TWRP in AP section > untick Auto-Reboot in options and flash.
4. Done! Restart to TWRP Recovery. (power button+vol.up+home button)
Recovery Method (TWRP Recovery already installed)
1. Download .img of TWRP Recovery. [You can find everything in my Collection]
2. Reboot to Recovery by holding Power Button + Volume Up (+).
3. Press Install Image.
4. Locate the recovery.img you recently downloaded.
5. Select it and choose the option Recovery and Flash.
6. Go back and Reboot to Recovery.
7. Done! Your new recovery should be installed.
CLEAN INSTALL CUSTOM ROM
Note: If you have issues after flash check possible solutions here:
Check integrity of all downloads (compare checksums), do the downloads again.
Make sure you Wiped everything and Formated Data (format data not just wipe) except external SDCard and USB OTG.
Flash only the ROM (without GApps and Magisk) and check if the problem persists. If yes, flash another ROM.
Try other GApps package.
If nothing helps, go back to stock and start from scratch.
Note: You can also Flash Custom ROM using ADB sideload Method.
1. Backup all your data to PC or to external SDCard. [All your data into Internal Storage will be lost on step 7 while Formating Data or Wiping Internal Storage]
2. Install the latest Bootloader & Modem for your S4 variant. [Read the Install Bootloader & Modem Guide above]
3. Download: [You can find everything in my Collection]
TWRP Recovery.
Custom ROM of your choice.
GApps (be sure you have selected Platform: ARM and the proper Android version of the ROM you are going to flash) if the ROM you are going to flash does not include. [Optional]
Magisk Root. [Optional]
4. Move all these files in one folder to your PC or to External SDCard if you have one.
5. Install TWRP Recovery. [Read the Install Custom Recovery Guide above]
6. Turn off your device and Reboot to Recovery Power Button + Volume Up (+)
7. Installation:
Steps without external SDCard:
Select Wipe > Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Connect your device to PC while you are on TWRP and transfer into Internal Storage, the ROM, GApps etc. and the files you want to flash.
Flash ROM > GApps [Optional]
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk (you need to download it again if you previously had it in Internal Storage) then reboot to system and enjoy!
Steps with external SDCard:
go to Advanced > File Manager > External_SD and delete all folders in ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom ROM/Gapps/Magisk/DFE you want to flash.
Each app on your phone with the WRITE_EXTERNAL_STORAGE permission may create files or folders in ur sdcard. Most of these folders have once been created by one of these apps and many of them may be deleted with a few exceptions (e.g. Android, .data, .android_secure, these contain important system or app data like a game's downloaded content):
.android_secure: apps installed and then moved to sdcard
Android: app data/cache
data: app data
.estrongs: ES file manager
LOST.DIR: sort of trash folder (collects recovered files after phone crashes)
DCIM: phone gallery's photos and previews
OTA-update: Over The Air update service
ppy_cross: an unknown third-party app's data.
So I recommend to delete them so you can put your phone/sdcard in a clean state and is guaranteed to be able to re-create these folders.
Select Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Flash ROM > GApps [Optional]
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk then reboot to system and enjoy!
DIRTY INSTALL YOUR CUSTOM ROM
Note: Before you start flashing, keep in mind the ROM you dirty flashing MUST be the same with the one you have already installed.
1. Make a full nandroid backup, just in case something goes wrong. You can use TWRP to do that. (TWRP > Backup > Select everything) [Optional]
2. Remove all Magisk modules. [Optional]
3. Reboot to TWRP and Wipe Dalvik / ART Cache, System and Cache.
4. Flash the ROM > GApps [Optional] > Magisk [Optional]
5. Reboot and Enjoy!
I've skipped some explanations, because if you are going to dirty flash, you already know for example how to boot to TWRP.
CLEAN INSTALL OFFICIAL STOCK ROM
Note: For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have QK1 Stock ROM then you need to have QK1 Modem/Bootloader. On Custom ROMs doesn't matter. You can have any Modem/BL of your variant you want but recommend is always the latest.
1. Download the latest stock ROM (Firmware), Modem & Bootloader for your variant, TWRP Recovery (.tar file) and ODIN to your PC. [You can find everything in my Collection]
2. Install TWRP Recovery [Read the Install Custom Recovery Guide above]
3. Reboot to TWRP Recovery and Select Wipe > Advanced Wipe
4. Select Dalvik / ART Cache, System, Data, Cache, External SDCard (if you have) and then Swipe to Wipe.
5. Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
6. Reboot to Download Mode Power by pressing Power Button + Vol.Down + Home Button
7. Run Odin as adminstrator from your PC > connect your device > put the Stock Rom (Firmware) file to AP section and flash it!
8. Let the ROM boot.
9. Install the same version of Bootloader & Modem as your Firmware. [Read the Install Bootloader & Modem Guide above]
10. Enjoy!
BACKUP & RESTORE ROM (NANDROID BACKUP)
Check this Youtube Video to see the process in action.
Backup:
1. Reboot to Recovery (Power Button + Volume Up (+))
2. Choose Backup and Select Boot > System > Data (excl. storage)
3. Select Storage and choose SDcard if you have one otherwise let it on Internal Storage.
4. Swipe to Backup.
5. Done!
Restore:
1. Reboot to Recovery. (Power Button + Volume Up (+))
2. Select Wipe > Advanced Wipe.
3. Select Dalvik / ART Cache, System, Data, Cache and then Swipe to Wipe.
4. Press Home Button to go back and Select Restore.
5. Select the backup file with the ROM and make sure Boot, System and Data (excl. storage) are selected.
6. Select Swipe to Restore and when completed Reboot to System.
7. Done!
MAGISK ROOT
The easiest way to root your device is via Magisk, it should work in all ROMs, Stock and Customs.
Install Magisk:
1. Install latest TWRP Recovery. [Read the Install Custom Recovery Guide above]​2. Download the Magisk [You can find it in my Collection]​3. Reboot to TWRP Recovery by pressing Power Button + Volume Up (+) and flash it.​4. Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK. [You can find it in my Collection]​Note#1: From Official TWRP Recovery 3.5.1 and onward (and other recoveries based on that), Magisk.apk can be flashed as apk without the need of rename it to .zip. So you can simply flash the Magisk.apk in TWRP.​Manually Creation of Flashable Zip:​Download the latest Magisk APK and rename the Magisk.apk → Magisk..zip.​​Note#2: If your bank apps detect root, follow this Guide.​
Uninstall Magisk:
Flash the Uninstall.zip in TWRP Recovery and reboot. [You can find it my Collection]
If Magisk App isn’t uninstalled automatically, manually uninstall the app.
Manually creation of Flashable Uninstall Zip:
Download the latest Magisk APK and rename the Magisk.apk → uninstall.zip
Uninstall Magisk directly through the Magisk app. Simply press the Uninstall button.
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
MIXER_PATHS (INCREASE VOLUME VALUES)
Check HERE and HERE.
HOW TO TAKE LOGS
How to take logs on Android
SCREEN RETENTION FIX
Screen Retention FIx: If you have an issue with screen retention apply this configuration to your device ROM.
BATTERY TIPS
Samsung Galaxy S4 Battery Model: B600BE
Battery Replacment (Video)
Advanced Guide
Simple Battery & Charging Tips
Improve your SOT
Battery Calibration
Method 1
Steps:
1. Discharge your phone fully until it turns itself off.
2. Turn it on again and let it turn itself off.
3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.
4. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.
5. Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.
6. Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.
Method 2
Notes: It won't dramatically extend battery life, but it will give your old battery at least 30 minutes additional run time.
Steps:
1. Get "GSam or Ampere" from the Google Play Store.
2. Launch the app and fully charge your phone. (Important: Only proceed with the calibration when the word "Full" appears in GSam or Ampere.)
3. While your phone is still connected to the cable reboot your phone to recovery mode, open file manager and navigate to "/data/system" and delete "batterystats.bin," "batterystats-checkin.bin," and "batterystats-daily.xml."
4. Reboot your phone (while it is still plugged in) and charge it until it reads "full" on GSam or Ampere.
5. Unplug the cable and use your phone normally until it shuts down (0 percent )
6. Charge your phone to 100% while it is turned off.
7. Boot into os and plug in your phone and charge it until it says "full" on the GSam or Ampere.
8. Unplug and have fun!
Battery Capacity Health
Notes:
1) Before checking the battery health, charge the device to 100%.
2) Check charge counter values and consider first 4 digits from left as your battery capacity in mAh. And check charge counter. (Charge counter/level)*100 is the battery capacity.
To find battery capacity in Windows:
Enable Developer options in your device.
Enable USB Debugging in your device.
Conect your device to PC and give permissions.
Open Minimal ADB (run cmd.exe) or Platform tools.
Type "adb shell dumpsys battery" command in Minimal ADB or Platform tools.
To find battery capacity in Android (Terminal) - Root needed:
Download an android terminal app like Termux,
Open terminal and type: cat/sys/class/power_supply/battery/charge_full
Overheating
Following reasons will lead to device heating issue:
During the initial setup after purchase or when restoring data.
Downloading large files.
Using apps that require more power or using apps for extended periods such as:
Playing high-quality games for long time.
Recording videos for extended periods.
Streaming videos while using the maximum brightness setting.
Using the Screen Mirroring / Smart View feature (connecting mobile to a TV).
While multitasking or when running many apps in the background i.e:
Using Multi window.
Updating or installing apps while recording videos.
Downloading large files during a video call.
Recording videos while using a navigation app.
Large amount of data for syncing with the cloud, email, or other accounts.
Exposing device under sunlight when temperature is high around you.
Extensive usage of mobile hotspot and tethering feature.
Using device in areas with weak signals or no reception or in roaming network.
Charging the battery with a damaged / unapproved USB cable.
Device's multipurpose jack is damaged or exposed to foreign materials, such as liquid, dust, metal powder, and pencil lead.
Solution:
Turn off Wi-fi, GPS , bluetooth and other connectivity options when not in use by dragging the notification panel.
Decrease screen brightness.
Close background running applications.
Too many applications installed in device may result in device heating since their corresponding process will keep on running in background. It is advised to uninstall un-necessary apps if not using them.
Avoid using apps like GPS, data dependent apps or graphic intensive games for longer duration since they require more energy to function, causing device to heat.
It is advised not to use device while charging as it may cause the device to over heat.
General:
DO:
Use manual brightness or dim the screen.
Turn off notifications for apps you don't use. Better still, delete/disable the apps entirely if you don't need them.
Enable battery or power saving mode when you want to extend your battery life.
Use the power adapter that came with your phone. Other chargers can charge slowly/faster but they can also damage your phone or battery.
Turn off bluetooth, location tracking, and Wi-Fi (unless you are actively using it)
Turn off print services from bluetooth connection preferences.
Avoid extremes of heat and cold. If your phone gets very hot or cold it can strain the battery and shorten it's lifespan.
DON'T:
Have Bluetooth or Wi-Fi turned on constantly.
Leave apps running in the background. Instead restrict background usage off apps that you don't need running.
Push email means your device is always listening for new email which drains alot of battery.
Drain your phone battery all the way to 0% or charging it all the way to 100%. Keep it between 20% - 90% for longer battery lifespan.
The more advanced the graphics and animations are (games, videos, photos, animations), the harder the processor and graphics chip in your smartphone have to work. More activity means more battery use.
PRIVACY & SECURITY
Some useful links:
All about Privacy & Security at Privacy Guides.
Electronic Frontier Foundation.
PrivacyTests: Open-source tests of web browsers privacy.
Check if your email address or your phone number is in a data breach at Have I been Pwned & at Firefox Monitor.
Test your browser to see how well you are protected from tracking and fingerprinting at Cover Your Tracks by EFF and at Bromite fingerprint mitigations tests.
WebRTC IP Leak Test. WebRTC is a new communication protocol that relies on JavaScript that can leak your actual IP address from behind your VPN. You can find more infos how to disable it at Privacy Guides in browsers section.
Ad Block Tester is a free service on the Internet to evaluate content blocking solutions. It is not designed to be a benchmark, but it reveals the level of blocking against a set of hosts that are very popular.
Check on AM I FLoCed? by EFF if your your Chrome browser has been turned into a guinea pig for Federated Learning of Cohorts or FLoC, Google’s latest targeted advertising experiment.
How to block ads on Android.
εxodus: εxodus analyzes Android applications in order to list the embedded trackers and ads.
Spyware Watchdog Article Catalog: A catalog which determinate under tests and tracking if an app is spyware and what data it collects.
CryptPad: CryptPad is built to enable collaboration. It synchronizes changes to documents in real time. Because all data is encrypted, the service and its administrators have no way of seeing the content being edited and stored.
PrivateBin: PrivateBin is a minimalist, open-source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256-bit AES. It is the improved version of ZeroBin.
ShutUP10++ , Privacy.Sexy: Disable major tracking features of Windows.
General:
Always prefer Open Source or well popular Programs, Apps, ROMs, Kernels & Stuff.
Open Source doesn't mean it's 100% safe but it's unlikely to have something suspicious, since you and other users can check the code in GitHub or in any other code hosting platform the "stuff" is hosted. You can also find and use FOSS apps at Droid-ify.
Prefer ROMs & Kernels with SELinux Enforcing. You can find informations here.
Always download and install Apps, Programs, ROMs & Stuff from official sources and do not use redirection links from different sites. Google is your friend to find the official source of the stuff you want.
Always check the permissions an app requires, before download and install it to your device. If an app ask for permissions which has nothing to do with the app functionality then it's should be reconsider or ask the developer why these permissions needed.
You can also check if the app includes trackers and ads with εxodus.
If you want to avoid Google and Play Store (De-Google), you can choose a ROM without GApps preinstalled like LineageOS and use Droid-ify client which is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device. Note that not all apps from Play Store will be available in Droid-ify or F-Droid. Only Open Source projects. You can find alternatives though.
Alternative you can use LineageOS for microG or any ROM which support signature spoofing and can support microG and use Aurora Store.
For Windows use the default Windows Defender & Malwarebytes to scan your files whenever you want (Prefered before open or install them). Also use the addon/extension uBlock Origin in your Browser. These should be enough for normal users. You can also use the tool ShutUp10++ or Privacy.Sexy to disable major tracking features of Windows.
For Android Do not use any antivirus - antimalware since it's useless, just check what apps and from where you installing.
Always verify the source of addons/extensions in your browser. Avoid installing random and unpopular addons/extensions. Keep it minimal and clean, so browser can be fast and safe, no need bunch of extensions.
If you are using VPN, always check the terms and rules of the provider. Avoid random VPN Services.
Recommended VPN Services.
Using a VPN will not keep your browsing habits anonymous, nor will it add additional security to non-secure (HTTP) traffic.
Recommended is to encrypt your data/files always before uploading them to cloud with tools like Cryptomator.
Always use unique and strong passwords for each of your accounts.
Use awarded open source Password Managers like KeePass or KeePassXC for Desktop and KeePassDX for Android to manage your passwords and have them with you safe, encrypted and secure. Must be noted you can use the same database file between these programs.
Always enable 2 Step Authentication wherever is available for your accounts.
You can use apps like Aegis Authenticator.
Do not open or click on links attached in unknown emails or SMS you may get. Always check the address of the email or the number of SMS and verify it's legit from the official source.
Create and use "burned" email for accounts/sites you have concerns but you definitely want to try them. Do not use your personal or business email. You can also create and use email aliases of your email with SimpleLogin which is open source and awesome service.
DISCORD SERVER
Please verify yourself at #welcome channel. Read #FAQ channel.
Discord Server

Changelog
Note: Changes in Collection & Guides happens in real time. The date I post these Changelogs is just a sum up since I can't post all the changes the time that happening to avoid spamming the thread. So you can always consider the Collection & Guides Up-to-Date. However, I may announce some big changes in posts before I include them in the Changelogs.​
LATEST
Update: 18/01/2023
Changelog
ARCHIVED
Update: 29/10/2022
Changelog
Update: 01/07/2022
Changelog
Update: 07/05/2022
Changelog
Update: 01/04/2022
Changelog
Update: 28/02/2022
Changelog
Update: 04/02/2022
Changelog
Update: 23/12/2021
Changelog
Update: 01/10/2021
Changelog
Update: 31/08/2021
Changelog
Update: 01/05/2021
Changelog
Update: 19/04/2021
Changelog
Update: 27/02/2021
Changelog
Update: 28/01/2021
Initial Release

Hi guys,
I can't manage to install the Bootloader & Modem via Odin on my phone.
Does the phone need to be already rooted in order to install the B&M?
Attached is also the capture I took when rebooting the phone in Download mode.
I selected "reboot to bootloader" in order to install the B&M, because otherwise Odin won't detect that the phone is connected to the PC. Probably I'm doing something wrong.
Any help will be very much appreciated.
Thanks in advance.
{
"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"
}

R_A_N_D_Y said:
Does the phone need to be already rooted in order to install the B&M?
Click to expand...
Click to collapse
I'n not 100% sure, but I think no
R_A_N_D_Y said:
Attached is also the capture I took when rebooting the phone in Download mode.
Click to expand...
Click to collapse
The picture shows your device in recovery
R_A_N_D_Y said:
I selected "reboot to bootloader"
Click to expand...
Click to collapse
How did you do that? I'm not aware of such a reboot option.
You should boot into download mode (see above for how to). It should look like attached picture 1
In Odin, before you start flashing, you should see a success message "<ID ... Added!! If not, you should check if you have all required driver installed for your device.

pocketrule said:
I'n not 100% sure, but I think no
The picture shows your device in recovery
How did you do that? I'm not aware of such a reboot option.
You should boot into download mode (see above for how to). It should look like attached picture 1
In Odin, before you start flashing, you should see a success message "<ID ... Added!! If not, you should check if you have all required driver installed for your device.
View attachment 5212215View attachment 5212217
Click to expand...
Click to collapse
Thank you very much !

R_A_N_D_Y said:
Hi guys,
I can't manage to install the Bootloader & Modem via Odin on my phone.
Does the phone need to be already rooted in order to install the B&M?
Attached is also the capture I took when rebooting the phone in Download mode.
I selected "reboot to bootloader" in order to install the B&M, because otherwise Odin won't detect that the phone is connected to the PC. Probably I'm doing something wrong.
Any help will be very much appreciated.
Thanks in advance.
Click to expand...
Click to collapse
No need root.
Download and install the Samsung USB Drivers in your PC. (You can find it in my collection)
Download the Combined Bootloader & Modem for your variant from my collection.
Turn off your device.
Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator.
Put the COMBINED BOOTLOADER_MODEM.tar to AP section, untick Auto-Reboot in options and flash!
When It's done, reboot your device by pressing Power Button for couple of seconds.

New Update:
Changelog:
Added Changelog Tracking at #3 post
Added Privacy & Security section in Guides.
Added a Note to check Privacy & Security Guide at Useful Apps section in Collection.
Added Flashable Zips for Install & Uninstall Magisk in Collection.
Updated the Magisk Guide and added Flashable Zip method.
Reordered the sections in Guides.

Hi Retrial, first of all this is a really useful post thank you so much!
I just bought a brand new S4 GT-I9505 and I used the latest TWRP in your post wich is twrp-3.5.1_9-0-jflte.img.tar for flashing lineage-17.1-20210116-UNOFFICIAL-jflte.zip and I have some question if you are so kind to aswer me:
I want to update the firmware so I downloaded the last one for Italy from Updato.com which is I9505XXUHPK2 (Genuary 2017) and I would like to know if is a good idea to flash it with Odin and if I have to fresh re-installing Lineage. Then I would like to know if after updating the firmware I can update only XXUHQC1_BOOTLOADER and XXUHQC1_COMBINED which are the international versions and obviously the most recent versions.
Do you think is possible? Thanks in advance. Kind Regards

hermes127 said:
Hi Retrial, first of all this is a really useful post thank you so much!
I just bought a brand new S4 GT-I9505 and I used the latest TWRP in your post wich is twrp-3.5.1_9-0-jflte.img.tar for flashing lineage-17.1-20210116-UNOFFICIAL-jflte.zip and I have some question if you are so kind to aswer me:
I want to update the firmware so I downloaded the last one for Italy from Updato.com which is I9505XXUHPK2 (Genuary 2017) and I would like to know if is a good idea to flash it with Odin and if I have to fresh re-installing Lineage. Then I would like to know if after updating the firmware I can update only XXUHQC1_BOOTLOADER and XXUHQC1_COMBINED which are the international versions and obviously the most recent versions.
Do you think is possible? Thanks in advance. Kind Regards
Click to expand...
Click to collapse
Hello,
If you flash firmware u need to reflash lineageos from start along with twrp. U can only do it via Odin.
Btw use the latest for your variant from my collection. Doesn't matter the country.
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
You can flash bootloader and modem seperate yes (but I recommend to use my combined .tar which include both of them), without the need to flash everything again. Just go to Odin and flash the combined .tar I have made to AP. Once again, all the latest versions are included in my collection, doesn't matter the country so just use them.
All the infos and steps you need are in my collection and guides. Let me know if you have more questions.

Retrial said:
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
Click to expand...
Click to collapse
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.

hermes127 said:
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
Click to expand...
Click to collapse
Just follow what Retrial said; flashing his combo-file will accomplish what you want. Starting from scratch like you wanna do isn't any better.
I flashed bootloaders and modems so often, I can't even remember. Flashing stock firmware? Maybe once!

hermes127 said:
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
Click to expand...
Click to collapse
Firmware=Stock Samsung ROM. Firmware does not include Modem & Bootloader. So even if u flash Firmware u have to also flash Bootloader & Modem.
Now you say that u are on lineageos, I don't know what version you are but you can flash via Odin the combined .tar file which include Bootloader & Modem and then clean install via TWRP the latest LineageOS along with latest GApps if you use.
If you want to start from scratch-fresh then follow my Guides: "Clean Install Official Stock ROM" and then the guide "Clean Install Custom ROM".
With few words: go to TWRP wipe everything, the connect ur device to PC and flash via Odin the latest Firmware (stock ROM). Let it boot and then flash via Odin the latest Bootloader & Modem. Then flash TWRP and clean install the latest LineageOS with GApps (optional).
Everything you need is on my collection and all steps in my guides. Since u have i9505 variant you need the latest Firmware/Modem & Bootloader which is I9505XXUHQK1.
Let me know how it goes or if you have any other questions.

Retrial said:
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
Click to expand...
Click to collapse
Retrial said:
Firmware=Stock Samsung ROM. Firmware does not include Modem & Bootloader. So even if u flash Firmware u have to also flash Bootloader & Modem.
Now you say that u are on lineageos, I don't know what version you are but you can flash via Odin the combined .tar file which include Bootloader & Modem and then clean install via TWRP the latest LineageOS along with latest GApps if you use.
If you want to start from scratch-fresh then follow my Guides: "Clean Install Official Stock ROM" and then the guide "Clean Install Custom ROM".
With few words: go to TWRP wipe everything, the connect ur device to PC and flash via Odin the latest Firmware (stock ROM). Let it boot and then flash via Odin the latest Bootloader & Modem. Then flash TWRP and clean install the latest LineageOS with GApps (optional).
Everything you need is on my collection and all steps in my guides. Since u have i9505 variant you need the latest Firmware/Modem & Bootloader which is I9505XXUHQK1.
Let me know how it goes or if you have any other questions.
Click to expand...
Click to collapse
Wow your instructions are absolutely detailed and useful, thank you so much Retrial for your support.! I'll opt for the "start from scratch-fresh" install by following your guides. If I can take advantage of your competence I would like to ask you just one last advice: I switched to Lineage OS for privacy reasons (I don't like google so I don't need GApps) and I also use it for sharing internet to my MacBook Pro with USB tethering (not wifi tethering which is not safe for privacy) so do you think that the Optimized Lineage OS (Android 10) version from JDCTeam is the right version for me? May I use the Android 11 version? Probably I'm asking you to much things and I can understand if you can't answer me, you have been really kind and I really appreciated your help. Anyway I'll post here my experience with "start from scratch-fresh instal" .

Anything for the AT&T S4 Active (+) variant?

hermes127 said:
Wow your instructions are absolutely detailed and useful, thank you so much Retrial for your support.! I'll opt for the "start from scratch-fresh" install by following your guides. If I can take advantage of your competence I would like to ask you just one last advice: I switched to Lineage OS for privacy reasons (I don't like google so I don't need GApps) and I also use it for sharing internet to my MacBook Pro with USB tethering (not wifi tethering which is not safe for privacy) so do you think that the Optimized Lineage OS (Android 10) version from JDCTeam is the right version for me? May I use the Android 11 version? Probably I'm asking you to much things and I can understand if you can't answer me, you have been really kind and I really appreciated your help. Anyway I'll post here my experience with "start from scratch-fresh instal" .
Click to expand...
Click to collapse
Don't worry mate, ask whatever you want. I will help if I can.
Optimized LineageOS 10 is great but it's EOL (end of life). Optimized LineageOS 11 is also great and it's currently under development.
But since you are looking for privacy & security it's better to use Official LOS with guarantee monthly security patches cause lately optimized los stays a bit behind on updates. (Dev is busy) Soon official 11 will also be released.

blackhawk said:
Anything for the AT&T S4 Active (+) variant?
Click to expand...
Click to collapse
I think ur variant has locked bootloader so I don't know if anything exist.

Retrial said:
I think ur variant has locked bootloader so I don't know if anything exist.
Click to expand...
Click to collapse
Thank you. If you become aware of any work arounds please let me know.
It's a phone that is expendable now

blackhawk said:
Thank you. If you become aware of any work arounds please let me know.
It's a phone that is expendable now
Click to expand...
Click to collapse
I know there is a workound for S4 AT&T on specific firmware with locki patched TWRP but I don't think it's exist anything for ur S4 active at&t. I will let u know if I find anything.

Retrial said:
Don't worry mate, ask whatever you want. I will help if I can.
Optimized LineageOS 10 is great but it's EOL (end of life). Optimized LineageOS 11 is also great and it's currently under development.
But since you are looking for privacy & security it's better to use Official LOS with guarantee monthly security patches cause lately optimized los stays a bit behind on updates. (Dev is busy) Soon official 11 will also be released.
Click to expand...
Click to collapse
Ok thank you, I'll follow your advice.

[GUIDE] OOS 10.3.8 degoogled, debloated + MigroG

I have successfully degoogled and debloated the latest OOS (atm 10.3.8) and have a working microg setup using nanodroid package. Battery life is nice. 45hrs with 10,5hrs SOT on the first go! Not any unwanted background data moving, success I'd say! So for anyone interested, here are roughly the steps I took.
I couldn't deodex the services.jar with VdexExtractor so I used FakeGapps from Edxposed. Works!
In following guide we will first get a factory state OOS with twrp and root WITHOUT internet. Then we uninstall system app 'android setup', allow internet, get Edxposed working and FakeGapps installed. Then we install Nanodroid package from twrp to get a working microg and setup it and debloat. + Disable trackers using App Manager from F-droid repositories or github. Get it ready for sideloading or use adb. Support the developer!
General guide (everything gets erased):
1. Pure factory installment using MSM tool for 10.3.8 from Oneplus 6 unbrick tools. (XDA forum)
2. The phone starts, go through the initial setup bypassing everything you can. DON'T SETUP ANY WIFI!
3. Immediately switch off mobile data from quick settings, just in case. We dont want android setup to update any apps.
4. Enable unlocking the phone, reboot to bootloader
5. Unlock the bootloader (fastboot oem unlock)
6. Do parts 2 and 3 again (choose Oneplus slate font at this time if you ever want it to work)
7. Enable USB debugging, connect to computer, check 'adb devices' to get the window to allow the computer to appear. (The daemon needs to be running)
This all was to get the phone into pure factory state without automated changes, bootloader unlocked and adb working.
8. Install twrp and magisk. Boot up the phone.
9. Remember! No internet connections yet! Uninstall the system app 'Android Setup'. I used sideloaded AppManager for that. You'll know when you have uninstalled the correct app when the notification of android setup disappears.
10. Reboot
11. Now you can connect to internet.
12. In magisk, install Riru core, (mandatory reboot here!) and Riru Edxposed (2nd reboot)
13. In Edxposed, install FakeGapps and activate it. Reboot.
13. Now you can connect to internet.
This was all done to setup the phone for Nanodroid package and get safely to internet without unwanted updates.
14. Download a nanodroid package from github. I used just the microg version. Flash it from twrp. It should debloat some necessary google stuff, install aurorastore and aurora services and straight up working microg.
15. Check if microg is working and do registrations and enable cloud and location stuff. Reboot.
16. Install any app that uses google cloud service for push notifications and check from microg settings that it shows in the list. Don't continue installing any such apps until it does. Reboot or troubleshoot if necessary with microg related info.
17. Back up current setup from twrp for fallback.
18. Debloat to your heart content, except only disable and force stop the play store. In my case the app is still the official one. Don't use.
19. From AppManager, run disable all trackers, including system apps from 1-click ops.
There! Use some time, and if everything is to your liking, make a backup. Remember to disable trackers from every app you install after you have configured it.
Sidenote: Aurora store did not work when installed systemlessly, but worked fine as a user app

Reserved, just in case

[FIXED] I done did it... First time bricking my phone... [Cannot Wipe - PlayStore Schenanigans]

I did it!
After many years of using root and twrp and whatnot. I finally bricked my OnePlus 5t.
Here is the story how I did it:
*many years after using root*
*opens [REDACTED], installs modified google play store as a system app (trusted source)*
*stops being able to use google services*
[REDACTED - I cannot fully specify what I was using]
*Basically I install google play store as a user app, then as system app but then I Can't remove the system app*
*So I download a system app remover and force to remove google play store with root*
*Nothing, still can't change or update to the original play store*
...
*uses a couple more system app removers for google play store*
*tries to reinstall original playstore again and I am forced to reboot*
*Bootloop to recovery*
*scratches head*
*Goes to TWRP, attempts to install stock rom I had lying around in the filesystem*
*attempts to reboot*
*stock recovery*
*ok... I am getting scared... flashes to recovery twrp again*
*goes into twrp.... led on... black screen... USB_BULK stuff*
*huh... Downloads qualcomm drivers*
*Ermm... What do I even do?...*
*Goes back to recovery*
*downloads full stock ota*
*attempts to sideload zip* (this isn't possible)
*no chance... omfg... omfg what did I ******* do?!*
*Checks on this thread: https://forum.xda-developers.com/t/...storage-on-most-of-qualcomm-devices.3949588/*
*Wtf is a firehose file?*
*Finds a .elf file on the stock rom I had downloaded*
*How do I put it on the program???*
*gives up*
*Googles: Phone bricked, is it even possible to backup my data on a encrypted filesystem?*
*Still have no clue*
*spends night atttempting fix phone... its 7:29 am atm, my job starts at 10 am and I have no phone...*
*Gives up, when all else fails... I made this thread*
Notes:
My phone is a OnePlus 5t
I had android Q (10)
Can't seem to flash, for some reason, TWRP, gives me a black screen. (? wtf)
There is sensitive data on the phone, like my pics, my authy app (2FA tokens app with backups BUT I dont have the same phone number I used back then)
ATLEAST! AT THE VERY LEAST! I just want my 2FAtokens. ALL of my accounts that support 2FA are protected with 2FA!
Please help... I am about to lose a loooooooooooot of stuff...
...Gonna sleep 2 hours and go to work and later when I come back I will be able to cry again...
I am going to attempt to try to recover my 2FA on another phone...
Just to see if I can even get them back somehow...
I don't care about my pics, my porn, my apps, my info, nor whatever I have on my phone, just those darn 2FAs...

FIXED! If anyone has this problem, they can check this...
What I did:
So I knew that play store was at fault for me, causing the brick.
1: I used this program: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/
1.1: Set it to OP5T device type in TAIO (the tool all in one), since we are in a very limited mode without being able to upload files to the phone we need twrp to do this for us.
1.2: Click Recovery flasher and device rooter
1.3: Set it to TWRP 3.2.1 Universal OP5T (maybe other versions don't work? Try them)
1.3: Uncheck all checkboxes and click only the following checkboxes:
1.4: Check "Automatic TWRP MD5 check", "ONLY boot it"
1.5: Click Flash and wait
2: In TWRP, I sent via PC USB directly to the phone the gApps file I needed (https://opengapps.org/)
(Select arm64 pico (for OP5T) I had android sdk 27 (V8.1 rom) because I had installed it on top of android 10 rom I had, so I downloaded it for sdk 27, if you dont know which rom version you have right now or you can't check because of the brick, just download gApps for android 10 and run it on twrp, in the logs it will tell you it can't install because your rom is has a different version, telling you the version of your phone)
2.2: Ran it until it was successful (android version missmatch in my case)
2.3: Ok so your playstore is reinstalled fully and all essentials, so let's now grab a full latest OTA from official oneplus website
2.4: Send it to the Phone like you did for gApps (Better use a /ROOTTOOLS folder or something in the root of the device, easier for me)
2.5: You can't seem to run the OTA on TWRP, so go back to normal recovery (if you dont have stock recovery, get one for oneplus 5t online and fastboot flash it into recovery just like twrp)
3: Now that you have the OTA on ROOTTOOLS and are inside the custom stock recovery, run the full OTA and wait.
3.1: If everything goes right just reboot your phone and see if it's unbricked, all data and app data should still be intact! (It might take around more than 10 minutes on the booting animation of the red and white balls, if the device doesn't go to recovery, doesn't reboot, doesn't do anything but this, leave it be for atleast 1 hour, put your faith in it)
4: TADA UNBRICKED! Kiss your phone like I did, while it loads the enviroment.
4.1: Now go back to fastboot in your phone, go back to your computer, open TAIO (the tool all in one) and root your device again
4.2: Click Recovery flasher and device rooter
4.3: Uncheck all checkboxes and click the following: "Automatic TWRP MD5 Check", "and boot it", "root after boot", select your magisk version you want (I got a md5 error saying it couldn't be checked, but dammit we already come this far, I think its a bug)
4.4: Click Flash and Root and wait
4.5: You will be in TWRP, wait for the magisk zip to install automatically
4.6: Reboot the phone
5: Use Phone and kiss it and get covid from the screen surface... (jkjk, dont do that, kinda afraid now ngl)
Happy girl after bricking her phone, because she removed playstore like a rootnewb...
(vader dancing)
...well this only took like... 7 hours to discover...
And I am supposed to be working...
Cya later, I gotta go.
(Mr.Incredible working)

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge Stock to Android 13

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge Stock to Android 13
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge (hero2lte Exynos SOC) Stock to Android 13 / LineageOS 20
Supported models
International & Canada:
- SM-G935F
- SM-G935FD
- SM-G935X
- SM-G935W8
Korea:
- SM-G935S
- SM-G935K
- SM-G935L
This detailed step-by-step guide helps you transform your Samsung Galaxy S7 Edge hero2lte to a powerful one with Android 13.
Make sure your phone is hero2lte/Exynos SOC before going further: in Android, go to Settings > About phone > Check Model number is listed above.
If not, quit this tutorial.
### READ THOSE WARNING COMMENTS
CHANGELOG
v5. Back to TWRP 3.6 (3.7 oversize)
v4. Android 13, TWRP 3.7
v3. BitGApps v1, Magisk 25.2
v2. Update TWRP, add adb to change screen definition, update download link
v1. Initial release for Android 12
1) DOWNLOAD
- djibe Galaxy S7 hero2lte pack: https://bit.ly/djibe-galaxys7edge-pack
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.6.2_9-0 official recovery + Magisk Root + adb.exe). Unzip files.
+ ROM Unofficial LineageOS 20: https://forum.xda-developers.com/t/...ofing-ota-updates-for-s7-edge-exynos.4484511/
Download latest build: https://ivanmeler.github.io/devices/hero2lte.html
+ BiTGApps Package ARM64 13: https://github.com/BiTGApps/BiTGApps-Release/releases
OR NikGApps T Basic: https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-T/
OR MindTheGApps 13 ARM64: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
+ Charge phone to 100%
2) BACKUP DATA
Install Samsung USB drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use Google built-in cloud to backup apps like SMS Backup & Restore to backup texts, contacts, etc.
Backup your WhatsApp messages in Google Drive.
Everything else: podcasts, Authenticators, TODOs etc...
Then copy the backup on your PC.
Make sure you have latest official updates for your phone:
Connect to Wifi and go to Settings > About device > Software update > Update now
### BACKUP NOW, you will lose everything.
3) FLASH TWRP 3.7 RECOVERY
Go to Settings > About phone> Software information.
Tap 7 times on Build number item to unlock Developer options.
Go to Settings > Developer options, switch OEM unlock ON and Confirm.
Shutdown phone.
Boot in Download Mode: hold Home + Power + Volume- until you see blue-green Warning screen and release buttons.
Confirm access to Download mode by pressing Volume+.
Phone now displays "Downloading..., Do not turn off target".
Connect phone in USB, wait for drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT ticked while F. Reset Time is ticked.
In AP > select twrp-3.6.2_9-0-hero2lte.img.tar
### Same recovery for Korean models (G930S/K/L variants)
### Warranty will be Void after next click ###
Click Start.
Wait until flash Success message appears.
Unplug phone.
Restart phone to recovery :
- hold Power + Home + Volume- until phone screen becomes black...
- and immediatly switch from Volume- to Volume+ (still holding Power + Home) and hold until Samsung's logo is displayed to land in TWRP recovery.
### If Android launches, hold 3 buttons until phone restarts and Samsung logo appears.
4) BACKUP IMEI PARTITION AND SYSTEM (Nandroid backup)
(Boot in Recovery Mode: Hold Home + Power + Volume+ until you see Samsung's logo then release and wait a few seconds for TWRP recovery to boot)
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Wipe > Format Data.
Type: yes and confirm with bottom right check icon.
Encryption is removed. You can now access partitions.
### If you miss this step you won't have access to any partition.
Back to home menu > Backup.
You can now select the partitions you want to save.
Select at least EFS partition to backup your IMEI. If a flash fails and partition is damaged you will still be able to restore this partition and use the phone.
If IMEI is lost during a flash, phone won't be able to reach cellphone networks.
I prefer to backup Boot, System, Baseband and EFS partitions. In case of problem, you will have your phone in its original state.
Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
Save backup: still under TWRP recovery, connect phone to PC.
Go to Mount menu and check Data partition is checked and MTB button is on "Disable MTP" state.
From Windows explorer, access phones memory and copy-paste the TWRP folder (located in root folder, beside DCIM and Music folders) somewhere safe on your computer.
5) FORMAT PARTITIONS
### Make sure you copied TWRP backup from internal memory to somewhere safe.
Go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup at step 2), then Swipe to Wipe.
Back to TWRP home screen, go to Reboot > Recovery and swipe to reboot.
On next launch, check the checkbox to remember choice and swipe to allow modifications.
6) FLASH ROM, (MAGISK ROOT) AND GAPPS
Back to TWRP main menu, go to Mount menu again to connect phone to PC again.
Connect phone to PC and use Windows explorer to copy files on phone's internal memory.
Copy TWRP folder from your phone to somewhere safe on PC.
This backup can restore your phone to its original Samsung state.
Copy files of ROM + BitGApps + Magisk on phone.
Go back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
Optional for root: Add More zips > Magisk*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Go to Reboot > Recovery and swipe to reboot.
After restart, go to Install, select bitgapps*.zip and swipe to flash.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System and on Install TWRP App? menu, tap on button Do Not Install
Wait for the phone to boot during 5 minutes.
7) ROOT ACCESS
Configure Android as you like.
Don't try to set fingerprints at first setup. It will crash.
No need for extra work to be root.
Magisk launches with Android.
Superuser permissions can be managed from Magisk Manager app.
8) TWEAKS
- Calibrate battery: https://www.ifixit.com/Wiki/Battery_Calibration
- Set dark Mode to improve battery by 30%
Settings > Display > Dark theme.
- For better battery, remove Always on display
Settings > Display > Lock screen > Ambient display
- Activate Developer options
Go to Settings > About.
At bottom, tap 7 times on Build number. You activated Developer options.
Go to Settings > System > Advanced > Developer options.
- Change screen definition for low GPU/CPU usage: from 1440x2560 to 1080x1920
You need developer options to enable USB debugging.
Open a terminal where adb.exe from my pack is located.
Plug phone and Authorize USB debugging.
Then type:
Code:
adb shell wm size 1080x1920 && adb shell wm density 400
// Defaults 1440x2560 and 504
- Screen sensitivity is too low ?
Try to recalibrate screen sensitivity with https://play.google.com/store/apps/details?id=touchcalibration.favoritappindia&hl=en&gl=US
Enjoy,
djibe
Thanks: @Ivan_Meler, LineageOS team, TWRP team, TopJohnWu
---------------------------------------
Coming from another ROM
- Backup
- Recovery: Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy
Force Samsung Galaxy S7 restart
Hold Power + Volume down for 10-20 seconds

Thanks for the detailed instructions.
Please fix two minor typos: In the Odin instructions, the files should be hero2lte* not herolte*.
Re Magisk: 24.0, I suppose, should be used / upgraded to. (I've run into issues with 24.2 on another platform.)

steve8x8 said:
Thanks for the detailed instructions.
Please fix two minor typos: In the Odin instructions, the files should be hero2lte* not herolte*.
Re Magisk: 24.0, I suppose, should be used / upgraded to. (I've run into issues with 24.2 on another platform.)
Click to expand...
Click to collapse
Hi, you are correct and I'll fix glitch.
For Magisk, as you report bugs, I'll wait to move to 24.x. You can create an Issue here: https://github.com/topjohnwu/Magisk/issues
Thanks for sharing

I have a problemi instaled twrp format data and and instal rom after configuration rom when i rebooting to twrp data is encrypted. why ?

zulwik said:
I have a problemi instaled twrp format data and and instal rom after configuration rom when i rebooting to twrp data is encrypted. why ?
Click to expand...
Click to collapse
Hi, did you Format Data then Advanced Wipe > Format Cache, System ?
Then
Reboot to Recovery
Flash ROM
Reboot to recovery
Flash BitGapps
Reboot

I solved problem.
I installed older version TWRP with Odin and new version

hey @djibe89 & other XDA folks, thanks for these steps.
I have a SMG935W8 and currently borked on the BiTGApps step. All proceeded smoothly until there and now I'm seeing an error on TWRP and I'm not really sure how to resolve it.
It's complaining that the install config is not found and that it's an unsupported Android SDK version, which doesn't seem quite right.
Any tips would be highly appreciated

Judging from my deep dive, the current LineageOS 19.1 builds are SDK 32, and the BiTGapps builds only support up to 31... Definitely looking for tips, still.
Going to try this post's GApps

Hi, for now, stick to latest LOS 19 build: https://github.com/ivanmeler/ota_provider/releases/tag/herolte_lineage-19.0_1646935359, not 19.1

Or could you try NikGapps and tell us?

Thanks @djibe89 ! I went with NikGapps and that was a win.
It might be good to edit the top post to say 19.0 or have the NikGapps linked in it, for future readers.
Phone's working great. I appreciate it!

Bujiraso said:
Thanks @djibe89 ! I went with NikGapps and that was a win.
It might be good to edit the top post to say 19.0 or have the NikGapps linked in it, for future readers.
Phone's working great. I appreciate it!
Click to expand...
Click to collapse
Hi, I'll update it.
I hoped a newer BitGapps update would be released by now.
Enjoy, this phone is awesome

Hey again!
Been daily driving this for a bit and here's a laundry list of the issues I see, in no order at all.
I'm not sure if they're Lineage issues or artifacts of being an "unsupported" Lineage build.
1. The screen just stays on despite the power save settings (I've tried 15s, 30s, you name it) if I'm on the home screen. Trebuchet, is it?
It's like it has some keep alive function a la YouTube. It's not 100% but it seems far more than 50% of the time that I have to manually lock the device. Anyone know if I've just configured something wrong or if this is how the launcher is supposed to work?
2. Phone services will not stop demanding my location, no matter what I configure. It's every few minutes and it's creeping me out a ton. Why is it so nosey?
3. The call audio quality is still barely usable. While I *can* have intelligible business conversations when required, they suffer the quality noticeably and are terribly robotic and tinny. For personal calls, I tried to play it off once but immediately was laughed out of the call: they asked before even a "how are you" could pass if we could switch to VoIP since it was so comically bad. After some kind tips from Ivan I tried mucking with the mixer levels to no avail. They did seem a bit "low" compared to the 18.1/19.0 values, so I pumped them in a couple places (NB volume from 22 to 32, call default volume on 917 from 98 to 164 -- I have no clue what any of these mean). It might be louder now? It's not worth an A/B test to confirm what should be the expectation, but my point is that it didn't fix the robotic, tinny quality.
4. Banking app complains of the device being rooted, but it isn't. "Great." I hear the latest Zygisk might fix? I haven't tried yet.
Now, I'm still excited to be on 12L! I'm trying to buff my ability to dev on this ROM and fix up some of these issues, as I really don't think this phone needs to be replaced yet, but being stuck on stock Oreo isn't working either, so I say let's hack this thing till it's stable as stock!

Hi @Bujiraso , thanks for sharing.
Didn't use it on a daily basis
Have you tried another launcher ?
I think bank apps detect custom ROM, nothing can be done. Hope I'm wrong. Some genius of signature spoofing can pass this I believe. But I'm not.

djibe89 said:
- To tweak overclocking and more, use SmartPack-Kernel Manager
SmartPack-Kernel Manager - Apps on Google Play
The ultimate tool to manage your kernel
play.google.com
Enjoy,
djibe
Click to expand...
Click to collapse
We're sorry, the requested URL was not found on this server. New Link please.

SERGE4NT said:
We're sorry, the requested URL was not found on this server. New Link please.
Click to expand...
Click to collapse
Hi, you can try https://play.google.com/store/apps/details?id=com.performancetweaker.app or https://f-droid.org/repo/com.smartpack.kernelmanager_174.apk

hi, is it possible for the model number SM-G9350

Klein44 said:
hi, is it possible for the model number SM-G9350
Click to expand...
Click to collapse
Hi, sadly no.
9350 and 9300 have Snapdragon SOCs, not Exynos.
Only Android 8 ROMs: https://forum.xda-developers.com/f/samsung-galaxy-s7-edge-snapdragon-roms-kernels.5975/

Oh, ok. And is there any good custom rom for the SM-G9350 model?

Klein44 said:
Oh, ok. And is there any good custom rom for the SM-G9350 model?
Click to expand...
Click to collapse
Like you see here: https://forum.xda-developers.com/f/samsung-galaxy-s7-edge-snapdragon-roms-kernels.5975/
No.
This happens with Qualcomm proprietary SOCs