CyanogenMod 11 is a free, community built distribution of Android 4.4.X (KitKat) which greatly extends the capabilities of your phone.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is the support thread for CM11 on the AT&T Galaxy S3. It's a major work in progress. It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
Known issues:
Recording video can sometimes result in strange things happening. This includes random reboots or discoloration of the video stream.
Install instructions:
1. Install TWRP Recovery for "d2att".
2. Download your correct; updated bootloader/modem from here, and here.
3. Get the nightly build here.
4. Reboot into recovery and install both.
d2lte is all inclusive. It works with all of the phones listed here.
Google Apps are not included in this ROM. You'll need to find those yourself if you want them. (Or just follow the link below.)
I prefer this.
Follow the changelog!
http://www.cmxlog.com/11/d2lte/
First. Awesome feeling
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Second
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Awesome. Thanks for the new thread. Questions:
For someone coming from CM10 or earlier, is there a special bootloader that one needs to flash prior to flashing CM11?
Has there been an "M" release for d2lte?
Aqua1ung said:
Awesome. Thanks for the new thread. Questions:
For someone coming from CM10 or earlier, is there a special bootloader that one needs to flash prior to flashing CM11?
Has there been an "M" release for d2lte?
Click to expand...
Click to collapse
Updated OP with information regarding updating of bootloader/modem.
d2lte is all inclusive. It works with all of the phones listed here.
Please correct me if I'm wrong.
Will it still work on cwm recovery or do we have to have twrp?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
SeXyStEpH87 said:
Will it still work on cwm recovery or do we have to have twrp?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It will still work with CWM, but TWRP was recently updated to support some more aspects of KitKat, and it's what I use personally, and since I can confirm it works, I wanted to list it as my recommended recovery.
Any compatible kernels with the nightlies? I tried KT747 (3/9/14) and BMS (3/5/14) and they don't seem to work as the com.phone.application stops responding after a reboot from installing the kernel. In particular, I want to know why BMS doesn't work with CM11 because it's based on the same CM kernel and they even have the same Linux kernel (3.4.x) so what went wrong? What makes BMS kernel incompatible with the CM11 ROM? I'm currently using a d2lte build on an SGH-i747M.
GlassRaven said:
Any compatible kernels with the nightlies? I tried KT747 (3/9/14) and BMS (3/5/14) and they don't seem to work as the com.phone.application stops responding after a reboot from installing the kernel. In particular, I want to know why BMS doesn't work with CM11 because it's based on the same CM kernel and they even have the same Linux kernel (3.4.x) so what went wrong? What makes BMS kernel incompatible with the CM11 ROM? I'm currently using a d2lte build on an SGH-i747M.
Click to expand...
Click to collapse
Have you tried the Quantum Kernel?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
GlassRaven said:
Any compatible kernels with the nightlies? I tried KT747 (3/9/14) and BMS (3/5/14) and they don't seem to work as the com.phone.application stops responding after a reboot from installing the kernel. In particular, I want to know why BMS doesn't work with CM11 because it's based on the same CM kernel and they even have the same Linux kernel (3.4.x) so what went wrong? What makes BMS kernel incompatible with the CM11 ROM? I'm currently using a d2lte build on an SGH-i747M.
Click to expand...
Click to collapse
Make sure you're using the latest d2lte nightly. I had the same issue a while ago. Apparently it had something to do with a ramdisk update.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
RJantu said:
Make sure you're using the latest d2lte nightly. I had the same issue a while ago. Apparently it had something to do with a ramdisk update.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So after the 3-12-14 the incompatibility goes away? I haven't read the logs yet about the ramdisk update.
Sent from my SGH-I747M using Tapatalk
Not sure if you installed the Google Dialer, but that will cause issues with the latest CM builds, so it may not be kernel related but I'm guessing without more info. Check your System/add-on directory and see if you have a Google dialer entry. If yes, in the FAQ it walks you through the steps to take to clear out the dialer, which is basically wipe system, install ROM, install gapps, wipe caches, good to go.
GlassRaven said:
Any compatible kernels with the nightlies? I tried KT747 (3/9/14) and BMS (3/5/14) and they don't seem to work as the com.phone.application stops responding after a reboot from installing the kernel. In particular, I want to know why BMS doesn't work with CM11 because it's based on the same CM kernel and they even have the same Linux kernel (3.4.x) so what went wrong? What makes BMS kernel incompatible with the CM11 ROM? I'm currently using a d2lte build on an SGH-i747M.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
johnhazelwood said:
Not sure if you installed the Google Dialer, but that will cause issues with the latest CM builds, so it may not be kernel related but I'm guessing without more info. Check your System/add-on directory and see if you have a Google dialer entry. If yes, in the FAQ it walks you through the steps to take to clear out the dialer, which is basically wipe system, install ROM, install gapps, wipe caches, good to go.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
There's only the com.android. dialer entry that I've found so far. I've read the procedure that you suggested but I think that's the same thing as installing a new ROM and pushing out the GApps package again which might've included the Google dialer. AFAIK, CM intertwined the Dialer app with the Phone one so removing the Dialer one might not seem ideal..
Sent from my SGH-I747M using Tapatalk
To confirm it's in the add on folder, not the system folder. Meaning you shouldn't have a googledialer file in the add on folder.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Work on SGH-I747M of Telcel México? with 4.3 officialy, of course i need root.
Sent from my SGH-I747M using XDA Premium 4 mobile app
chivas1311 said:
Work on SGH-I747M of Telcel México? with 4.3 officialy, of course i need root.
Sent from my SGH-I747M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Read the OP.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Tried to flash the bootloader but it didn't work
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Flashing the bootloader didn't work? How do you know? What did you do? What file did you flash?
SeXyStEpH87 said:
Tried to flash the bootloader but it didn't work
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I flashed the one for my phone using twrp and it failed
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 09:05 PM ---------- Previous post was at 08:55 PM ----------
I flashed the one for my phone through twrp but it failed
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Anyone install 03/17 with any problems? Seems like a lot of changes were made.
Sent from my S3
Related
CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a nightly build of CM for the Galaxy S3 on Sprint.. It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
Please submit a patch to our Gerrit instance if you want to help out.
Install instructions:
1. Install ClockworkMod Recovery for "d2spr". Sorry, CM cannot provide support for other recoveries, although they may work fine.
2. Get the nightly build http://get.cm/?device=d2spr.
3. Reboot into recovery and install.
Do not report bug to the bug tracker if you are using this build.
Its on !
Sent from my SPH-L710 using xda premium
Still unable to get past the Galaxy S III screen on first reboot from recovery unfortunately
Running CWM 6.0.1.2
Is special formatting necessary?
http://d-h.st/fiX
minor update with minor changes
Now this is the real deal!!!!! THANKS for all your hard work
Sent from my SPH-L710 using xda premium
Yeah!
brooklyn718941 said:
Now this is the real deal!!!!! THANKS for all your hard work
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Definitely flashing this!!!
socioteq said:
Still unable to get past the Galaxy S III screen on first reboot from recovery unfortunately
Running CWM 6.0.1.2
Is special formatting necessary?
Click to expand...
Click to collapse
Booted fine for me. Did you wipe?
Sent from my SPH-L710 using xda premium
Ok, just realized my 4.2 gapps pack isnt working. Anyone using one that is?
Sent from my SPH-L710 using Tapatalk 2
Great work
Sent from my SPH-L710 using xda premium
maybe im asking a dumb question but in your cm10 preview u have in the instructions to flash gapps i dont see that for this 10.1 preview build do we not need to flash gapps?? just for clarification im asking
How are previews different from nightlies?
Sent from my SPH-L710 using xda premium
http://forum.xda-developers.com/showthread.php?t=2028167
Use gapps from here
Sent from my SPH-L710 using xda premium
ok so i installed this looks pretty nice but my sdcard wont mount now everything else works fine but that
noobnl said:
http://d-h.st/fiX
minor update with minor changes
Click to expand...
Click to collapse
This is the same link as in the op. I take it op was updated?
Awesome work, guys
Sent from my SPH-L710 using Tapatalk 2
cballin22 said:
ok so i installed this looks pretty nice but my sdcard wont mount now everything else works fine but that
Click to expand...
Click to collapse
Same here. But remember its a preview build expect bugs
Sent from my SPH-L710 using xda premium
cballin22 said:
maybe im asking a dumb question but in your cm10 preview u have in the instructions to flash gapps i dont see that for this 10.1 preview build do we not need to flash gapps?? just for clarification im asking
Click to expand...
Click to collapse
Does anyone have a link to 4.2 GAPPS???.. EDITED: My bad, didn't see BK718941's post before...THANKS!
i dont mind the bugs also it remamped my entire internal memory so might want to be aware of that also
socioteq said:
Still unable to get past the Galaxy S III screen on first reboot from recovery unfortunately
Running CWM 6.0.1.2
Is special formatting necessary?
Click to expand...
Click to collapse
I can't either. Coming from PAC man. Did the full wipe deal. Tried with the 1130 gapps as well as no gapps
cballin22 said:
i dont mind the bugs also it remamped my entire internal memory so might want to be aware of that also
Click to expand...
Click to collapse
Hmm this tweaks partition sizes?
socioteq said:
Still unable to get past the Galaxy S III screen on first reboot from recovery unfortunately
Running CWM 6.0.1.2
Is special formatting necessary?
Click to expand...
Click to collapse
Did you pull battery? Reboot...
Sent from my SPH-L710 using Tapatalk 2
Hello, I've worked with custom roms and such before, but only stable things. I installed the Cyanogenmod 10.1 nightly builds, and I've been updating them every day, through TWRP by just flashing the rom, and gapps. A snapshot was just released, and I was wondering if I just do it the same method, or do I have to do the wipe system and all that when you first install a brand new rom. I'm pretty sure I do it the same way, but I just want to make sure there isn't have to be anything else. Better safe than sorry.
Oh my why are you going through all that trouble CyanogenMod has a built in updater all you do is go to about and then CyanogenMod update I believe it will ask you the frequency to check for updates. Make sure you change the options to nightly builds. The phone will notify you when there's an update, after downloading the phone will update itself and all your apps will still be there so you won't need to flash G apps each time.
Sent from my SPH-L710 using xda app-developers app
The process to do this is called a "dirty flash" because you are flashing over what you already have without wiping again. Usually if its an updated version of the same rom you dont need to rewipe everything
However, if you come upon this in some other rom (you're updating to a new version of it), make sure that the OP's instructions dont mention a full flash, because the nature of some big updates WILL require you to do a full wipe and then flash
But for this specific case, just do what the guy above me said
Sent from my PG06100 using xda premium
So... Noob Question coming in 3 2 1.... What is a snapshot? How is it different from a nightly....
Sent from my SCH-R530M using xda app-developers app
belizaire said:
So... Noob Question coming in 3 2 1.... What is a snapshot? How is it different from a nightly....
Click to expand...
Click to collapse
It is a more stable build designation. Still not an official release. Think of it as a monthly nightly!
Thank you!
Sent from my SCH-R530M using xda app-developers app
I have the AT&T S3 running an 4.2.2 aosp custom rom "jellybam" and i really want to overclock but in the Performance Control it only lets me go to 1512MHz. Can some1 plz help me overclock it but still keep my rom.
Flash this kernel
http://forum.xda-developers.com/showthread.php?p=28399829
It's kernel related. You have to find kernel that support higher overclock.
Sent from my GT-I9300 using xda app-developers app
There is various kernels in the Original development thread that support overclock.
Make sure yo read the OP and figure out which is best for you and your phone.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
So i downloaded the file on my s3 booted into recovery and flashed it then i got stuck in a boot loop. I restored my phone but now what did i flash it wrong?
Sent from my SAMSUNG-SGH-I747 using xda premium
tylerray0040 said:
So i downloaded the file on my s3 booted into recovery and flashed it then i got stuck in a boot loop. I restored my phone but now what did i flash it wrong?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Could be a few issues.
You could be on an old version of JellyBam that does not use the 3.4 kernel. You also could have downloaded the wrong kernel from the page linked. If you could give us your ROM version that would help.
Its 7.5.0
But do u have to flash a kernel with odin
Sent from my SAMSUNG-SGH-I747 using xda premium
tylerray0040 said:
Its 7.5.0
But do u have to flash a kernel with odin
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Kernels are flashed in recovery, not Odin. The problem may be the recent display changes in KT's kernel. You may want to check his thread for an earlier build (pre 4/19) before the display commits were added.
CamFlawless said:
Kernels are flashed in recovery, not Odin. The problem may be the recent display changes in KT's kernel. You may want to check his thread for an earlier build (pre 4/19) before the display commits were added.
Click to expand...
Click to collapse
correct. flash his 4/11 release.
and if you ever find yourself in a bootloop from flashing the wrong kernel, just flash the correct kernel in recovery. wipe cache/dalvik, fix permissions and reboot. good to go without having to restore or reset anything.
also, i'd stick with ROMs in this forum that are supported by the dev.
Closing this one...as OP has posted duplicate thread here...http://forum.xda-developers.com/showthread.php?t=2246321
Code:
Built from source using [URL="https://github.com/Root-Box"]RootBox Repos[/URL] and [URL="https://github.com/victorator"]My Repos[/URL].
Feel free to use my repo to build your own roms.
Hi Guys!
Since the jflte family of devices is almost exactly the same I thought I would post my I9505 (jflte) Rom here for you as well!
It has been tested by jfltetmo and jfltecan users and is confirmed working!
To install it, just download the I9505 rom and then flash the appropriate device specific package I created.
Download the rom from this thread
Download the appropriate device specific package
Install CWM or TWRP recovery.
Boot into recovery, install ROM, then install the device specific package then install gapps.
Wipe Data/Factory Reset if coming from another Rom.
Reboot and enjoy!
Your device name might show up as I9505. If you are bothered by it you can edit the file /system/build.prop in the rom .zip package before you flash it.
This does not affect the way the rom functions in any way.
Please let me know if you have successfully installed and running this rom on any of the US variants of the S4. I don't own the device!
Donate to Bajee, the creator of this rom
Donate to CyanogenMod
Donate to AOKP
Click to expand...
Click to collapse
Devhost mirror for device specific packages
Thank you. This works flawless flashed on my att i337 s4 with ktoonsez kernel. Cheers.
Sent from my I9505 using XDA Premium HD app
Thank you for sharing. Definitely gonna give this a go.
Nice! Was wondering when rootbox was going to work on the s4.
Sent from my Samsung Galaxy S4
CZ Eddie said:
I would love to see this ROM for the AT&T Galaxy S4 (I337) if you have time.
Our bootloader has been bypassed via Loki:
http://forum.xda-developers.com/showthread.php?t=2292157
Click to expand...
Click to collapse
victorator said:
I'll post it on your forums.
Click to expand...
Click to collapse
Woot, that was fast. I just asked last night! Thank you! :good:
.
is bajee affiliated with this in any way?i used his rootbox rom on my s3 just curious?
djmouse said:
is bajee affiliated with this in any way?i used his rootbox rom on my s3 just curious?
Click to expand...
Click to collapse
It says Bajee in the OP.
I didn't notice any way of adjusting the kernel.
Have I missed something?
Sent from my I9505 using xda premium
Flash ktoonsez kernel. It comes with ktweaker. I got a 2.5 days with his ktoonservativeq governor and deadline on AOKP.
Sent from my I337 using XDA Premium HD app
I tried installing the ktoonz kernel, but my phone wouldn't boot up.
Sent from my SGH-I337M using xda premium
Gordietm said:
I tried installing the ktoonz kernel, but my phone wouldn't boot up.
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
Did you flash the AOSP version of KT's kernel? Wipe cache, fix permissions, etc.?
Sent from my SGH-I337 using Tapatalk 2
JediSooner said:
Did you flash the AOSP version of KT's kernel? Wipe cache, fix permissions, etc.?
Sent from my SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Yes I did.
Sent from my SGH-I337M using xda premium
Gordietm said:
Yes I did.
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
I flashed Koontz T-mobile AOSP kernel and works perfectly.
Sent from my I9505 using xda premium
Is the DPI supposed to be a 480 for all screens or just some of the screens/apps? Some screens still look tiny to me and I can't select more than 320dpi.
Using this ROM with kt's kernel on the at&t variant and phone calls reboot the phone, anyone else experiencing this?
Found the problem. Do not enable in call volume boost under device options - > sound.
Got the ROM flashed with Kt's aosp kernel. Few questions if anyone can help
How do I get rid of the on screen Nav bar and the circle menu on the lock screen?
And how do I get my signal and WiFi bars to be blue instead of gray?
Thanks for the help
Edit: also having bad connectivity problems. One bar to none where I would normally have 3-4 bars? What would cause this?
Sent from my I9505 using xda premium
Hm. After wiping, flashing RootBox-JB-i9505-victorator-20130528.zip, followed by jflteatt.zip, followed by gapps, my initial Samsung splash now has a "custom" lock icon underneath it, followed by a yellow triangle with exclamation point:
System software not authorized by AT&T has been found on your phone.
In tiny red text in the top right: "SECURE FAIL: KERNEL"
Looks like the kernel wasn't loki-patched for some reason? I thought this would be done for us as part of an i337 ROM distribution. Are we expected to loki-patch RootBox as part of installing it on the phone?
I think I followed the instructions... What am I missing?
djthread said:
Hm. After wiping, flashing RootBox-JB-i9505-victorator-20130528.zip, followed by jflteatt.zip, followed by gapps, my initial Samsung splash now has a "custom" lock icon underneath it, followed by a yellow triangle with exclamation point:
System software not authorized by AT&T has been found on your phone.
In tiny red text in the top right: "SECURE FAIL: KERNEL"
Looks like the kernel wasn't loki-patched for some reason? I thought this would be done for us as part of an i337 ROM distribution. Are we expected to loki-patch RootBox as part of installing it on the phone?
I think I followed the instructions... What am I missing?
Click to expand...
Click to collapse
The rom isn't loki-patched because it was made for the I9505 variant. You need to flash Kt's kernel (AOSP version) after flashing RootBox.
Sent from my SAMSUNG-SGH-I337 using xda premium
Guys I'm using the latest build of omnirom 4.4.1 the 26.12 build and I was just wondering is there a somewhat stable enough kernel that is compatible with it yet?
Sent from my SGH-I317 using xda app-developers app
Give this one a try,
http://forum.xda-developers.com/showthread.php?t=2239453
I haven't flashed it, but I will do it later today.
aradhaya10 said:
Guys I'm using the latest build of omnirom 4.4.1 the 26.12 build and I was just wondering is there a somewhat stable enough kernel that is compatible with it yet?
Sent from my SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
The cm 11 kernels should work fine. Pretty much any aosp kernel based on 4.4 will work.
Sent from my phone
Thanks I will give devil kernel a try.
Sent from my SGH-I317 using xda app-developers app
210euser said:
The cm 11 kernels should work fine. Pretty much any aosp kernel based on 4.4 will work.
Sent from my phone
Click to expand...
Click to collapse
Actually they have been some issues with some of the AOSP roms. example I tried to flash Devil on SlimKat a week back and it got stuck on a boot loop. As per the kernel dev it was due to each rom using different initramfs.
http://forum.xda-developers.com/showpost.php?p=47826836&postcount=178
jibust said:
Actually they have been some issues with some of the AOSP roms. example I tried to flash Devil on SlimKat a week back and it got stuck on a boot loop. As per the kernel dev it was due to each rom using different initramfs.
http://forum.xda-developers.com/showpost.php?p=47826836&postcount=178
Click to expand...
Click to collapse
This ^^^^..
The devs are working the kernels pretty hard right now...and I'm sure that devil kernel will be 4.4 capable before long...
We are just well ahead of the curve on 4.4...and devs need time to catch up on all of the extra mods....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
jibust said:
Actually they have been some issues with some of the AOSP roms. example I tried to flash Devil on SlimKat a week back and it got stuck on a boot loop. As per the kernel dev it was due to each rom using different initramfs.
http://forum.xda-developers.com/showpost.php?p=47826836&postcount=178
Click to expand...
Click to collapse
This is true. Hopefully most aosp rom should be built to boot the same.
Sent from my phone
Alright so might as well wait for the appropriate launch of a compatible kernel, thanks a lot guys
Sent from my SGH-I317 using xda app-developers app