Related
Here is a link to the most recent CM nightly for the ATT S4. All credit goes to CM team and djrbliss. I just ran the loki patch against the stock jfltecan CM kernel and edited the build.prop and updater-script for our devices. Of course you'll need custom recovery and the usual wipe/gapps routine for CM.
Please feel free to mirror.
5/24 Nightly:
https://truck.it/p/aELheGFdu8
gapps:
http://goo.im/gapps
Scarchunk said:
Here is a link to the most recent CM nightly for the ATT S4. All credit goes to CM team and djrbliss. I just ran the loki patch against the stock CM kernel and edited the build.prop and updater-script for our devices. Of course you'll need custom recovery and the usual wipe/gapps routine for CM.
Just a public dropbox link. Please feel free to mirror.
https://dl.dropboxusercontent.com/u/35529167/cm-10.1-20130523-NIGHTLY-LOKI.zip
Click to expand...
Click to collapse
You're the man now, dog.
Scarchunk said:
Here is a link to the most recent CM nightly for the ATT S4. All credit goes to CM team and djrbliss. I just ran the loki patch against the stock CM kernel and edited the build.prop and updater-script for our devices. Of course you'll need custom recovery and the usual wipe/gapps routine for CM.
Just a public dropbox link. Please feel free to mirror.
https://dl.dropboxusercontent.com/u/35529167/cm-10.1-20130523-NIGHTLY-LOKI.zip
Click to expand...
Click to collapse
Thanks!
Sent from my SGH-I337 using Tapatalk 2
Hmmm this or slim bean? I am really liking slim bean
How is this comparable to SlimBean? What should I use?
MIRROR:
https://truck.it/p/YX-QrCrKn6
Feel free to add to OP
Slim Bean seems to be pretty cool, but I gotta try this out too... I have a feeling I am going to be spending a lot of time flashing this weekend
Scarchunk said:
Here is a link to the most recent CM nightly for the ATT S4. All credit goes to CM team and djrbliss. I just ran the loki patch against the stock CM kernel and edited the build.prop and updater-script for our devices. Of course you'll need custom recovery and the usual wipe/gapps routine for CM.
Just a public dropbox link. Please feel free to mirror.
https://dl.dropboxusercontent.com/u/35529167/cm-10.1-20130523-NIGHTLY-LOKI.zip
Click to expand...
Click to collapse
Boots like a champ. Good work.
There seems to be a problem getting LTE to connect though. Anyone know about this?
EDIT: Ooop, nevermind! Network mode has to be set to LTE / GSM/WCDMA!
Here is a Mirror on my Server
http://storagecow.eu/index.php?dir=Xda/AT&T+S4/CM+10/
spectrumfox said:
Boots like a champ. Good work.
There seems to be a problem getting LTE to connect though. Anyone know about this?
Click to expand...
Click to collapse
You need to change your Mobile network Network Mode to LTE\GSM\WCDMA and APN to: ATT LTE
Works for me
rob_rector said:
You need to change your Mobile network Network Mode to LTE\GSM\WCDMA and APN to: ATT LTE
Works for me
Click to expand...
Click to collapse
Yup! Got it!
Love every one of you.
Are we able to just flash Slim bean as well?
Scarchunk said:
Here is a link to the most recent CM nightly for the ATT S4. All credit goes to CM team and djrbliss. I just ran the loki patch against the stock CM kernel and edited the build.prop and updater-script for our devices. Of course you'll need custom recovery and the usual wipe/gapps routine for CM.
Just a public dropbox link. Please feel free to mirror.
https://dl.dropboxusercontent.com/u/35529167/cm-10.1-20130523-NIGHTLY-LOKI.zip
Mirror: https://truck.it/p/YX-QrCrKn6
Also before anyone asks, you have to set your APN to pta and your Network Mode to LTE/GSM/WCDMA in order to get LTE.
Click to expand...
Click to collapse
Would you mind outlinine the steps you took in the command line process? Im attempting to complete this myself and i am running into errors
Thanks
Drew
So how is this cm 10.1 running on your at&t sgs4's?
Better than the nexus 4?
One thing I'm noticing is even without Samsung's bloat, there's still only 9.57GB usable space out of 16GB.
Perhaps the device needs to be re-partitioned somehow?
spectrumfox said:
One thing I'm noticing is even without Samsung's bloat, there's still only 9.57GB usable space out of 16GB.
Perhaps the device needs to be re-partitioned somehow?
Click to expand...
Click to collapse
Yes the device needs to be re partitioned.
And as far as I know its not possible yet.
SysAdmNj said:
So how is this cm 10.1 running on your at&t sgs4's?
Better than the nexus 4?
Click to expand...
Click to collapse
It's running like a dream.
Also, the phone has better specs than the Nexus 4, so I would say yes it's better.
The advantage of the Nexus 4 is still getting updates straight from Google though.
spectrumfox said:
It's running like a dream.
Also, the phone has better specs than the Nexus 4, so I would say yes it's better.
The advantage of the Nexus 4 is still getting updates straight from Google though.
Click to expand...
Click to collapse
Disadvantage is lack of LTE
Sent from my SGH-I337 using Tapatalk 4 Beta
drewdatrip said:
Would you mind outlinine the steps you took in the command line process? Im attempting to complete this myself and i am running into errors
Thanks
Drew
Click to expand...
Click to collapse
I pulled my aboot.img using the instructions on djrbliss's github:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
exit
exit
adb pull /data/local/tmp/aboot.img
Then downloaded the CM build and the loki_patch-linux-x86 files. Extracted the boot.img from the CM zip and moved all three files over to a Cent box.
./loki_patch-linux-x86 boot aboot.img boot.img boot.lok
That's it for command line. Everything else was notepad++ and winrar. :good: Noticed I forgot to change the model in the build.prop from the SGH-I337M to the SGH-I337. So you might wanna fix that while your at it.
What error you getting?
Once I get this, would I able to update using the in built updater, or would the updates also have to be loki'd?
About OmniROM
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Click to expand...
Click to collapse
Disclaimer
Standard disclaimer applies, your warranty is void, this may eat your dog or burn your house down, delete all your pictures, etc.
Instructions
0. You need a recovery that supports SELinux. I'm told that recent versions of CWM support it, but I haven't tried them myself. The best option is the official TWRP 2.7.0.0 release (other recoveries may not be compatible with OpenDelta updates for nightlies).
If you want to flash my recovery, download the recovery.img and flash it using ODIN or Mobile ODIN. You can also use Recovery Tools to flash it from your device
1. Flash the ROM.
2. Flash SuperSU if you want root (it's not yet included in the ROM). I have not tried any other Superuser apps but SuperSU is supposed to be incorporated into Omni eventually. Important: you may need to install a backup script using SuperSU to persist it across flashes - see the settings in SuperSU for that.
3. Flash Kitkat/4.4 compatible Gapps (PA has some that work with this ROM).
1-3 can be queued in TWRP.
4. If coming from a different ROM wipe data/factory reset, otherwise you probably won't boot
Downloads
TWRP 2.7.0.0 official builds are here.
TWRP 2.6.3.1 (unofficial version; the 4th digit is basically just for device specific changes). Use Flashify, Mobile Odin, or Recovery Tools to flash .img files.
twrp-2.6.3.1-n8000.img
twrp-2.6.3.1-n8013.img
ODIN flashable tars:
twrp-2.6.3.1-n8000.tar.md5
twrp-2.6.3.1-n8013.tar.md5
You must flash this (or other 4.4 compatible recovery) if you're on the official TWRP 2.6.3.0 or other outdated recoveries, if you get an error about set_metadata_recursive when flashing
N8000 Nightlies
N801x Nightlies
Changelog
N8000
N801x
Sources
Device trees:
android_device_samsung_n80xx-common
android_device_samsung_n8000
android_device_samsung_n801x
Thanks, and have a nice day!
XDA:DevDB Information
OmniROM, a ROM for the Samsung Galaxy Note 10.1
Contributors
iofthestorm, marco9333, TheMorpheus, humberos, Entropy512, espenfjo
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Created 2014-03-01
Last Updated 2014-04-05
FAQs
Where can I report bugs?
http://jira.omnirom.org/ - be sure to assign them to me, Ibrahim Awwal, if they're device specific.
Where is multiwindow?
Multiwindow is still a work in progress, if you want to try it out you'll have to use my unofficial builds from http://forum.xda-developers.com/showthread.php?t=2550308
I can't flash the ROM, I get an error about set_metadata_recursive
Make sure you are using an up-to-date recovery, see the OP for a link to my recovery builds.
Reserved
Hi,
Thanks again for the great ROM. I was wondering if maybe you can add a section here of flashable zips for some possible cherry picks like multi window. This way we can get night lies but also get the latest and greatest. TIA.
Sent from my GT-N8013 using Tapatalk
avruma said:
Hi,
Thanks again for the great ROM. I was wondering if maybe you can add a section here of flashable zips for some possible cherry picks like multi window. This way we can get night lies but also get the latest and greatest. TIA.
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
Hmm, it's not really possible to do that for frameworks changes like that. I think if there is an xposed module or something for Multiwindow then that may work but I don't know if such a thing exists or if it could actually be done (but that's more likely to work than a flashable zip).
avruma said:
Hi,
Thanks again for the great ROM. I was wondering if maybe you can add a section here of flashable zips for some possible cherry picks like multi window. This way we can get night lies but also get the latest and greatest. TIA.
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
iofthestorm said:
Hmm, it's not really possible to do that for frameworks changes like that. I think if there is an xposed module or something for Multiwindow then that may work but I don't know if such a thing exists or if it could actually be done (but that's more likely to work than a flashable zip).
Click to expand...
Click to collapse
XMultiWindow
JamMasterClay said:
XMultiWindow
Click to expand...
Click to collapse
Thanx I tried that a few days ago and it didn't play nice with omnirom and omniswitch
Sent from my GT-N8013 using Tapatalk
Please support N8000..:crying::crying:
dannyella said:
Please support N8000..:crying::crying:
Click to expand...
Click to collapse
They're working on it. Use the unofficial builds for now.
Just flashed the latest 8013 build and for some reason my bookmarks wont sync in browser or chrome. Hmmmm... Strange.
Sent from my GT-N8013 using Tapatalk
I noticed that sometimes the back arrow on the bottom bar sometimes goes dim. Does anyone know why it does that or how to make it stop? It's starting to mess with my OCD...
Sent from my GT-N8013 using Tapatalk
---------- Post added at 09:18 PM ---------- Previous post was at 09:13 PM ----------
I also wanted to suggest a temporary solution for MultiWindow on the nightlies. I have been using the latest XHaloFloatingWindow KitKat test build, and it works great once you get all the settings right. It's an Xposed mod, so you will have to have that installed and enabled for it to work. Check out the XDA page for that build
Sent from my GT-N8013 using Tapatalk
---------- Post added at 09:20 PM ---------- Previous post was at 09:18 PM ----------
http://forum.xda-developers.com/showthread.php?t=2419287
Sent from my GT-N8013 using Tapatalk
Huh, I've noticed that too, I just thought I was going crazy. Not sure why it happens but I feel like it started around the time navbar customization was added, so I should look near that time period. If you can get a screenshot and logcat when it happens could you post it on JIRA? That way we can try to figure out if it's a common bug (check whether it'd already been reported of course).
Sent from my GT-N8013 using Tapatalk
dannyella said:
Please support N8000..:crying::crying:
Click to expand...
Click to collapse
Official N8000 nightlies are now up!
iofthestorm said:
Official N8000 nightlies are now up!
Click to expand...
Click to collapse
Yay!!
iofthestorm said:
Official N8000 nightlies are now up!
Click to expand...
Click to collapse
Yes, and OpenDelta works great!!
Does anyone know if I can assign OpenDelta to flash a second or third .zip after updating? You know, for SU
Sent from my GT-N8013 using Tapatalk
electrikjesus said:
Does anyone know if I can assign OpenDelta to flash a second or third .zip after updating? You know, for SU
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
Yes, there is a folder under OpenDelta where you can put additional file!
Sent from my LG-D802
electrikjesus said:
Does anyone know if I can assign OpenDelta to flash a second or third .zip after updating? You know, for SU
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
yes you can... check out FlashAfterUpdate -> http://forum.xda-developers.com/showthread.php?t=2575966 ... i think thats what your looking for.
its a folder in /sdcard/OpenDelta/ and you can place zips there ... see link for templates.
but for supersu you just need to let it install backup-script from inside supersu...
edit: oops, late
TheMorpheus said:
Yes, and OpenDelta works great!!
Click to expand...
Click to collapse
lucky n8000 users ... since the n8000 went nightly the n801x somehow stopped...no nightlies yesterday and today. Might just be a coincidence, a few other devices also stopped on 7th...
edit2: nightlies up again for n801x
tabtxk said:
yes you can... check out FlashAfterUpdate -> http://forum.xda-developers.com/showthread.php?t=2575966 ... i think thats what your looking for.
its a folder in /sdcard/OpenDelta/ and you can place zips there ... see link for templates.
but for supersu you just need to let it install backup-script from inside supersu...
edit: oops, late
lucky n8000 users ... since the n8000 went nightly the n801x somehow stopped...no nightlies yesterday and today. Might just be a coincidence, a few other devices also stopped on 7th...
edit2: nightlies up again for n801x
Click to expand...
Click to collapse
I think there was an issue with the build server, but it was fixed.
Works great but I think I don't have root access (supersu is not able to install binary), any help?
Past two days I have been unable to install cyanogen nightly builds. Twrp says that it won't install because the file is for a sm-p9005. Did cyanogen fork again? If so what device name is my T-Mobile note 3 under?
Lawful123 said:
Past two days I have been unable to install cyanogen nightly builds. Twrp says that it won't install because the file is for a sm-p9005. Did cyanogen fork again? If so what device name is my T-Mobile note 3 under?
Click to expand...
Click to collapse
Just confirming. I have the same issue. Last good install was Nov 11th. Since then, nightlies will not install. And gives that message.
I installed the latest nightly last night and it works fine. Are you guys installing the "hlte" version?
Sent from my SM-N900T using Tapatalk
Vish.N said:
I installed the latest nightly last night and it works fine. Are you guys installing the "hlte" version?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Yes. I downloaded the 11-14 hlte nightly. It will not install.
IIRC, CM11 forked HLTE back to HLTETMO.
DrawnToLife said:
IIRC, CM11 forked HLTE back to HLTETMO.
Click to expand...
Click to collapse
So then they do not have a new nightly posted for download then? They must be trying to fix NFC.
Lawful123 said:
So then they do not have a new nightly posted for download then? They must be trying to fix NFC.
Click to expand...
Click to collapse
Yeah I don't know. I haven't been able to find them either.
Since the thread called "Official CM11 Nightlies" has not been updated by the OP with the correct links, and there are many people asking which one is correct, I felt it a better option to create a new thread than keep posting in the comments of which one to use. There is only one section for the Note 3. All nightlies/snapshots have been combined into one release. Here are the correct links:
ROM download:
http://download.cyanogenmod.org/?device=hlte
Gapps:
http://wiki.cyanogenmod.org/w/Google_Apps
Enjoy.
Is this still correct seeing as how CM is splitting the TMO build from the HLTE buids?
Jonphinguyen7 said:
Is this still correct seeing as how CM is splitting the TMO build from the HLTE buids?
Click to expand...
Click to collapse
Where did you hear that? Looking at the nightlies I only see hltetmo still showing from Jan, and the htle is from today. When are they suppose to split them?
bobbyphoenix said:
Where did you hear that? Looking at the nightlies I only see hltetmo still showing from Jan, and the htle is from today. When are they suppose to split them?
Click to expand...
Click to collapse
Done already. The last hlte nightly that included tmo was 11/11. tmo builds have not started back up yet.
If you must install the latest nightless, install twrp for hlte not hltemo.
I do have hlte twrp installed but still can't flash pacman ROM, cm11 official ROMs. What gives?
Sent from my SM-N900T using XDA Free mobile app
U need the CWM from philz last realese
Sent from my unknown using XDA Free mobile app
TheBestEver said:
I found that I needed to reflash the 2.8.1.0 hlte .IMG file with #Rashr from the play store to get anything after the 11th to flash right. .zip didn't work only the .img here's where you need to get the file from http://www.techerrata.com/browse/twrp2/hlte Make sure you flash the correct one for your bootloader
Click to expand...
Click to collapse
.zip worked fine for me.
Hey guys
Does anyone know when we will get Cyanogen OS 13? I have been on stock for 2 weeks now due to a rumour of COS13 coming. If you have any news or even a beta build then please post it below.
Regards
Yasteel
AFAIK it's already released.
Android one Second Gen user here
nhmanas said:
AFAIK it's already released.
Android one Second Gen user here
Click to expand...
Click to collapse
really? I do not see it on https://cyngn.com/support
Dior DNA said:
really? I do not see it on https://cyngn.com/support
Click to expand...
Click to collapse
Ota released. Not ROM.
I though it was only the one plus one and only in india that rec'd the update
and still without the Modlife implementation
nhmanas said:
Ota released. Not ROM.
Click to expand...
Click to collapse
thanks! and what is name like cm-12.1 was YOG7DAS2FI crackling?
Dior DNA said:
thanks! and what is name like cm-12.1 was YOG7DAS2FI crackling?
Click to expand...
Click to collapse
I don't know we're discussing in a Turkish forum
nhmanas said:
I don't know we're discussing in a Turkish forum
Click to expand...
Click to collapse
once someone receives OTA cm 13 let us know, then we can ask support to publish file
Dior DNA said:
once someone receives OTA cm 13 let us know, then we can ask support to publish file
Click to expand...
Click to collapse
http://builds.cyngn.com/incremental/crackling/cm-crackling-c295bd1167-to-f865a1ad0e-signed.zip
6.0.1 ota
This is Cyanogen Mod, not Cyanogen OS.
koegs said:
This is Cyanogen Mod, not Cyanogen OS.
Click to expand...
Click to collapse
Has any flashed this to confirm exactly what it is
*edit* I'll confirm myself.. this is the real incremental to 6.0.1 'Mod ready' COS 13
To my surprise...it runs pretty well
ReneX10 said:
Has any flashed this to confirm exactly what it is
*edit* I'll confirm myself.. this is the real incremental to 6.0.1 'Mod ready' COS 13
To my surprise...it runs pretty well
Click to expand...
Click to collapse
updater-script says
Source 5.1.1 LMY48Y/YOG7DAS2FI
Target 6.0.1 MMB29V/ZNH0EAS25I
ReneX10 said:
Has any flashed this to confirm exactly what it is
*edit* I'll confirm myself.. this is the real incremental to 6.0.1 'Mod ready' COS 13
To my surprise...it runs pretty well
Click to expand...
Click to collapse
1. update package was verified without problems
2. installed without problems
3. won't boot... can't even get into recovery
InFlames0r said:
1. update package was verified without problems
2. installed without problems
3. won't boot... can't even get into recovery
Click to expand...
Click to collapse
Mine was a clean stock 12.1 install first, then update applied from recovery to 13
Mine is working just fine, no problems to report at all..... hrmm so, I wonder what's different
http://s32.postimg.org/vz9j03dhx/Screenshot_20160429_190709.png
Me too that's exactly what I did load 12.1 by fastboot to ensure everything is overwritten
note super su stock dosn't work but the beta does
I'm I noob here and I don't understand what everybody's talking about here. From my understanding, a flashable COS13 zip is out in the open and works? How should I go about flashing it if I want to keep TWRP recovery? Do I have to do a clean install?
seb5049 said:
I'm I noob here and I don't understand what everybody's talking about here. From my understanding, a flashable COS13 zip is out in the open and works? How should I go about flashing it if I want to keep TWRP recovery? Do I have to do a clean install?
Click to expand...
Click to collapse
as far as I am aware there is NO COS 13 zip for the crackling, only this incremental update (ie an update from 12.1, so that needs to be installed as a base first and then the update flashed from recovery)
There is CM 13, both snapshots and nightlies that an be flashed from TWRP as ZIPs
TWRP an be flashed from fastboot whenever you like, so that shouldn't cause you any major concerns :good:
ReneX10 said:
as far as I am aware there is NO COS 13 zip for the crackling, only this incremental update (ie an update from 12.1, so that needs to be installed as a base first and then the update flashed from recovery)
There is CM 13, both snapshots and nightlies that an be flashed from TWRP as ZIPs
TWRP an be flashed from fastboot whenever you like, so that shouldn't cause you any major concerns :good:
Click to expand...
Click to collapse
I have the stock rom already (COS 12.1), so does that mean I'm good if I flash it then?
seb5049 said:
I have the stock rom already (COS 12.1), so does that mean I'm good if I flash it then?
Click to expand...
Click to collapse
Personally I would ensure I have backed up, but in theory ..Yes, though if it were me.. I would, backup, wipe, flash stock recovery, update
I am afraid I can't answer fully, as I always flash clean...soz
ReneX10 said:
Personally I would ensure I have backed up, but in theory ..Yes, though if it were me.. I would, backup, wipe, flash stock recovery, update
I am afraid I can't answer fully, as I always flash clean...soz
Click to expand...
Click to collapse
Ok. Well, if I backup beforehand then I should be fine if anything goes wrong. One last question though, do I need stock recovery in order to flash the zip?