Develop Bugs

[wip][rom][aosp] ns2

Change of plans, hopefully with the help of anyone who is willing I'd like to compile an aosp build for the Sprint GS2 from source instead of trying to hack a port together, as suggested in this thread and other places, it just feels like it will be a lot more of a fruitful experience for all involved and have a better end result.
(a big thank you to everyone who so far have been super encouraging and friendly with noob questions, it's much appreciated!, I hope that if you wanted to help with the port you'll help with this build as well!)
This is a WIP. Starting out with Samsung's open source platform and kernel instructions on how to build from aosp and I'll take it from there.
I've setup some repos to get this all started in one place:
Samsung SPH-D710 platform source - https://github.com/thefredelement/sph-d710_platform_source
Samsung SPH-D710 kernel source - https://github.com/thefredelement/sph-d710_kernel_source
Team Hacksburg kernel source - https://github.com/thefredelement/android_kernel_samsung_c1spr
Stock kernel initramfs (thanks buddy323!) - https://github.com/thefredelement/stock-initramfs-eg30-epic-4g-touch
https://github.com/thefredelement/Samsung-Galaxy-S2-Sprint-Epic-4G-Touch-AOSP-Build - will be where the build will live after I push over Samsung's platform make and upload it!
--- old stuff that will make your head spin ---
If anyone wants to continue working on this, feel free.
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: you don't want this...

Reserved for changelog, when hopefully it gets that far

Awesome to see a project like this, good luck in the port!
Sent from my SPH-D710 using XDA App

O_OMG <3 :-!
Sent from my SPH-D710 using xda premium

Good luck! Looking forward to this.

What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App

deano0714 said:
What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
This boots using the stock Sprint/Samsung kernel.

xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
What kernel are you using?

thefredelement said:
What kernel are you using?
Click to expand...
Click to collapse
im using stock

xploPR said:
im using stock
Click to expand...
Click to collapse
Did you wipe all of your user data before installation?
Do you get to the boot animation?

Constructive criticism would be for me to point out you must not have read the OP because it clearly said nothing works because we don't have a aosp kernel yet but you are just rude.
Sent from my SPH-D710 using xda premium

xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
ehusidic said:
The title clearly states its not ready or stable so chill out while the devs do what they do
Click to expand...
Click to collapse
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.

I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.

jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic ore infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
Sorry for the horrid insults I aimed at the complaining member. Too uncouth.
Sent from my SPH-D710 using xda premium

Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
Thanks for the heads up. I agree this is a much better idea.

jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
i like that mandatory vacations with paid vacations to hawaiii, can xda hook it up or what?

thefredelement , good luck. glad to see new devs... i hope to be there one day but i'm way off...
Thanks!

thefredelement said:
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: http://www.multiupload.com/OF1HXSSOCJ
Click to expand...
Click to collapse
hit me up i can get ur rom working with wifi/3g/4g/whatever. zedomax at gmail dot com

Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
I recall rumor about samsung sending a GS2 to Cyanogen so that he could "get to work". Guess that never materialized - or they gave him something else to do once they hired him...
Sent from my SPH-D710 using xda premium

it was one of the cyanogen devs that got a galaxy2 & they have nightlies for the gs2 now.... It should not be hard to get it ported over
....
One of the devs on teamhacksung was asking for people with the phone to help with it ..he ask on twitter like the 16th so they are probably working on it....
Sent from my SPH-D710 using xda premium

[rom][cm9][4.0.3][cdma] cm9 semi-kang

CM9 NIGHTLY (UNOFFICIAL SEMI-KANG) FOR CDMA TORO
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.

Glad your making a Rom, but...
1) its in the wrong forum and
2) you dont have a link because of your "probation" status of < 10 posts
Good luck with your work though!

Also there's (unofficial) builds by a CM developer in the development section already:
http://forum.xda-developers.com/showthread.php?t=1397122

@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.

toroidal_loop said:
CM9 NIGHTLY (UNOFFICIAL SEMI-KANG)
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.
Click to expand...
Click to collapse
I love seeing new developers come here everyday
One small issue though, this is posted in the wrong section. This should be posted in the GSM Galaxy Nexus Android Development or CDMA Galaxy Nexus Android Development (depending whether its GSM or CDMA)

toroidal_loop said:
@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.
Click to expand...
Click to collapse
Did you ever ask the guys from cm team before you post the kang build?I dont think this allowed.
Sent from my Galaxy Nexus using Tapatalk

Getting your post count up and then posting in Development would have been the thing to do. This will get lost in General, and I can't see it being moved to Development or everyone and his mate would be using that loophole.

@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
@Kalavere I'm not trying to get this moved to the Dev. If there's enough interest in it, I'll repost the thread to Dev when I'm able. The problem I had was that there wasn't a vanilla build of CM that I could find anywhere for the CDMA/LTE toro.

toroidal_loop said:
@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
Click to expand...
Click to collapse
Perfect .Just mention it because i dont want to see another locked thread

[ROM] Unofficial CyanogenMod 9.0.0 Testing builds for Epic 4G Touch

Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** If one of this builds bricks your phone, kills your cat or causes
** a thermonuclear war, don't point at us. We'll laugh at you.
** You decided to make this modifications to your Phone.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on experimental builds is the leading
** cause of male impotence.
Hey all, you may remember me from back on the cdma hero. Well, I decided to pick up dev'ing again, and have been pushing source up to my github for working code for ice cream sandwich on our Epic 4G touches. It's my pleasure to say it's mostly functional, with just a few bugs remaining, of which i'll post at the end of my thread here. If I didn't list some functionality you're looking for in the bugs list, either it already works, or i forgot about it. Chances are high that it already works, though . Once I get nightlies to run, i'll make another thread for that.
Follow me on twitter for updates, and testing builds Please, follow the instructions listed below for flashing, to prevent any damage to your phone
Or, for the lazy, click HERE which is also mirrored for a download, which will also be mirrored HERE. note that my laziness will probably hinder me from updating the OP frequently to keep up with my updates i post on twitter.
Don't forget to flash GAPPS if you're coming from a non-CM-based ROM
Kernel: FC07
Recovery: CWM
What works
- GPS
- Camera
- SMS/MMS
- YouTube
- External SD mounted to /emmc
- Pretty much everything else
Bugs
- apps2sd doesn't work for EXTERNAL SD
- Video recording doesn't decode the files properly to mp4, so the output is unusable
- Music occasionally FCs. Feel free to post some logcats (pastebin'd only) if this happens to you
Installation Instructions
*WARNING* There have been a number of people over the past 6 weeks experiencing HARD BRICKS of their E4GT when flashing ICS from ROGUE 1.2.1 on FB15 AND NEWER KERNELS. Please see THIS THREAD for more information. As such, I am STRONGLY recommending that ALL FLASHING of this ROM be done ONLY from the STOCK CWM EL26 RECOVERY (download) EDIT: As an update to this, we're fairly certain this issue is sporadically occurring whenever a partition is being formatted by the recovery. this led us to believe that the problem lies in the kernel samsung has been putting out in the leaks. Please, for your sake, use, a recovery with a gingerbread kernel when flashing this rom, or doing nandroids, or even doing data wipes.
First install of CM9
BACKUP your existing ROM
Did you backup your existing ROM? No? BACK IT UP, GENIUS
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED (*note* backup/restore seems okay, it's only the actual zip/kernel flash that risks bricking. See THIS THREAD for more information.)
Reboot to recovery (power+vol-up)
WIPE DATA
Flash CM9
Flash GAPPS
Reboot to system
After rebooting, if you go BACK to recovery, you'll be on Rogue 1.2.2
Upgrading CM9
This build will upgrade from any CyanogenMod rom just fine. Just, be sure you're using the EL26-CWM recovery when flashing this rom. read my Edit up above for further details.
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED (*note* backup/restore seems okay, it's only the actual zip/kernel flash that risks bricking. See THIS THREAD for more information.)
Reboot to recovery (power+vol-up)
Flash CM9
The newest update changes the way backuptools work for the install script. it reads custom user scripts in /system/add.d. Since the first rom i put out didn't have that, you'll need to reflash google apps after flashing cyanogenmod. after flashing this latest update, subsequent updates won't need you to reflash Google Apps
Wipe cache
Reboot to system
Enjoy!
EDIT: I updated the OP with the link to the rom. This is using some better coding for mms and sms receiving, and the LOS bug was fixed by the epiccm group, and pushed to mainstream cyanogenmod, so we we're benefiting from this. also, added in were sprint visual voicemail and sprint updates. There's surely other stuff i'm missing to add to what's working and what's not . Note that Cyanogenmod doesn't normally use stock kernel, rather it uses cm-kernel. the issue is that we don't have source for the kernel in ics, so we can't merge our board-files, etc into it just yet. But this isn't an issue, as far as functionality. It's just not the full CyanogenMod experience .
EDIT2: I had jerdog change the thread title to unofficial, because we aren't really in CM just yet. It's more because of my discrepancy, with not wanting the device tree to be pulled, because i'm still doing work on it.
EDIT3: Guys, don't be flashing any themes over this rom, reason being because i changed the framework files a bit in my source, and it hasn't been pulled into mainstream cyanogenmod yet.

Wow, I ran your stuff on my hero. So nice to have you here.

Sick great to have you here

Wow thank you so much I've heard great things about your work!
Sent from my SPH-D710 using xda premium

Woot woot I remember the old hero days...
Sent from my GSII.

Wow dude, my hero memories are rushing back to me! Great to see you here!
Sent from my SPH-D710 using xda premium

Nice, glad to have you here!

Man your about to be a real "hero", darchstar to the rescue, glad to have you here man. Ill be installing this since it comes with recovery, very small chance of a brick now,,, THANKS again.
Sent from a phone with kNOw CIQ ...

Good stuff buddy!
Sent from my SPH-D710 using xda premium

damn epic touch scene getting better and better with all these ics

**** yea glad to see you again
Sent from my SPH-D710 using xda premium

A quick note:
As with all CM9 ROMs, we have been seeing some RARE bricks (hard brick, unbootable, no download mode, blue LED of death) when flashing from FB?? and newer Rogue kernels. These are RARE but they DO happen. See this thread for more info: http://forum.xda-developers.com/showthread.php?t=1525495
I would recommend doing ALL of your flashing from EL26 StockCWM (if you can still find it).
You have been warned.

darchstar said:
Bugs
- Sporadic instances where 3g doesn't pick up coverage again, after coming out of low signal areas.
Click to expand...
Click to collapse
Have to keep waiting.

neatchee said:
A quick note:
As with all CM9 ROMs, we have been seeing some RARE bricks (hard brick, unbootable, no download mode, blue LED of death) when flashing from FB?? and newer Rogue kernels. These are RARE but they DO happen. See this thread for more info: http://forum.xda-developers.com/showthread.php?t=1525495
I would recommend doing ALL of your flashing from EL26 StockCWM (if you can still find it).
You have been warned.
Click to expand...
Click to collapse
thats some excellent advice

Oh man, darchstar's in? sh*t just got real. I wish I could just jump forward a few weeks.. Good to see you here!
EDIT: Darchstar, let me know if you want me to take this down, but I'm gonna put a link here to make it a bit easier: http://t.co/bn3AW0bD
EDIT 2: I evidently didn't make it big enough...LINK IS IN THIS POST [and Darchstar's twitter]UNTIL FURTHER NOTICE
I just put it here to save from the "where's the link" posts..
P.S. Downloading and I'm tweaking cause I'm so excited to flash this.

just flashed from fb27 with no issues but dont do it if your scurrrrrrred

Where's the link.
Sent from my SPH-D710 using Tapatalk

Will of fire said:
Where's the link.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
post 15 has the link

both links from your twitter and the one provided Above are not working.
Sent from my SPH-D710 using xda premium

Mms is sending but not able to download. Charging light works. Woohoo. Thanks for the release.
Sent from my SPH-D710 using Tapatalk

[ROM] Unofficial CM9 Testing builds for Epic 4G Touch

Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** If one of this builds bricks your phone, kills your cat or causes
** a thermonuclear war, don't point at us. We'll laugh at you.
** You decided to make this modifications to your Phone.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on experimental builds is the leading
** cause of male impotence.
Hey all, you may remember me from back on the cdma hero. Well, I decided to pick up dev'ing again, and have been pushing source up to my github for working code for ice cream sandwich on our Epic 4G touches. It's my pleasure to say it's mostly functional, with just a few bugs remaining, of which i'll post at the end of my thread here. If I didn't list some functionality you're looking for in the bugs list, either it already works, or i forgot about it. Chances are high that it already works, though . Once I get nightlies to run, i'll make another thread for that.
Please, follow the instructions listed below for flashing, to prevent any damage to your phone
Follow me on twitter and github for updates, and what's going on right as it happens.
I think i already mentioned this once, but please, follow the instructions below when flashing this rom, for your phone's sake!
Here is my build from 03-15-12
And a mirror
MD5 checksum: 3ca7871541bf1fb5ecba70fd9661baef
Google Apps: HERE
Kernel: FC14
Recovery: Stock
What works
- GPS
- Camera
- SMS/MMS
- YouTube
- External SD mounted to /emmc
- Pretty much everything else
Bugs
- apps2sd doesn't work for EXTERNAL SD... unless you unmount the internal storage
- Video recording doesn't decode the files properly to mp4, so the output is unusable
- Music occasionally FCs. Feel free to post some logcats (pastebin'd only) if this happens to you
Once again, follow the instructions below, for flashing this ROM!!!
Installation Instructions
*WARNING* There have been a number of people over the past 6 weeks experiencing HARD BRICKS of their E4GT when flashing ICS from ROGUE 1.2.1 on FB15 AND NEWER KERNELS. Please see THIS THREAD for more information. As such, I am STRONGLY recommending that ALL FLASHING of this ROM be done ONLY from the STOCK CWM EL26 RECOVERY (download) EDIT: As an update to this, we're fairly certain this issue is sporadically occurring whenever a partition is being formatted by the recovery. this led us to believe that the problem lies in the kernel samsung has been putting out in the leaks. Please, for your sake, use, a recovery with a gingerbread kernel when flashing this rom, or doing nandroids, or even doing data or cache wipes.
First install of CM9
BACKUP your existing ROM
Did you backup your existing ROM? No? BACK IT UP, GENIUS
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED
Reboot to recovery (power+vol-up)
WIPE DATA
Flash CM9
Flash GAPPS
Reboot to system
After rebooting, if you go BACK to recovery, you'll be on Rogue 1.2.2
Upgrading CM9
This build will upgrade from any CyanogenMod rom just fine. Just, be sure you're using the EL26-CWM recovery when flashing this rom. read my Edit up above for further details.
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED
Reboot to recovery (power+vol-up)
Flash CM9
The newest update changes the way backuptools work for the install script. it reads custom user scripts in /system/add.d. Since the first rom i put out didn't have that, you'll need to reflash google apps after flashing cyanogenmod. after flashing this latest update, subsequent updates won't need you to reflash Google Apps
Wipe cache
Reboot to system
Here's a README in my github, that has thanks and whatever comes with a README
Enjoy!
EDIT: I updated the OP with the link to the rom. This is using some better coding for mms and sms receiving, and the LOS bug was fixed by the epiccm group, and pushed to mainstream cyanogenmod, so we we're benefiting from this. also, added in were sprint visual voicemail and sprint updates. There's surely other stuff i'm missing to add to what's working and what's not . Note that Cyanogenmod doesn't normally use stock kernel, rather it uses cm-kernel. the issue is that we don't have source for the kernel in ics, so we can't merge our board-files, etc into it just yet. But this isn't an issue, as far as functionality. It's just not the full CyanogenMod experience .
EDIT2: I had jerdog change the thread title to unofficial, because we aren't really in CM just yet. It's more because of my discrepancy, with not wanting the device tree to be pulled, because i'm still doing work on it.
EDIT3: Guys, don't be flashing any themes over this rom, reason being because i changed the framework files a bit in my source, and it hasn't been pulled into mainstream cyanogenmod yet.
EDIT4: Hey, i updated the OP with the build from yesterday, that i built. wasn't really planning on giving it out, but it appears that everyone is already using it, so might as well post the link in the OP. Please, don't ask what's changed, because not much has really changed: for this i wasn't planning on posting it... but oh well, it's out . Enjoy

Unacceptable
There seems to be a significant amount of animosity that permeates throughout the Android related forums. I'm not certain as to why this is, nor do I want to hear any reason for justification; what I do know is that it is unacceptable.
As moderators, we spend more time cleaning up flame & troll posts than working on our own community contributions. Unfounded accusations such as KANG'ing serve to drive away those valued members who try to contribute to XDA ... further lowering the quality of threads and posts on this forum.
XDA is about bringing together folks who have similar passions about mobile technology. I would have expected more maturity and professionalism. Instead, I find a thread full of inflammatory posts ... it is not constructive and serves no purpose.
While the Forum Moderator(s) take time from their busy schedule to effect cleanup and "damage control"; further detracting of this thread once it is re-opened will result in permanent holidays for those involved, rest assured that appeals will be non-negotiable. I would encourage members who have posted in this thread to reacquaint themselves with the forum rules - the best moderation is self-moderation.
Forum rules, please read!

To make sure this is clear from the beginning, and since I had to close the previous thread due to trolling and abuse, there is no kanging go on.
sbrissen and darchstar are and have been collaborating for awhile on this, helping each other out in the true spirit of the community. This thread will remain closed until darchstar is ready to have it opened.
http://twitter.com/#!/sbrissen23/status/178160581851889664
https://twitter.com/#!/darchstar/status/178170605747716096
If you look at the github and commit log you'll see the collaboration going on between the two. darchstar is publishing the builds per an agreement between the two. This is open source and community involvement at it's finest.
Any trolling will not be tolerated.

Just took the plunge and flashed.... No problems with the flash and loving the rom.
Sent from my SPH-D710 using xda premium

Great.
Just want to say thanks Darch loving all the builds

Game plan:
Get source for ICS kernel so we can shut down brix city! Good things are coming

A HUGE thanks to the XDA community, darchstar, Sbrissen, and Team Rogue for putting out an excellent product on my E4GT!
Sent from my SPH-D710 using Tapatalk

Steady Hawkin said:
Game plan:
Get source for ICS kernel so we can shut down brix city! Good things are coming
Click to expand...
Click to collapse
+100000000000
coming from a new resident of brix city trying to upgrade from the 309 version to the 311 version blod, forgot I had changed the kernel to the fc07 rouge before nandroiding, stupid me, 35 dollars later and a refurb im back in business

@darchstar, are you wanting us to post bugs/issues here in the thread?

drdrewdown said:
@darchstar, are you wanting us to post bugs/issues here in the thread?
Click to expand...
Click to collapse
Sure, but i don't really want everybody to go on about the same issue over and over again. It really makes the thread really hard to look through, and find actual bug reports, with someone actually following proper protocol, and attaching as many log files as they can. i really do look at every post, btw. So yea please everyone be kind and help me out in this aspect here

darchstar said:
Sure, but i don't really want everybody to go on about the same issue over and over again. It really makes the thread really hard to look through, and find actual bug reports, with someone actually following proper protocol, and attaching as many log files as they can. i really do look at every post, btw. So yea please everyone be kind and help me out in this aspect here
Click to expand...
Click to collapse
cool, did you happen to see my post/everyone else commenting about the volume issue of playing music & receiving a notification of sorts (sms etc) where the volume gets really low until you toggle the levels
it's so easy to duplicate & i've tried looking through logcats but can't find anything particular. should i still pastebin something for you?
edit: i'm grabbing a cable now to capture some logs
&& it appears to only do it via the headphone jack

Anybody know of a vnc viewer that will work with this?
Sent from my SPH-D710 using xda premium

Good job Team, so far so good.. gonna test this out so more..

Thanks so much, been running great, and I could not be happier having darch, sbrissen, steady, and all the other greats on our team working together! Thanks again guys.

I'm not sure if this is a CM9 issue or a xda app issue but I just now noticed it with CM9 (since it's worked in the past with AOKP/Samsung leaks) Taking a screenshot and trying to upload it to any thread the app gives/says that the file is not a valid format. However I can upload it via the web without issues.

cidica said:
I'm not sure if this is a CM9 issue or a xda app issue but I just now noticed it with CM9 (since it's worked in the past with AOKP/Samsung leaks) Taking a screenshot and trying to upload it to any thread the app gives/says that the file is not a valid format. However I can upload it via the web without issues.
Click to expand...
Click to collapse
I get that every time I try to upload from the app since they updated. I am using a pre-update themed version for that reason
Sent from my SPH-D710 using xda premium

JohnCorleone said:
I get that every time I try to upload from the app since they updated. I am using a pre-update themed version for that reason
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
meh that's lame. Oh well guess it's time for a bug report to xda for the app then

everything for me is working decently well using it as daily so i love it
only issue that irks me is the very weak signal

Love it! Better than any Sammy ics leak, and prefer it over anything official even!? Everything looks great and is smooth. Unable to install sprint NBA mobile though as unable to install on any storage seems like. Also, mms is funky sometimes. Have to toggle 4g to fix.
Anybody notice super heavy battery drain between 14%-4%?
Sent from my SPH-D710 using XDA

Fyi to all, the feedback thread was moved to general and I updated the OP with tips made by others.
Here is the link:
[FEEDBACK]Darchstar CM9 ROM *Help,Tips, and Tricks*
http://forum.xda-developers.com/showthread.php?t=1543349
Sent from my SPH-D710 using Tapatalk

[FAQ] [REF] [GUIDE] Welcome to your device, T-Mobile Galaxy S4 (SGH-M919)

Welcome to your device. The Samsung T-Mobile Galaxy S4 (SGH-M919) is a great device! Why don't we learn about it before we go any further?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Other names associated with this device:
SGS4 ✓
Galaxy S4 ✓
SGH-M919 ✓
M919 ✓
Click to expand...
Click to collapse
This device is NOT a:
GT-I9500 ✗
GT-I9505 ✗
SGH-1337 ✗
SCH-1545 ✗
SPH-L720 ✗
SCH-R970 ✗
Click to expand...
Click to collapse
Device Specs:
Size and Weight:
- 5.4 x 2.7 x 0.3 inches
- 4.6 ounces
Operating System and Processor:
- Android 4.2 (Jelly Bean)
Battery Life:
- up to 15.5 hours talk time
- up to 18 days standby time
Memory:
- 2GB RAM, 16GB ROM
Connectivity:
- Sync methods: Bluetooth, WiFi, USB, NFC
- 4G Capable
- Wi-Fi Calling
- Audio and Multimedia
- T-Mobile TV
- GPS and Apps
- GPS enabled
International:
- UMTS: Band I (2100);UMTS/HSPA+: AWS Band IV / 2100 / 1900 / 850;Band II (1900);Quad Band GSM;LTE
- Hearing Aid Compatibility
- M3
Click to expand...
Click to collapse
Unique Features:
S Beam
Screen Share
S Voice
Smart Stay
Extended Gesture UX/Motion
Pop-up Play
Burst Photo
Best Photo
Click to expand...
Click to collapse
Great! What Android versions can be ran on this phone?
JellyBean - 4.2.2 - TouchWiz ROMs are 4.2.2 and there's a few CM10.1 ROMs out there still.
JellyBean - 4.3- CM10.2 ROMs are rolling out but remember, you may encounter bugs as it is still a WIP (Pretty stable, though.)
Click to expand...
Click to collapse
Cool, but I'm a noob, what should I start off with?
My suggestion to you is for you to run some TouchWiz ROMs to get you comfortable with the flashing, nandroiding, tweaking processes and then move on to something else. Above all read and search.
Click to expand...
Click to collapse
Okay, I see.. but I don't quite understand what flashing, nandroiding, tweaking, etc. mean?
* - anything and everything possible. A good example would be "All my friends live at 10* Croxley Street." This is saying that they are all live at 100, 101, 102, 103, 104, 105, 106, 107, 108 and 109.
Dev - See developer.
Developer - A man or woman who has created (developed) software.
ROM - 1. A modified version of the Android operating system operating system. 2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free (see open-source)
Open-source - (not to be confussed with free) A peice of software that is free to edit, use, distribute and share with no charge.
CM - See cyanogenmod
Cyanogenmod - A free open-source project based on the AOSP. It is a modded (see modded) version of the Android firmware
Firmware - see ROM (1)
Stock - An unchanged version of something. Example: I just flashed stock sense
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
FOTA - "Firmware over the air" this normally refers to ROM's but can refer to radio firmware (see OTA)
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM (1)
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
Radio Firmware - (see firmware) a type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
Kernel - An important part of all operating systems that handles the CPU and other vital components. A modded kernel may be used for overclocking.
Overclock - (not to be confused with underclock) to exced the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Underclock - to change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
Modding - To perform a mod
Modded - to have included mods
Modification - see mod
Governor - a system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop bellow the (just as eaisly configurable) minimum frequency.
Library's/Libs - a set of instructions for applications to use to function. A functioning camera lib would allow the camera to be used.
WFS - "Wildfire S" an armv6 device made by HTC in 2011.
Logcat - A logging system built into the ADB
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
SDK - "Software Development Kit" a set of tools used for software development.
WIP - "Work In Progress"
JDK - "Java Development Kit" an SDK for the java platform. It is needed to run the Android SDK.
JRE - "Java Runtime Environment" a collection of binarys and files to allow java software to execute.
Execute - To "run" or "start" a binary
Binarys - (sometimes called bin's) a group of executable files.
RAM - Could be one of three meanings: 1. Memory for the CPU to process processes. 2. Random Access Memory, a place where information can be used, executed from, modified, or deleted. 3. A type of sheep.
SD - Short term for MicroSD
Marvel - A gsm version of the phone
Marvelc - The cdma version of the phone
Marvelct - A rare Easten CDMA version of the phone.
Marvel* - all versions of the HTC Wildfire S (see *)
GB - Could mean one of two things. 1. Gingerbread or 2. Great Britain
Gingerbread - Android 2.3
Froyo - Android 2.2
Honeycomb - Android 3.x. it was never released or ported to the wildfire s because it was built for tablets.
Ice cream sandwich / ICS - Android 4.0. The latest version of Android.
CM9 - Cyanogenmod 9. A modified version of ICS. (see cm)
JellyBean / JB - Android 4.1 / 4.2 / 4.3 - The latest version of Android.
CM10 - Cyanogenmod 10. A modified version of JB. (see cm)
RUU - "ROM Update Utility" An automatic installer for Radio Firmware, ROM and HBOOT
HBOOT - The bootloader for all modern HTC Android phones.
Custom recovery - A o version of the stock HTC recovery to install unoffical ROMs.
AFAIK - "As far as I know"
KANG - The process of creating a code based of someone else's code.
Zipalligned - This is something that makes a ROM faster. If you can improve this please contact me!
Deodexed - Where ODEX files are moved into the actual applications
APK - "Android Package" an Android application
Click to expand...
Click to collapse
This was written by benjamingwynn and brought over to the Vibrant section by Woodrube, so thanks goes out to them!
Okay, I think I'm ready to begin! Where do I start?
You have a few ways to go here..
But before we continue, let me explain something to you. Our phones have this 'flash counter' built in.
There is a way to reset it after you've triggered it, so don't be alarmed.
Flash counter? What's that?
The flash counter is a binary counter built in Samsung phones that is used by Samsung to basically help identify if you have been tampering with your firmware and flashing unofficial software.
Each time you flash unofficial firmware via Odin, your binary flash counter goes up by 1.
Click to expand...
Click to collapse
Ah, okay.. is there anyway to bypass that?
Yes and no.
How to get root easier and faster, triggering the counter:
Chainfire has developed an way to flash a custom recovery and root your phone.
Visit this thread to download and see the many features it has: http://forum.xda-developers.com/showthread.php?t=2294005
Big thanks goes out to him for making things so simple!
Click to expand...
Click to collapse
NOTE: You CAN reset your flash counter to 0 using an application developed by Chainfire called Triangle Away which can be found here: http://forum.xda-developers.com/showthread.php?t=1494114
What can I do now that I have root?
You can backup your apps using Titanium Backup found in the Google Play store.
Use apps that require root.
Etc.
Click to expand...
Click to collapse
What can I do now that I have a custom recovery?
Make a NANDROID backup of your current setup and restore that backup!
Flash ROMs, modems, kernels, themes, etc.
Wipe data, clear cache, etc.
Click to expand...
Click to collapse
​
Credits and Thank you's:
- s15274n for his great guides and borrowed words!
- Woodrube for his great guides and borrowed words!
- Anyone else I may have missed.
Note: I will update this thread daily and keep everything current.
These are my ways of flashing my device and they have worked perfectly, there are other ways as well and they have been posted.
So look around if you find this confusing!

Useful Links and Resources​
How to SIM Unlock your S4: Here
[GUIDE] Better Battery life when Idle: Here
Click to expand...
Click to collapse
Useful Downloads​
Odin Program:
ODIN v3.07: Here
Stock File:
T-Mobile Galaxy S4 SGH-M919 UVUAMDL (Android 4.2.2) | ODIN FILE: Here
Recoveries (ODIN):
[CWM Advanced Edition] PhilZ Touch: Here
CWM Recovery (Non Touch) (IMG File): Here
STOCK Recovery (Touch) (IMG File): Here
Click to expand...
Click to collapse

How to ROOT your T-Mobile Galaxy S4 on a Mac / Linux PC using Heimdall​
Link: http://forum.xda-developers.com/showthread.php?p=45538268
Click to expand...
Click to collapse
How to ODIN back to stock after messing up trying to flash a ROM or rooting.​
Follow this amazing guide written by @k0nane
Link: http://forum.xda-developers.com/showthread.php?t=2258628
Click to expand...
Click to collapse
How to ODIN back to COMPLETE stock (Reset flash counter as well).​
Follow this amazing guide written by @djintrigue808
Link: http://forum.xda-developers.com/showthread.php?t=2336392
Click to expand...
Click to collapse

Frequently Asked Questions (F.A.Qs)
​
Q: I flashed back to stock, but my phone hangs at the Samsung logo, what do I do?
A: Don't forget after you ODIN, you have to boot into stock recovery, wipe data and cache, reboot!
Click to expand...
Click to collapse
Q: How do I get into Recovery Mode?
A:
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
Click to expand...
Click to collapse
Q: How do I get into Download Mode?
A:
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
Click to expand...
Click to collapse

Great idea.
Simple and to the point :good:
Btw, I was reading this:
"Battery Life:
- up to 15.5 hours talk time
- up to 18 days standby time"
Where can I get me one of these :silly::laugh:

From all the guides Ive seen for phones and ones Ive written while a staff member on Android Forums, I gotta say this is probably the cleanest most organized guide Ive ever seen. Very nice job man. Will help alot of people.

Added a new guide:
[GUIDE] How to ROOT your T-Mobile Galaxy S4 on a Mac / Linux PC using Heimdall

Great thread!! This is just what I needed. Thanks a lot.

i Have Q
is there somw way to track my mobile if stolen from me without internet enabled just only by GPS ??

themes...
Are there any other themes for wicked v9.1 beside the toxic green?
any help is appreciated.

Hotfile has been seized.

re: thread
Brianzdman said:
Great thread!! This is just what I needed. Thanks a lot.
Click to expand...
Click to collapse
I think that I may also have a good use for this thread. LOL

whats the truth?
I was looking around at various sources when I updated to MK2_4.3 from 4.2.2 and I read that once you've Flashed MK2, updated 4.3 that there is no way to go back down to 4.2 . . . is this true? Also is it possible and/or stable to flash 4.2.2 Roms from MK2?
---------- Post added at 01:15 PM ---------- Previous post was at 12:15 PM ----------
I was looking around at various sources when I updated to MK2_4.3 from 4.2.2 and I read that once you've Flashed MK2, updated 4.3 that there is no way to go back down to 4.2 . . . is this true? Also is it possible and/or stable to flash 4.2.2 Roms from MK2?

re: 4.2.2 - 4.3
Robot916 said:
I was looking around at various sources when I updated to MK2_4.3 from 4.2.2 and I read that once you've Flashed MK2, updated 4.3 that there is no way to go back down to 4.2 . . . is this true? Also is it possible and/or stable to flash 4.2.2 Roms from MK2?
---------- Post added at 01:15 PM ---------- Previous post was at 12:15 PM ----------
I was looking around at various sources when I updated to MK2_4.3 from 4.2.2 and I read that once you've Flashed MK2, updated 4.3 that there is no way to go back down to 4.2 . . . is this true? Also is it possible and/or stable to flash 4.2.2 Roms from MK2?
Click to expand...
Click to collapse
That is only true if you have done one of these three thing:
#1: Allowed OTA update to 4.3
#2: Updated to 4.3 using Kies
#3: Odin flashed the official stock 4.3 firmware from http://SamMobile (or elsewhere)
If you have not done any of those three things you can go back and forth between 4.2.2 and 4.3.
Good Luck!

Misterjunky said:
That is only true if you have done one of these three thing:
#1: Allowed OTA update to 4.3
#2: Updated to 4.3 using Kies
#3: Odin flashed the official stock 4.3 firmware from http://SamMobile (or elsewhere)
If you have not done any of those three things you can go back and forth between 4.2.2 and 4.3.
Good Luck!
Click to expand...
Click to collapse
How would I know if I were able to flash 4.2.2 Rom or not? Just give it a try and if it works then im good and if not it will say error or what (I am just asking so I don't try something and screw things up)
Also kinda off topic but Ive been trying to Flash a jfltexx Rom which is the GT-9505 int variant, I tend to use alot of their Roms and never have problems but latley when flashing aosp based roms like omni it says that i could only use jfltetmo builds, I was thinking that I could flash a TW based build like Foxhound or something then factory reset and flash from there and maybe it would register as a jfltexx but so far no luck. Thanks again

re: 4.2.2 roms
Robot916 said:
How would I know if I were able to flash 4.2.2 Rom or not? Just give it a try and if it works then im good and if not it will say error or what (I am just asking so I don't try something and screw things up)
Also kinda off topic but Ive been trying to Flash a jfltexx Rom which is the GT-9505 int variant, I tend to use alot of their Roms and never have problems but latley when flashing aosp based roms like omni it says that i could only use jfltetmo builds, I was thinking that I could flash a TW based build like Foxhound or something then factory reset and flash from there and maybe it would register as a jfltexx but so far no luck. Thanks again
Click to expand...
Click to collapse
Personally I stay away from roms like that, I just stick to the
M919 Samsung Jellybean Touchwiz based custom roms.
Don't get me wrong I tried basically all of those AOSP/AOKP/CM/GE/KitCat and the Ported roms
but found that they all have one thing in common, they are basically stripped bare from all the niceties
and the bells and whistles which make the M919 Tmobile Jellybean Touchwiz based roms so excellent.
Since I am really not too much into those other roms, I would hate to guess at giving you or anyone
else any suggestions as to how to fix any issues you are having with those other roms.
As far as trying to go back to the M919 4.2.2 Jellybean Touchwiz based custom roms go it's easy,
just make a nandroid backup of your existing rom and see for yourself, if you don't get any errors
or other unusual issues trying to flash those roms then then you are Ok and need not worry about
the KNOX pox.
Remember there are only three ways to get KNOX on your phone as you saw in my previous post.
Good luck!

Turn off Amber Alert
I am running Wicked V9.1 on both my and my wife's phone. She, but not I, keeps getting Amber Alerts - 8 today alone. Is there any way to stop receiving them?

hisself said:
I am running Wicked V9.1 on both my and my wife's phone. She, but not I, keeps getting Amber Alerts - 8 today alone. Is there any way to stop receiving them?
Click to expand...
Click to collapse
It might be coming from Cell Broadcast.. I'm not sure if Wicked has it or not but I remember getting amber alerts from the cell broadcast that was on the cm rom and there was settings on there to turn it on & off or if you wanted it keep it on you were able to control the types of emergency's to get alerts from like weather emergency's like hurricanes etc or amber alerts
Sent from my SGH-M919 using XDA Premium 4 mobile app
---------- Post added at 12:47 PM ---------- Previous post was at 12:36 PM ----------
Misterjunky said:
Personally I stay away from roms like that, I just stick to the
M919 Samsung Jellybean Touchwiz based custom roms.
Don't get me wrong I tried basically all of those AOSP/AOKP/CM/GE/KitCat and the Ported roms
but found that they all have one thing in common, they are basically stripped bare from all the niceties
and the bells and whistles which make the M919 Tmobile Jellybean Touchwiz based roms so excellent.
Since I am really not too much into those other roms, I would hate to guess at giving you or anyone
else any suggestions as to how to fix any issues you are having with those other roms.
As far as trying to go back to the M919 4.2.2 Jellybean Touchwiz based custom roms go it's easy,
just make a nandroid backup of your existing rom and see for yourself, if you don't get any errors
or other unusual issues trying to flash those roms then then you are Ok and need not worry about
the KNOX pox.
Remember there are only three ways to get KNOX on your phone as you saw in my previous post.
Good luck![/QUOTERom.
Yeah I know what you mean... I agree with you about touchwiz ROMs compared with aosp/aokp/cm/pa/...
I was just asking because I've had this problem before and some how it went away and I never thought of it again until this last week went trying to flash Omni Rom...
What is your favorite Rom or some of your favorites... Like do you use several different roms or do you stay with a particular rom update to update?? Just wondering
Click to expand...
Click to collapse

re: roms
Robot916 said:
It might be coming from Cell Broadcast.. I'm not sure if Wicked has it or not but I remember getting amber alerts from the cell broadcast that was on the cm rom and there was settings on there to turn it on & off or if you wanted it keep it on you were able to control the types of emergency's to get alerts from like weather emergency's like hurricanes etc or amber alerts
Sent from my SGH-M919 using XDA Premium 4 mobile app
---------- Post added at 12:47 PM ---------- Previous post was at 12:36 PM ----------
Misterjunky said:
Personally I stay away from roms like that, I just stick to the
M919 Samsung Jellybean Touchwiz based custom roms.
Don't get me wrong I tried basically all of those AOSP/AOKP/CM/GE/KitCat and the Ported roms
but found that they all have one thing in common, they are basically stripped bare from all the niceties
and the bells and whistles which make the M919 Tmobile Jellybean Touchwiz based roms so excellent.
Since I am really not too much into those other roms, I would hate to guess at giving you or anyone
else any suggestions as to how to fix any issues you are having with those other roms.
As far as trying to go back to the M919 4.2.2 Jellybean Touchwiz based custom roms go it's easy,
just make a nandroid backup of your existing rom and see for yourself, if you don't get any errors
or other unusual issues trying to flash those roms then then you are Ok and need not worry about
the KNOX pox.
Remember there are only three ways to get KNOX on your phone as you saw in my previous post.
Good luck![/QUOTERom.
Yeah I know what you mean... I agree with you about touchwiz ROMs compared with aosp/aokp/cm/pa/...
I was just asking because I've had this problem before and some how it went away and I never thought of it again until this last week went trying to flash Omni Rom...
What is your favorite Rom or some of your favorites... Like do you use several different roms or do you stay with a particular rom update to update?? Just wondering
Click to expand...
Click to collapse
For years now my favorite rom has been and still is @evil1art 's "Wicked" custom rom.
Other people have their own favorites, but Wicked rom is and has always been mine.
Good luck!
Click to expand...
Click to collapse

Yeah I like Wicked also, very stable well rounded Rom