Related
WARNING KNOW WHAT YOU ARE DOING BEFORE ATTEMPTING THIS, IF YOU DON'T UNDERSTAND WHAT IS BEING TALKED ABOUT HERE YOUR BEST TO LEAVE IT ALONE
This is a Vibrant kernel/recovery image that includes EXT2/3/4 support as well as init.d support for user scripts. Everything works as expected Wifi/GPS/BT etc
This eliminates the race condition as the scripts in init.d run before the default Android services.
You can add any user scripts you want by adding them to the /system/etc/init.d folder e.g "05userscript" They are parsed by order 00 then 01 then 02 etc
BEFORE FLASHING THE KERNEL You must flash the init.d update to add the needed folder and files to boot with this kernel. That is because the completion script sets a prop value telling the default Android services to run. If that prop isn't set you will be sitting at the Vibrant screen forever.
The new init.d updates remove any other versions of busybox and install the correct version and symlinks to take care or the issues people have been having with multiple BB installs. There is a version that has no data to SD script for those that want to run other lag fix's. And then there is one with the data to SD script.
Default CPU frequencies and Overclocked versions available.
OCv4
Clock Drift fixed
Fix scaling bug, performance level was set past end of table on sleep
Scaling enhancement, selectable clock source for GPU
GPU clocked at 222MHz for all speeds except 100MHz, where it matches CPU clock
more up/down threshold changes
Wake Lag improvements
Switched back to "CFQ" for perf reasons over deadline and no-op
BB symlinks removed from ramdisk (to avoid conflict with mods that make their own links to BB)
OCv3
NO MORE WAKE LAG!!!!
Reverted back to OC on boot
up/down threshold adjustments again
rebuilt with crosstool-ng 1.8.0 gcc 4.3.4
OCv2
Extra steps are back. [100/200/400/600/800/1000/1200] YOU MUST use setCPU to up it to 1.2Ghz it is set at 1Ghz default for stability reasons,this CPU is very sensitive to voltage/freq changes. Should be more stable overall then prev build. (Thanks Unhelpful)
up/down threshold adjustments
SCv9
No More WAKE LAG!!
Uncommented FM Radio module in init.rc
SCv8
Conservative/Deadline
SCv7
Ondemand/Deadline are default now in
SCv6
ADB issue resolved.
Busybox issues resolved. Can now update through stericson's BB utility from the market.
OC version available with extra 600mhz and 1200mhz step added (you still have 800, 1000 etc) Linpacks in the 10.0's (Thanks to ivanmmj for the help)
SCv5
Volume rocker fixed
cleaned up RAMDISK
reverted to stock recovery (rev1 had clockwork as the recovery but was having a few issues)
added symlinks for busybox applets
Fully compatible with Clockwork (backups/restore from ROM manager) (no more annoying reboot before Clockwork starts)
INSTRUCTIONS
Note:The new init.d updates install BusyBox for you and create the symlinks. They also remove any other prior version before doing so
1.Choose one of the init.d updates that suites you.
A.
Data and Dalvik init.d-busybox with data to SD update.zip
MD5:0317ae432d2db15e51fd0da2c4d53857
B.
Data and Dalvik init.d-busybox without any lagfix scripts update.zip
MD5:9e720b587188676e7fff2f144433bd23
2.Reboot into recovery and flash this. Once booted check your system/etc dir for the init.d folder and scripts inside before moving forward. If they are there we move on.
3.Download the kernel/recovery image
OCv4 1.2 No Wake Lag/No Time drift
Update.zip (flash through clockwork recovery)
www.justanotherdev.slackdev.com/Kernel-Vibrant-OCv4.zip
MD5:33487d4bec50d123d0bb10843d141723
ODIN Image
www.justanotherdev.slackdev.com/kernel-vibrant-OCv4.tar
MD5:5aae7e5ab08227e1fd4c931c24f678ac
OCv3 1.2 No Wake Lag
kernel-vibrant-OCv3-NG.tar
MD5:1e2ddb9bd9fe4adb0ccc73fa818c63be
OCv2 1.2Ghz with extra steps back in. More aggressive up/down thresholds
kernel-vibrant-oc-ng.tar
BETA OC 1.2Ghz (no added steps for now)
kernel-vibext4-oc1.tar.md5
MD5:d1e26f769406c5d368492855c7b5059e
SCv9 No Wake Lag
kernel-vibrant-SCv9-NG.tar
MD5:0614a8205087a84fe34bbe2c653183a9
SCv8
kernel-vibext4-8.tar.md5
MD5:e9c2a45d89d994c485b8af8e1b1a923c
SCv7
kernel-vibext4-7.tar.md5
MD5:cedbad0273a2dd2a1b2d0a4ed3e89fce
4.Reboot into download mode and use ODIN to flash the kernel. Use the CSC field with no PIT file. This will flash the kernel/recovery
NOTE:You can find ODIN in my other thread here
If you have an EXT2/3/4 partition I used tabbals script (to tired and will be re-writing this shortly) for the mean time to bind your data to the EXT partition or otherwise known as the "EXT hack" for those that want those wondering. If you do not want this script you can remove the 07a2sd script from the init.d folder before flashing the kernel.
Now you can add any user scripts you like to the init.d folder and we dont need to use the "playlogos" hack anymore. This is a work in progress and more tweaks/features will be integrated and updated as they are tested and made available in this thread. I had to give you guys something to mess around with. And a proper way to run user scripts.
Thanks to Unhelpful, supercurio, cyanogen, scepterr, wes garner, Eugene_373 and everyone that helps out in the XDA community!
Sources:
Kernel: T959 source from opensource.samsung.com
Voodoo-fix http://github.com/project-voodoo
OC patch posted below
Enjoy!
Need to revert to the stock kernel??
www.justanotherdev.slackdev.com/kernel-vibrant-stock.tar.md5.tar
MD5:9f89f8c5a6c785ff967806a4ca70906f
Beautiful! now if only we can find a way to flash the kernel from recovery without needing odin.....
anomalous3 said:
Beautiful! now if only we can find a way to flash the kernel from recovery without needing odin.....
Click to expand...
Click to collapse
Agreed. Feel free to use this kernel/recovery in your ROMS just give credit and I'll be more than happy
Also more to come folks just sit tight. This is my hobby and I have to take care of some real life issue ATM...cough ...the woman...cough.
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
frank707 said:
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
Click to expand...
Click to collapse
Any scripts will work fine just as before. The main difference is that we dont need the "playlogo" hack that was used previously which runs a script called userinit from /system/bin/ now all user scripts will go in /system/etc/init.d/
Now we have this folder (init.d) to store all are user scripts in and gives us the option to choose which runs first according to how they are labeled. Just have a peek inside the init.d folder to see what I'm talking about. Init.d is pretty common on Linux boxes just not Android
Also to be clear this should clear up race conditions as any user scripts in init.d will run before the default Android services.
FYI tabbals scripts is renamed "/system/etc/init.d/07a2sd" (which I should have names d2sd but whatever lol) in this build. Same script so yes the scripts will work just fine
frank707 said:
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
Click to expand...
Click to collapse
one of the main purposes of the kernel is to give us a linux-standard place for people to add startup scripts, and to make data2sd possible without trouble, including ext4 which combines most of the speed of ext2 with the stability of ext3.
anomalous3 said:
one of the main purposes of the kernel is to give us a linux-standard place for people to add startup scripts, and to make data2sd possible without trouble, including ext4 which combines most of the speed of ext2 with the stability of ext3.
Click to expand...
Click to collapse
Exactly.
Have fun I'm off to bed for now. I've been running this for 2 days without issues. Please let me know if you find any bugs. WiFi BT and everything else should be working just like the stock kernel I also haven't had one kernel panic yet.
justanothercrowd said:
FYI tabbals scripts is renamed "/system/etc/init.d/07a2sd" in this build. Same script so yes the scripts will work just fine
Click to expand...
Click to collapse
can't wait till take takes off. So is tabbal's script already setup to run automatically as long as i have my ext partition setup?
Im definately +1 for getting rid of odin, Jac do you use github at all ?
frank707 said:
can't wait till take takes off. So is tabbal's script already setup to run automatically as long as i have my ext partition setup?
Click to expand...
Click to collapse
This is correct yes.
bbuchacher said:
Im definately +1 for getting rid of odin, Jac do you use github at all ?
Click to expand...
Click to collapse
I use git/mercurial but not github. I will be creating an account their to share code as people have been requesting it
bbuchacher said:
Im definately +1 for getting rid of odin, Jac do you use github at all ?
Click to expand...
Click to collapse
good to see some Super D/E/F power using this phone. Would I be correct in thinking the main problem with packing the kernel into a boot.img would be the offsets, or do you think we're dealing with something a bit more serious?
Would I have to wipe if I flashed this kernal? Or can this be flashed on top of what I have now and not lose anything?
Goog1e Phone said:
Would I have to wipe if I flashed this kernal? Or can this be flashed on top of what I have now and not lose anything?
Click to expand...
Click to collapse
No Wipe is needed. Make sure you flash the update first though it is a REQUIRMENT for it to boot with this kernel.
justanothercrowd said:
No Wipe is needed. Make sure you flash the update first though it is a REQUIRMENT for it to boot with this kernel.
Click to expand...
Click to collapse
attempted to flash the first zip but init.d folder wasn't created. Wouldn't flash through stock recovery, attempted to flash through cw, will try again and update
The follow error occurs on flash
Code:
E:Can't chown/mod system/etc/init.d/02a2sd
(No such file or directory)
E:Failture at line 7:
set_perm 0 1000 0755 SYSTEM:etc/init.d/02a2sd
Installation aborted.
problem is in script, just edited it, about to try to flash
no dice, no install
davbran said:
no dice, no install
Click to expand...
Click to collapse
EDIT: realized my FTP client wasnt uploading in binary mode which caused some issues.
Re-download the files they have been hashed and double checked.
Enjoy!
Onyx is simply a TouchWiz Free version of Obsidian. The changelog is listed there, in addition to those changes the following have been made.
Will make flashable nonwiping updates available until all the bugs are worked out and cleared. Once they are the newer and stable revision will be posted with complete skinning in two seperate versions. Please make requests for feature changes and things you would like removed.
4.2
- Added inharent support for Backlight Notification compatible kernels (BLN)
- Optimized Build Prop with ROM Identification Added
- Streamlined Frameworks
- Numerous Corrected Images
- Return of TouchWiz MMS w/ Blurry mms Fix
- Integrated WirelessADB
- Additional I/O scheduler, VM management, kernel scheduler, and minfree edits via sombionixInit script
- Integrated Flashing with Universal Lag Fix system. (Source by sztupy @ XDA, Ported by Krylon360 @ TeamWhiskey)
Team Whiskey Universal LagFix Kernel Features
- All lagfixes and tweaks activated directly within clockwork advanced menu
- MULTIPLE lagfix options, new and old
- Integrated TW logo
- 3e recovery built into kernel
- No longer required to disable lagfixes before flashing
- Enable/disable back light notifications
- Option to switch to 2e recovery
- Option to install Superuser
- Enable/disable I/O scheduler tweaks
- Enable/disable VM management tweaks
- Enable/disable kernel scheduler tweaks
- Enable/disable misc. tweaks
- Reboot into download mode
How To Utilize Universal LagFix Kernel:
1. Flash ROM as you normally would via clockwork recovery
2. Let device boot and then reboot back into clockwork recovery
3. Once in recovery, you will now see 2 new options at the bottom
4. Within the new menus, you will find options to enable/disable certain features and an assortment of lagfixes
5. Enabling/disabling features and tweaks are fairly self explanatory, so have fun with those.
6. Lagfixes are also fairly simple, however, if you are not extremely familiar with them, I suggest sticking to what you know such as the OCLF or voodoo options
7. Once you select the lagfix you want, you will see that your current configuration is updated. You must then go back and select reboot.
8. It will kick you back into clockwork very quickly and give you options before converting your partitions to your selected lagfix. I suggest you pick the first one which creates a backup and restore of your system.
9. Your device will now convert your partition, reboot your phone, and you're done!
Known Issues:
PLEASE READ PLEASE READ PLEASE READ PLEASE READ
- Currently, there is a VERY small percentage of users who have reported that their internal sd partition has been wiped. This is happening to roughly 1/20 people who flash 4.2 with the universal lag fix. If this happens, you will have to odin back to JFD and then upgrade back to 4.2 or any version of your choice. The kernel works very well, however, this is the first time this source and recovery modding has been ported to the Vibrant. None of my dev team has had this happen to any of us so we unfortunately cannot reproduce the problem and pinpoint the problem. We are thinking its hardware related at the moment. Please flash this at your own risk. If it does work for you, you'll love it, trust me! If you're one of the unfortunate ones that gets your internal wiped, well, I apologize, but you've been warned. I suggest ONLY experienced users download the rom with the ULF included. All others should download 4.2 w/stock kernel. THIS IS A KERNEL RELATED ISSUE, NOT ROM RELATED!
Update:
For those VERY VERY few unfortunate people who get their internal sdcard partition wiped, we have confirmation that using odin, going back to JFD, then back to Obsidian/Onyx 4.2 works fine. Everyone that has done this has had no further issues regarding the wipe issue.
3.1
-Even MORE framework edits
-tamed dragons
-now prints money
3.0
-Additional Framework Edits
-Beginning of a complete graphical overhaul
-Reskinned DialerTab Functions
2.2
-Fixes Mounting
2.1
-Corrected several improper strings
-Repaired twframework and framework
-removed power menu
R2.1 fixes a few issues, random dropping into airplane mode, crash when using the power button, repeat mms notifications, and more.
2.0
-TouchWiz Disabled and removed
-Standard LauncherPro installation w/ Fusion Skinning
-Reskinned to include Onyx button bar and status bar
All the other changes that were listed in R1 in beta were combined with Obsidian to make one big pile of awesome.
Reverting back to previous iteration, it was running clean and bugfree. Does not have the same stability previous Rev did. Took those peices and reintegrated into R2+
Removed some edits, much more stable now. I KNOW How you hate flashing updates, I promise I will try to make this the last major flashing update for a very long time. Its stable and perfect as far as I can see other than the known mounting issue. Enjoy!
Additional Option Flashes:
If you REALLY like the samsung apps I removed flash this - http://teamwhiskey.com/bin/onyx/FlashPa ... gExtra.zip
If you REALLY liked the WiFi calling and need it back, even if it slows your phone down, constantly, even in the background - http://teamwhiskey.com/bin/onyx/FlashPa ... alling.zip
OCLF/Voodoo Displaced, not removed.
To enable your new box of awesome, you will first need to reboot back into recovery. You will notice this is slightly different from your standard recovery. I will keep this as brief as I can and to the point. You can do any combination you want of lagfix, from simple bind to overkill mode and replace the entire FS to JFS + EXT2 Binds. This is totally at your discretion.
Personally, I enabled EVERYTHING and activated the most OVERKILL mode I could, because I like things over the top lol.
Its fast, wicked fast, its like fast took meth and kicked not so fast in the face in a single springboard motion to be faster.
Reboot to Recovery
Go to the Advanced menu below CWM
Set tweaks and options as you want to, I turned on Backlight Notifications and all the tweaks personally
After that, go to the LAGFIX section and shop for your weapon of choice, pick whichever you want. (Understand that converting data is a dragon in disguise, like a shoplifter in a cage inside an ATM that he COULD BREAK FREE from. Use at your own discretion.)
Reboot
Allow it to convert, could take a long time. Get a snack. Watch Hulu.
Once it boots, its done, reboot after about 15 or 20 for good measure and extra flavor.
Restore your data, dont restore EVERYTHING from Titanium Backup if youre coming from an Eclair build, single select restore your apps and their data. Otherwise Titanium Backup tries to make you some Froyeclair in a blender.
Backlight notifications are awesome, use them.
IF YOU ARE A BATTERY MONGER AND HATE IF YOUR BATTERY DOESNT LAST FOURTYSEVENTYTEEN Hours. Flash the stock kernel, otherwise you will get an average of 10-14 hours with this kernel.
Download:
Onyx 4.2 w/stock kernel
ULF Removed for Stability Issues in flashing
If you are one of the ones that had serious issues with ULF properly flashing we are very sorry that you are having those issues. We have pulled the ULF kernel due to its inconsistant flashing and are moving forwards with a few different concepts. If you are still having issues with this kernel and going back to normal please visit Sombionix or Viralblack in the TeamWhiskey IRC channel.
NEW internal/external mounting fix - after flashing, reboot phone and computer
Download Rom Extras:
Rom Extras
Thank you, this Rom rocks!!!!
Question: The USB debug mode enables itself everything the phone reboots. Is it supposed to be this way?
Thanks again for a awesome rom
Wait 10-14 hours of battery with this kernel? i know the features are awesome but that seems pretty bad. is that 10-14 hours with normal use or just chilling? cause moderate to heavy use and 12 hours doesnt seem so bad.
Awesome rom. Love it as usual.
I was one of the unfortune that got their SD wiped, but I made a bakup.
I flashed froyo via Odin, then reflashed Onyx v4. Works like awesome sause.
Not sure what caused this, Onyx or the overkill JS lagfix, but when I mount my internal/external sd card, the external shows up as a cdrom drive. The internal one is fine.
Can you please make a version with stock kernel
Sent from my SGH-T959 using XDA App
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
whats up with this new stuff? i selected the very bottom option in the tweaks for the JS overkill? is this JFS thing the new hotness? i dunno which to pick. i want this thing to be as epicly cracked out as i can make it. can you doo voodoo WITH this new thing or is it one or the other?
right now im sitting at 1406 quadrant and all i did was select that option
aeok18109 said:
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
Click to expand...
Click to collapse
Correct, their website shows:
"SECOND FLASHABLE STOCK KERNEL, use if you dont want to risk dragons."
aeok18109 said:
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
whats up with this new stuff? i selected the very bottom option in the tweaks for the JS overkill? is this JFS thing the new hotness? i dunno which to pick. i want this thing to be as epicly cracked out as i can make it. can you doo voodoo WITH this new thing or is it one or the other?
right now im sitting at 1406 quadrant and all i did was select that option
Click to expand...
Click to collapse
W/ voodoo it's either one or the other.
JFS = Journaled File System or JFS is a 64-bit journaling filesystem created by IBM.
RFS = Remote file sharing - essentially this is what Samsung originally went with and it's slow.
Viralblack said:
OCLF/Voodoo Displaced, not removed.
To enable your new box of awesome, you will first need to reboot back into recovery. You will notice this is slightly different from your standard recovery. I will keep this as brief as I can and to the point. You can do any combination you want of lagfix, from simple bind to overkill mode and replace the entire FS to JFS + EXT2 Binds. This is totally at your discretion.
Personally, I enabled EVERYTHING and activated the most OVERKILL mode I could, because I like things over the top lol.
Its fast, wicked fast, its like fast took meth and kicked not so fast in the face in a single springboard motion to be faster.
Click to expand...
Click to collapse
Quadrant scores aren't everything, if it feels fast, looks fast. It's fast.
oh yea i know. i personally could give a rats dong about Quadrant scores. This thing is pretty fast. i just posted it for reference. you know SOMEONE is gonna ask lol
Awesome, this is legit, had It since yesterday!
Sent from the speed demon
Okay, I was running the Macnut ROM (Eugene's ROM) and, having tried Onyx from the first beta, I decided to go back. I installed from CWM with no issues (no Internal SD wipe, etc.), let it sit for a bit then went into recovery to do the ULF. I didn't know what to choose but, I ain't afraid o' no ****in' dragons so, I chose the bottom most option for the works. After letting it sit for about 15 mins again and a Titanium restore of my apps, this thing screams. After a fresh reboot, I got 1852 on Quadrant and there is absolutely no lag on this thing. NONE. The only slight beef I have with this rom is that I miss the completely black Swype keyboard.
Stock Kernel
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
1. How do you use the WirelessADB??
2. What is Backlight Notifications?
miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
it means flash the R4 zip in CWM, then flash the stock kernel in CWM WITHOUT REBOOTING IN BETWEEN.
fearless1964 said:
1. How do you use the WirelessADB??
2. What is Backlight Notifications?
Click to expand...
Click to collapse
it makes the 4 android keys at the bottom light up when you have notifications... awesome for those of us who came from phones like the Nexus One that had a notification LED and miss it like woah
miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
flash one, then flash the kernel right after before rebooting into the rom for the first time. My issue is the stock kernel dl link is dead =\
miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
flash the R4 zip then flash the stock kernel without booting the device in between
rsfaze said:
flash one, then flash the kernel right after before rebooting into the rom for the first time. My issue is the stock kernel dl link is dead =\
Click to expand...
Click to collapse
Here it is. One stock Kernel, enjoy.
how do u use WirelessADB???
fearless1964 said:
how do u use WirelessADB???
Click to expand...
Click to collapse
ADB functions without a wire (USB cable)
Hi guys I decided to flash a new rom minicm7 and flash its latest kernel naa 13.
A couple of problems:
MY rom is minicm7 with naa latest version 13.
1.when I open the menu to access all my applications the scrolling feels laggy and if I were to scroll in settings file manager or anything else it's smooth any reason why?
2.Secondly which kernel suits you better for this rom (minicm7): Alfs? or NAa?
(I don't want comments like 'see for yourself' this question is based on your OWN invaluable experience)
3. for alfs 8acm7 i'm considering on seeing if it will workout for my device or not (minicm7). Before I do that:
Do I also need to flash chargemon on top of that? and does the flashing of chargemon straight after you flash any version of alfs kernel (except for the ones that already have it attached) apply to any rom regardless as well?
If so which chargemon do I flash? the v2 with the 17k downloads? (sorry im derping out)
4.Do I also need to flash anything else for naa just like how there was an extra file to flash for alfs?
5. I also installed tweaks 3 tweaks such as adre boost, odex, and e15 optimizer. Will these tweaks vanish if I flash a new rom + kernel?
6. Do you keep ANYTHING if you flash a new rom or kernel?
7. Do you lose anything of any sort if you flash a kernel?
8. How do you guys get such high scores in benchmark tests?
I have the same thing as a lot of people do but they seem to get 200 or even 300 higher. Could it because my sd card is filled with anime and music leaving only 5 - 6 gigs / 16gigs ?
I usually went by the rule of flashing 2.1.1.0 and rerooting my device and doing everything again just to stay safe
I don't know if these questions might be derp or not but I don't care please answer by putting a number first I really need answers.
Thank you once again
From my experience and opinion: (Please correct me if I'm wrong...)
1. IDK... BTW Is your MiniCM7 2.2.1 or Nightlies? Have your tried rebooting once or twice? Because mine was smooth...
2. nAa because it is more stable. They also said that the performance is faster with Alfs but I don't like FPS caps problem (Higher chance to get screen cut otherwise laggy scrolling visually)...
3. IDK... I haven't tested it...
4. No...
5. Most likely because you'll need to full wipe before installing a ROM (not kernel)...
6. Anything unless it requires to full wipe...
7. Yes... I think it overwrites some system apps and even some user apps and user data might be corrupted... (maybe when doing cross flashing of ROMs)
8. Overclock (The most effective and dangerous way), Supercharger (I think AutoKiller Memory Optimizer is the same), Swap (different partition), Adrenalines, Odex and et cetera...
Lily48 said:
From my experience and opinion: (Please correct me if I'm wrong...)
1. IDK... BTW Is your MiniCM7 2.2.1 or Nightlies? Have your tried rebooting once or twice? Because mine was smooth...
2. nAa because it is more stable. They also said that the performance is faster with Alfs but I don't like FPS caps problem (Higher chance to get screen cut otherwise laggy scrolling visually)...
3. IDK... I haven't tested it...
4. No...
5. Most likely because you'll need to full wipe before installing a ROM (not kernel)...
6. Anything unless it requires to full wipe...
7. Yes... I think it overwrites some system apps and even some user apps and user data might be corrupted... (maybe when doing cross flashing of ROMs)
8. Overclock (The most effective and dangerous way), Supercharger (I think AutoKiller Memory Optimizer is the same), Swap (different partition), Adrenalines, Odex and et cetera...
Click to expand...
Click to collapse
Hi there thanks a lot for your help and I am using minicm 2.2.1. And how do you swap different partion?
Ftwisawesome said:
Hi there thanks a lot for your help and I am using minicm 2.2.1. And how do you swap different partion?
Click to expand...
Click to collapse
You can use the recovery for creating SWAP but with Ext though...
[Ext is another partition for user apps and it's advantage is that you can use the apps on the partition while the sd is mounted on PC]
1. Back up everything on SD because it will be formatted...
2. Enter Recovery -> advanced -> Partition SD Card
3. Choose you Ext size -> Choose 128M Swap size... they said 256M is not recommended...
4. Reboot -> Terminal -> su (if required) -> free -> DONE!
If you want to use Ext, you may install Link2SD -> Choose Ext4 -> Reboot -> Launch Link2SD -> Start linking... DONE!... (Warning: sometimes it breaks app when the annoying error comes (I forgot))... I think you can also use the CyanogenMOD -> Performance -> A2SD (ext) but IDK how to use it...
See also Tips & Tricks To Increase Our Phone's Speed
Wow thanks!
So do I need to do this before I swap?
because when I dled swapper and swapped I ran free it was working fine but I felt no ingame improvment in anyway.
SO all I have to do is the above then swap and im good to go?
Ftwisawesome said:
Wow thanks!
So do I need to do this before I swap?
because when I dled swapper and swapped I ran free it was working fine but I felt no ingame improvment in anyway.
SO all I have to do is the above then swap and im good to go?
Click to expand...
Click to collapse
Swap is already done after partitioning... it's ready after reboot... the terminal is only used to check if it is mounted...
Only the Ext needs setup...
PS: I tried GingerDX and all Dalvik-Cache files went to the Ext without any setup ... Swapper makes mounting SD to PC very SLOW... SWAP Partition doesn't work with MiniCM9 3.0.2 but working on IScreamDX v004...
Ftwisawesome, learn to use the search function, most answers to your questions can be found when you show a little initiative.
This is the continuation of Neked-Nook but for Nougat. This should work with ALL S2's. So may I present to you for your flashing pleasure....
Neked_Maker_ROM
This is NOT A FULL ROM. This will modify your existing STOCK ROM. So DO NOT wipe /system in TWRP!!!!
You Flash this at your own risk!!!!! I am not responsible if your Tab breaks!!!!
MAKE A BACKUP IN TWRP FIRST!!!!!!
Snapdragon S2 Owners. Please read post #2 to confirm your mount points
ONLY FOR V1 AND V2!!!!
Features:
Based on T710XXU2DRB1 - for V3 ONLY FOR 2015 EXYNOS S'2s
Based on T710XXU2DQCL - But SHOULD work for ALL S2's
DO NOT FLASH V1 THEN V2!!!! FLASH ONE OR THE OTHER - These zips modify your build.prop so you will end up with extra lines in it.
All S2's
V1 will remove Google apps - Drive, Gmail2, GoogleTTS, Hangouts, Maps, Music2, Photos, Videos, Youtube - These are all downloadable
V2 will remove almost ALL Bloat - as above plus Microsoft, Samsung, stuff - you can look at the updater script to see specifics.
2015 Exynos S2's 2DRB1 ONLY
V3 removes as much as possible to make room for DualbootPatcher installed in /system and still keep all functionality
Wifi fix - thanks to @Ather V3 modifies it more for All regions
Smart view fix so you can watch tab on TV
Probably a couple other things.
Install:
You MUST ODIN N FIRST if you want to use this!!! (May work for "M" also) For V3, you must Odin 2DRB1
MAKE A BACKUP SECOND!!!!!
DO NOT TAKE ANY PLAYSTORE UPDATES
*If you wanna be lazy, you MAY be able to use this without Odin'ing first. But the apps will still be there in data. Which you SHOULD be able to uninstall. *No promises this way will work properly though.
This is NOT A FULL ROM. So DO NOT wipe /system in TWRP!!!
Flash Maker in TWRP
(Everything is automatic but wiping cache and dalvic can't hurt)
Profit!!
Possible bugs
DO NOT FLASH V1 THEN V2!!!! FLASH ONE OR THE OTHER - These zips modify your build.prop so you will end up with extra lines in it
V3 is for 2DRB1 ONLY!!! 2015 EXYNOS S2's
Downloads:
V1 - https://www.androidfilehost.com/?fid=745425885120737915
V2 - https://www.androidfilehost.com/?fid=673368273298960770
V3 - https://www.androidfilehost.com/?fid=890129502657587931 For 2DRB1 ONLY!!! See this post https://forum.xda-developers.com/showpost.php?p=75758700&postcount=47 for infos
819 Confirmed working. See post #36 Thanks to @Kingvtt
Should work for any S2 with /dev/block/36. Confirm this with app in Post #2
V1 - https://www.androidfilehost.com/?fid=673368273298962184
V2 - https://www.androidfilehost.com/?fid=673368273298962183
XDA:DevDB Information
[ROM]Neked-Maker-N, ROM for the Samsung Galaxy Tab S2
Contributors
engine95
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Stable Release Date: 2017-06-04
Created 2017-06-04
Last Updated 2017-06-04
Let me know if there are other apps to be removed from countries other than USA
The updater-scripts are all inclusive. Meaning you can flash /data and kernels, all in one zip. But you'll need to modify the script.
Snapdragon S2 owners: Use this app, https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en to ensure your /system and /boot are:
/system - /dev/block/mmcblk0p19,
/boot - /dev/block/mmcblk0p9.
Use 819 zips if:
/system - /dev/block/mmcblk0p36,
/boot - /dev/block/mmcblk0p18.
So let me be extra cautious and ask for confirmation that this ROm will work on the Galaxy Tab S2 SM-T819 variant? I see in the OP the statement that this may work on all Snapdragon S2s?
It worked properly. I see that in the future you plan on adding your custom kernel here. Will test the screen mirroring with my TV when I get back home next Friday.
Moe5508 said:
So let me be extra cautious and ask for confirmation that this ROm will work on the Galaxy Tab S2 SM-T819 variant? I see in the OP the statement that this may work on all Snapdragon S2s?
Click to expand...
Click to collapse
It has worked in the past. But there are new variants since then. Just use that app from post #2. If it matches, then you're good to go.
Dariusdd said:
It worked properly. I see that in the future you plan on adding your custom kernel here. Will test the screen mirroring with my TV when I get back home next Friday.
Click to expand...
Click to collapse
It works just fine on the 710, so it should work for all.
Hopefully, on the kernel. But I'm not sure on all the variants for Exynos yet
is it also für T819?
thanks!
@Moe5508 and @bavmouse
You both asked the same question. So have either of you done as I asked in the OP, post #2, and your questions?
It's a very simple app and I'd like to know also.
/system should be 19
and
/boot should be 9
If they are, then you're good to go
Edit: Or any other Snapdragon S2 owner for that matter. They are all the same.
I installed on t719, no problem at all. It is small debloat, but wifi fix is very significant and working @engine95 thanks , I also suggest much stronger debloat
ivanox1972 said:
I installed on t719, no problem at all. It is small debloat, but wifi fix is very significant and working @engine95 thanks , I also suggest much stronger debloat
Click to expand...
Click to collapse
Thanks.
You should have went with V2. Everything extra is gone. You could still flash V2, but there would be extra repeated lines in the build.prop that should be edited out.
Edit. Or tell me the extras so I can add them. I'd need the full name in sys app or priv app
Thanks boss.
Actually I applied v2. I was already done even bigger debloat but wifi fix was highly needed.
I don't understand statement about build. prop?
About bigger debloat I have followed this thread and until now no problem. Of course O not deleted most of gsm functions apps
https://forum.xda-developers.com/showthread.php?t=3533604
Sent from my SM-A810F using XDA-Developers Legacy app
after flashing this, system is lost.
ivanox1972 said:
Thanks boss.
Actually I applied v2. I was already done even bigger debloat but wifi fix was highly needed.
I don't understand statement about build. prop?
About bigger debloat I have followed this thread and until now no problem. Of course O not deleted most of gsm functions apps
https://forum.xda-developers.com/showthread.php?t=3533604
Sent from my SM-A810F using XDA-Developers Legacy app
Click to expand...
Click to collapse
The script writes to the build.prop each time it's flashed. I added 3 lines to the build.prop, so it'll keep adding those 3 lines each time it's flashed. Then you'll have repeat lines that aren't needed.
On the stronger debloat, I can't remove too much as this is for any S2. It's not build specific. So I just keep it basic for those that want to just flash and go. Not everyone is comfortable removing apps or editing build.props.
If I remove too much, it'll work for the WiFi variants, but not the LTE variants. Or vice/versa
bavmouse said:
after flashing this, system is lost.
Click to expand...
Click to collapse
There's only 2 reasons I can think of that that could happen.
You wiped /system in TWRP by accident
Don't do any wipes, when and if, you install this again. Let the script do all the work
or
Your /system is different from everybody else's.
Did you confirm that /system is at /dev/block/mmcblk0p19 ? While this is very rare, it's possible that the script over-wrote that block and that's why /system is gone. It got moved. But that shouldn't happen because the script also looks to the name of the block.
Do you have any more info that I could use to help you out? There have been over 18 DL's so far, and the original "Maker" has over 300 Dl's and this is the first time I have heard of this happening.
Edit: I guess you could also have a bad download. Make sure to compare the md5sum. AFH gives that with every DL.
i think it is a twrp problem. i did a system backup with twrp and afterwards system was gone again.
bavmouse said:
i think it is a twrp problem. i did a system backup with twrp and afterwards system was gone again.
Click to expand...
Click to collapse
You might have to use Odin to fix it. Then you can restore your backup. Just remember that Odin will wipe your internal SD. External SD won't be touched.
Also, and I hadn't thought of this, this is not a full ROM. This modifies your existing stock ROM. So if you wipe /system in TWRP, then it will be gone. I will update the OP.
I am still on Neked Nook 5.1.1. Will this work if I install it, or do I have to install marshmallow first?
Install:
You MUST ODIN N first if you want to use this!!! (May work for "M" also)
MAKE A BACKUP FIRST!!!!!
This is NOT A FULL ROM. So DO NOT wipe /system in TWRP!!!
Flash Maker in TWRP
what means: You MUST ODIN N first if you want to use this!!!
Thanks!
engine95 said:
Let me know if there are other apps to be removed from countries other than USA
The updater-scripts are all inclusive. Meaning you can flash /data and kernels, all in one zip. But you'll need to modify the script.
Snapdragon S2 owners I comfirmed this earlier, but it's nagging at me. Use this app, https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en to ensure your /system and /boot are:
/system /dev/block/mmcblk0p19,
/boot /dev/block/mmcblk0p9.
Let me know if its different. It shouldn't be.
Click to expand...
Click to collapse
Sent from my Samsung SM-T819 using XDA Labs
loooney2ns said:
I am still on Neked Nook 5.1.1. Will this work if I install it, or do I have to install marshmallow first?
Click to expand...
Click to collapse
It may? But it's 2 iterations behind, so you might as well Odin to Nougat. Updato is what most people are using to get the Odin .tar to upgrade.
bavmouse said:
Install:
You MUST ODIN N first if you want to use this!!! (May work for "M" also)
MAKE A BACKUP FIRST!!!!!
This is NOT A FULL ROM. So DO NOT wipe /system in TWRP!!!
Flash Maker in TWRP
what means: You MUST ODIN N first if you want to use this!!!
Thanks!
Click to expand...
Click to collapse
Now we have a problem. Your /system is blk039, not blk019 like everyone else. You will have to use Odin to fix your tablet. N is Android OS Nougat.
Odin is what the factory uses to upgrade and fix Samsung Tablets and phones. It's not difficult to use, and there are a lot of helpful posts on how to use it.
These posts have links to many things to help you out. https://forum.xda-developers.com/tab-s2/general/index-samsung-tab-s2-one-index-t3544310 and here https://forum.xda-developers.com/tab-s2/general/guide-root-tab-s2-t3205019
While I can change the script to install on the 819, you don't have a /system or working backup to restore it.
In "Disk info" app, go to settings and check the first 5 boxes. Then go back to the app and find out what blk039 is. And also what number /system and /boot are. Your /system shows blk039.
But if your using Disk info, and your tablet has no /system. How are you showing me that picture? Did you get it fixed? If so, give the info above so I can fix the script to work for the 819.
engine95 said:
It may? But it's 2 iterations behind, so you might as well Odin to Nougat. Updato is what most people are using to get the Odin .tar to upgrade.
Now we have a problem. Your /system is blk039, not blk019 like everyone else. You will have to use Odin to fix your tablet. N is Android OS Nougat.
Odin is what the factory uses to upgrade and fix Samsung Tablets and phones. It's not difficult to use, and there are a lot of helpful posts on how to use it.
These posts have links to many things to help you out. https://forum.xda-developers.com/tab-s2/general/index-samsung-tab-s2-one-index-t3544310 and here https://forum.xda-developers.com/tab-s2/general/guide-root-tab-s2-t3205019
While I can change the script to install on the 819, you don't have a /system or working backup to restore it.
In "Disk info" app, go to settings and check the first 5 boxes. Then go back to the app and find out what blk039 is. And also what number /system and /boot are. Your /system shows blk039.
But if your using Disk info, and your tablet has no /system. How are you showing me that picture? Did you get it fixed? If so, give the info above so I can fix the script to work for the 819.
Click to expand...
Click to collapse
I flashed the Firmware with Odin, now look the Screenshots:
"You will have to use Odin to fix your tablet. " How can i fix it?
bavmouse said:
I flashed the Firmware with Odin, now look the Screenshots:
"You will have to use Odin to fix your tablet. " How can i fix it?
Click to expand...
Click to collapse
Screenshot
[M.O.D. KERNEL Q]
*** NOTE: a dev has posted on TG the FOD fix for beta/ MIUI 12 forked from my code, download there! I asked for GitHub source to comply with XDA and will post once I have it and provide a link to the file link "Mi9/Mi9T Pro Optimization and Overclocking" Telegram has it now: https://t.me/joinchat/NNTe_E9G4ZcZKXCUrajFYQ ***
MIUI 11 Mi9/ 9T Pro MOD 1.5
MOD-Q 1.5 is for stable MIUI 11 variants for Mi9 only - Xiaomi.eu 11.0.5 stable is what it was built for, runs best on, just use it. The Mi9T Pro version supports MIUI 11 variants plus many AOSP builds. If you use an official MIUI 11 Xiaomi version you will get a warning message "Contact device manufacturer." You can ignore that, it means nothing. But I highly suggest using Xiaomi.eu 11.0.5, or another MIUI 11 variant like MiRoom or some use Revolution OS.
***DO NOT USE ANY PERFORMANCE (CPU/GPU/ETC) MAGISK MODULES WITH THIS FOR BEST PERFORMANCE!!! IT INSTALLS IT'S OWN OPTIMIZED MAGISK MODULE AUTOMATICALLY***
FP scanner will only work up to 11.0.5. Xiaomi keeps changing the code and not releasing it to made Dev builds not work. There were "patches" that worked until a few weeks back, but Xiaomi has yet again changed their FP scanner code. So I will not update the FP code, do not ask, it is a complete waste of time. Sorry, but Xiaomi.eu 11.0.5 and MOD 1.5 work very very well together.
Features:
835mhz GPU, Adreno Boost, Dynamic Fsync, Boeffla WL blocker (better battery idle), F2FS optimizations, LZ4 ZRAM. EXFAT USB/SDCard support added. Sultan Boost + PapaSmurf's Op7Pro tweaks, Dynamic Overclocking + Underclocking with frequency boost for smooth, fast, clean performance and fluid scaling. Many thanks to PapaSmurf who greatly influenced this kernel; portions are ported from his Op7 Pro Repo.
Mi9T Pro version also reported to work on AOSP ROMs using the original FOD implementation (Derpfest, MSM, CRDroid, Havoc, LOS).
Just use the Magisk Module it installs for you automatically when you flash the zip from TWRP, likely the best results will be obtained. SmartPack can be installed to choose between profiles under Performance Tweaks - battery / balanced / performance / gaming, although the default installed Magisk module is highly recommended by itself for optimal performance and good battery drain.
Github source has been added for MOD 1.5 here. Please read the Readme that's why it's there.
https://github.com/mrslezak/MODQ1.5
Releases are available here: Download them for your device and follow the instructions there. If you already have TWRP and Magisk, it will be easy. Just read please it will answer your questions.
https://github.com/mrslezak/MODQ1.5/releases/tag/MOD1.5
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[M.O.D. KERNEL PIE] Mi9 Android9 GPU830mhz F2FS data/cache Dynamic Fsync LZ4 WLblocker V2 [STABLE]
MOD Pie notes:
***New features added! Dynamic Fsync replaces the Fsync toggle (credits to author Paul Reioux aka Faux123 <[email protected]>), and Boeffla Wakelock blocker 1.1.0 (credits to author: andip71 <[email protected]>) has been added. The GPU830mhz runs on a higher regulator now so even 3DMark runs without issue, this is as stable as it gets. A battery saving Magisk Module has been added for longer life and scored 422.5K still on AnTuTu! It will throttle and hotplug (idle) cores as needed to save battery ***
Super tweaked kernel for the Mi 9. Best AnTuTu Benchmark 432K thus far, expect 420K-430K in daily operation with good battery life. This will vary based on the ROM selected. Stock AnTuTu is 370K. So you can run your phone faster than any production 855+ at the moment. This kernel is setup on purpose to allow anything from stock to maximum performance, you can set parameters as you like in a kernel manager.
GitHub Source: https://github.com/mrslezak/MODKernel-V2-Cepheus
Releases are available here:
https://github.com/mrslezak/MODKernel-V2-Cepheus/releases/tag/V2
TG Name: MattoftheDead
M.O.D. Kernel (MattoftheDead). This kernel is STABLE, everything works, it runs on any MIUI based ROM (MIUI Global Dev, MIUI China Dev, MiGlobe, Xiaomi.eu, AOSP, etc.). ***If you install this kernel and don't follow the tweak instructions, it runs exactly like stock. There is now a Magisk module that will run with the optimal settings to make this easy! *** So read up. You can apply any tweaks you'd like. These include:
GPU 830mhz overclock - stable and smooth. The GPU will throttle down when not being used to a lower mhz. The Magisk Module will enable the max 830mhz clock for you. Or you can go without if you have a dialcode supported GPU MaxFreq OC mode *#*#8106#*#*
ZRAM LZ4 data encryption enabled - fastest encryption method, smaller ZRAM sizes (512mb is good) work very well [2GB is the stock ZRAM default, LZO is the default kernel compression which is slow]. ZRAM is in-memory swap so it is ultra fast. This allows you to have more free RAM for apps to run.
F2FS data and cache partition support - full ICE AES 256bit encryption. Note only @mauronofrio TWRP 3.3.1-39 + supports F2FS partition mounting so you MUST use this TWRP recovery!!!
F2FS has been tested on MIUI Global Dev 9.6.27 and Xiaomi.eu 9.7.22, 9.8.1, MiGlobe, RevOS, AOSP, Havoc thus far (more added daily) and read/write speeds and app access are definitely fast. Support was enabled by working directly with @mauronofrio on XDA (thanks Mauro) so we originated F2FS support for Mi9 - there are also F2FS kernel tweaks that help the speed in the kernel.
BOEFFLA Wakelock Blocker 1.1.0 - blocks wakelocks and allows you to change what gets blocked that is waking up your phone and preventing deep sleep. There are defaults blocked already in this build that are known to be blockable safely. If you want to add more, use SmartPack Kernel manager under Wakelocks. It will also show you what apps are causing them and the frequency so you can disable the ones that are not needed.
If you want to join in the discussion and see updates in realtime, World MI9 & Mi9T Pro Optimization and Overclocking is a TG group which has many things related to MOD and any other kernels, mods for the phone, Magisk Modules, all types of things for the devices.
Step 1: [KERNEL REQUIRED FILES]
Go to the releases page posted earlier and download everything.
Step 2: [ROM SELECTION]
If you already have a Pie MIUI based DEV ROM installed, you can continue to use it. Global Dev 9.6.27 is recommended. But this supports up to Xiaomi.eu 9.8.1. If you want to use a new MIUI based ROM, download it and setup the device (between these ranges of releases - some like MiRoom, some like stock, some like Xiaomi.eu). If you are clean flashing everything, don't bother restoring all the apps - they will be deleted when you switch to F2FS. Just set it up so you can login and get to the default menu with the default apps displayed. Either way, you will have to setup the device as a new phone. So back up all your user data (photos, downloads, etc), apps, etc. using Google Drive, Xiaomi Cloud, Titanium Backup Pro, or any other app that backs up apps and settings. It's often easiest to put them on your PC since you will be plugged into it during this install process with your USB cable.
Step 3: [MAURO TWRP INSTALLATION FOR F2FS SUPPORT]:
Boot Mi9 holding Power + Volume Down
Hook up to your phone to the PC with the charging cable
Open a command prompt. Go to your Minimal ADB and Fastboot folder.
Type: fastboot devices
And hopefully you see your device ID pop up. If not you don't have the right driver, the cable is bad, or something else is wrong. Search Google.
Next flash Mauro TWRP:
fastboot flash recovery twrp-3.3.1-41-cepheus-mauronofrio.img (or use his latest from the link at the bottom of this thread)
Hopefully you see it flash to the device in a few seconds successfully and it's ready to go.
Booting to TWRP:
Turn off your phone. Now hold down power + volume up. Once the boot Logo appears, let go of the power button but keep holding volume up. TWRP should boot. If not, try again. I usually have to remove the phone case. Now enter your password and proceed to the next section. If it asks you if you want to keep the system read only SAY NO! You will be modifying system components, keep it writable to avoid installation issues.
Step 4: [FLASHING THE M.O.D. KERNEL]
Check the releases page posted above. Just unzip the file there and flash via TWRP as an image to boot. It's patched with Magisk already.
Step 5: [CONVERT EXT4 TO F2FS}:
Converting EXT4 data and cache partitions to F2FS:
Check the releases page posted above for fstab_patch_F2FS_MI9_Cache_NoBarrier.zip required to enable F2FS. You MUST flash this in TWRP or your OS will NOT be able to boot an F2FS data partition!!!! This file has been kanged all over the internet, it was created here. Feel free to use it, everyone already is.
***Note flashing TWRP / Install / fstab_patch_F2FS_MI9_Cache_NoBarrier.zip MUST be repeated any time you change ROMs or you won't have access to your data!!! So back this up!!!!***
Boot back into TWRP. You will need to go to Wipe, Advanced Wipe, Click Data, Repair or Change File System, Change File System, and click F2FS. Swipe to change. It will format and you'll have nothing on your data partition. Next format cache. Go to Wipe, Advanced Wipe, Click Cache, Repair or Change File System, Change File System, now click F2FS. Swipe to change. Again it will format and be wiped.
Step 6: [SETTING UP YOUR "NEW" PHONE]:
Next, reboot to System. The device should boot up and welcome you to your "new" device. It has no data apps so it has to be new. You will have to login to your Xiaomi account if it is associated with the device. Then you can choose to restore from a Google Backup and next from Xiaomi Cloud. You can do either one to get your apps back. I would suggest Xiaomi Cloud after Google completes all its downloads - it will place icons in the right places and install your root apps if you had them. And after setting up your apps, now boot back to TWRP and make a Backup. Now for this Nandroid backup you should backup data, boot, dtbo, and vendor partitions (vendor has the fstab.qcom file that allows your F2FS supported partition to boot now). Even if you save to your internal device initially, be sure to put it on a PC for safe keeping. Then If you accidentally wipe your partition later, you can skip importing, get to the main screen after minimal setup completes, enable file transfer from the connected PC, and then copy the Nandroid backup to your Internal Memory. Boot into TWRP and restore the backup and you're back in business.
Step 7: [INSTALLING MAGISK MANAGER AND KERNEL MANAGER]:
So now you install the MagiskManager-v7.3.2.apk to enable all root functions. If you want Google Pay and anything else setup posts are here in the Mi9 forum that show you how. Generally hide all banking apps, trading apps, Google Pay, GMS, etc. And I suggest installing GMS doze for better battery life and the Mi9 Auto Brightness fix.
In addition, to have the MOD kernel setup for the best performance, go into Magisk Manager, Modules, and flash the (Magisk)MOD-Battery-Saver+_v2.zip from the releases page. It will auto set all the parameters the kernel features, and does a great job with extending battery life at the same time.
This is the best setup for performance. Pictures are included below.
If you would like to change the settings, you need a kernel manager. So next you can install the Smart Pack APK SmartPack_Kernel_Manager_v8.7.apk to enable or disable all the tweaks you desire.
Pictures are attached below to show the TWRP screens for flashing and F2FS partition conversion. Also the settings of best performance using Smart Pack kernel manager are here. If you want to change any of the best settings after flashing the Magisk Module, do it in the kernel manager of your choice and set on boot - where to change those options is in the pictures below for SmartPack.
Enjoy!
Mauro TWRP
https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
SmartPack Kernel Manger
https://forum.xda-developers.com/android/apps-games/app-smartpack-kernel-manager-t3854717
FK Kernel Manager CPU Profile
https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en_US
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
And one last thing. I have been working with some of the most well known devs out there on XDA on Telegram, Private Messaging, and other channels to get this kernel where it is - but I have no XDA presence. I've helped hundreds of people on Telegram setup their systems or diagnose their issues. If you find this post useful, helpful, innovative, or install my kernel and like it, please click the Thanks button to acknowledge the work that I've done to get the Mi9 to this point. It would be greatly appreciated to get some thank yous for all the hours I've put into this development work for the Mi9, and provides some motivation to keep improving. Other kernels are on the way as well for more Xiaomi / Redmi devices if I feel some love from the community. Much appreciated!
Thanks goes out to @smeroni68 and @mauronofrio for helping fix the fstab.qcom zip that cost several hours of pain yesterday for users and I on Telegram that did not have the Vendor partition mounted when flashing the old fstab.zip file - it will flash now mounted or not from TWRP. And thanks to @ilia1985 for providing a Magisk Module template for the kernel manager settings, now OC setup doesn't even need a kernel manager!
***DISCLAIMER - APPLYING ANY ROOT MODS IS ALWAYS AT YOUR OWN RISK! I AM NOT RESPONSIBLE FOR BRICKED DEVICES, DAMAGE OR OTHER THAT MAY OTHERWISE OCCUR. THIS HAS BEEN TESTED EXTENSIVELY BUT USE AT YOUR OWN RISK***
First.. that's the first time.
Huge thanks to the dev for their contribution!
Awesome work!
What does "miui based rom" mean?
Is Havoc OS miui based?
Troomak said:
Awesome work!
What does "miui based rom" mean?
Is Havoc OS miui based?
Click to expand...
Click to collapse
Nah, it's aosp
Looks like it's base on last one version of android9 MIUI DEV 9.8.1 to modify its kernel, doesn't it ?
So it's not base on linux kernel 4.14.139 to develop ?
Kris
Kris Chen said:
Looks like it's base on last one version of android9 MIUI DEV 9.8.1 to modify its kernel, doesn't it ?
So it's not base on linux kernel 4.14.139 to develop ?
Kris
Click to expand...
Click to collapse
4.14.83 per the hardware device settings. Q is already upstreamed to the latest Linux and CAF so just waiting on a source release so kernels can be made. No need to spend time upstreaming unless another dev wants to (I'm in contact with the other kernel dev here on XDA we're working together now, he may upstream). He upstreamed his to 4.14.139 and will pull my source repo soon to fix bugs in his build so he may just upstream this kernel or fix bugs in his kernel in the process. Collaboration is a good thing. I've been waiting for assistance for a long time and it's good to team up with others devs. We don't get paid we do this as a hobby.
Thanks !
Can I use Ex kernel manager to tune kernel parameters ?
In another one - Will there CPU/GPU frequency table exist to choose which one of frequency combination I want to use base on condition of phone usage - Gaming, multimedia application, and general usage !
mslezak said:
4.14.83 per the hardware device settings. Q is already upstreamed to the latest Linux and CAF so just waiting on a source release so kernels can be made. No need to spend time upstreaming unless another dev wants to (I'm in contact with the other kernel dev here on XDA we're working together now, he may upstream).
Click to expand...
Click to collapse
Kris Chen said:
Thanks !
Can I use Ex kernel manager to tune kernel parameters ?
In another one - Will there CPU/GPU frequency table exist to choose which one of frequency combination I want to use base on condition of phone usage - Gaming, multimedia application, and general usage !
Click to expand...
Click to collapse
Yes EX Kernel Manager is a good one to use. You will have to experiment with if it can lock in frequencies. Follow the guide for CPU settings they are optimal. You could by app adjust if needed and if it is supported by EX. Some support per app some don't. I think SmartPack does. The issue is that the 830gpu clock is an additional clock. The others are all stock clocks. This is for maximum battery life and compatibility. The highest 830GPU is only fully settable via dial code *#*#8106#*#* at this time - try in your ROM to see if it is supported. In some KM you can set max and min to 830mhz and it will lock in the frequency (FK) although this was only tested for 1 day on an unstable build (too hot thermals). More tests are needed, feel free to try and post what you observe.
hiperglyde said:
Nah, it's aosp
Click to expand...
Click to collapse
Many AOSP builds are still on Xiaomi underlying code. The test would be to install the TWRP mentioned and take a backup of boot and dtbo partitions. Stay on EXT4. Then flash the restore TWRP provided and see if it boots. I user has already made it to the logo screen on AOSP using this method. He is using an unencrypted partition though. If you are on an encrypted partition the likelihood of it working is higher. The TWRP is bootable from fastboot as well so you will be able to access recovery. Advise you save the backup to removeable media / computer before flashing. Report back your results please.
Hey There.
I am trying to mount the fsqtab.qcom an do not get how to do it on my Mi9 using these directions?
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
How do you do whats listed above 'precisely'?
I can make everything else work. I just cannot seem to get this file inserted in Vendor?
Can you help please
(my profile says senior member but I am really not )
Great work!! Thanks for the kernel.
Any chance Kcal will be possible?
Finaly installed it on aosp extended.Thanks for developer
Bryceicle1971 said:
Hey There.
I am trying to mount the fsqtab.qcom an do not get how to do it on my Mi9 using these directions?
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
How do you do whats listed above 'precisely'?
I can make everything else work. I just cannot seem to get this file inserted in Vendor?
Can you help please
(my profile says senior member but I am really not )
Click to expand...
Click to collapse
Did you turn on the option ADB sideload in twrp? Under advanced?
*justintime* said:
Did you turn on the option ADB sideload in twrp? Under advanced?
Click to expand...
Click to collapse
I just installed it via root browser
Two ways you can do:
1.To use root explorer copy fstab.qcm under /vendor/etc ...
2.Enter TWRP and mount vendor parition, then copy fstab.qcm under /vendor/etc ...
Kris
QUOTE=Bryceicle1971;80122399]Hey There.
I am trying to mount the fsqtab.qcom an do not get how to do it on my Mi9 using these directions?
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
How do you do whats listed above 'precisely'?
I can make everything else work. I just cannot seem to get this file inserted in Vendor?
Can you help please
(my profile says senior member but I am really not )[/QUOTE]
*justintime* said:
Did you turn on the option ADB sideload in twrp? Under advanced?
Click to expand...
Click to collapse
No. Does that allow the terminal to find the file in your USB?
I've been leaving the extracted files in my c-type USB plugged into the cell
---------- Post added at 10:30 AM ---------- Previous post was at 10:26 AM ----------
Kris Chen said:
Two ways you can do:
1.To use root explorer copy fstab.qcm under /vendor/etc ...
2.Enter TWRP and mount vendor parition, then copy fstab.qcm under /vendor/etc ...
Kris
QUOTE=Bryceicle1971;80122399]Hey There.
I am trying to mount the fsqtab.qcom an do not get how to do it on my Mi9 using these directions?
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
How do you do whats listed above 'precisely'?
I can make everything else work. I just cannot seem to get this file inserted in Vendor?
Can you help please
(my profile says senior member but I am really not )
Click to expand...
Click to collapse
[/QUOTE]
Thanks. I'll try your an other suggestions
*justintime* said:
Did you turn on the option ADB sideload in twrp? Under advanced?
Click to expand...
Click to collapse
Have tried to turn on ADB side load an it keeps failing after a long wait? What am i missing?
---------- Post added at 12:07 PM ---------- Previous post was at 12:00 PM ----------
mslezak said:
[M.O.D. KERNEL] Mi 9 Android 9 Pie GPU830mhz F2FS data/cache Fsync LZ4 ZRAM [STABLE]
MOD-KERNEL-TOOLS.zip -> kernel and all software to use the features of the kernel: https://mega.nz/#!TopRnIDK!6GbL_8QPToK0oLCSDnJ_d9EUnZ9AflDgf-9pu6JCiKo
GitHub Source: https://github.com/mrslezak/Xiaomi_Kernel_OpenSource branch: cepheus-p-oss
Telegram Group: https://t.me/joinchat/NNTe_E9G4ZcZKXCUrajFYQ
Telegram Name: @MattOftheDead
M.O.D. Kernel (MattoftheDead). This is a kernel project that has been going on for months now behind the scenes. It is STABLE, everything works, it runs on any MIUI based ROM (MIUI Global Dev, MIUI China Dev, MiGlobe, Xiaomi.eu, etc.). Android 9 (Pie) only as Android 10 has not been released and Xiaomi decided to change the kernel components (boot.img and dtbo.img will flash to Q, but no WIFI, no calls, and colors are "off."). If you install it and don't follow the tweak instructions, it runs exactly like stock. You can apply any tweaks you'd like. These include:
GPU 830mhz overclock - stable and smooth - most MIUI Dev based ROMs can enable via dialing *#*#8106#*#* - enable MaxFreq GPU Mode - you can test before installing. The GPU will throttle down when not being used to a lower mhz.
FSync toggle (enable/disable) - disable gives higher speed at the risk of data corruption if a system crash occurs. Note I've used this 4 months with no issues, if you use stable software you are less likely to run into problems. Eventually dynamic Fsync will be added if I ever have time or help (writes to disk when screen is off, safer than just disabling).
ZRAM LZ4 data encryption enabled - fastest encryption method, smaller ZRAM sizes (512mb is good) work very well [2GB is the ZRAM default, LZO is the default kernel compression which is slow]
F2FS data and cache partition support - support with full ICE AES 256bit encryption. Note only @mauronofrio TWRP 3.3.1-39 + supports F2FS partition mounting so you MUST use this recovery!!!
F2FS has been tested on MIUI Global Dev 9.6.27 and Xiaomi.eu 9.7.22 thus far and read/write speeds and app access are definitely fast. Support was enabled by working directly with @mauronofrio on XDA (thanks Mauro) so we originated F2FS support for Mi9 - there are also F2FS kernel tweaks that help the speed.
Now if you want to install this kernel, you can right away and use it on EXT4 (default for all Xiaomi ROMs). To use with F2FS you will need to adb push a modified fstab.qcom file to /vendor/etc/fstab.qcom. Or you can use a root browser and just copy it over if you are currently rooted. It will boot either EXT4 or F2FS with encryption with the same fstab.qcom file. And then you will enter the danger zone once it is time to enable F2FS! You will have to backup all your apps. This means MiCloud (for root apps this is good, saves APKs and settings), Google backup (the backup frequency seems random to me, although if a backup is recent you'll get all your PlayStore apps back), Titanium Backup Pro ($ PAID, you can't use the free version as the internal data will be wiped when the partition is formatted), or search for another backup solution online. Nandroid backups won't work after conversion either as they include the partition format (EXT4, F2FS, etc.) so don't bother. More on this later in the thread.
To save everyone time and space (I don't have a good way to upload files), join my Telegram channel. Read the instructions and you will be up and running in no time. They are outlined in great detail there along with tons of other discussions around optimizations and benchmarks. However, I will attempt to summarize installation on XDA as best as I can. Telegram Link: https://t.me/joinchat/NNTe_E9G4ZcZKXCUrajFYQ -> XDA MI9 Optimization and Overclocking
I have also provided a Mega.nz zip file with a bunch of tools you can use to get up and running. It comes with the modified kernel (boot.img GPU830_F2FS_Fsync_CRC_LZ4_boot.img and dtbo.img GPU830_F2FS_Fsync_CRC_LZ4_dtbo.img), the modified fstab.qcom file for encrypted F2FS support, the Mauronofrio TWRP version required twrp-3.3.1-39-cepheus-mauronofrio.img, Magisk-v19.4.zip Canary, MagiskManager-v7.3.2.apk, SmartPack Kernel Manager com.smartpack.kernelmanager-v8.7-20190815-release.apk to set tweaks along with a file SmartPack_init.d.txt that can be copied and pasted directly into SmartPack (in the menu, Init.d, enable Init.d, add new, copy and paste the text in, save it, and everything will be setup optimally) - NOTE init.d does not work on all ROMs (even with it enabled on boot in the software), so you may need to click on the profile under Init.d manually to execute after boot. A Franco Kernel Manager CPU Profile is included Maxfreq-CPUs-FK_Kernel_Manager_Profile if you use FK since it won't let you set CPU frequencies in the software (included just for people who have FK or prefer it over SmartPack - it won't setup ZRAM to LZ4 or 512mb for you, or toggle FSync, so you will have to manually do it if you use FK). Also the latest Windows Minimal ADB and Fastboot minimal_adb_fastboot_v1.4.3_setup.exe is included, although you probably already have it since you have a bootloader unlocked phone
Now some very basic steps to the more complicated, much you should already know since you clicked on a custom kernel post!!!!
Flashing Mauro TWRP:
Boot Mi9 holding Power + Volume Down
Hook up to your phone to the PC with the charging cable
Open a command prompt. Go to your Minimal ADB and Fastboot folder.
Type: fastboot devices
And hopefully you see your device ID pop up. If not you don't have the right driver, the cable is bad, or something else is wrong. Search Goggle.
Next flash Mauro TWRP:
fastboot flash recovery twrp-3.3.1-39-cepheus-mauronofrio.img
Hopefully you see it flash to the device in a few seconds sucessfully and it's ready to go.
Booting to TWRP:
Turn off your phone. Now hold down power + volume up. Once the boot Logo appears, let go of the power button but keep holding volume up. TWRP should boot. If not, try again. I usually have to remove the phone case.
Flashing boot.img, dtbo.img, and Magisk19.4.zip:
You can do this manually or from a TWRP backup. In the MOD-KERNEL-TOOLS zip file, you can unzip [TWRP-Restore-Backup] MODKernel-Magisk19.4 to internal storage or OTA SD card / USB drive, click Restore, and restore boot and dtbo. Then it is already patched with Magisk 19.4 (you have root access). Then reboot. Now for the more manual method. You can select Install. Then select Flash Image. Select GPU830_F2FS_Fsync_CRC_LZ4_boot.img and flash to the boot partition. After flashing, go back in TWRP and flash GPU830_F2FS_Fsync_CRC_LZ4_dtbo.img to the dtbo partition. Now go back in TWRP again and click on Flash Zip. Select Magisk19.4.zip and flash. After this completes, reboot.
Setting up F2FS data and cache partitions:
The process to setup F2FS is to first download a compatible ROM if you don't already have one installed (MIUI based, Android 9 (Pie), this includes MIUI Dev, Xiaomi.eu, MiGlobe, Revolution OS, etc.) ENSURE ANDROID 9 PIE: 9.8.1 variants are usually the last Android Pie build. After downloading, you can install it as a new phone after following the guide below so don't bother setting anything up other than a Xiaomi account login if prompted; don't restore apps yet either. You can setup with defaults now and not import apps. You should make it to the home screen though. All apps will be deleted after formatting.
You will be setting up a new phone and will have to login to all your apps over again. So to reiterate, MAKE COPIES OF ALL YOUR PROGRAMS BEFORE DOING THIS! Xiaomi Cloud, Google Backup, Titanium Backup, etc. - use something not on your phone, NOT a Nandroid backup! NOT in internal storage! (it will be wiped)!
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
Now in TWRP, you will need to go to Wipe, Advanced Wipe, Click Data, Repair or Change File System, Change File System, now click F2FS. Swipe to change. It will format and you'll have nothing on your data partition. Next format cache. Go to Wipe, Advanced Wipe, Click Cache, Repair or Change File System, Change File System, now click F2FS. Swipe to change. Again it will format and be wiped.
Next, reboot to System. The device should boot up and welcome you to your "new" device. You will have to login to your Xiaomi account if it is associated with the device. Then you can choose to restore from a Google Backup and next from Xiaomi Cloud. You can do either one to get your apps back. I would suggest Xiaomi Cloud after Google completes all its downloads - it will place icons in the right places and install your root apps if you had them. If you accidentally wipe your partition later (as I just did while making this tutorial, ouch), you can skip importing, get to the main screen, enable file transfer from the connected PC, then copy the Nandroid backup you absolutely should make and transfer to a PC right after setting all your apps up (logging in etc.). Now for this Nandroid backup you should backup data, boot, dtbo, and vendor partitions (don't forget that fstab.qcom we put here!). Even if you save to your internal device initially, be sure you later put it on a PC for safe keeping. I am just now copying back my TWRP directory to restore my phone this moment as I type...
Pictures are attached below to show the TWRP screens. Also the settings for the best performance using Smart Pack kernel manager included in the ZIP file download (will add after I restore). And a picture of the dial code + GPU Max Freq screen where you turn on the 830mhz GPU clock. Enjoy!
Links to XDA files included in the MOD-KERNEL-TOOLS.zip:
Mauro TWRP
https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
SmartPack Kernel Manger
https://forum.xda-developers.com/android/apps-games/app-smartpack-kernel-manager-t3854717
FK Kernel Manager CPU Profile
https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en_US
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
No system no boot an a bootloop. This enhancement is a bit complex an I'm kind of confused?
Bryceicle1971 said:
Have tried to turn on ADB side load an it keeps failing after a long wait? What am i missing?
---------- Post added at 12:07 PM ---------- Previous post was at 12:00 PM ----------
No system no boot an a bootloop. This enhancement is a bit complex an I'm kind of confused?
Click to expand...
Click to collapse
Witch rom are you using?
Inviato dal mio MI 9 utilizzando Tapatalk
smeroni68 said:
Witch rom are you using?
Inviato dal mio MI 9 utilizzando Tapatalk
Click to expand...
Click to collapse
Xiaomi.eu for Mi9 9.7.22 v10-9
Bryceicle1971 said:
Have tried to turn on ADB side load an it keeps failing after a long wait? What am i missing?
---------- Post added at 12:07 PM ---------- Previous post was at 12:00 PM ----------
No system no boot an a bootloop. This enhancement is a bit complex an I'm kind of confused?
Click to expand...
Click to collapse
You copied fstab.qcom to /vendor/etc/? Boot into recovery, attached to your PC. Then from a command prompt in Minimal ADB and Fastboot,copy fstab.qcom there. Then type: adb devices. It should show a device ID. Then type adb push fstab.qcom /vendor/etc/. It should say succeeded. Then reboot. This only makes a difference if you are on F2FS.
If you aren't booting to system go ahead and try the TWRP recovery version - unzip and flash that package to boot and dtbo from TWRP Restore. It's already patched with Magisk 19.4 and several people are on it that had issues flashing the files separately.