Develop Bugs

[30.03.2012][CF-Root 4.4] J-P/S/Q-*,JV-1KBHIOPQRSTAUV,JVU,JW4 - su+bb+2e/CWM-rfs+ext4

This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and (unprotected recovery and CWM compatibility) OR (CWM3)
If you are looking for highly optimized kernels or kernels that perform specific functions, look elsewhere. All CF-Root's are based on original Samsung kernels, they are NOT recompiled, and thus ensure maximum compatibility.
THIS IS NOT A ROM - it is only a kernel. You need to have a firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions.
MAKE SURE YOUR PHONE CAN ENTER DOWNLOAD MODE USING THE KEYCOMBINATION WHILE BOOTING BEFORE FLASHING CF-ROOT (or anything, really)
Donate
There have now been over 200.000 downloads of CF-Root for various devices, and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!)
Features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Root
- Superuser 2.3.6.1
FROYO ( CF-Root < 2.4 versions )
---- Busybox 1.15.3 or 1.17.1 (if not mentioned in the filename it is 1.15.3)
---- "2e" recovery (can flash unsigned update.zip's)
---- Integrated fix for ClockworkMod's nandroid (2.5.0.4+)
GINGERBREAD ( CF-Root >= 2.4 versions, JVK and newer )
---- Busybox v1.16.2androidminimal (from CWM)
---- Integrated CWM 3.0.0.5 / RFS
CF-Root v4.3 (JVT and newer)
--- Superuser updated to v3
--- Kernel is now in "insecure" mode (rooted ADB shell)
CF-Root v4.4 (JW4 and newer)
--- SuperSU
--- ro.secure=1, patched adbd to act as if ro.secure=0
Instructions (short)
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
Instructions (long)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Instructions (alternative if you are already running CF-Root 2.5 or newer)
- Copy the zip file to your SD card
- Stop sharing SD card with computer over USB, unplug the cable, etc
- Applications -> CWM -> Flash kernel. Select the ZIP file on your SD card.
- Done
Other kernels
Replacing CF-Root with other kernels (speedmod, voodoo, etc) and vice-versa sometimes works, sometimes it doesn't. I don't have a list.
When going from CF-Root to another kernel, root will usually stay, while 2e recovery will be lost (unless the other kernel also includes it), but there should not be issues.
CF-Root is made to be applied on a stock kernel. Going from a lagfixed kernel to CF-Root usually does not work. Unlagfix first.
Voodoo If you are running the latest Voodoo, you probably do not need CF-Root at all. Voodoo has the basic root features in place, but not the applications. Voodoo does not come with 2e recovery, but it does come with CWM, so there is no need for 2e on Voodoo. To get Superuser and Busybox on Voodoo, simply open Market and search, download, and install them ! Voila !
ClockworkMod on FROYO ( CF-Root versions < 2.4 )
CF-Root is ClockworkMod compatible, it does not include CWM itself. It uses 2e recovery, which means it can flash unsigned update.zip's, like CWM.
To use CWM, either place the update.zip in the correct location ( /sdcard ), or install it through the ROM Manager application.
When you boot into recovery, you will get the 2e recovery, even if CWM is installed. It does not boot directly into CWM (though it may do so when you boot into recovery from the ROM Manager application). Select "flash update.zip" in recovery to start CWM.
Important note: The very first time you do this on a ROM, it will usually not work. The phone will reboot normally after you flashed the update.zip. You need to reboot into recovery a second time and flash update.zip again. Then you will be launched into CWM. After this, it will work the first time you select it.
ClockworkMod on GINGERBREAD ( CF-Root versions >= 2.4, excluding JV1 on which CWM is broken )
CF-Root includes a special version of CWM3, modified to work with RFS. CWM3 by default does not support RFS, koush' versions are all based on ext4. The RFS compatibility is done with heavy scripting, the same method used on CF-Root for Galaxy Tab. For SGS CWM3 is also recompiled from source with some slight modifications to handle key input correctly.
CF-Root/CWM3 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly.
- Booting into recovery will immediately give you CWM. The standard recovery is completely gone.
- A "CWM" icon is added to your applications, which will reboot your device into recovery mode (CWM).
- ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.
- When connected to ADB in recovery, you need to use "rootsh" command to get root, instead of "su". This will not prompt you, it will just give you root. Obviously the "rootsh" command does not work when booted normally.
- Version jumped from 1.3 to 2.4 to keep the cross-device CF-Root versioning in-sync (CF-Root is also available for Galaxy Tab).
- If you wonder where your bootup/shutdown sounds have gone, CF-Root probably removed them to make sure it has enough space available.
- ( CF-Root versions < 2.6 ) Make sure to boot up your device fully at least once before flashing CF-Root. This is because the device may have some code it needs to run at first boot. CWM disables this code.
CWM Manager on GINGERBREAD ( CF-Root versions >= 2.5 )
Because of incompatibility with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011) and beta. You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options.
Features:
- Boot to CWM
- Backup firmware
- Restore backups
- Delete backups
- Install APKs ( CF-Root versions >= 2.8 )
- Flash CWM3 update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP)
Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility ! At this version of CWM Manager this does not produce errors, it just doesn't do what you expect it to
Tweak Manager on GINGERBREAD ( CF-Root versions >= 2.8 )
CF-Root includes a number of tweaks that are applied on startup. From CF-Root versions 2.8 and up a "Tweaks" application is included you can use to select which tweaks to apply.
Ext4 Manager on GINGERBREAD ( CF-Root versions >= 2.8 )
CF-Root supports ext4 mounts for the main mount points. Converting between rfs and ext4 however requires a secondary external package (which you can find in the download area a great many posts below this one), because it is all too large to fit inside the kernel. Download the APK from below, put it on your sd card, start CWM Manager, select "Install APK", find the APK and tap to install. Now you can use the "ext4" app to convert between filesystems, manually check the filesystem, etc.
Obviously you should revert back to rfs before flashing a new stock ROM. A lot of custom ROMs support ext4 as well, but it is still advised to revert to rfs before installing them.
Please note that when first using the tool to convert, you will probably notice /system is not converted. If this happens, it is because /system does not have enough free space for the extra space overhead of ext4. You will need to free up some space on /system before the conversion will succeed.
Features:
- Show current filesystem status
- Convert between rfs <=> ext4 and back
- Manual fsck
- Selects either internal or external sdcard for temporary storage, depending on which has the most space
- Automatically reverts on conversion failure
- If it tells you to PANIC !, please do so
Custom boot / init scripts on GINGERBREAD ( CF-Root versions >= 2.8 )
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use #!)
- /system/bin/customboot.sh (busybox sh)
- /system/xbin/customboot.sh (busybox sh)
- /data/local/customboot.sh (busybox sh)
Please make sure you chown / chmod the scripts correctly so they can be executed.
Custom boot animations and binaries on GINGERBREAD ( CF-Root versions >= 2.9, broken in 2.8 ! )
CF-Root also supports custom boot animations:
- /system/media/bootanimation.zip
- /data/local/bootanimation.zip
CF-Root v3.0 and up also support:
- /data/local/bootanimation.bin
Installing busybox over the included version on GINGERBREAD ( CF-Root versions >= 3.0 )
It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
Notes
- (FROYO) ADB in recovery is flaky. Sometimes it works, sometimes it doesn't. If you go into ClockworkMod it usually works, though.
- (FROYO) An older version of BusyBox is used (in some versions) because the newer versions drive me absolutely crazy with throwing color codes into the shell while it isn't supported.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. Took me a few days to get it to this state. If this works right, however, next time it will probably take me a few hours tops
Help! I don't know which file to pick! The filenames confuse me!
First thing: don't panic! It's all rather easy, and you won't easily do something bad! I am personally attentive to use the exact same version as the ROM I am running, but it's not that important.
First, go to Settings -> About phone -> Build number. It should say something like FROYO.xxJPy. It's primarily the JPy that we are interested in. Try to match that with a download link available in this (and the next few) posts. Some of the downloads dont just have JPy file name format, but are called xx_xxx_JPy.
Let me explain that. Samsung isn't always very precise in naming/marking their different (leaked) firmwares. CF-Root's are modified kernels, the filenames explain in more detail which exact firmware ROM the base kernel was taken from, for those experts who understand.
If you are not one of those people, go back to the JPy thing. The "y" in JPy is 0-9, A-Z. If they run out of numbers, they use letters. So A would be 10 (9 + 1), while Z would be 35 (9 + 26). Find the one that is closest to yours, if yours is not present, and flash that one.
The truth is, these kernels, they don't differ all that much. It's quite likely that the very latest version (at time of writing: JPY) will work perfectly fine on your ROM. There are some small differences, but using a different version is unlikely to cause serious issues. The closer the versions are, the less likely there are to be issues, BUT it is still quite possible that the latest version will work better for you than the matching version (or not!).
If you are just installing CF-Root to flash a custom ROM like Darky, make sure you have ROM Manager already installed, ClockworkMod flashed, then simply install the latest CF-Root, reboot once normally, then reboot in recovery and run the Darky update.zip. In this case it does NOT need to be a near match at all!
Download
LOOK WELL AT THE FILENAMES, MAKE SURE YOU ARE GETTING THE RIGHT VERSION !
DOWNLOADS CONTINUED IN NEXT POSTS !
CF-Root-JPH-v1.0.zip
CF-Root-JPH-v1.1.zip
CF-Root-JPK-v1.1.zip
CF-Root-JPM-v1.2-Busybox-1.15.3.zip
CF-Root-JPM-v1.2-Busybox-1.17.1.zip
CF-Root-JP6-v1.2-Busybox-1.15.3.zip
CF-Root-JP6-v1.2-Busybox-1.17.1.zip

--- more downloads ---
CF-Root-JPJPA-v1.2-Busybox-1.15.3.zip
CF-Root-JPJPA-v1.2-Busybox-1.17.1.zip
CF-Root-XX_XEU_JPO-v1.2-Busybox-1.15.3.zip
CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip
CF-Root-XW_XEE_JPA-v1.2-Busybox-1.15.3.zip
CF-Root-XW_XEE_JPA-v1.2-Busybox-1.17.1.zip
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.17.1.zip

--- more downloads ---
ROOTING JVK: See this post instead. It contains a CF-Root version specifically for JVK, you do not need to flash back the original kernel again. I also strongly advise you to read the first post of this thread.
ROOTING JV1: The JV1 version is not compatible with ANY version of ClockWorkMod (CWM).
CF-Root-XX_XEU_JPX-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_XEU_JPX-v1.3-BusyBox-1.17.1.zip
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.15.3_NO-CWM.zip
CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.17.1_NO-CWM.zip

--- more downloads ---
CF-Root-XW_OXF_JS2-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_OXF_JS2-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_XEN_JS3-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_XEN_JS3-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_XEE_JS7-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_XEE_JS7-v1.3-BusyBox-1.17.1.zip

--- more downloads ---
Note: it is NO PROBLEM to flash new JVK version over old JV1 or JVK version!
Release notes for v2.5: http://forum.xda-developers.com/showpost.php?p=12507221&postcount=1188
Release notes for v2.6: http://forum.xda-developers.com/showpost.php?p=12526079&postcount=1211
Release notes for v2.7: http://forum.xda-developers.com/showpost.php?p=12563930&postcount=1256
Fix for iptables / Droidwall for JVK: http://forum.xda-developers.com/showpost.php?p=12527335&postcount=1212
Note that v2.8 is available in the next post
CF-Root-XX_DBT_JQ3-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_DBT_JQ3-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_NEE_JS8-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_NEE_JS8-v1.3-BusyBox-1.17.1.zip
CF-Root-XX_OXA_JVK-v2.4-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.5-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.6-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.7-CWM3RFS.zip

--- more downloads ---
Note: it is NO PROBLEM to flash new JVK version over old JV1 or JVK version!
Release notes for v2.8: http://forum.xda-developers.com/showpost.php?p=12652182&postcount=1332
Release notes for v2.9: http://forum.xda-developers.com/showpost.php?p=12672516&postcount=1400
Release notes for v3.0: http://forum.xda-developers.com/showpost.php?p=12736616&postcount=1536
Release notes for v3.1: http://forum.xda-developers.com/showpost.php?p=12823970&postcount=1663
Release notes for v3.1 JVB: http://forum.xda-developers.com/showpost.php?p=12950723&postcount=1774
Release notes for v3.2 JVH: http://forum.xda-developers.com/showpost.php?p=13619653&postcount=2012
Release notes for v3.7 JVP: http://forum.xda-developers.com/showpost.php?p=14582942&postcount=2227
Apparently this CIFS patch works for JVB/JVK CF-Root: http://forum.xda-developers.com/showpost.php?p=12997697&postcount=123
More downloads after the ext4 and license posts!
CF-Root-XX_OXA_JVK-v2.8-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.9-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v3.0-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v3.1-CWM3RFS.zip
CF-Root-XW_XEE_JVB-v3.1-CWM3RFS.zip
CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.zip
CF-Root-XX_OXA_JVO-v3.2-CWM3RFS.zip
CF-Root-XX_OXA_JVP-v3.7-CWM3RFS.zip

ext4 tools
Note: don't link to this post directly, as it will move down in the thread when more CF-Root downloads become available!
The ext4 tools addon for CF-Root requires CF-Root version 2.8 or later
Release notes for v1.0: http://forum.xda-developers.com/showpost.php?p=12652182&postcount=1332
Release notes for v1.1: http://forum.xda-developers.com/showpost.php?p=12672516&postcount=1400 (non-essential update)
Release notes for v1.2: http://forum.xda-developers.com/showpost.php?p=12736616&postcount=1536 (non-essential update)
Release notes for v1.3: http://forum.xda-developers.com/showpost.php?p=13619653&postcount=2012

LICENSE for CF-Root v3.0+, ext4 tools v1.2+
As it seems a number of kernels are being based on CF-Root, and CF-Root is being included in custom ROMs, I'm going to set up a number of rules. The rules are meant to be fair to both you and me, and futher cooperation, not limit it. If you are an end-user, do not distribute kernels based on CF-Root, and do not distribute ROMs using it, you can skip this post, it is not for you. If you make kernels based on CF-Root, or your ROMs include CF-Root, read this post and follow the rules.
I don't mind you using the CF-Root hacked kernels, in fact I think it's great All parts of CF-Root are free to use/include in your own stuff, if these rules are followed.
If something doesn't work for you, feel free to PM/ask for a change. None of these rules are set in stone, maybe you have a good reason to want something different.
Usage of "CWM Manager", "Tweak Manager", and "ext4 tools" apps
- You may not modify these APKs in any way, if you include or redistribute them. The only exception to this rule is modifying the icons to match your ROM's theme.
- You may not re-post these files anywhere else (separately from CF-Root), but you may of course link to the post (not the download directly!) in the CF-Root thread containing these files. In other words, either you include them or you don't, but you can't offer them as a separate download.
- You must use the appropriate versions, released at the same time as the kernel, or any newer version released by me. For example, if you are using CF-Root v3.0, if you use/include these apps, you must use CWM Manager 1.50+, Tweak Manager 1.20+ and ext4 Manager 1.20+.
- You must test that their functionality remains 100% intact regardless of your (kernel/ROM) modifications. If the functionality is not as expected with your (kernel/ROM) modifications but you still include the apps, you must clearly state what you know is broken.
If you are just using CF-Root in your custom ROM, but do not modify the CF-Root kernel in any way (except icons)
- You must include a notice that the ROM uses CF-Root, and the version of CF-Root used.
- You should (not required but strongly encouraged) also include a link to this thread ( http://forum.xda-developers.com/showthread.php?t=788108 )
- You should (not required) include a link to donate to me, Chainfire ( http://www.jongma.org/dx.php )
- You should (not required) inform me that you are using it either by posting in the CF-Root thread or sending me a PM. (Thanks!)
- As you are not modifying CF-Root in any way (except icons), you can skip the rest of this post
Modifications to CF-Root (aside from the icons)
- Due to a lot of bickering and argueing, I'm simply no longer allowing this at all
- You can still kang a script or two left and right, I don't mind, as long as you are not basing an entire kernel on mine, or re-branding it, etc. Use common sense, you know exactly what I mean.

--- more downloads ---
JVI: Untested by me
JVQ: Untested by me
JVT: v4.3, Superuser updated to v3.0.2, and "insecure" mode
JVA: Untested by me
JVU: Untested by me
JVZ: Untested by me
CF-Root-XW_DBT_JVI-v3.7-CWM3RFS.zip
CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.zip
CF-Root-XX_OXA_JVR-v4.1-CWM3RFS.zip
CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.zip
CF-Root-XF_TSR_JVA-v4.3-CWM3RFS.zip
CF-Root-XW_TMN_JVU-v4.3-CWM3RFS.zip (OLD !! Not the 2012 version !!)
CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip
This is the December 29, 2011 / Android 2.3.6 / JVU / Value Pack ? build:
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
March 2012 / Android 2.3.6 / JW4 / Value Pack build:
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.zip

In Odin, repartition unchecked?

Awesome news saves me a lot of battery in battery out hassle - here's the kicker - I'm going back to JPC because of MODEM file issues and touchwiz lag - anychance of a JPC version ?

This is good stuff. I will test it tomorrow.

ed10000 said:
In Odin, repartition unchecked?
Click to expand...
Click to collapse
Don't touch anything except the PDA and START buttons, as per the instructions.
DangerMUK said:
Awesome news saves me a lot of battery in battery out hassle - here's the kicker - I'm going back to JPC because of MODEM file issues and touchwiz lag - anychance of a JPC version ?
Click to expand...
Click to collapse
Making a JPC version requires testing and some trial and error... not something I'm looking forward to be doing, as JPH is newer.

Thank you so much.
Can I flashed this if I have lagfix ?

poowe893 said:
Thank you so much.
Can I flashed this if I have lagfix ?
Click to expand...
Click to collapse
It should not be a problem. I flashed it myself over an active installation of CF-LagFix. Cannot guarantee it will be without issues, but I do not expect it to be a problem.

Flashed like a charm for me. But on restart, I got totally wierd settings, frequent FCs etc, those were very anxious 10 minutes, the I pulled the battery, reinserted, restarted the phone, & everything is normal. Thanks.

Hi there. Thanks for this release. I already have a JPH ROM flashed. How do I reflash this one, meaning, do I need to erase/wipe cache or format my SD card? Or just simple over writing will work?
Thanks so much.

ragin said:
Flashed like a charm for me. But on restart, I got totally wierd settings, frequent FCs etc, those were very anxious 10 minutes, the I pulled the battery, reinserted, restarted the phone, & everything is normal. Thanks.
Click to expand...
Click to collapse
I had this myself in one of my tests. Not completely sure what causes it but I suspect it is because in the background SU is being installed/upgraded. Waiting a few minutes and rebooting solved the issue for me as well. As it only occurred once for me I did not mention it, but I have now updated the first post with this info.
rajuki said:
Hi there. Thanks for this release. I already have a JPH ROM flashed. How do I reflash this one, meaning, do I need to erase/wipe cache or format my SD card? Or just simple over writing will work?
Thanks so much.
Click to expand...
Click to collapse
Yes, you already need the JPH firmware installed. You do NOT need to wipe cache, data, SD card, etc. Just follow the instructions - this patch only overwrites a small partion of the ROM.

Works for me..great it's fast and easy. Good Job

Great job, I'll test it asap.
Just one question for you: did you symlink available busybox commands or just put in the BB executable?

[CWM][Root]SuperSU 0.97

I didn't see this posted so I thought I would upload it for those that like to root the old fashioned way
First off thanks to Chainfire for this great app.
SuperSU is quickly becoming the root option of choice. I have been using it for a few weeks and haven't had any problems with it plus I enjoy the extra features and neat interface.
This zip will remove SuperUser and install SuperSU. Of course if you are already rooted you can just download it from the market. This is to be used if you are in the situation where you need to root from recovery.
If you have SuperUser installed on the data partition you will want to remove it from the application menu. For some reason when I had it delete from data it would leave a phantom icon even after clearing cache and dalvik. Not sure why but it is best to just uninstall it.
If you have SuperUser in system/app but it isn't named Superuser.apk, SuperUser.apk or com.noshufou.android.su-1.apk you will want to manually remove it.
For more information on SuperSU visit https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
This wipes cache and dalvik for you.
Download: http://www.androidfilehost.com/?fid=9390169635556426038

Updated to 0.97.
What's in this version:
- Fixed issue with modified AOSP su binary
- Fixed wrong translation crashing app on toast
- Fixed possible exploit (preventive)
- Modified system and shell user - no longer granted root by default
- Added "ADB shell" display
- Added warning to selecting full content logging
- Added method for apps to disable (by default only) full content logging if known to be problematic
- Updated languages

[ROM][ICS] sediROM - current inside - stable - smooth - rooted or not-rooted

|
|
| sediROM - or why I created a new ROM based on good old (ancient) ICS
|
|
| Read the background and the whole story and all the discussions about sediROM here:
| http://forum.xda-developers.com/showthread.php?t=2789119
|
|____________________________________________________________________________________________
Some first words:
A lot has changed since I forked LiteROM v0.9 in May 2014 and therefore started sediROM. sediROM has grown up in the meanwhile to a standalone ROM with some mods coming from LiteROM but in comparison to the current state of sediROM they are not many anymore.
LiteROM was a very good starting point for me to dive into ROM development and doing my first steps here so many thanks going to thegreatergood, of course.
As a result of that learning process I will change the base of sediROM in one of the next major releases (see Roadmap) to remove the rest of LiteROM stuff which I do not need/use anymore.
Summary:
Debloated, Partially De-odexed, Zip-aligned, SuperSU, Busybox, Init.d Support, Tons of Memory and Build.prop Tweaks, Sysctl Tweaks, 14 toggles Mod, Power Menu, Tethering fix and more...
Aroma Install
Customizable Apps, Tweaks, Mods
BLN Support
Selectable Kernel, Modem, Bootanimation
No Samsung backdoor inside!
Full Feature List:
Explanation: Default values in "Easy Installation" mode are marked in the following lists in RED
Installer:
sediROM flashing will be done by AROMA installer which gives you 2 selectable modes when starting:
Easy Installation:
This will do all the hard stuff for you and installs besides the ROM itself well tested preselected apps & enhancements.
You need to choose this mode when you install sediROM the first time or want to install an upgraded version of sediROM.
Default values in "Easy Installation" mode are marked in the following lists in RED
.
Modify Installation:
This mode needs an existing sediROM installation first. So you can choose the Easy Installation mode first and after that has finished simply choose this mode to modify things like the Kernel, Modem whatever. This mode can be choosen whenever you want - e.g. you can test a Kernel X and after a while you want to test another one - no problem - simply restart the Installer and choose the Modify Installation mode!
Available Kernels:
sediKERNEL v1.0 (Kernel 3.1.10) (see changelog for details)
CM11 based (Kernel 3.1.10)
JB 4.2 LiteKernel release-20130222 (see changelog for details)
JB 4.2 LiteKernel release-20130221 (see changelog for details)
LiteKernel v1.2.2 GPU not OverClocked and with UnderVoltage
LiteKernel v1.2.2 GPU OverClocked and with UnderVoltage
LiteKernel v1.2.2 Original LiteRom v0.9 Kernel.Tweaked - LiteKernel v1.2.2 overclocked with UnderVoltage
LiteKernel_l2hsicpatched-bubor-r20150506 with L2_HSIC patch based on code of 2014-04
Stock ICS Kernel UCLJ3 (Kernel 3.1.10)
Enhanced UCLJ3 stock Kernel
enhancements:
- init.d support (this enables sediROM bluetooth fix for this kernel)
- added custom boot animation support
Stock ICS Kernel UCLH2 (Kernel 3.1.10)
Available Modems:
UCLJ3
UCKL1
UCLH2
UCKI3
RUXKJ5
Some meaningful Apps & Tools:
ATOM launcher
Several other launchers available in "modify" mode (Apex, Nova, ADW, Stock)
Ghostery, Quickpic, ES File Explorer, AndroidTerm, Vodoo Sound Control
Camera apps: Open Camera, HD Camera Ultra, Stock, ICS, JB)
Kii Keyboard, Samsung Keyboard (default enabled), Go Keyboard, Stock Keyboard
"Under the hood" - Integrated Features:
The possibility to execute shutdown scripts (and for boot-up but every Kernel in sediROM supports that out-of-the-box)
The possibility to choose a non-rooted mode! If you're running Apps which detects root (and hiding is not possible) or if you want to be most secure than this mode is for you. Enterprise users may want this to be complain with their security policy e.g.
(Major) Bugfixes (related to ICS and/or LiteRom):
That was driving me nuts and costs WEEKS to fix -> BT fix (better a fully working workaround) for loosing paired devices after a reboot!!!
Lags/waits when pressing the power button to switch the display on
Within Aroma installer: Many many fixes and enhancements when modifiying or/and installing the ROM to get the most out of it
There are many other fixes which can be found in the full changelog
Device encryption was not working in LiteROM. That was fixed in sediROM since v1.1.
Known issues:
Check the open bug reports for a complete list: Click
HOW-TO flash & Download:
Disclaimer:
sediROM is not fully finished nor bugfree (yet).
[*]But is has less bugs and more features then it's fork "LiteROM" and fixes bugs within stock ICS as well.
[*]I use it continuesly since 1th of May 2014 and sporadically developing / enhancing sediROM since then.
Installing sediROM may result in several explosions in your garden (or in that of your neighbour) .. you have been warned!
DO NEVER USE OPTIONS WHICH ARE MARKED AS "TESTING" IN THE INSTALLER!
I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE (nor the things that happens to your house and/or car!)
Requirements:
Do a nandroid backup and ensure you have an EFS backup, too !! EFS: (http://forum.xda-developers.com/showthread.php?t=2019540)
COPY THAT BACKUP TO AN EXTERNAL DEVICE TOO !!!! --> SAVED MY DAY TODAY BECAUSE OF MD5 MISMATCHES THAT CAN HAPPEN.. (I cannot recommend that "fixes" cursing around to simply workaround MD5 sum checking! If the md5sum mismatch you should NOT restore IMO. That may simply not work or can result in bad behaviour etc minutes later or some days later)
Check your backup! (e.g. md5sum -c nandroid.md5) in BOTH places (on the Glide AND on your external ressource)
Install TWRP(!) or migrate to it! DO NOT USE CWM - flashing may fail with CWM (and is besides that not recommended).
DL- Link CWM: CWM v6 (click) (several users reported CWM will not work! use TWRP!)
DL- Link TWRP: twrp v2.7.1 (click)
You should have a windows box running Odin + TWRP near - just for the case.
Flashing Guide:
I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE (nor the things that happens to your house and/or car!)
Copy BOTH the sediROM zip AND the sediROM md5 file to your Glide!!
Boot into Recovery mode (Poweroff the device then Power on while holding Volume Down)
Ensure that you use TWRP and that the MD5 sum file is in the same directory as the sediROM zip! Only then TWRP will automatically check the MD5 !
Flash the latest sediROM zip file
Choose "Easy Installation" mode
Answer the few questions and wait until the flashing finishes
When finished - reboot and wait until it has fully started up
The Android setup wizard should come up (if not -> flash again
Go through the wizard and reboot once again afterwards
Enjoy
Please read the FAQ (click)!
Please file a bug if you encounter problems: File a bug (click here)
Download:See above in the Download Menu (click here to open it)http://forum.xda-developers.com/devdb/project/?id=4942#downloadshttp://forum.xda-developers.com/devdb/project/?id=4942#downloads
Mirror:
Use this ONLY when the above xda DL does not work!! Mirror Downloads may be outdated or not available all the time! Mirror-Link <-- DOWN. Write me a PM if the xda download does not work and I will upload it for you
Take also a look on:
Changelog
FAQ
Roadmap
Trouble
File a bug
Request a feature
Best regards
xdajog
Special THANKS (please give them a Thanks-Click ! That costs you nothing but 2 seconds (for each)!!)
thegreatergood for LiteROM v0.9 and LiteKernel builds --> Give a "Thanks" here
bartito for Shutdown-Script option (and therefore the possibility to fix the BT issues!!) --> Give a "Thanks" here
PS: Happy for every single click on my "thanks" button (you are free to do that on the changelog, roadmap and faq post again... )
And as an absolutely premiere I want to say thank you to maddbomber83 for the donation.
You're the first one (until now the only one ) who say thx this way. Highly appreciated and motivating.
Sources:
sediROM --> https://github.com/xdajog/android_i927_sediROM
sediKERNEL --> https://github.com/xdajog/kernel_samsung_i927
.
XDA:DevDB Information
sediROM, ROM for the Samsung Captivate Glide
Contributors
xdajog, bubor (for all his work! highly appreciated!), maddbomber83, organic2 (for heavy testing!)
Source Code: https://github.com/xdajog/android_i927_sediROM
ROM OS Version: 4.0.x Ice Cream Sandwich
ROM Kernel: Linux 3.1.x
ROM Firmware Required: sediTWRP or TWRP >= v2.7
Based On: STOCK, LiteROM
Version Information
Status: Stable
Current Stable Version: v2.1 (2.1.2)
Stable Release Date: 2016-01-04
Current Beta Version: ---
Created 2014-07-11
Last Updated 2016-07-26

FAQ
Frequently Asked Questions (FAQ)
Why another ROM and why build on ICS?
Please read the full story here: http://forum.xda-developers.com/showthread.php?t=2789119
[*]Do you need to network unlock the Glide?
Follow the excellent guide here: >Click here<
And also take a look on my additions to it here: >Click here<
[*]When version [FILL-IN-WHATEVER-YOU-LIKE] will be released?
Please keep in mind that this project is not a full time job so questions about a release date is something I will / can not reply to.
This is not because I don't like you but it is because I cannot promise anything. RL is my priority and this can not be controlled (fully) as you may know
[*]Is device encryption supported?
Yes, device encryption is supported since sediROM v1.1
You may want to check out a working TWRP version to be able to still do nandroid backups here sediTWRP with decrpytion support (click)
Hint: Device Encryption is fully supported when choosing the easy installation mode while installing.
That means if you choose the modify mode afterwards be careful what to choose within the TWEAK section (kernel optimization/swap internal to external sdcard/...). Those are not all tested yet so do a backup before choosing them. ALSO for /sdcard! because that gets encypted to.
If you choose the easy installation method and change only apps/kernel/modem etc you will be safe though.
[*]Can I upgrade from a previous version of sediROM?
basic* --> will be explained some lines later (pls look for: "What does "tested (basic)" means?" in this FAQ)
v2.0 ----> v2.1
Yes: tested (basic + full)
basic --> pls look for: "What does "tested (basic)" means?" in this FAQ
full -----> tested on my production device, too
v1.7 ----> v2.0
Yes: tested (basic + full)
basic --> pls look for: "What does "tested (basic)" means?" in this FAQ
full -----> tested on my production device, too
v1.6 ----> v1.7
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ)
v1.5 ----> v1.6
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ)
v1.1 ----> v1.6 (this is the last upgrade test for v1.1. I will not test upgrading to higher releases from v1.1!)
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ)
v1.1 ----> v1.5
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ)
The same pre-requirements necessary as in v1.0 ---> v1.1 !
v1.0 ----> v1.1 (this is the last upgrade test for v1.0. I will not test upgrading to higher releases from v1.0!)
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ).
Manual pre-requirements necessary! To upgrade from v1.0 to v1.1 you need to wipe /system partition manually before you start the upgrade because there is a bug in v1.1 and v1.5 preventing from doing the partial wipe which normally will do that for you.
These are the steps:
Within TWRP choose the wipe menu and then "advanced". Afterwards select only "system" !
Go on and afterwards start the sediROM installer again and choose "partial wipe". Because you have wiped /system manually the installation should run fine afterwards.
This way you will NOT wipe any configs or apps or something as long as you leave /sdcard and /data untouched in step 1.
That workaround should work even when you already tried the partial wipe in "Easy Installation" mode.
If you use L2SD here a special note: from @maddbomber83:
maddbomber83 said:
Just as a note; upgrading an install that has a lot of symlinks (such as L2SD) does not appear to be working properly. If your install includes any of these then as the Developer has stated, MAKE SURE TO DO A NANDROID BACKUP!
On mine at least, the phone had a lot of FC errors focused around the PHONE APK. If you did do a data wipe and can get back into your phone but are missing your linked apps then:
Q. I upgraded/changed my ROM and I can not see my linked apps, their files are on the 2nd partition but the system can not see the apps. How can I make them available, do I need to reinstall and relink them again?
No, if you didn't wipe data when updating ROM the only thing you need to do is to run "Recreate mount scripts" from "menu -> more" within Link2SD and do a normal (not quick) reboot.
If you wiped data, after executing "Recreate mount scripts" and rebooting, run "Relink all application files" from "menu -> more" and then reboot. All of your linked apps should be available again after reboot.
If you also wiped dalvik-cache, in addition to the above step run "Link dalvik-cache files".
Click to expand...
Click to collapse
What does "tested (basic)" means?
When I test upgrades I do that very basic. As the system is still the same (ICS 4.0.4) and normally no android related things changed I strongly believe that doing upgrades shouldn't harm anything. Even all the apps should work as long as you don't played around with system apps (In Titanium Backup and other tools you can make an app a system app which means it will also be copied to the /system area which will be overwritten due to the upgrade. If you have converted a user app to a system app it will be lost then). Normally you wouldn't do such a conversion but as it is possible I need to add that hint here..
When I state an upgrade path as "tested (basic)" it means that it SHOULD work but as always no guarantee
My Test setup is always as follows:
a custom wallpaper (Home + Lock Screen)
added some icons to the launcher
set a lock screen password
system settings for screen timeout and screen off
WiFi settings for my WLAN
Installed Titanium Backup app
acquiring root permission (ES File Explorer and after "adb shell")
Upgrade guide:
do a nandroid backup! <-- sigh this is VERY important do not skip that step!!
copy that backup to your pc just to be sure!
choose to install sediROM
choose easy installation
then (the upgrade magic): choose "partial wipe" !
complete the rest of the installation and you're done.
[*]Screen wakeup delay?
I have a screen wakeup delay when using sediROM! AND I use sediROM < v2.0 (e.g. v1.7).
The problem here is the default used kernel in sediROM before v2.0.
All smaller versions uses "Litekernel" as the default kernel which is the root cause for this problem.
Before v1.7 there is no really option for fixing this other than installing another kernel manually.
In v1.7 you are able to switch to the CM11 kernel in the modify mode within the sediROM installer but the shipped version has issues with MTP (connecting storage to PC).
So that is also not a workaround for everyone unfortunately but if you do not use MTP (USB mass storage works btw) this may an option for you.
Well so what is the solution?
Install sediROM v2.0 and use the latest sediKERNEL (default in easy installation mode) or the CM11 kernel (including the MTP fix) provided by bubor or the modified STOCK UCLJ3 kernel by xdajog (me).
All of them have no screen wakeup delay issues and working fine.
All are available in v2.0 and you can switch between them in the modify mode as always (sediKERNEL is default since v2.0)
[*]What is that "Bluetooth HSP fix"?
Bluetooth HSP (HeadSet Profiles) is buggy in ICS 4.0.4. All paired devices gets lost after a reboot. In sediROM there is a fix for this implemented. To be honest that fix was the reason why I started sediROM..!
It is implemented in two steps:
a shutdown script which backups the bluetooth pairings and settings
an init.d script on boot which restores those pairings
The problem that pairings go to hell after a reboot is kind of special. The first thought was to simply backup the correct folders and restore them again when boot up. That alone won't work - the pairings will not shown up when enabling BT afterwards because they are deleted right when BT gets enabled. I tried to find out why but without success. Then I found a way by simply protecting the BT config file. That said when BT starts up it can not delete it anymore and stops trying that and that means the restored pairings will be read and shown.. A little bit crazy I know but it works very great (in my case).
Further Readings (they may related to this issue):
Kenneth Thorman's discoveries
Google Issue 34161
Some suggestions at stackoverflow (5885438)[/MENTION]
Another one from StackOverflow: 5102549
There are different caveats depending on which sediROM version you are using with the current implementation:
sediROM >= v1.7
Since v1.7 the BT fix is very stable and the caveats we have are absolutely minor:
Bluetooth will from now on always beeing OFF after a restart. That is wanted and nothing really bad and is a protection that things goes right.
After sediROM is up'n'running you can switch on BT and/or off again - only when rebooting BT will be always off again.
The system needs to be fully started in order to get BT working. As this is only a couple of seconds (about 10-20 sec) and starts while in boot process this has no impact for the user.
sediROM < v1.7
If you change the name in BT settings that will not be restored atm so it is sticked at "SGH-I927"
Under some circumstances the BT fix hasn't worked. check out the details at the bottom to find out the reason.
sediROM = v1.5 OR sediROM < v1.5
If you want to delete a pairing it was restored in sediROM <v1.5 when you reboot - to completely delete a pairing you need to:
in sediROM = v1.5:
You don't need to do anything. If you delete a pairing or add a pairing both will be saved and no need to do anything else then reboot.
In case you have problems you can delete /sdcard/.sediROM/btfix/00_btbackup.tar and/or check the logs in /sdcard/.sediROM/btfix/ . But that is normally not needed anymore.
in sediROM < v1.5:
delete "/data/local/tmp/00_btbackup.tar" and then reboot
Detailed background information
and the reason why before v1.7 it may haven't worked for everyone:
"rm" will delete the directory and I'm not able to find out which file will be deleted first and therefore I can't prevent the deletion of the pairings as I do before!
Background:
/system/bin/bluetoothd will remove the whole directory /data/misc/bluetoothd (well that is known and at the end the reason why the pairings gets lost in ICS)
I "fixed" that by making the config file immutable so Android is not able to delete the directory anymore which results in the fact that the pairings will stay!
Unfortunately it is not such easy as thought. On my second device I saw that my pairings still get lost..
Well ... As mentioned bluetoothd wants to remove and it uses "rm -r" for this. Exactly it will call "rm -r /data/misc/bluetoothd/".
.. and "rm" uses the C function "readdir()" when it parses the directory and readdir() will give you the result randomly (it depends on several not predectivable things).
There is no chance to know the exact order and even when it would be the case then mine would be different from yours!
... but that's not all. Some docs said that subdirs will be deleted first when using "rm -r" but in fact that is NOT true! If it would be true then the solution would be very easy.
The question stays why it happens on my productive phone and the previous fix still working fine on my DEV device. I believe that it is because I restored a previous made BT backup after I installed sediROM v1.6.
The command "tar" uses the same behaviour as readdir() so it is also randomly when it comes to restoring a backup. That would explain it maybe but I'm not totally sure.
You can test that readdir() behaviour very easily. If you execute a "find . -type f -print" you will see what readdir() see.. The result is obviously unsorted.
Execute it again and the result stays the same but that changes when files are deleted or other things happens to the filesystem!
In my case the problem occured after enabling encryption because that changes also things related to readdir() obviously.
Further readings:
- http://linux.die.net/man/3/readdir
- http://utcc.utoronto.ca/~cks/space/b...x/ReaddirOrder
- http://stackoverflow.com/questions/8...antee-an-order
The way of finding a solution:
- I tried to find out the root cause again (means bluez Java code).
- I tried to port the latest v4 of the bluez stack which contains a lot of fixes.
- I tried to re-compile bluetoothd in order to remove the whole folder deletion.
- I tried to save/restore the settings.db sqlite3 database (alone and together with the BT files)
- I tried some other stupid things.
The solution:
At the end I found a working solution (again). Instead of protecting a single file only which readdir() accesses randomly I switched over to protect the whole directory.
This way the order within the directory doesn't matter anymore
That alone wasn't enough. I needed to completely restructure the way of handling that fix.
That means:
- the bluetooth main.conf was changed to set InitiallyPowered=false !
- I stop all bluetooth related processes when booting
- I restore the previous BT settings and pairings
- I make the BT dir(!) immutable
- Then I give rfkill0/state the info (add a "1") that bluetooth is able to start
- Then I start all BT processes in correct order
- Then I remove the immutable bit from the BT dir
(Minimal) Caveats:
- Bluetooth will from now on always beeing OFF after a restart. That is wanted and nothing really bad and is a protection that things goes right.
After sediROM is up'n'running you can switch on BT and/or off again - only when rebooting BT will be always off again.
- The system needs to be fully started in order to get BT working. As this is only a couple of seconds (about 10-20 sec) and starts while in boot process this has no impact for the user.
[*]What is that "adb" thing??
adb stands for: Android Debug Bridge and can help a lot when it comes to work with your device. It is not for developers only but they use it a lot of course.
But a normal user can use this to exchange files without the need of mounting, backing up the device, reboot the device and use it as a very comfortable way of having a terminal emulator.
Normally adb itself is not available as a standalone application - it comes with the Android SDK which is very big and heavy if you want to use adb and/or fastboot (another great tool) only.
But we live in a great world with many people wanting to make things easy so here you go when you want/need only adb and fastboot:
download & install adb at lifehacker
(Direct link for Windows users: Got to easy ADB install thread)
[*]What is a "nandroid" backup?
nandroid means essentially: "a full image of all your partitions" so it is a full snapshot of your ROM including all your apps and contents.
The name NANDroid is a portmanteau of "NAND" (as in Flash memory - NAND flash) and "Android." (Source)
[*]How to create a "nandroid" backup?
(See above for the meaning of "nandroid backup")
You have several options on how to do that.
The normal and absolutely recommended way is to do that "offline" (from within recovery mode) but you can also do it "online" (while Android is running).
.
Offline nandroid backup by using TWRP recovery: Guide
If you have no custom recovery installed read on.
.
Online nandroid backup:
by using an app:
There is 1 (known to me) "online" nandroid backup tool available which will backup from within your running Android: PlayStore.
I tested it and still using it since a while and I really like it but I would not fully resist on it.
I had no problems backing up but sometimes an app is lost when restoring. This may have been fixed but well it is like imaging a running Windows or Linux system:
Do not do it online if you can - it may/will work but there could be problems/inconsistencies later!!
If you never made a nandroid before doing it online will not harm anything and should be your first start. So install the Online Nandroid backup tool and begin.
Check out this guide for some hints: Guide
(If you like the Android app do not hesitate to buy the unlock key to support the developer!)
by using commandline tools:
First of all you need "adb" installed (check out the FAQ #8 above).
Then you need someone who is telling you the device partition table and you need a big sized SD card to hold the images.
The reason is that you will use a special command named "dd" which images the whole partition (not the content only!).
dd is a VERY dangerous tool because if you use it wrong your device may get bricked so it is essential that you are using the
correct command and check that twice!
Check out the next FAQ on how to do this for the i927.
[*]How to create a "nandroid" backup for the i927/cappy - WITHOUT having a custom recovery?
The whole process will take a big amount of time but it is worth to follow each step including the md5sum checks at the end.
Please read the previous FAQ first because there you will find more information about background and other options you may have.
Ensure you have a SD card inserted which is big enough and having enough free space available (4GB at least! I recommend at least 8 GB but this depends on the size of your current data partition. A completely stock ROM with nothing installed and unused will need 3 GB space).
.
Install "adb" on your pc (check out the FAQ #8 above).
root your device (check out FAQ #12)
connect with adb to your (running) i927:
adb shell
(you should see a prompt)
su
(you need to grant permission if you haven't yet)
Then backup your current ROM and data:
dd if=/dev/block/mmcblk0p2 of=/storage/external_SD/system.2015-07-20.img
dd if=/dev/block/mmcblk0p9 of=/storage/external_SD/boot.2015-07-20.img
dd if=/dev/block/mmcblk0p6 of=/storage/external_SD/userdata.2015-07-20.img
dd if=/dev/block/mmcblk0p8 of=/storage/external_SD/recovery.2015-07-20.img
# If you never backed up your EFS you really should do that once:
dd if=/dev/block/mmcblk0p1 of=/storage/external_SD/efs.img
Click to expand...
Click to collapse
Just to be sure you can do an online backup now, too ( Guide ) Online Nandroid backup App
.
copy the backup(s) to your device (connect USB cable - open your external storage and drag&drop) <--- DO NOT SKIP THIS STEP!!!! It is absolutely essential!
Check your copy on your device:
md5sum /storage/external_SD/system.2015-07-20.img
md5sum /storage/external_SD/boot.2015-07-20.img
md5sum /storage/external_SD/userdata.2015-07-20.img
md5sum /storage/external_SD/recovery.2015-07-20.img
md5sum /storage/external_SD/modemst1.img
md5sum /storage/external_SD/modemst2.img
Click to expand...
Click to collapse
Download a md5sum checker like this one Windows MD5 and load each file you copied to it (on Linux the "md5sum" command can be used of course).
compare the md5sums from the above output and ensure that they are all matching.
[*]How to root the i927/cappy?
There are several guides on this here are 2:
- First or
- Second
[*]"efs" backup and/or restore?
There are several guides on this but here is mine.
Backup efs:
1) open a terminal
2) type in su --> now you may need to give root permissions
3) type in tar zcvf /sdcard/efs-backup.tar.gz /efs
4) type in dd if=/dev/block/mmcblk0p1 of=/sdcard/efs-dd.img
5) connect your device to a PC and copy both the efs-backup.tar.gz and efs-dd.img to your PC
6) now you have a full backup of your efs and therefore your phone unlock state
Step 2 is essential you need root for this in order to work.
Normally you can see a change from a dollar $ sign to a hash # one after root has been achieved like this:
xxxxxx:/ $ > su (answering the request for root permissions with yes)
xxxxxx:/ # >
Restore previously saved efs:
1) open a terminal
2) type in su --> now you may need to give root permissions
3) connect your device to a PC and copy your dd-image backup "efs-dd.img" to /sdcard of your device
optional: do the same for the tar archive "efs-backup.tar.gz". This is just needed for the case the dd image is corrupt.
4) type in the terminal dd if=/sdcard/efs-dd.img of=/dev/block/mmcblk0p1
optional: if that step fails ensure you have mounted /efs (ls -la /efs should show you several files) and execute (press Enter after each line):
su
cd /
tar xvzf /sdcard/efs-backup.tar.gz
5) reboot your device
6) now your efs is fully restored and therefore your phone unlock state, too
Step 2 is essential you need root for this in order to work.
Normally you can see a change from a dollar $ sign to a hash # one after root has been achieved like this:
xxxxxx:/ $ > su (answering the request for root permissions with yes)
xxxxxx:/ # >
.

Changelog
Changelog of sediROM
v2.1.0 - v2.1.2 (Release date: 2016-01-04)
--------------------------------------------------
Bugfix Release
Github detailed changelog (compared with the previous version):
https://github.com/xdajog/android_i927_sediROM/compare/v2.0...v2.1
Github tag for this version:
https://github.com/xdajog/android_i927_sediROM/tree/v2.1
Enhancements
introducing sediROM testsuite: /system/xbin/sediROM_testsuite.sh
execute it like this to test if your sediROM version is fully working:
adb push sediROM_testsuite.sh /sdcard/ && adb shell "su -c sh /sdcard/sediROM_testsuite.sh"
Fixes
issue #25 (https://github.com/xdajog/android_i927_sediROM/issues/25)
YES ALL THE FOLLOWING IS > 1 < SINGLE RELEASE
v2.0.68 -v2.0.1 (Release date: 2015-12-29)
--------------------------------------------------
Major Release
Github detailed changelog (compared with the previous version):
https://github.com/xdajog/android_i927_sediROM/compare/v1.7...v2.0
Github tag for this version:
https://github.com/xdajog/android_i927_sediROM/tree/v2.0
Enhancements
first sediROM app (sediROM_boot.apk) inside.. the app itself is extremely simple: a text and a button thats all. When
sediROM boots the first time a new added init script will detect if this is the first boot and if this is the case it will open
the sediROM_boot app. Read & follow carefully the hints there!
you to reboot. May be annoying but due to douzends of changes in v2.0 it is really necessary to point to a clean reboot.
All scripts related to run sediROM on github now !!!! Starting from v1.7.
Introduced the first version of sediKERNEL (v1.0) a customized kernel optimized for STOCK ICS so as for sediROM.
sediKERNEL is based on CM11 kernel made by bubor (so l2_hsic patched, no wakeup delays, OC etc) enhanced by:
- adding MTP support for STOCK ICS!
- less battery drain
default kernel = sediKERNEL v1.0
Upgraded AROMA from v2.56 to v2.70-RC2 (means compiling 2.70rc2 from the sources!)
Go DIRECTLY from the installer to the MODIFY mode!
That means when you choosen the easy installation mode and everything went fine you will get the
offer to open the modify mode instead of rebooting
No adb debugging from initial ram disk (security fix)
No adb debugging as default (security fix)
Integrated LiteKernel_l2hsicpatched-bubor-r20150506 with L2_HSIC patch included (hopefully fix battery drain)
The kernel is based on code of 2014-04 afaik also maded by bubor
Integrated enhanced UCLJ3 stock Kernel (option in modify mode)
enhancements:
- init.d support (this enables sediROM bluetooth fix for this kernel)
- added custom boot animation support
Migrated and integrated JB 4.2 LiteKernel release-20130221 to sediROM (option in modify mode) which comes with the following changelog:
(all changes between v1.2.2 to 20130221)
- Interactive set as default governor ... Wheatley lags on AOSP
- Added FM Radio Driver
- Fixed Mic for AOSP
- Fixed/Added 1.4ghz frequency
- Fixed/Added Smartassv2
- Removed USB Whitlists
- Recoded BLN myself so that there is no need for an app... has in kernel blinking ...
- Tons of Cleanup
- XZ Kernel Compression
- Removed Wake Lag
- Fixed and increased Charging Current
- Tweaked Ondemand for better performance
- New Storage Setup
Migrated and integrated JB 4.2 LiteKernel release-20130222 (option in modify mode) which comes with the following changelog.
HINT: MTP does not work with this kernel. I will not fix that! If you need MTP use release-20130221 or sediKERNEL!
(all changes between r20130221 to r20130222)
- Entropy Tweaks inspired by lambgx02s Seeder (for silky smoothness)
- Memory Managment Tweaks
- Added Dynamic vsync
- Zipaligning and Fix permissions at boot (zeppelinrox script)
- Tons of Kernel Tweaks for Battery life and Performance...
- IO tweaks...
- Auto EFS Backup...
- New Experimental WIFI Management battery saving feature: If at screen off, WIFI is inactive and or using very little traffic, it gets turned off
and then on again once you wake device, if battery level is below 50% it will no longer turn wifi on again, if you disable WIFI it will be left alone...
- Decreased Vibration Intensity (when you boot up device you will feel a slight vibration)...
- New Experimental CPU Management feature: Frequency get changed according to battery level....
- No more laggy lock screen drawing ...
- Instant wake to lock screen
- Removed Increase Charging Current mod till more testing can be done
- Improvements for better battery life
- Stability
- Option to Disable WIFI and CPU Control
- Clear Memory after boot
- Massive Improvements to: Performance, Battery Life
- Fixed Battery leak with CPU + WIFI manager
- Memory Management Improvements
- SD card Speed Tweaks
- Reduced Wake Lag
- Reduced Stuttering when playing music on screen off
- CPU-Manager is now enabled by default ... it boosts wake speed manages sleep speed and reduces max speed as your battery diminishes ... the profiles are fully modifiable and all with no battery drain ...
- MTP is now the default pc connection ... if you want mass storage change /data/LiteKernel/MTP to "0"
- Memory management improved .... should also help for battery life
- frequency with Interactive governor will now stay a little lower ... should help with screen on battery life ....
crond (provided by busybox) activated to automatize things like in Linux
init script 00sediROM will prepare the settings, paths etc for crond to start
and init script 99sediROM will start the crond
Open Camera will be the only camera app installed by default. HD Ultra camera stays an option in modify mode.
added this changelog to AROMA installer screen
added modify option after easy install in README of the installer zip
updated sqlite3 binary to v3.8.7.4 (THANKS to user tech128 details: http://forum.xda-developers.com/showpost.php?p=52174054)
Removed all my own copyright hints and licensed all sediROM scripts under CC BY-SA 4.0 (http://creativecommons.org/licenses/by-sa/4.0) license! Freedom for everyone ;o)
New script header including new version concept of all sediROM scripts
Updated SuperSU app and binaries to v2.46
Installation of SuperSU is now completely based on the original installer to avoid any problems while installing
Added a new minimalistic terminal app AndroidTerm (https://play.google.com/store/apps/details?id=jackpal.androidterm) which replaces connectbot as default installed terminal app.
Connectbot will not being installed by default anymore but you can still install it in modify mode.
Connectbot has many advantages but 1) updating within a ROM is harder then with AndroidTerm and 2) I want to keep it minimal so no ssh, telnet. only a local console.
BACKUP Connectbot before upgrading when you still want to use it.
If you want to continue using CB you can upgrade and at the end of the installer select "Start sediROM modify mode"
and install Connectbot directly after installation (Screen "Main Features" - Section "Tools"). Nevertheless you still need to restore your settings as they are lost.
Added Ghostery (v1.2.1) - a very tiny (around 2 MB installer files), fast, stable and anonymous browser (https://www.ghostery.com/en/how-it-works). Will be installed by default!
Removed Google Chrome to save disk space (the installer files are 64 MB!)
Chrome is VERY slow on our phone in comparison to other browsers (try to open several tabs & browsing) and last but not least updating it within sediROM is harder then with other browsers.
BACKUP Google Chrome before upgrading when you do not want to loose settings.
Started to use a common function file for the init scripts in sediROM (/system/etc/sediROM/init.func)
Several new boot logs are written to /cache/*.debug which makes debugging easier (commit b053e738 and commit e3fe9332).
After sediROM is booted fully up everything will be moved to: /preload/.sediROM/boot/.
Added commandline aliases/shortcuts for remounting any mountpoint as read-write (remountrw) or read-only (remountro) - handled by commit 41fcc3c6.
Added automatic /efs backup !!!
- The backup is a full image dump made by dd
- backup will be saved to /sdcard/efs_[current-date].dd
("[current-date]" will be replaced by the current date+ unix timestamp)
- if somehow no timestamp could be generated the sediROM version number will be used instead
- if the backup fails we will CONTINUE! That means the installer will not abort to ensure that you will not end with an unused device
That also means that you should not rely on that efs backup it is a help for those not familar with the CLI only.
Added a "getdate.sh" script in aroma installer to filter tzdata errors
Added a sediROM bootanimation (NSA) and made it default
Removed facebook installer files from sediROM zip (was unused since the beginning) which frees some space of the ZIP
Fixes
on first boot bluetooth will be enabled once. This is needed to ensure that /data/misc/bluetoothd/MAC-ADRESS will be created.
That directory is device specific and will be created by Android when not existent. As the bluetooth fix from this version on
depending on a indicator file within this directory it is necessary to enforce its creation by enabling bluetooth once.
This is done within the init script 00sediROM_1stbootDT.
(!) whenever a soft reboot or system force close has happened bluetooth has stopped working. The only workaround was to
reboot the device. A fix was added which checks every minute if the bluetooth indicator file is there and if not the init
script for fixing bluetooth will be restarted. This way in worst case scenario of a soft reboot crash after 1 minute latest
Bluetooth becomes usable again (so no reboot anymore needed).
Changes:
- /etc/cron.d/root
Added:
- /system/xbin/sedi_btFCdetect.sh
fixing some problems with encrypted storage detection
due to a timing issue some early logfiles of sediROM were not got written to /sdcard. The fix was to use /preload instead:
When sediROM boots the init script 00sediROM_first will try to mount /preload.
If mounting /preload was successful it will be used for all logs and existing data will be moved to /preload.
It would be nive to have a symbolic link here but this is not possible across different filesystem types. So there will be
an indicator created in /sdcard/.sediROM with the hint to goto the /preload for logs instead.
All scripts within sediROM were modified to check for the existence of this indicator file and dependending on that they use
/preload or /sdcard for their logging data.
(!) when a soft reboot occured the bluetoothd directory gets trashed, too. If you then rebooted the empty bluetooth settings gets
backed up and therefore you boot with emtpy BT settings. This was fixed by using an indicator file (btfix.indicator) which
will be added after booting the first time. When a system shutdown is initiated sediROM will check for this file and as a
soft reboot would also delete that indicator file it will detect this and backup when this indicator file is still there.
In other words: when a soft reboot has occured you can safely reboot now and your settings will be there on the next reboot and
not lost.
cosmetics within updater-script output and AROMA
(!) Extreme battery drain caused by Google Play Framework Service.
This fix is a big one and splitted into 3 parts:
1) When system booting up /system/xbin/sedi_fix-gplay-drain will be triggered by /system/etc/init.d/00sediROM_first
2) /system/etc/init.d/00sediROM_first will also enable the cron daemon crond (coming with busybox) so we can automatize things
"enable" crond means several things need to be setup first:
a) creating a /etc/passwd
b) creating /etc/cron.d/
c) starting crond as a process
3) With the now introduced crond we can run the script /system/xbin/sedi_fix-gplay-drain every 8 minutes.
This is to ensure that even when Google updates (this will be done SILENTLY! by Google) it's app(s) it will be fixed again on the next cron run.
/system/etc/cron.d/root contain's the magic line for that.
For details checkout the original thread here:
http://muzso.hu/2014/09/18/how-to-f...yanogenmod-11-with-google-play-services-and-o
http://forum.xda-developers.com/showpost.php?p=53881089
http://www.imoseyon.com/2011/02/cron-on-android-is-awesome.html
init.d scripts cleanup. 00sediROM_tweaks in the installer package under /system was never used because always replaced by the BTfix one.
I moved the both scripts 00sediROM_first and 00sediROM_last to /system/etc/init.d/ instead of havin them within BTfix.
All this is firstly cosmetic only but becomes more and more important to have things clear for coding.
Removed the option to install Cranium & IcePop Bluetooth (was for testing purposes only)
compat linkage when coming back from JB now respecting it's existence. That means it will check first and do the links when needed only.
RNGD's init script was blocking for 30s the next boot scripts (changed to 3s intervalls)
changed order for the BT fix init script (from 99 to 92)
the 00 sediROM init script was not respecting encryption state which itself is not a problem but as the switch to /preload is happening in this
version this has result in problems. The fix was to check for encryption state and /data/misc before proceeding
fixing enhancing databases coming with init script 16sqlite:
- sqlite3 binary was not working (since literom days....!) and therefore replaced!
- when /data and/or /sdcard is encrypted no enhancements had taken place (now respecting encryption state and wait until decrypted)
installer: When FULL-wiping all init scripts were not executed because of missing /preload/.sediROM and /sdcard/.sediROM. Those directories are
created by the installer now or when they exist the following files gets deleted instead:
- /preload/.sediROM/.initialized
- /preload/.sediROM/dir-moved-2-preload.txt
- /sdcard/.sediROM/.initialized
- /sdcard/.sediROM/dir-moved-2-preload.txt
installer: When PARTLY-wiping all init scripts were not executed because of missing /preload/.sediROM and /sdcard/.sediROM. Those directories are
created by the installer now or when they exist the following files gets deleted instead:
- /preload/.sediROM/.initialized
- /preload/.sediROM/dir-moved-2-preload.txt
- /sdcard/.sediROM/.initialized
- /sdcard/.sediROM/dir-moved-2-preload.txt
BETA-related (fix affects BETA release only): litekernels in modify mode could not be installed (therefore may soft bricked the phone!)
RFKILL switch desc added inside 92sediROM_btfix, slightly modified the log output too
(!) Not everything was cleaned/removed when UN-ROOT was selected. The uninstallation/unrooting will remove all related parts now including dalvik cache etc.
daemon mode in install-recovery.sh makes no sense in sediROM as it is not SDK 18+ and no selinux forced therefore removed
When switching the kernel the modules within /system/lib/modules/ were not deleted (e.g. dhd.ko) which could had caused trouble in rare situations.
The installer now deletes all modules when switching to another kernel
BETA-related (fix affects BETA release only): new sediKERNEL version (v1.0 build 50). Change: wifi as kernel module instead builtin.
On encrypted devices the installer was not able to mount /data and /sdcard. Now it will:
- check for the existence of dm-0 and dm-1 which are the unlocked /data and /sdcard partitions
- when they can be found they will be mounted and used accordingly and correctly
- when they can NOT be found an abort is raised to avoid data loss - 3 hints are given to solve the situation
- you N--E--E--D sediTWRP - Clockworkmod cannot unlock encrypted devices and "normal" TWRP versions are not able to unlock STOCK ROM encryption!!
--> sediTWRP can be downloaded here: http://forum.xda-developers.com/showthread.php?t=3007035
installer: When upgrading / partial wiping the system partition will be deleted at the END now. This is to avoid data loss e.g. when you have an encrypted
device and not unlocked the partitions in sediTWRP (or when using CWM or other "normal" TWRP versions)
installer: When normal installing / full / recommended wiping the system partition will be deleted after successful mount of /data and /sdcard first.
This is to avoid data loss e.g. when you have an encrypted device and not unlocked the partitions in sediTWRP (or when using CWM or other "normal" TWRP versions)
installer cosmetics:
- Easy installation description changed
- "Recommended Wipe" renamed to "Clean install / Recommended Wipe"
- "Partial Wipe" renamed to "Upgrade mode / Partial wipe"
fixes an issue where Android goes into a boot loop in rare circumstances (issue #11). In rare cases several XMLs will be zeroed out by Android when not shutdown cleanly.
Those XML files still be there but they are empty! When Android boots up it tries to open those XMLs and as they are empty the whole boot process will hang!!!
I fixed this by:
- adding a new function which searches for all opened /data/system/.*xml files after a given period of time
- after this time period a file size check will be made: if the open xml is 0 it will be renamed
- when a renaming happened the parent process will be killed to ensure the boot process will not stop
moved the first boot detector to the near end of the boot process instead! That may fixes other issues as well regarding displaying the first boot app
better integration of the wait for system readiness while booting up (commit d0970abf6ec6c65af9999e2428b96fe293a55f17).
bluetooth file exchange was not working since a change in audio.conf
content in installer welcome screen
modify mode: when no kernel was selected the radio/modem force selection dialog appears
modify mode: removed several hard coded preselections
modify mode: modifying failed under some circumstances which resulted in aborting and may have left you with an unusable device
For older releases see attached file (View attachment CHANGES.log) !
Click to expand...
Click to collapse
Dev facts
sediROM v2.1 (Bugfix Release)
Development duration: about 8 hours
Finished on: 2016-01-04
Builds taken: 3
Changes: 2
sediROM v2.0 (Major Release)
Development duration: about 304 hours
Finished on: 2015-12-29
Builds taken: 69
Changes: 64
sediROM v1.7 (Important Bugfix Release)
Development duration: about 68 hours
Finished on: 2015-02-02
Builds taken: 7
Changes: 6
sediROM v1.6 (Important Bugfix Release)
Development duration: about 24 hours
Finished on: 2015-01-08
Builds taken: 22
Changes: 11
sediROM v1.5 (Big Maintenance Release)
Development duration: about 67 hours
Finished on: 2014-12-24
Builds taken: 24
Changes: 21
sediROM v1.1 (Bugfix Release)
Development duration: about 28 hours
Finished on: 2014-10-21
Builds taken: 15
Changes: 8
sediROM v1.0 (First Stable Release)
Development duration: about 640 hours!
Finished on: 2014-09-02
Builds taken: 58
Changes: more than 82
Click to expand...
Click to collapse

Trouble?
Trouble after flashing?
For EVERY request you have to upload the install log:
after every installation an automatic logfile will be saved to /sdcard/install_sediROM_vX.x.x.log where vX.x.x is the sediROM version number. Upload that log to pastebin and give me the URL.
Flashing failed? or Download mode always coming up?
Download rooted stock ICS http://forum.xda-developers.com/showpost.php?p=30421243&postcount=1
Go in download mode
Open Odin in Windows
Select Auto-Reboot and nothing else and add in the PDA section the above ROM (unzip first - you need the tar.md5 inside)
When it finishes your Glide should reboot (and Odin should say PASS). You do not need to wait if it is fully booting up and you can reboot once again in the download mode
Open Odin in Windows again
Flash TWRP (pretty nice gui, better handling, charging while active) or CWM (ugly gui, more robust, will NOT charge while active) over the PDA slot again (see flashing guide above for DL links)
(I use TWRP and several reflashings etc and it is working fine for me - but keep in mind that Nandroid backups are NOT compatible between those both recovery tools so choose the one you had before. I can highly recommend that you switch to TWRP when you currently using CWM because the handling and features are great (besides flashing probs of course)
For those who need more details and screenshots etc: http://unbrick.itcse.com/unbrick-soft-bricked-samsung-captivate-glide-sgh-i927/
"no recovery kernel" displayed when trying the recovery menu?
That is easy to solve when you know the correct partition name.. That is for the glide "LNX".
On Linux: Start heimdall or heimdall-frontend and simply flash a kernel back. For this you need a pit file which need to be catched first:
Download PIT:
Code:
$> heimdall download-pit --output mycurrent.pit
Flash the kernel with that catched PIT info: (Click to see an image of the heimdall frontend)
Flashing itself failed? Corrupted image message or /cache mount failures?
Flash with TWRP instead of CWM! See the OP for the DL Link (section Howto & Download)
loosing signal / bad signal ?
In my case I had sometimes problems with my baseband (loosing signal / bad signal) which was silly.
I found out that this was not ROM related because happens with several ROMs and total random.. Because of that randomness it was first hard to say if it is ROM/Modem based or not.
So if you come in such a situation and a modem change does not help I can recommend to open you Glide's back and check the SIM..
Sometimes (not often) it can be easy: In my case a little tape fixed my problems with that because the SIM is hanging very lax in it's case..
Maybe that little trick helps others, too

Roadmap
ROADMAP FOR sediROM
I never promise that a requested feature will be in a specific version or even added!
But you can add your ideas and wishes here if you like:
Open a Feature request (click here)
If you find a bug then it is your absolute responsibility to file a bug.
You can do it here: >CLICK HERE<
Version X.x
The Roadmap has been completely moved to github:
Github Milestones
upcoming features/enhancements need to fulfill at least one of those:
Fixing a (real) bug or serious problem
Performance optimization
Battery optimization
System optimization or stability
Even if your request met one ore more of those requirements I will decide on my own if it will be added or not.
If you don't like that you're free to create your own ROM
On the roadmap the base of sediROM was planned as UCLJ3 but to be honest according to the thread poll () I will look into the base question before starting v3 again.
The poll result is clear: It has to be stable - I don't care about the base
So I'm free to decide I will look into the issues CM9 has and compare them with UCLJ3 and then I will decide which will be the base at the end.
If someone is willing to help - let me know your results, analysis!
sediROM BETA download area / file exchange
http://tinyurl.com/pv7utvl
(password protected - PM me to get access)

Great!!! :laugh: Downloading tonight! :fingers-crossed::fingers-crossed::fingers-crossed:

It's great to have so many choices for people to choose from
I've added this to the guide of course ;D People would love using this ROM because you can be close stock and have the stability of a custom ROM!
Also I would like to remind people if you cant post bugs in the dev section,post what ROM your using and bug in my thread so we can figure it from there

Waiting for the link:thumbup:
Sent from my HTC6435LVW using XDA Premium 4 mobile app

I believe sediROM's installer is the main show stopper atm.
but as now it is good enough to state as alpha because it is working fine in my tests (tested preseleted config only) and therefore if someone wants to help me - even when it is still a risc - write me a PM.
... and I cannot say it often enough:
DO A NANDROID BACKUP
COPY THAT BACKUP TO AN EXTERNAL DEVICE TOO !!!! --> SAVED MY DAY TODAY BECAUSE OF MD5 MISMATCHES THAT CAN HAPPEN..
ENSURE THAT YOUR BACKUP IS FULLY OK (e.g. md5sum -c nandroid.md5) in BOTH places (on the Glide on on your external ressource)
You should have a windows box running Odin + CWM6) near - just for the case. TWRP is not such bulletproof then CWM in my case..
regards
xdajog

This is great! Thank you all for the continuing support for our Glide!
Sometimes ancient is better when it was made with at least some support from the manufacturer. I'm still running GB based OsiMood as I haven't found a better alternative (because of Samsung's non-existant support for our great devs).

Yeah today I shot a used Cappy. That will be much easier for development when not needing to use my productive device. Will be here in 2 weeks..
Sent from my SGH-I927 using XDA Free mobile app

THat Rom can install in Roger?
Sorry My English Not good

joedeng said:
THat Rom can install in Roger?
Click to expand...
Click to collapse
yes it will work on Rogers variant, too. But I cannot recommend to use sediROM when you do not have good enough english skills to understand what you need to do in case of trouble.. You need to know how you can rescue your system in case of error or problems.
I wrote a very basic troubleshooting guide in the original post of this thread.
If you still want to try write me a PM and I provide you the download link to the current testing version (v1.0.18) of sediROM.
regards
xdajog

xdajog said:
yes it will work on Rogers variant, too. But I cannot recommend to use sediROM when you do not have good enough english skills to understand what you need to do in case of trouble.. You need to know how you can rescue your system in case of error or problems.
I wrote a very basic troubleshooting guide in the original post of this thread.
If you still want to try write me a PM and I provide you the download link to the current testing version (v1.0.18) of sediROM.
regards
xdajog
Click to expand...
Click to collapse
I do not generally write good English but I can understand. That the rom of your development from LiteRom v0.9 rom right? On the status bar has percent battery and 14 toggle it? If the trial is still okay, right? just as there were some errors when spending alone is not
p/s Finally i will try it, you get me your link, i will test it ^^

joedeng said:
I do not generally write good English but I can understand.
Click to expand...
Click to collapse
ok just wanted to be sure that you know what you're doing
That the rom of your development from LiteRom v0.9 rom right?
Click to expand...
Click to collapse
Yes it is based on LiteROM v0.9 as stated in the OP. (Well atm I'm currently re-thinking this and testing a complete new build on stock ICS instead of LiteROM).
On the status bar has percent battery and 14 toggle it?
Click to expand...
Click to collapse
yes to both
p/s Finally i will try it, you get me your link, i will test it ^^
Click to expand...
Click to collapse
You have a PM

Hey i have already install your rom. It awsome, but you can add some more app. Example click Volume Up or Down wake phone. Get some launcher LG, Samsung, Sony...More theme. recent app, status bar add slide brightness......

Today i have test, it can not share file via bluetooth...Stock ROm can do it. But Your Rom can not share file via Bluetooth....

joedeng said:
Today i have test, it can not share file via bluetooth...Stock ROm can do it. But Your Rom can not share file via Bluetooth....
Click to expand...
Click to collapse
From your device to another one or
from another one to your one or
in both direction?

Call for enhancements for sediROM v2
My idea for the upcoming version v2 is:
Keep as close as possible to Stock, fix known issues, remove bloatware and enhance it by features coming from apps - and not by re-compiling sensitive things like framework etc. The only reason for touching system components would be if that would fix something but not to add features into it. An example is the Quick settings bar which is not workin as expected in LiteROM. There are apps out there (e.g. a well configured Widgetsoid bar or one of the others) who can do the same but they do not touch system files. the sames goes to Bluetooth which seems to not working (as joedeng reported) like expected but it do work in Stock.
One another very important thing to mention:
I do not want to be a full-feature-blown-containing-everything-what-is-available-ROM!
upcoming v2 features/enhancements need to fulfill at least one of those:
Fixing a (real) bug or serious problem
Performance optimization
Battery optimization
System optimization or stability
So I hope you got the idea
So as I'm currently developing both directions it would be possible to hear your thoughts about that way.
This is your chance to be part of sediROM v2
So: If you have features you want to have or if know about issues within ICS STOCK Rom let me know!

Send me your link v2 in my box...Whay u don't post link down in top? I think your rom it good...

Pixel Experience 12 for Galaxy A51

What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0 (11 is available but 12 has no difference in terms of issues and is faster an the better ui and everything else of course)
Disclaimer:- This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
Read all the steps correctly
(NOTE: do not apply the fixes if a bug does not affect you)
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
Source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
Rom download.
1.Need TWRP 3.4.0 or higher!
2. Unpack the "xz" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
5 flash PrismaKernel
https://forum.xda-developers.com/t/prismakernel-r1-oneui3-x-gsi-stable-enforcing.4344411/
5.45 install magisk (the one linked above only) (optional but you should as a lot of modules are listed here are very important (ie the acc module and the fast charging module)
5.5.Reboot and enjoy!
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Install gcam go (or gcam if you get it working)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Optimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk (install both ipv4 and ipv6 versions) (this will switch you to cloudflares faster and more secur dns
Cloudflare dns magisk download​
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
(you get better battery and performance in adaway)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devs
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces

Thank You my friend Big ROM

Zainullahk1234 said:
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0 (11 is available but 12 has no difference in terms of issues and is faster an the better ui and everything else of course)
Disclaimer:- This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
Read all the steps correctly
(NOTE: do not apply the fixes if a bug does not affect you)
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
Source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
Rom download.
1.Need TWRP 3.4.0 or higher!
2. Unpack the "xz" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
5 flash PrismaKernel
https://forum.xda-developers.com/t/prismakernel-r1-oneui3-x-gsi-stable-enforcing.4344411/
5.45 install magisk (the one linked above only) (optional but you should as a lot of modules are listed here are very important (ie the acc module and the fast charging module)
5.5.Reboot and enjoy!
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Install gcam go (or gcam if you get it working)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Optimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk (install both ipv4 and ipv6 versions) (this will switch you to cloudflares faster and more secur dns
Cloudflare dns magisk download​
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
(you get better battery and performance in adaway)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devs
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces
Click to expand...
Click to collapse
Bro what is the difference between vnkdlite img or img file

Kashif Hussain12 said:
Bro what is the difference between vnkdlite img or img file
Click to expand...
Click to collapse
System read and wite (its very usefull)

Zainullahk1234 said:
System read and wite (its very usefull)
Click to expand...
Click to collapse
Should i download vnkdlite img

Kashif Hussain12 said:
Should i download vnkdlite img
Click to expand...
Click to collapse
yes

Zainullahk1234 said:
yes
Click to expand...
Click to collapse
Which kernel is best for gaming for this rom

Kashif Hussain12 said:
Which kernel is best for gaming for this rom
Click to expand...
Click to collapse
the one i said on the post

May I ask what does "tailored to samsung devices" mean specifically?

Yillié said:
May I ask what does "tailored to samsung devices" mean specifically?
Click to expand...
Click to collapse
the post and the img files available are the ones that work on samsung devices
and the post has all fixes workarounds and install method which works on the a51

Zainullahk1234 said:
the one i said on the post
Click to expand...
Click to collapse
Bro when I flash IMG file there is a option of super(system vendor product odm I have to click on this

Zainullahk1234 said:
the post and the img files available are the ones that work on samsung devices
and the post has all fixes workarounds and install method which works on the a51
Click to expand...
Click to collapse
So if I understood it right, the gsi files provided via the download redirect link are just mirrors of Ponces' PE builds?

Yillié said:
So if I understood it right, the gsi files provided via the download redirect link are just mirrors of Ponces' PE builds?
Click to expand...
Click to collapse
yes (i removed the ones not needed like arm32 and slim)

Zainullahk1234 said:
yes (i removed the ones not needed like arm32 and slim)
Click to expand...
Click to collapse
K so your title is kinda misleading with no mention of it being a GSI ( both in the title and in the entire thread ), you've linked to a specific canary build of Magisk while even the stable works fine on A51, slim variant does indeed work on A51 and idk why you just can't link to Ponces' release post and specify the variant they have to download. Uh well nvm, I got the answer I was looking for but I would really appreciate it if you mentioned GSI in the title + don't take this as a hate comment lol.

Zainullahk1234 said:
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0 (11 is available but 12 has no difference in terms of issues and is faster an the better ui and everything else of course)
Disclaimer:- This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
Read all the steps correctly
(NOTE: do not apply the fixes if a bug does not affect you)
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
Source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
Rom download.
1.Need TWRP 3.4.0 or higher!
2. Unpack the "xz" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
5 flash PrismaKernel
https://forum.xda-developers.com/t/prismakernel-r1-oneui3-x-gsi-stable-enforcing.4344411/
5.45 install magisk (the one linked above only) (optional but you should as a lot of modules are listed here are very important (ie the acc module and the fast charging module)
5.5.Reboot and enjoy!
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Install gcam go (or gcam if you get it working)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Optimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk (install both ipv4 and ipv6 versions) (this will switch you to cloudflares faster and more secur dns
Cloudflare dns magisk download​
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
(you get better battery and performance in adaway)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devs
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces
Click to expand...
Click to collapse
Hello, I don't see "system" when I try to flash the image. I only see Super ( system, etc) is it the same thing?

tumarido666 said:
Hello, I don't see "system" when I try to flash the image. I only see Super ( system, etc) is it the same thing?
Click to expand...
Click to collapse
no dont do that

Zainullahk1234 said:
no dont do that
Click to expand...
Click to collapse
I agree with this. Before this guide was even put out, I flashed a PE rom to super and it did a boot loop (funny enough i also did this in school so i had to wait 4 hours in order to fix it)
Is there any fix though from your standard? I've been wanting to flash a rom to system and not super. I got a A515F/DS 128GB 4GB RAM from Panama (I live in Canada btw).

install Project Arcana OS v4.1 GSI | Dream on Galaxy A51 + Overview​Android 12 GSI running perfectly

Zainullahk1234 said:
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0 (11 is available but 12 has no difference in terms of issues and is faster an the better ui and everything else of course)
Disclaimer:- This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
Read all the steps correctly
(NOTE: do not apply the fixes if a bug does not affect you)
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
Source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
Rom download.
1.Need TWRP 3.4.0 or higher!
2. Unpack the "xz" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
5 flash PrismaKernel
https://forum.xda-developers.com/t/prismakernel-r1-oneui3-x-gsi-stable-enforcing.4344411/
5.45 install magisk (the one linked above only) (optional but you should as a lot of modules are listed here are very important (ie the acc module and the fast charging module)
5.5.Reboot and enjoy!
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Install gcam go (or gcam if you get it working)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Optimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk (install both ipv4 and ipv6 versions) (this will switch you to cloudflares faster and more secur dns
Cloudflare dns magisk download​
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
(you get better battery and performance in adaway)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devs
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces
Click to expand...
Click to collapse
tumarido666 said:
Hello, I don't see "system" when I try to flash the image. I only see Super ( system, etc) is it the same thing?
Click to expand...
Click to collapse
same problem here, why i cant see "system option"?

franciscopelle31 said:
same problem here, why i cant see "system option"?
Click to expand...
Click to collapse
use twrp 3.6.0

[2022 Root For S7/S7Edge Oreo Rev4_To_Rev10/A_Odin Flashable Or ADB Method] Plus [Limited Root Method Rev11/B _Using Combo_Firmware]

Oreo Root For The S7/S7E (Will work on Rev4-Rev10/A Bootloader) Adb Install
A big thanks goes out to @klabit87 he is 99 percent the reason we have root! Also @stang5litre and stang5litre test group.​Prefered Root Method Oreo Only Using Odin Only For Rev-4 Too Rev10/A
Odin Install Root Method For S7 Flat Can Be Found Here
Odin Install Root Method For S7 Edge Can Be Found Here
Root Method Using Odin Only For Rev-11/B -- Please Read Limitations On The Thread
Rev11/B Root Method For S7 Flat Can Be Found Here
Rev11/B Root Method For S7 Edge Can Be Found Here
ADB Method Oreo Or Nougat For Rev-4 Too Rev10/A -- Must Use Adb Method For Nougat Root
2023_S7_Flat_Edge _ADB_Root_Plus_Safestrap_V1.7z​
Directions:
This works for Oreo Rev4-Rev10/A Bootloader Roms or Nougat Rev4
As always there is a chance of bricking your phone
1. Download and extract 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z
2. Reboot your phone to download mode
3. Inside the 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z folder you will find an Odin_Firmware folder. Use Odin and flash the Eng Boot Image for your phone
4. Once phone is rebooted and connected to computer click on the cmd-here.exe and type Install_One_Click.cmd in the command window and hit enter
5. Once root is done and root bat closes your phone will reboot too stock recovery where you must wipe data
6. Once booted click on SuperSu app and update su binary if app ask then reboot
7. Don't flash any superuser zips in recovery that are not made by me or use any other SuperSu apk
Rebooting Too Safestrap Recovery
1. Reboot phone as you would too boot stock recovery Pwr + VolUp + Home. It takes up too 40 seconds too boot recovery. Ignore the mount system errors on info screen
2. Enter recovery.
3. Too leave just reboot system ignore no system installed message if you get it
4. There is screen lag issues on scrolling in recovery. There is aroma file manager that takes care of this issue while in recovery but selecting zips too install may present a problem for this you can use the kernel manager recovery flash option while phone is booted too system. Simply select zip too flash and phone will reboot too recovery and flash it and reboot back too system. Most other function in recovery should work the issue is just scrolling too select files.
5. Flashfire is installed as an alternative as well
Features:
1. SuperSu Root- Do not use any other SuperSu app. Its ok to update su binary if app ask.
2. Safetrap recovery-Still working out scrolling issue
3. Flashfire
4. Kernel tweaks CPU governor set too Conservative
5. Entropy/Swapiness set to High
6. Build Prop tweaks to combat lag
7. Bloat removed from rom
8. Knox removed from rom
Bugs:
Eng Boot Image causes lag
Safestrap Recovery has scrolling issues
Random Reboots will most likely happen
Safetynet will not pass
Battery life may not be optimal
SuperSu cannot be updated
Flashfire may need date changed too 2016 to function if it just keeps closing on you
Volte And Hotspot Fix
View attachment 4555265
Old Downloads
S7_Oreo_Nougat_Adb_Advanced_Root_V12.zip Recommended Root Zip
This zip gives you the option to install some cpu tweaks and will also. Install the entropy tweak that the SEFix app does. The tweak sets entropy to high by default I also include the SEFix app if you want to change the settings. I also set the swappiness settings to very high. If you want to change these settings you can download the speedup swap app from playstore. The above zip also removes knox and changes the fstab.qcom file to disable dm-verity on system files and remove all file encryption which makes it seem to work better and make it compatible with my no root roms that has to have this done to allow safestrap to work. Installing the above zip requires a data wipe unless you have already installed it or you are coming from my non rooted roms
S7_Oreo_Su_Binary_Only_ADB_Root.zip Alternative Root Zip
This root zip is only for oreo an only installs the su binary to the system/xbin folder giving you root privelages it has no tweaks and does not change the fstab.qcomn file to remove dm-verity and system file encryption. There is no SuperSU app installed either but you will have root privelages.
Credits:
- @Raymonf for modified odin
- @afaneh92 for safestrap
- @me2151 for help and finding alternative flash methods
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for help
- @partcyborg for help and guides other devices root methods
- @elliwigy for being great help when I need it
- @stang5litre
- @jds3118
- @Krog18
If I missed you please pm me
Donations
If you would like to donate please send all donations to @klabit87 PayPal Link Here and give a thanks!

Main Root thread with all discussion is found here
[2022 Root For S7/S7Edge Oreo Rev4_To_Rev10/A_Odin Flashable Or ADB Method] Plus [Limited Root Method Rev11/B _Using Combo_Firmware]
Oreo Root For The S7/S7E (Will work on Rev4-Rev10/A Bootloader) Adb Install A big thanks goes out to @klabit87 he is 99 percent the reason we have root! Also @stang5litre and stang5litre test group. Prefered Root Method Oreo Only Using Odin...
forum.xda-developers.com