Related
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Skripka said:
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Click to expand...
Click to collapse
Well, that's just not true. I use 2.6.3.4 to flash my ROMs (and radio when I don't RUU), and those ROMs are all 4.4.2.
But to answer your question OP, I don't know since I haven't looked at that part of the source. But I believe TWRP is the only supported recovery, so keep that in mind when thinking about bug reports and error messages.
PonsAsinorem said:
Well, that's just not true. I use 2.6.3.4 to flash my ROMs (and radio when I don't RUU), and those ROMs are all 4.4.2.
But to answer your question OP, I don't know since I haven't looked at that part of the source. But I believe TWRP is the only supported recovery, so keep that in mind when thinking about bug reports and error messages.
Click to expand...
Click to collapse
Don't mind me...I forgot I was in the Omni boards and not my local device sub-forum
lozohcum said:
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
Click to expand...
Click to collapse
No. TWRP's configuration is more "self-contained" in terms of many of its build dependencies. CWM requires tentacles throughout the entire Android source tree over 4-5 or more projects that I'm not merging unless they can be proven to be needed for more than just CWM.
Skripka said:
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Click to expand...
Click to collapse
Um, TWRP is the only supported recovery for Omni. Most specifically, OpenDelta is GUARANTEED to fail with official CWM since Koush blocks advanced recovery scripting by anything other than ROM Manager.
TWRP works to flash Omni on every supported device I know of that's receiving nightlies. If this isn't the case on ANY device it's a pretty big bug the maintainer needs to address.
Entropy512 said:
No. TWRP's configuration is more "self-contained" in terms of many of its build dependencies. CWM requires tentacles throughout the entire Android source tree over 4-5 or more projects that I'm not merging unless they can be proven to be needed for more than just CWM.
Um, TWRP is the only supported recovery for Omni. Most specifically, OpenDelta is GUARANTEED to fail with official CWM since Koush blocks advanced recovery scripting by anything other than ROM Manager.
TWRP works to flash Omni on every supported device I know of that's receiving nightlies. If this isn't the case on ANY device it's a pretty big bug the maintainer needs to address.
Click to expand...
Click to collapse
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Skripka said:
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Click to expand...
Click to collapse
I've been flashing OmniROM on my Note II since the very first day only using TWRP. Before that not a single nightly zip of CM 10.1/2, PA or PAC was a problem.
Sent from my GT-N7100 using Tapatalk
lozohcum said:
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
Click to expand...
Click to collapse
Today I installed OMNI ROM 4.4.2 on Galaxy Note with CM 10.1 + CWM (6.0. ...)
- it works Ok.
Generally I followed the "Installing Omni on your device" instruction at docs.omnirom.org
- excluding TWRP installing
- I downloaded Google Apps for Android 4.4 from CyanogenMod site (gapps-kk-20140105-signed.zip)
Skripka said:
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Click to expand...
Click to collapse
Only thing I can think of is TWRP is out of date and needs updating for that device, or there are updated TWRP builds and you're not running one.
lozohcum said:
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Click to expand...
Click to collapse
What does that have to do with this thread?
libm compiles just fine as it is in omni - if it didn't, then none of our nightlies would build
lozohcum said:
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Click to expand...
Click to collapse
Complicated? Breakfast your device, and brunch it. Maybe use DonkeyCoyote's device binaries repository if needed (IIRC, even CM needs this), and that's about it. If you MUST use CWM, get PhilZ's, I hear he unblocked the advanced function calls.
dibblebill said:
Complicated? Breakfast your device, and brunch it. Maybe use DonkeyCoyote's device binaries repository if needed (IIRC, even CM needs this), and that's about it. If you MUST use CWM, get PhilZ's, I hear he unblocked the advanced function calls.
Click to expand...
Click to collapse
So can I just replace PhilZ recovery with TWRP?
Like he said in his thread just sync to bootable/recovery?
lozohcum said:
So can I just replace PhilZ recovery with TWRP?
Like he said in his thread just sync to bootable/recovery?
Click to expand...
Click to collapse
That'd be my guess- don't forget to remove package in your local manifest.
EDIT: I misunderstood your question, so I apologize if I was overly harsh.
dibblebill said:
That'd be my guess- don't forget to remove package in your local manifest.
EDIT: I misunderstood your question, so I apologize if I was overly harsh.
Click to expand...
Click to collapse
No problem. Thanks for replying, it helped me.
Once the first build is finished I'm going to change recovery.
lozohcum said:
No problem. Thanks for replying, it helped me.
Click to expand...
Click to collapse
If setting up the local_manifest gives issues, let me know- I can try to sort one out for you. I've replaced packages like Calculator, but never the recovery.
Hey,
first of all my specs:
Note 3 (SM-N9005) international LTE (hlte)
C-ROM with stock Kernel
TWRP 2.7.2.0
so... whenever I try to flash a custom Kernel my screen stays black after the Samsung Bootlogo showed up.
My steps are:
Create Nandroid
Flash Kernel which is confirmed to work with this version of the rom
wipe cache/dalvik
reboot
Anyone else has this problem? Or even solved it already?
Any help would be really appreciated!
cheers
Altair681 said:
Hey,
first of all my specs:
Note 3 (SM-N9005) international LTE (hlte)
C-ROM with stock Kernel
TWRP 2.7.2.0
so... whenever I try to flash a custom Kernel my screen stays black after the Samsung Bootlogo showed up.
My steps are:
Create Nandroid
Flash Kernel which is confirmed to work with this version of the rom
wipe cache/dalvik
reboot
Anyone else has this problem? Or even solved it already?
Any help would be really appreciated!
cheers
Click to expand...
Click to collapse
Are you sure it's an aosp based kernel and not for tw?
Rosli59564 said:
Are you sure it's an aosp based kernel and not for tw?
Click to expand...
Click to collapse
Yep. Others already confirmed that kernel (lean 3.1)to work with the latest C-ROM.
Altair681 said:
Yep. Others already confirmed that kernel (lean 3.1)to work with the latest C-ROM.
Click to expand...
Click to collapse
lean is at V3.7 actually
try to dl and install it...
I install it on c-rom without any problems
rayman95 said:
lean is at V3.7 actually
try to dl and install it...
I install it on c-rom without any problems
Click to expand...
Click to collapse
just tried that one now... still nothing. Black screen after sammy logo :/
edit:
am I right to flash the
AOSP kernel builds: http://1drv.ms/1pK3eqW
or do I have to flash
leanKernel other n900x devices: http://1drv.ms/1pXzyT1
https://bzo4sq.by3301.livefilestore...Vliw8WRb8w/lk_hltecm-v3.7.zip?download&psid=1
rayman95 said:
https://bzo4sq.by3301.livefilestore...Vliw8WRb8w/lk_hltecm-v3.7.zip?download&psid=1
Click to expand...
Click to collapse
thanks, but that is the file I just tried... I'm really clueless why it isn't working...
could the problem be my recovery? I see you're using philz...
Altair681 said:
thanks, but that is the file I just tried... I'm really clueless why it isn't working...
could the problem be my recovery? I see you're using philz...
Click to expand...
Click to collapse
yes last philz
look at your mp
I'll try to flash the kernel via philz now. Let's hope that'll work On Leankernel it's possible to enable ART am I right there?
edit:
didn't work... f**k
Altair681 said:
I'll try to flash the kernel via philz now. Let's hope that'll work On Leankernel it's possible to enable ART am I right there?
edit:
didn't work... f**k
Click to expand...
Click to collapse
Bad download maybe?
Rosli59564 said:
Bad download maybe?
Click to expand...
Click to collapse
Nope... tried several downloads and kernel versions :/
Altair681 said:
Nope... tried several downloads and kernel versions :/
Click to expand...
Click to collapse
Hmmmm it would work
C-RoM meaning the 7.1 version? @aways version?
You can only use lean 3.1 or temasek 3.76 without black screen. As soon as I read this thread I knew this was it. Don't know about the people who replied above....
C-rom Kang by Vikas wil allow for use of Lean 3.7 make sure you are downloading the HLTE AOSP version not the touchwiz versions.
Thank you all so much guys! Finally it worked!! Looks like it was TWRP that didn't let me flash another kernel... With latest Philz CWM, C-ROM 7.1 and temasek 3.76 it worked like a charm! @mods solved --> close please
Mod Edit
Thread Closed - @ OP Request
ronnie498
Forum Moderator
Hi everybody
I have made a flashable kernel zip from latest nightly update for 11s
Has all latest patch from cm.
I test with 38R
If you are coming from custom kernel s make sure that system files is untouch
Flash from recovery
geowolf1000 said:
Hi everybody
I have made a flashable kernel zip from latest nightly update for 11s
Has all latest patch from cm.
I test with 38R
If you are coming from custom kernel s make sure that system files is untouch
Flash from recovery
Click to expand...
Click to collapse
Didnt this the nightly with the new Touch update? I read that this causes sensor problems. I think there is another version to be released with the 28th nightly (tonight)
Just update to 28
geowolf1000 said:
Just update to 28
Click to expand...
Click to collapse
I am on rooted Stock 38R ROM. My wifi setting broke after installed this kernel, but the kernel did have much more improvement over stock 38R kernel.
Is there anyway to install the kernel without breaking wifi? Thanks!
bingbinghaha said:
I am on rooted Stock 38R ROM. My wifi setting broke after installed this kernel, but the kernel did have much more improvement over stock 38R kernel.
Is there anyway to install the kernel without breaking wifi? Thanks!
Click to expand...
Click to collapse
Let me guess, you were coming back to this kernel from Franco?
Also, to OP, are you going to keep maintaining this thread? Maybe having a regular (like weekly) updates or so?
zaphodbeeb said:
Didnt this the nightly with the new Touch update? I read that this causes sensor problems. I think there is another version to be released with the 28th nightly (tonight)
Click to expand...
Click to collapse
I can flash it or someone has a kernel update to the last nightly?
inscythe said:
Also, to OP, are you going to keep maintaining this thread? Maybe having a regular (like weekly) updates or so?
Click to expand...
Click to collapse
I will try
I am doing this for my self but i want to share with xda friends
Thread update to 31
Amazing improvement to touchscreen
how did u compile this kernel ??
was there any update officially from oneplus for the kernel of the stock 38r firmware?
reyscott1968 said:
how did u compile this kernel ??
was there any update officially from oneplus for the kernel of the stock 38r firmware?
Click to expand...
Click to collapse
After R38 can use nightly built
They impement kernel source
Its original from cm download page
Working like a charm
Thats why post here and not to developers threads
I dont compile nothing
I buy this phone because i do not have time to make my own and update from best
My wifi broke with this as well. Running completely stock 38R.
Can you share Source code please?
CrunchSA said:
My wifi broke with this as well. Running completely stock 38R.
Click to expand...
Click to collapse
Have you backup?
Just restore only system from revovery
Yeah, did that. Just reporting here that it was broken as an FYI.
https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
Would this flash over Franco fine? Thanks in advance.
geowolf1000 said:
After R38 can use nightly built
They impement kernel source
Its original from cm download page
Working like a charm
Thats why post here and not to developers threads
I dont compile nothing
I buy this phone because i do not have time to make my own and update from best
Click to expand...
Click to collapse
Hmmm... I'm not that sure, but I guess there are some differences in the kernel between the standard CM11 and CM11S. Not too sure whether it is a good idea to flash kernel from nightly into 11S... How's your experience so far btw?
inscythe said:
Hmmm... I'm not that sure, but I guess there are some differences in the kernel between the standard CM11 and CM11S. Not too sure whether it is a good idea to flash kernel from nightly into 11S... How's your experience so far btw?
Click to expand...
Click to collapse
Why not ?
The device boot fine and all hardware are working fine
If was not compatibility the device could even boot
Which hardware are different to nightly????
geowolf1000 said:
Why not ?
The device boot fine and all hardware are working fine
If was not compatibility the device could even boot
Which hardware are different to nightly????
Click to expand...
Click to collapse
If you see other custom kernel pages, usually they would have different versions for CM11 and CM11S... So I would assume that there are inherent differences between them. But if it is working fine for you, then great! Maybe I'll try it myself too
runderekrun said:
Would this flash over Franco fine? Thanks in advance.
Click to expand...
Click to collapse
Reflash (dirty) your ROM first to restore WiFi firmware
First I want to say I didn't build this rom, or have anything to do with Mokee Open Source. Any bug reports or feature requests should be directed to Mokee developers.
I only started this thread to provide a link to the roms, as they are not available on xda until now, and a lot of users may not be aware they are still around.
Personally I have found this rom to be very stable, with some nice features.
Links:
Mokee Official Site
Mokee on Google+
Changelog
Bug Tracker
Official Rom Releases
http://download.mokeedev.com/?device=i9100
Recommended Gapps
Open Gapps
Warning(particularly for MM builds): If you try to flash gapps, you will probably find it won't fit on the stock /system partition. In this case you will need to repatition - Repartitioning guide.
Make sure you choose a pit file that increases /system and not just /data(eg, I91001GB_4GB.pit)
Alternatively use Lanchon's re-pitting tool if you want to avoid losing your data
If you want to donate to Mokee and make their life a bit easier(donations will go towards bandwidth etc),
you can donate HERE
Instructions
1. Wipe data/factory reset(from KK compatible recovery)
2. Format /system
3. Flash rom
4. Flash gapps(optional)
5. Flash isorec recovery(for MM, see below), you only need to do this once
6. Reboot
Credits
- Mokee Developers
- CyanogenMod
- AOSP
- SlimRoms
- OmniRoms
Note: Now that Marshmallow(6.x.x) has been released, a warning for anyone flashing these latest nightlies. The kernel(isorec CM kernel) comes bundled with CM recovery, which is more or less useless. If you want a working recovery, you will need to flash the rom, followed by gapps(if you want play store), followed by an isorec recovery from HERE
Be sure to flash either CWM or TWRP for i9100. It is obvious from the name of the file.
And read about Isorec if you are not sure.
Thank you to @Troubadour666 for the Youtube review
Thank you @noppy22 for starting this thread. I had been downloading the ROM from G+ but the added benefit of a thread here on xda means that you have fellow S2 users to discuss problems etc with. Thank you again mate.
downloading....
thx for share
Thank you for the rom....downloading :good:
@noppy22 Have you run Mokee using Lanchons iso-Rec kernel and arnabs Twrp recovery? If so, how did it run?
Drhedphuk said:
@noppy22 Have you run Mokee using Lanchons iso-Rec kernel and arnabs Twrp recovery? If so, how did it run?
Click to expand...
Click to collapse
Mokee has already got my twrp recovery as I supplied it to them back in june 2015
@arnab Thank you.
Drhedphuk said:
@noppy22 Have you run Mokee using Lanchons iso-Rec kernel and arnabs Twrp recovery? If so, how did it run?
Click to expand...
Click to collapse
I've only run it with stock kernel. The only thing I changed(with Kernel Audiutor) was i/o scheduler to row. I suspect any cm12.1 compatible kernel will work. I might give one of Lanchons trim kernels a go in the next day or so
Edit: I tried the last trim/twrp kernel and got bootloop on 160102 build....
noppy22 said:
I've only run it with stock kernel. The only thing I changed(with Kernel Audiutor) was i/o scheduler to row. I suspect any cm12.1 compatible kernel will work. I might give one of Lanchons trim kernels a go in the next day or so
Click to expand...
Click to collapse
Hi mate, I tried Lanchons isoRec kernel when flashing and it bootlooped. Xposed failed to flash for me too.
Thanks for getting back to me.
Drhedphuk said:
Hi mate, I tried Lanchons isoRec kernel when flashing and it bootlooped. Xposed failed to flash for me too.
Thanks for getting back to me.
Click to expand...
Click to collapse
I just edited my post, lol. Not sure whether maybe an AOSP kernel like DragonKernel might work, I'll upgrade tomorrow and give it a go...
Hi,
in one pass, rom + open pico gapps + xpose v79 sdk22 flashed ok
Troubadour666 said:
Hi,
in one pass, rom + open pico gapps + xpose v79 sdk22 flashed ok
Click to expand...
Click to collapse
Xpose will not flash for me.
OK, I tried the latest build(12/01) with DragonKernel(30/11), and got to optimizing apps, then bootloop. So, stock kernel seems the only option for now...
noppy22 said:
OK, I tried the latest build(12/01) with DragonKernel(30/11), and got to optimizing apps, then bootloop. So, stock kernel seems the only option for now...
Click to expand...
Click to collapse
You tried "ripping-out" arnab's kernel from his latest DU and put it over this ROM?
:good:
souler456 said:
You tried "ripping-out" arnab's kernel from his latest DU and put it over this ROM?
:good:
Click to expand...
Click to collapse
Well, no. The reports of freezing with his last release stopped me from trying that. BTW the GeneSys kernel(.tar) that was released is the same as the kernel in DU 9.8, but for me the DragonKernel I tried is the last "AOSP" kernel I found to be stable
Thanks for share... What features has this rom? On official Web site can't found anything about features?
I9100 Tapatalk, RR 5.1.1 Lollipop
089man said:
Thanks for share... What features has this rom? On official Web site can't found anything about features?
I9100 Tapatalk, RR 5.1.1 Lollipop
Click to expand...
Click to collapse
It's basically Cyanogen 12.1 with a couple of extra features like wakelock blocker. My own opinion, I think it is a lot smoother than stock Cyanogen.
To correct my earlier post. I reflashed the Rom and flashed xposed during the flash process and it flashed without any problems.
089man said:
Thanks for share... What features has this rom? On official Web site can't found anything about features?
I9100 Tapatalk, RR 5.1.1 Lollipop
Click to expand...
Click to collapse
I added some screenshots in the OP. Hope this gives you an idea of features....
noppy22 said:
I just edited my post, lol. Not sure whether maybe an AOSP kernel like DragonKernel might work, I'll upgrade tomorrow and give it a go...
Click to expand...
Click to collapse
Great ROM! I repartitioned my phone using 1/4G pit and this ROM works very nice. Thanks devs!
Xposed may not be installed in MoKee RELEASE version cuz they said they odexed the ROM.
Sent from my GT-I9100 using XDA Free mobile app
setting is in the rom
but fingerprint not recognized at all
why?
rowihel2012 said:
setting is in the rom
but fingerprint not recognized at all
why?
Click to expand...
Click to collapse
For me it's working, also for others. Did you clean install again? Maybe something is not fine with the installation. Did it work on other roms?
strongst said:
For me it's working, also for others. Did you clean install again? Maybe something is not fine with the installation. Did it work on other roms?
Click to expand...
Click to collapse
Is was working fine with cm 12 the stock one
But with slim 7. It wont work at all. No response wile settings it
rowihel2012 said:
Is was working fine with cm 12 the stock one
But with slim 7. It wont work at all. No response wile settings it
Click to expand...
Click to collapse
I don't know if the firmware files are missing or if you need to flash prior cm13... But better to discuss in the slimrom thread for sure :good:
strongst said:
I don't know if the firmware files are missing or if you need to flash prior cm13... But better to discuss in the slimrom thread for sure :good:
Click to expand...
Click to collapse
Other's complaining from cm14
Fingerprint not working too
Weard
rowihel2012 said:
Other's complaining from cm14
Fingerprint not working too
Weard
Click to expand...
Click to collapse
Maybe they forgot to flash CM13 before when coming from cos12.1 or they have hardware issue in general or something the fp reader will have from time to time which can be solved by deleting some files or credentials. There's a fingerprint tread in zuk forum where you can read about those common issues, they ALL have nothing to do with rom.
strongst said:
Maybe they forgot to flash CM13 before when coming from cos12.1 or they have hardware issue in general or something the fp reader will have from time to time which can be solved by deleting some files or credentials. There's a fingerprint tread in zuk forum where you can read about those common issues, they ALL have nothing to do with rom.
Click to expand...
Click to collapse
I did not flash cm 13 from stock
I flashed rom slim 6
Then flashed slim 7
rowihel2012 said:
I did not flash cm 13 from stock
I flashed rom slim 6
Then flashed slim 7
Click to expand...
Click to collapse
Try cm13
strongst said:
Try cm13
Click to expand...
Click to collapse
done
now working fine
thanks bro