Related
Tried many kitkat aosp rom. In all roms I can boot normally but in cm 11 I m unable to paas boot logo.
I m trying cm 11 nightly from Dec but on every time I always ended up with bootloop.
I think it's something related to cm 11 stock Kernel because i can safely boot in other aosp roms which are based on cm 11 but has their own Kernel.
Tried all things to paas boot logo but can't
exynoss said:
Tried many kitkat aosp rom. In all roms I can boot normally but in cm 11 I m unable to paas boot logo.
I m trying cm 11 nightly from Dec but on every time I always ended up with bootloop.
I think it's something related to cm 11 stock Kernel because i can safely boot in other aosp roms which are based on cm 11 but has their own Kernel.
Tried all things to paas boot logo but can't
Click to expand...
Click to collapse
If u have bootloop with this rom, u can try other. This is XDA Developers not the forum of cyanogenmod anyway
Ya I m in nameless rom right now which is based on cm 11.
But still want answer why its giving bootloop all the time but for other people its working fine :what:
Joku1981 said:
If u have bootloop with this rom, u can try other. This is XDA Developers not the forum of cyanogenmod anyway
Click to expand...
Click to collapse
Since when has discussion of CM not allowed in XDA? IMHO if you do not have a solution, please refrain from posting cynically.
Sent from my GT-I9100 using Tapatalk
Anyone ?
It's a cm11 problem. I had it too.. You have to remove the battery and wait few minutes. Then try to boot again..
I found that changing the kernel fix this problem, so if you can go to recovery mode you can try to flash KT kernal that is also more battery frendly
Inviato dal mio GT-I9505 utilizzando Tapatalk
Already tried battery trick but not worked for me.
And i am 99% sure its because of kernel so tomorrow will replace Kernel .img file with Kt Kernel .img in cm rom zip then will flash that.
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.
Hi
The f2fs thread is not up to date and has broken links.
Can anyone list some f2fs ROMS and kernels, kitkat or lollipop that i can try out?
Thanks
GorfDroid said:
Hi
The f2fs thread is not up to date and has broken links.
Can anyone list some f2fs ROMS and kernels, kitkat or lollipop that i can try out?
Thanks
Click to expand...
Click to collapse
Interested as well. Did you ever manage to install Lollipop with F2FS?
raz123 said:
Interested as well. Did you ever manage to install Lollipop with F2FS?
Click to expand...
Click to collapse
I did actually but you'll need an f2fs compatible kernel like sabermod Franco kernel.
Everyone says you need an f2fs compatible ROM but that has not always been my experience. I've used it with just an f2fs kernel and it worked.
I no longer use f2fs though. I use ext4 with journaling off. I understand it is the same thing and my phone is just as snappy.
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
Hello guys, I was trying to install cyanogenmod 13 on my Samsung S3 Neo+ (GT-i9301i) device using a custom recovery but when I choose the .zip file the installation failed!
This package is for device: m0, i9300, GT-I9300; this device is s3ve3g.
So is there anyway I can do to install this package or please suggest me another package that can be installed on my device.
Thanks in advance ^_^
You tried to install CM 13 in the S3 I9300
Our S3 Neo is I9301I and you can't install s3 roms in the s3 neo.
Wait for the release of cm 13 for your device
Do you think that it will make the device lags or it will be better for my device?
Do you mean using CyanogenMod instead of your stock ROM?
Like others said; You can't flash a regular S3 ROM on a GT-I93xx Neo.
Rox & n1kolaa are working on CM13 for the GT-I9301I, however, there is no ETA and they don't like giving ETA's so you'll have to wait and see when it's released...
Expect something around June/July before CM13 gets released.
No , instead of cm12.1
DELETED
s3 neo
this rom is for s3 neo ? help me pls
s3ve3g - it's S3 neo (i9301i and i9300i)
But what that's link and from ?...
In build.prop is s3ve3g so this is rom for our phone I think.. we don't know how bugs are in the rom - who will be first ?
meybe it is the version of rom CM13 by @Rox & @n1kolaa ? Meybe this rom not ready for now..?
Someone tried to flash the zip in the download link? Does it work?
triplex92 said:
try install CM13.
somebody I stole download link
https://mega.nz/#!xlc0ACbB!4vn1zcMTKkyaTmGjoHBQ_9w9ScbCFywRODf017F5Z_w
Click to expand...
Click to collapse
Tried with philz recovery
Aftert 'finishing boot', my phone reboot, and have a bootloop
igor40151 said:
Tried with philz recovery
Aftert 'finishing boot', my phone reboot, and have a bootloop
Click to expand...
Click to collapse
eventualy try to flash from TWRP 3.0.0.0 recovery and after flash wipe dalvik and cache
Can someone please give the link download the Gap file for the CM 13 for my s3 neo?
jafar00pppp said:
Can someone please give the link download the Gap file for the CM 13 for my s3 neo?
Click to expand...
Click to collapse
Try opengapps.org
Use Pico it only has; Google Playstore, Google Play Services, Google Contacts Sync & Google Play Framework
triplex92 said:
try install CM13.
somebody I stole download link
https://mega.nz/#!xlc0ACbB!4vn1zcMTKkyaTmGjoHBQ_9w9ScbCFywRODf017F5Z_w
Click to expand...
Click to collapse
Someone booted it?
Endless bootloop
Yes i just tried it myself. After updating apps after boot, it reboots and loops.
Until one of the recognized devs upload their working cm13 at our s3neo forum section, i shouldn't trust any other sources. It hasn't been posted because there isn't any working version released as of yet. There's no ETA so you'll have to wait for that one.
Forced me back to stock os...it made the cm12.1 by n1kolaa go into an endless bootloop too
Sent from my GT-I9300I using Tapatalk
I made a backup prior to flashing cm13. I'm back on Resurrection Remix. (Used Kang cm12.1 n1kolaa's build for a few weeks, and RR for a week now (curiousity) and i must say; superb!, even battery life is good) I think i like it better than kang!
I also use the Rox's 4.1-zRam kernel (ondemand) on RR. It's a great kernel.
nalas said:
eventualy try to flash from TWRP 3.0.0.0 recovery and after flash wipe dalvik and cache
Click to expand...
Click to collapse
Same problem with twrp