Q&A for [KERNEL][UNOFFICIAL][PERSONAL BUILDS]DorimanX
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][UNOFFICIAL][PERSONAL BUILDS]DorimanX. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Great to see the rebirth of the best kernel available for the S2! Would love to see TRIM and LP support! Best of luck to the dev
@stelicristi
Will U add Synapse support ?
Wysłane z Cyanofonika 12 beta...
MikiGry said:
@stelicristi
Will U add Synapse support ?
Wysłane z Cyanofonika 12 beta...
Click to expand...
Click to collapse
I have asked him on the development thread too. He seems make a lot of promises become true. Maybe he will be the next active dorimanx developer.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
acydwarp said:
Great to see the rebirth of the best kernel available for the S2! Would love to see TRIM and LP support! Best of luck to the dev
Click to expand...
Click to collapse
Yes, if he does this and also bring ext4 support of SD cards, I will call him a legend or god or whatever he wants.
gsstudios said:
I have asked him on the development thread too. He seems make a lot of promises become true. Maybe he will be the next active dorimanx developer.
Click to expand...
Click to collapse
I'm still new to SII forum but i now sth about this kernel. If he will bring DorimanX kernel to live (not like 'background activity') well..
It will be AWERSONE :
Kernel with tones if costomalizations , still up to date , compatible with all android versions... Unbelivnable!
Wysłane z Cyanofonika 12 beta...
Hi,
I'm on SlimSaber 21/12. I :installed your kernel but I have some troubles with from first installation:
- I got an advise log saying that my partitions are corrupted (I have a resized 1gb /System
- I can't either reinstall the kernel, recovery or ROM because "install zip on /storage/sdcard0" says there are no files (and I can't explore away).
- WiFi does not finish to be enabled (no networks shown).
Did I miss something when I flashed?
Thank you for your effort.
fragel said:
Hi,
I'm on SlimSaber 21/12. I :installed your kernel but I have some troubles with from first installation:
- I got an advise log saying that my partitions are corrupted (I have a resized 1gb /System
- I can't either reinstall the kernel, recovery or ROM because "install zip on /storage/sdcard0" says there are no files (and I can't explore away).
- WiFi does not finish to be enabled (no networks shown).
Did I miss something when I flashed?
Thank you for your effort.
Click to expand...
Click to collapse
Something went wrong with the installation? I would advise you to go into stweaks, go to the 'other' tab and find 'fix data'. Enable it and reboot. Note: Make sure you have a backup of all of your apps!
gsstudios said:
Something went wrong with the installation? I would advise you to go into stweaks, go to the 'other' tab and find 'fix data'. Enable it and reboot. Note: Make sure you have a backup of all of your apps!
Click to expand...
Click to collapse
Thank you.
While installing no errors were shown.
After first booting, the log error about partition corrupted (and the recommendation to go into stweaks to enable "fix data") was shown. I followed the recommendation, but problems remain. Maybe I did not a full clean installation of the kernel? (just wiped cache and dalvik).
First thing I tried was to go back into recovery and reinstall the kernel but, as I said previously, recovery is not able to explore folders (appears as /storage/sdcard0 unmounted, but mounting does not work either) .
Any advise to reinstall the kernel or the same ROM without passing by ODIN?
Need to say that the phone boots and "works" (seems very busy though), but the problems wrote in my previous post are there.
Thanks.
Edit: I forgot saying that when going into STweaks, a message appears at the beginning during a second:"Unexpected error!" and later disappears and goes into the tool as usual.
Edit 2: Reflashed SlimSaber from adb sideload and everything came back. It would be nice if you could indicate some indications in order to do a proper install of this kernel.
fragel said:
Thank you.
While installing no errors were shown.
After first booting, the log error about partition corrupted (and the recommendation to go into stweaks to enable "fix data") was shown. I followed the recommendation, but problems remain. Maybe I did not a full clean installation of the kernel? (just wiped cache and dalvik).
First thing I tried was to go back into recovery and reinstall the kernel but, as I said previously, recovery is not able to explore folders (appears as /storage/sdcard0 unmounted, but mounting does not work either) .
Any advise to reinstall the kernel or the same ROM without passing by ODIN?
Need to say that the phone boots and "works" (seems very busy though), but the problems wrote in my previous post are there.
Thanks.
Edit: I forgot saying that when going into STweaks, a message appears at the beginning during a second:"Unexpected error!" and later disappears and goes into the tool as usual.
Edit 2: Reflashed SlimSaber from adb sideload and everything came back. It would be nice if you could indicate some indications in order to do a proper install of this kernel.
Click to expand...
Click to collapse
I'm glad you solved your problem. To install the kernel properly, follow these steps:
1. Download sgs2kernelwipe by hawker onto your phone(you can find it in gustavo kernel thread).
2. Download the latest version of dorimanx kernel onto your phone
3. Reboot your phone into recovery
4. Install the kernel wipe zip first
5. Then install the kernel
6. Reboot
(Note: I assume you know how to flash everything already so I simplified it).
Also, I advise you to wait until a newer build is released as the current personal build has some problematic bugs.
I was able to install this kernel, but my internal sdcard partition was not detected properly, on sdcard0 there was a 300MB empty partition instead of my 10 gig one.
I'm on the latest Markox CM, had Gustavo's kernel previously and used the kernel cleanup script. Have a modified PIT with bigger data partition and small preload.
After flashing back Gustavo's, everything's fine.
EDIT: forgot to say, my internal sdcard is ext4 formatted
_petike said:
I was able to install this kernel, but my internal sdcard partition was not detected properly, on sdcard0 there was a 300MB empty partition instead of my 10 gig one.
I'm on the latest Markox CM, had Gustavo's kernel previously and used the kernel cleanup script. Have a modified PIT with bigger data partition and small preload.
After flashing back Gustavo's, everything's fine.
EDIT: forgot to say, my internal sdcard is ext4 formatted
Click to expand...
Click to collapse
There are still a lot of issues with the personal build of dorimanx. If you still want to use dorimanx, stick with the unofficial dorimanx by cybernetus. The problem is caused either by the recovery or broken implementation of something.
Cant open STWeaks
Hi! i can't open swteaks app, (root granted) it throw a "unexpected error". Already tried to delete data-cache of the app and wipe cache/dalvik cache of whole rom. Any help? thanks!
jjhaohao said:
Hi! i can't open swteaks app, (root granted) it throw a "unexpected error". Already tried to delete data-cache of the app and wipe cache/dalvik cache of whole rom. Any help? thanks!
Click to expand...
Click to collapse
Which version of personal build are u using.. I have installed build #2 and have no problem with root in my spare s2..
It could be many reason for receiving unexpected error
* Go to settings app and select ->developer options->root access-> Apps
* Check whether u have installed binary after flashing Dorimanx Personal build
* Dont update su app from playstore and use the SU app that came with kernel.
unable to download
Can someone share a working link for builds 2 and 3 please? Thanks
Hey just some quick results about my experience so far with Build 3
I'm on slimsaber 21/12/2014, coming from Cybernetus 10.44v007. It's a fairly new wipe but i've been having major issues with it prior to the personal build of dorimanx.
WiFi password kept being forgotten. This happened 7 or 8 times. I managed to fix it by typing in the password, connecting, selecting "forget network" and then typing it in again.
Battery drain seems comparable to my previous settings, WiFi is significantly faster to connect and unless I'm seeing things, signal seems much stronger too.
I used fstrim (lagfix) and everything went better than expected. Phone responsiveness seems to be through the roof (whether this is trim or something else, its pretty night and day).
So far all stable.
i cani can't move big apps in sd card. what's a problem
ext4
Hello guys,
someone here is using this kernel with ext4 on the internal sd card? As soon as i switch to the kernel, my internal ext4 formated card doesnt get mounted, until i switch to stock kernel again.
Somebody also have ext4 successfull running? Or is it only me with this mount problem?
I hope someone could give a try in LP kernel to full support init.d and swap. Basically, S2 lacks of memory, and I already acomplished the internal<->external memory swap fix, by using apollo's kernel, 'cause it have init.d support. But it lacks the support to OC. DorimanX in that matter, have a well balanced kernel for JB and KK. With the possible LP support we could have a very good balanced performance for our excelent phone, with 4 years old! It's a matter of time...
---------- Post added at 04:51 PM ---------- Previous post was at 04:46 PM ----------
aCIDsLAM said:
Hello guys,
someone here is using this kernel with ext4 on the internal sd card? As soon as i switch to the kernel, my internal ext4 formated card doesnt get mounted, until i switch to stock kernel again.
Somebody also have ext4 successfull running? Or is it only me with this mount problem?
Click to expand...
Click to collapse
Try Paragon's app. Should help you with the support automatically and it's free. But I think DorimanX's kernel already support that filesystem.
It's there any problem If I'll flash V8.44v005 over stock kernel with 3e recovery?
aef-em said:
hi,
I flashed your kernel (Kernel_Dorimanx-V10.44-_15-20_-_27-01) from Kernel_Dorimanx-V10.44v008.
then the stweak stop working. when launching it, all i get is the title bar and that is it.
tried to reset the stweak settings from the recovery, wipe dalvik and cache, and use HawkernelWipeV1.02, and then re-flash.
also tried to reset the superSU permissions for the stweak.
also - maybe i should mention - that lag fix button is greyed out - and says that TRIM is not supported.
what am i doing wrong??
btw the ROM i'm using is the latest cm11 nightly..+ updated superSU and busybox.
BIG thanks for all the good people around here!
Click to expand...
Click to collapse
I am using this kernel with latest nightly (as already with all nightlies since march) without any problem. Maybe redownload and try once more?
Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the Nexus One. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. I've only tested it quickly on my Nexus One, and it seems to work.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-passion.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-passion.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Thanks for compiling and posting this update here. I hope it works better than 3.0.0.5
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
gwassef said:
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
Click to expand...
Click to collapse
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
I got it damaged 2 times, I thought it was my S2E app, but when i sent them they told me remove the 3.0.0.5 as it is known with this issue, install an older version. Since i installed the release before this one, i have no problems at all.
zyonee said:
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
zyonee said:
If you're testing it, let me know if it works.
Click to expand...
Click to collapse
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
Should work, but you'll need to try it.
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
joesatri said:
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
Click to expand...
Click to collapse
Is the recovery properly flashed? Works well on my NS
Sent from my Nexus S using Tapatalk
sorry, blonde moment :L
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Spakainz said:
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Click to expand...
Click to collapse
You'll have to ask koush or the other devs about that. I only compiled from source. I'm not that skilled at modding this kind of code...
Sent from my Nexus S using Tapatalk
This recovery works well for me. Flashed using fastboot.
I also used this recovery to reformat the sd-ext partition and now my nandroid backups complete without freezing (they would freeze on the sd-ext backups last time requiring a battery pull).
Thanks for compiling and sharing this!
-D
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
This Corrupts EXT partition!
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
sir*mez said:
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
Click to expand...
Click to collapse
So it's safe if not using sd-ext. Sorry I can't help solve the problems...
Sent from my Nexus S using Tapatalk
accuphase said:
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
Click to expand...
Click to collapse
Yes, now having the same problem with sd-ext backups too.
zyonee said:
Only available in standard orange, I actually can't be bothered to find out how to make different color variants.
Click to expand...
Click to collapse
Aww
But still, thanks for bringing it over to the N1.
Updated OP to version 4.0.0.0.
Hi all,
Was running CM9 rc1 with no problems then upgraded to RC2 then to CM9 nightly 20120804. Installed Siyah Kernel by flashing in CWM recovery and added a second ROM (winamlite). Now superuser says it is denied superuser permissions in CM9. It works fine in Winamlite though.
I have tried reflashing CM9 nightly which reinstalled the CM kernel which didn't help and then reflashed siyah kernel. Still no luck. Read quite a few posts and tried a lot but nothing does the trick (flashed latest superuser from CWM, wiped superuser data, tried to install root from within extweaks).
Can someone point me in the right direction to sort this please?
Thanks,
Max
emptybee said:
Hi all,
Was running CM9 rc1 with no problems then upgraded to RC2 then to CM9 nightly 20120804. Installed Siyah Kernel by flashing in CWM recovery and added a second ROM (winamlite). Now superuser says it is denied superuser permissions in CM9. It works fine in Winamlite though.
I have tried reflashing CM9 nightly which reinstalled the CM kernel which didn't help and then reflashed siyah kernel. Still no luck. Read quite a few posts and tried a lot but nothing does the trick (flashed latest superuser from CWM, wiped superuser data, tried to install root from within extweaks).
Can someone point me in the right direction to sort this please?
Thanks,
Max
Click to expand...
Click to collapse
Wipe cm9 completely, flash it again, flash Siyah kernel on cm9, and flash the same siyah zip for wanamlite
Try it and it should be working, I did something like this when I had this problem
Sent from my S II Monster
Nasty_z said:
Wipe cm9 completely
Click to expand...
Click to collapse
Do you mean factory wipe data/reset? Thought this might be the case and was trying to avoid it as had just got the phone set up how I want it. Saying that I am going to upgrade to the stable CM9 so now's as good a time as any.
If I am going to go through with this, is there a way to completely wipe ALL data from my phone? Everything from photos, emails, old app data etc. I have done a factory wipe before but it seemed to leave some files and folders on the phone. (or maybe my memory is failing me).
Looks like I have my weekend planned out for me then. If only the sun would bu99er off and let me geek out without the guilt...
Thanks for the help.
p.s. Sorry for posting this thread in the wrong place MODs and thanks for moving it.
emptybee said:
Do you mean factory wipe data/reset? Thought this might be the case and was trying to avoid it as had just got the phone set up how I want it. Saying that I am going to upgrade to the stable CM9 so now's as good a time as any.
If I am going to go through with this, is there a way to completely wipe ALL data from my phone? Everything from photos, emails, old app data etc. I have done a factory wipe before but it seemed to leave some files and folders on the phone. (or maybe my memory is failing me).
Looks like I have my weekend planned out for me then. If only the sun would bu99er off and let me geek out without the guilt...
Thanks for the help.
p.s. Sorry for posting this thread in the wrong place MODs and thanks for moving it.
Click to expand...
Click to collapse
So you wanna wipe your sdcard too? It's not necessary though it's of course possible. You gotta reboot in to recovery, wipe data/factory reset, go to mounts and storage, format /system, if you wanna wipe your sdcard, you click on Mount /sdcard and then click on format /sdcard.
After all that is done, now go to advanced and wipe dalvik cache and wipe battery stats.
Now your phone is completely wiped. Actually, wanamlite ROM would still stay. Like you said before, you've lost the ability to dual boot. That means that your kernel changed from siyah to cm9. To remove wanamlite too, you need to get siyah kernel (this can be done before doing the above or after doing the above) and then you need to boot in to recovery, dual boot options, remove 2nd ROM
Sent from my S II Monster
If you format /sdcard, 2nd ROM will not work since there are no data and cache images.
If you install WanamLite zip through dual-boot options, it will prevent from installing other kernel.
About wiping /data. After wiping, those folders will be created always when Android is running, cause they're necessary.
przemcio510 said:
If you format /sdcard, 2nd ROM will not work since there are no data and cache images.
If you install WanamLite zip through dual-boot options, it will prevent from installing other kernel.
About wiping /data. After wiping, those folders will be created always when Android is running, cause they're necessary.
Click to expand...
Click to collapse
Yeah I totally forgot to tell him that 2nd ROM won't be there if he wipes sdcard.
However, wiping /data will wipe the folders and again create the folders. It's true but the new folders won't have stuff from the previous ROM. So it's recommended when flashing a new ROM. Correct me if I'm wrong.
Sent from my S II Monster
Same delima
I am having the same problem.. When using siyah kernel n dual booting..
Primary Rom ressurection remix V2.5
Secondary Rom Salman Ics
now in the 2nd Rom.. It says superuser permmison denied.. Apparrntly no root access.. I instanlled EX TWEAKS.. N clicked "remove root" n then "auto install root at boot" so it should have installed root when i resarted but no luck..
Sumone plz help.. How to get root in the second rom?can i use one click root software?
I have never experienced this problem while dual booting.
You guys can try to Fix permissions of the affected ROM in recovery.
Swyped from my Samsung Galaxy SII
I777 Builds: http://dl.omnirom.org/i777/ [courtesy of @Entropy512*]
ChangeLog: https://changelog.omnirom.org/#/i777/next
ChangeLog: http://omni.cmxlog.com/4.4/i777/
Wiki: http://docs.omnirom.org/Main_Page
Gerrit: https://gerrit.omnirom.org/
Butracker: http://jira.omnirom.org
G+ community
Be Advised:
=================
- Root access is not included by default. Flash SuperSU for root (Step 4 below)(also see "SURVIVAL" note).
- Feel free to leave bug reports on the bugtracker.
- This firmware will install TWRP as your device recovery. (To use OpenDelta with CWM, disable [secure] in {system updates})
-o- internal sd-card files are located at "emmc"
-o- to get back to CWM, see notes below.
Recovery requirement (prior to flashing this firmware):
================
CWM 6.0.4.4+
--OR--
TWRP 2.6.3.0+
-Renderbroken's OmniROM kernel
-or- Flash Omni's Boot.IMG via MobileOdin
--------------------------------
SGH-S959G; (courtesy of @mr-cook)
TWRP 2.6.3.0.zip
--OR--
CWM 6.0.4.5.zip.
Initial Installation:
=================
FLASH:
1) mr-cook's ROM wipe script
2) OmniROM: http://dl.omnirom.org/i777/
3) 4.4 Gapps: >PA 0 day< MICRO recommended (see GApps note)
4) ROOT access: Super-SU (optional)
Updating Nightlies (manual or OTA):
=================
FLASH:
1) OmniROM: http://dl.omnirom.org/i777/ (See "SURVIVAL" note)
-Happy Flashing
-Cyril
*Ownership:
Entropy512 said:
I'll create an official thread for this eventually... I suck at XDA threads for the devices I work on, as anyone who has seen the i777 CM threads can attest.
Yeah, I'm the one that did the bringup for the I777 (with help from many of the n7000 guys for general 4.4 bringup stuff).
Just as a warning the device is pretty low on my priorities list - it's kind of in automode. Of course, submissions to Omni gerrit are always welcome![...]
Click to expand...
Click to collapse
KNOWN ISSUES:
Attaching picture from camera folder crashes messaging
http://jira.omnirom.org/browse/OMNI-740
Click to expand...
Click to collapse
Repeated/frequent voice typing on AOSP keyboard causes soft reboot
http://jira.omnirom.org/browse/OMNI-739
Click to expand...
Click to collapse
menu-button unlocks device when feature is disabled UNTIL feature is toggled on and off again
http://jira.omnirom.org/browse/OMNI-138
Click to expand...
Click to collapse
Music player stops playing music from sd after some time
http://forum.xda-developers.com/showthread.php?t=2612329&page=18
http://forum.xda-developers.com/gal...l-cm11-omni-4-4-slimkat-t2222843/post51005727
Best workaround as of 2014, April 5: http://forum.xda-developers.com/showpost.php?p=51657055&postcount=304
Also, formatting both internal and external SD cards to exfat seem to solve the immediate issue, but do not solve the root fuse-daemon problem.
The internal SD card of the i777 can be formatted via ADB console in windows, or using exfat-utils in ubuntu
Click to expand...
Click to collapse
NOTES:
GApps: The size of full Gapps packages crowds /system, preventing the use of other /system based units (art, xposed, etc). Micro Gapps + google play installation of desired addons is a more efficient approach considering the resources available.
Click to expand...
Click to collapse
SURVIVAL: Go to super SU settings and install backup script. Root will survive updates. As for gapps, most installs include backup scripts. You don't need to re-flash them.
in system/addon.d, you should have a 99-supersu.sh, and 70-gapps.sh backup scripts, which survive the Rom update.
The script backs up beforehand and will restore after the flash.
From the backup script..
#!/sbin/sh
#
# /system/addon.d/99-supersu.sh (root:root 755)
# During an upgrade, this script backs up SuperSU-related files,
# /system is formatted and reinstalled, then the files are restored.
#
(info collected from this G+ conversation)
Click to expand...
Click to collapse
How to install CWM from TWRP?
3men2 said:
Boot into TWRP recovery
choose Install
Go to emmc to acces the internal sdcard and go to where you have the kernel with cwm( Siya, AJK, STI)
Flash the Kernel, when finished DON'T TOUCH REBOOT SYSTEM, Just go back to previous screen and choose the reboot to recovery option.
You will boot into CWM now and will be able to wipe everything without issues...
Click to expand...
Click to collapse
MobileOdin Install:
(procedure verified working (running SHOstock & Jeboo Kernel, & AT&T stock-rooted firmware) as of 2013-12-13 12:49):
With your phone on fully booted into (whatever ROM)
1) Gather all necessary flash files onto internal sdcard before performing these steps.
---a) Boot.IMG (extracted from omni-4.4.x-latesti777-nightly.zip)
---b) MrCook's ROM wipe.zip
---c) Omni-nightly.zip
---d) PA GApps (optional)
---e) SuperSU (optional)
2)Mobile-odin flash Omni's boot.img
>>the phone will try to reboot, but will likely fail. Three-finger salute (with the USB cable UNPLUGGED), until you are in TWRP recovery<<
3) [install] > [COOK'S ROM WIPE.zip] > [add more zips] > [omni-4.4.x-latesti777-nightly.zip] > [add more zips as desired] >>swipe to confirm flash>> [reboot system]
Click to expand...
Click to collapse
Spinergy02 said:
[...]"In system root data folder (/data) make a blank file named local.prop
Edit the file and add qemu.sf.lcd_density=195 I set my density to 195.
Set permissions to 644 (rw/r/r)"
So apparently settings in local.prop override build.prop and aren't lost when flashing a new nightly. I'd guess this would work for any settings that you wanted to retain between flashes. [...]
Click to expand...
Click to collapse
cyril279 said:
http://dl.omnirom.org/i777/
-Happy Flashing
-Cyril
Click to expand...
Click to collapse
Thanks! I will flash and test it out!
Running this as I type. So far so good. I'm on ST version
Sent from my SGH-959g using Tapatalk 2
Can this ROM dance with the AJK kernel?
atvspecialties said:
Running this as I type. So far so good. I'm on ST version
Sent from my SGH-959g using Tapatalk 2
Click to expand...
Click to collapse
What gapps did you flash?
BInspirinG said:
What gapps did you flash?
Click to expand...
Click to collapse
I myself flashed ParanoidAndroid's 4.4 GApps.
Untitled87 said:
Can this ROM dance with the AJK kernel?
Click to expand...
Click to collapse
Unfortunately, as of v4.9, it is not compatible with KitKat in general.
azeem40 said:
I myself flashed ParanoidAndroid's 4.4 GApps.
Unfortunately, as of v4.9, it is not compatible with KitKat in general.
Click to expand...
Click to collapse
Could you provide the steps in which you flashed this rom? I wiped both flashes, system and data. I've tried flashing 3 times now, but the only thing it'll do is reload and then go back into recovery mode.
I've always noticed that it says:
"script succeeded: result was [/system]"
Any help with the direction I should take?
Steps:
1) mr cook's ROM wipe script
2) Flash Omni
3)Flash PA 4.4 Gapps
BInspirinG said:
Could you provide the steps in which you flashed this rom? I wiped both flashes, system and data. I've tried flashing 3 times now, but the only thing it'll do is reload and then go back into recovery mode.
I've always noticed that it says:
"script succeeded: result was [/system]"
Any help with the direction I should take?
Click to expand...
Click to collapse
BInspirinG said:
Could you provide the steps in which you flashed this rom? I wiped both flashes, system and data. I've tried flashing 3 times now, but the only thing it'll do is reload and then go back into recovery mode.
I've always noticed that it says:
"script succeeded: result was [/system]"
Any help with the direction I should take?
Click to expand...
Click to collapse
I factory reset, wiped cache, wiped dalvik, installed Omni, installed Gapps, and rebooted phone.
I used the gapps linked in RenderBroken's 4.4. I also had to use the supersu option as root didn't show up. :thumbup::thumbup::thumbup::thumbup:
Sent from my SGH-959g using Tapatalk 2
azeem40 said:
I factory reset, wiped cache, wiped dalvik, installed Omni, installed Gapps, and rebooted phone.
Click to expand...
Click to collapse
BInspirinG said:
Could you provide the steps in which you flashed this rom? I wiped both flashes, system and data. I've tried flashing 3 times now, but the only thing it'll do is reload and then go back into recovery mode.
I've always noticed that it says:
"script succeeded: result was [/system]"
Any help with the direction I should take?
Click to expand...
Click to collapse
You may also need to update your recovery by flashing the last CM Nightly. Thats what i did and I had no issues.
I'll create an official thread for this eventually... I suck at XDA threads for the devices I work on, as anyone who has seen the i777 CM threads can attest.
Yeah, I'm the one that did the bringup for the I777 (with help from many of the n7000 guys for general 4.4 bringup stuff).
Just as a warning the device is pretty low on my priorities list - it's kind of in automode. Of course, submissions to Omni gerrit are always welcome!
And if any I9100ers drop by and wonder why there is no I9100 yet - I don't own one, and I'm not sure what happened to xplodwild's... I think his might be dead.
OmniRom nightlies for i777 use TWRP RECOVERY
I haven't been this happy about a release in god knows how long. I just did a FULL-ON HAPPY DANCE!
@Entropy512, I didn't mean to steal your thunder, I was excited to share your released work with the community.
I have tried manually wiping and formatting, along with using the rom script by cook. Both yields the same results for me. All 4 tried have been from the 11/26 CM 10.2 nightly.
Basically, after my wiping and flashing processes, the phone just reboots into recovery again.
I'm running this one.
http://dl.omnirom.org/i777/omni-4.4-20131127-i777-NIGHTLY.zip
These gapps
http://d-h.st/PbA
Sent from my SGH-959g using Tapatalk 2
I'm running the 1127 nightly with PA-Gapps (Modular Full).
When you're playing music on either the built-in player or Google Music, you get a ~1sec audio error (not a skip, more like a digital stutter) when the screen goes off and when you unlock.
I also switched to ART to see if it made any difference in the above. It didn't.
Not huge, just reporting.
auTONYmous said:
I'm running the 1127 nightly with PA-Gapps (Modular Full).
When you're playing music on either the built-in player or Google Music, you get a ~1sec audio error (not a skip, more like a digital stutter) when the screen goes off and when you unlock.
I also switched to ART to see if it made any difference in the above. It didn't.
Not huge, just reporting.
Click to expand...
Click to collapse
Idk why, but whenever I switch over to art with that same gapps package, I get force closes left and right. Weird...
---------- Post added at 04:05 PM ---------- Previous post was at 03:46 PM ----------
I have noticed that this ROM give me pretty bad battery life. Otherwise, performance is great. I will report back tomorrow night for my final verdict on battery life.
auTONYmous said:
I'm running the 1127 nightly with PA-Gapps (Modular Full).
When you're playing music on either the built-in player or Google Music, you get a ~1sec audio error (not a skip, more like a digital stutter) when the screen goes off and when you unlock.
I also switched to ART to see if it made any difference in the above. It didn't.
Not huge, just reporting.
Click to expand...
Click to collapse
Yepp that basically ear-raped me the first time it happened. And the second. Thats when I stopped listening to my music hahaha.
More customization coming soon?
Will the security element emulation for wallet become implemented? I always wanted to use NFC payment on this phone
Sent from my SGH-I777 using Tapatalk
I used F2FS file system on data and cache partition and now its like i have a nexus 6p there is little to no UI lag or even any delay in opening apps.
Used to use F2FS on my previous devices(lg g2, Galaxy S2 and Xperia Z ultra) and man the effect was noticeable from day1, so tried it on this device and guess what it works flawlessly.
Here is a thread for comparition between F2FS vs EXT4(the default one).
So here is guide for you guys its Highly dangerous setup so please follow this if you know how to restore a SoftBrick status.
Caution:--
ONLY FOR CM13 and N based roms which support F2FS, If used on OOS3 or H2OS(mm) it will result in not converting the data/cache partition properly and will end up 0mb partition because of modified twrp used for these roms and you wont be able to be mount your internal memory too.
Backup backup backup. Make sure you take a backup and save it on your pc before performing the steps.
Things you can do to make your life easier:--
Clean flashing of rom is highly recommended but you can try dirty too as it does not touch the system partition but still clean is preferred.
Use ZipMe app to make a zip file for your apps so that installing all those apps becomes easier if coming from clean flash.
Full backup of your internal memory files as this setup formats even your internal memory even if you select only the data partion.
Best stay on stock kernel as there is no mention of any cm13 custom kernel to have f2fs support. They may have but in any thread of these i couldnt find f2fs word anywhere. So stay stock.
Rom compatibility/tried on:--
Exodus.
All cm13 based roms work flawlessly.
LineageOS14
Kernel compatibility:--
Darkbeast
Stock kernel or the one provided by default by the rom.
Yarpin's kernel.
Benschold kernel.
Note:- Please this method has worked on F2FS supported roms only before following any of it make sure your rom developer has incorporated f2fs support in his/her rom.
Steps:--
Use revert2lollipop to revert back to lollipop firmware if you are on OOS3/H2OS and wanna try f2fs.
Download and upgrade your twrp version to latest.
Copy the .img file to your root folder and reboot to twrp select--->Install-->Install images button-->select the new .img file you copied and reboot to recovery.
Format everything including your internal memory.
Go to advance wipe and select cache partition and select repair and change file system, once there select change file system and change it to f2fs and swipe. Images.
Repeat the above step for data partition.
Go to twrp settings and tick rm -rf, this will make your device retain your f2fs system after clean flash of some roms.
Reboot your recovery once and copy back all your data back to your internal memory.
Flash the required modem for your rom and clean flash your rom for the best bug free experience.
Benefit!
PS:- Please if someone daring does use this on another rom and if everything works flawlessly then please post about it, i will add it compatible roms/kernels.
Press thanks if it worked for you and do post about any improvements you saw.
Credits:-
@Androguide.fr
@ opt devs for awesome roms.
@ jrummy Apps for zipme app.
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
jbarcus81 said:
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
Click to expand...
Click to collapse
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
So we need stock kernel
isoladisegnata said:
So we need stock kernel
Click to expand...
Click to collapse
Yeah for now, since for f2fs roms to work properly the kernel also needs to support the file system and no custom kernel has f2fs as a feature mentioned in their list. I couldnt find anything related to f2fs even with the search function, will update the thread if f2fs support is confirmed by the devs of the respective kernels.
chintu1234 said:
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
Click to expand...
Click to collapse
Yeah.. Not using any kernel other than what's built into AICP from the OP.. :highfive:
Added yarpin's kernel to the compatible kernels.
Using AOKP with stock kernel perfectly! Thanks for this OP and also for sharing the ZipMe app! Which is amazing, Didnt work for me on CM13 though but love the idea! JRummy devs make the best apps
Can i use titanium backup to app+data?
isoladisegnata said:
Can i use titanium backup to app+data?
Click to expand...
Click to collapse
Yes you can.
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
isoladisegnata said:
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
Click to expand...
Click to collapse
Yeah if you connect to PC after conversion you will be able to access your memory as you used to with default system.
Just make sure to wipe system,data,cache,dalvic,internal before going any further for good measure.
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Tatsuya_ said:
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Honestly I wouldn't notice a difference unless you put 2 phones running ext4 and f2fs side by side for comparison. But if I were to really force an answer out from myself I would say that app opening and switching times are greatly reduced.
you really deserved more thanks for this guide.. keep it up and great work!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
Nice! thanks for reporting, will add to OP.
Works great with Exodus ROM !!!
very good. Thank you very much. wonder why only cache and data? What about the system partition?
rakieta said:
very good. Thank you very much. wonder why only cache and data? What about the system partition?
Click to expand...
Click to collapse
It really isnt needed because in system partition most of the time only read function is done while data and cache constantly need read/write functions to be performed so you wont notice anything different if you format system to f2fs.
Introduction
Hello all, this is my version of TWRP for the Nexus 6P, which includes the ability to convert your /data and /cache partitions to F2FS. This will stay inline with TWRP's changes for the most part, the changes will be listed below.
What in the world is F2FS?
From Wikipedia:
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
F2FS was designed on a basis of a log-structured file system approach, which it adapted to newer forms of storage. Jaegeuk Kim, the principal F2FS author, has stated that it remedies some known issues of the older log-structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. In addition, since a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), it supports various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Click to expand...
Click to collapse
Before diving into this, I would recommend reading the official F2FS documentation to understand why this may be good for you. This is potentially unstable, F2FS is a file system that is very much in active development. There is a reason that most OEMs go with ext4 out of the box. But I digress, I am NOT here to sell you on F2FS; it makes zero difference to me if you use it or not, I am merely providing you with a tool to do so.
Changelog + differences
Differences:
f2fs-tools bumped to 1.7.0 (Omni's 6.0 branch is on 1.4.0)
TWRP app installation offer disabled by default
Conversion procedure
Download TWRP from the link above
Grab a kernel that supports F2FS (I use my own as I know it works)
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, you may need to ask your ROM developer to merge the two commits below.
Bug reports
You are NOT in ANY circumstance to report ANY bugs to the TWRP team.
If you have an issue with flashing something in TWRP, copy the recovery log to your sdcard and post it here.
If swapping to F2FS does not stick, try formatting your data with TWRP (Wipe > Format Data) or fastboot format userdata first.
If your phone does not boot after swapping to F2FS, either your kernel or ROM does not have proper support; post in their thread.
Additionally, check out some of these helpful posts:
https://forum.xda-developers.com/showthread.php?p=70699197
https://forum.xda-developers.com/showthread.php?p=71074016
Adding support to ROM
In order to properly support the initial conversion to F2FS, please add these two commits to your source:
https://github.com/omnirom/android_system_core/commit/1c6700a8fb31c6e314df4f031fa23fa9178c7ca7
https://github.com/omnirom/android_system_vold/commit/c879edb2fecae709f404c2d71c1d47ceac3a325e
The reason some people have issues converting is fs_mgr will try to read the block device as ext4 and destroy the f2fs block. This commit skips that check, allowing F2FS to pass through.
Sources
TWRP is licensed under GPLv3, meaning my changes must be disclosed. I also inline a custom kernel so that source is included as well. I also add in the other repos I modify.
Recovery: https://github.com/nathanchance/android_bootable_recovery/tree/android-7.1
Kernel: https://github.com/nathanchance/angler/tree/7.1.2-flash
Device tree: https://github.com/nathanchance/twrp_device_huawei_angler/tree/android-6.0
f2fs-tools: https://github.com/nathanchance/android_external_f2fs-tools/tree/android-6.0
First!
Thanks for the recovery. Been using it with flash kernel. I see considerable performance improvement in asphalt Xtreme game( idk if its the f2fs or kernel ).
Nice !!! :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you, and thank you for the exemplary GPL compliance. It's noticed and appreciated.
Now this is awesome... On it, will report soon
Much appreciated!
Sent from my Nexus 6P using Tapatalk
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Nitrogen : yes
Somebody must report it and i will update my post.
ThNks
ariefabuzaky said:
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Somebody must report it and i will update my post.
ThNks
Click to expand...
Click to collapse
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Worked perfect! Thanks Flash!!!
I tried this with PN and am now stuck in a boot loop. I flashed the twrp with F2FS support then tried to change the file system followed by installing the latest vendor, latest flashable bootloader+radio, latest pure nexus and gapps, flash kernel, and latest su. Didnt work. Im not stuck in a boot loop I cant get out of. Ive tried every combination of the above. I also tried restoring my backup but that gives me an error. I also tried changing the file system back to ext4. Nothing works. Anyone experience this or have any suggestions?
---------- Post added at 09:09 AM ---------- Previous post was at 08:58 AM ----------
jochem86 said:
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Click to expand...
Click to collapse
Im in the same boat.....what steps did you do to get back to stock?
Data keeps reverting back to ext4 after 1st boot.
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
Mine too....Im stuck in a bootloop. Are you?
Whats also weird is switching too f2fs wiped my storage but once the data reverted back to ext4....my original storage came back too!! Im not sure how or why that is happening either.
I just followed OP and formatted everything first, now i have SAOSP running with flash on f2fs..
Works great, so far it doesn't feel like a huge improvement though..
Sent from my Nexus 6P using XDA-Developers Legacy app
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
What makes you say that?
Back then when I was using Temasek on my Note 3, he incorporate a script that automatically format the system partition to F2FS when flashing his ROM. That is if the system partition is already in f2fs and I think that was pretty amazing but short live. I wonder if other ROM developer could go the same route if formatting F2FS system was popular enough. That would make updating new rom one step easier. Just for thought.
---------- Post added at 09:38 AM ---------- Previous post was at 09:16 AM ----------
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
minhgi said:
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
Click to expand...
Click to collapse
I wish you told this earlier....This is exactly what happened and I had to clean install
NoobInToto said:
I wish you told this earlier....This is exactly what happened and I had to clean install
Click to expand...
Click to collapse
It wouldn't matter though, I get a warning that the backup was made with EXT4 and that backup may not boot unless changed back to it
Iceburn1 said:
What makes you say that?
Click to expand...
Click to collapse
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
Exactly doing the same....
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
That's too bad its not working for you, its working on my side no problem, did you format in twrp if its not sticking? Im on RR with Flash kernel.