Related
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Syndicate is THE best imo
PS: make sure to enable journaling right after flashing it.
Best ROM
As I'm sure you've read before, every phone acts differently. Most people seem to gravitate towards ACS or Bonsai. For me, ACS was buggy and Bonsai was, while extremely fast, the worst on battery life.
I personally have had the most luck with the current MidNight ROM and more recently Simply AOSP. Even though there seem to be hundreds of threads on tweaks and hacks, most don't seem to take well to my phone. The big ones (No CIQ, for example) seem to be included in about everything now.
Give 'em a go, see what works. I can safely recommend the two above.
Yup id go with Srf 1.1.1 (1.11?) Best imo
Sent from my SPH-D700
Sturmie said:
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Click to expand...
Click to collapse
Bonsai 4.1.1
SRF 1.1.1
Midnight series
Frankenstein
Urban Fury
ACE 2.0
Supernova 3
All are great ROMs
Not sure how to get the other CWM back. I like Bonsai's recovery But, if you use Quickboot and boot into recovery it takes you to CWM and not the Bonsai recovery.
Maybe you got a bad download of the Bonsai 4.1.1? Did you try to reflash it after all the FCs? Did you post in the Bonsai forum or Bonsai thread here?
You could always Odin back to stock and just start fresh that way also. Then just root with One click and get your CWM that way.
2 rules I follow about ROMs
1. No ETAs lol
2. YMMV
Everything with our phones...is phone dependent, they are completely different from the next Epic
Edit:
Sorry to the Devs that I didnt list ROMs from! These were the ones that were just on my sd card right now!
Sturmie said:
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Click to expand...
Click to collapse
Use Odin Flash back to stock ECO5 rom.
You can then Flash back to clockwork using odin following the thread instructions for the specific rom you want to work with.
I like ACS Swiss Cheese it works great as long as when you are in a stock rom you get a lock for the gps before installing swiss cheese. There are several threads that explain load order for it to install correctly. I have had it running for near month now with no problems.
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Sturmie said:
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Click to expand...
Click to collapse
You should use Titanium Back and backup your information using nanroid to avoid FC errors. If just remember there newest Rom is only compatible with there own kernel. If you try another Kernel with it your won't get the stellar battery life. I am using a combination of Bonsai and anonymous gingerbread and it is working out well with me. I ran Bonsai and back up all my information on Bonsai then I flashed gingerbread and recovered the Bonsai Rom on top of it.
Sturmie said:
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Click to expand...
Click to collapse
I would definitely go e it another shot. Try using the enable_journal zip in the Bonsai Downloads section first, then flash the ROM. That should help you avoid the FC issues until you get the installation errors ironed out.
Sent from my SPH-D700 using Tapatalk
I had the same issues with my first Bonsai install, but then I ODINd back to STOCK EB13, used Bonsai One click root, wiped 3x, and installed. It is now totally flawless. Give that a shot, it only takes about 30 minutes total.
lattiboy said:
I had the same issues with my first Bonsai install, but then I ODINd back to STOCK EB13, used Bonsai One click root, wiped 3x, and installed. It is now totally flawless. Give that a shot, it only takes about 30 minutes total.
Click to expand...
Click to collapse
From what I've read, coming from EB13 is the best way to go. Even if you Odin EC05, it still seems to have problems. Their dev, Randy, knows the ins and outs of why, so I would suggest Odining EB13, rooting with with their unlocker, then flashing their newest ROM.
I personally use SRF 1.1.1 w/ the Genocide 1.0 kernel, and don't have any major complaints outside bluetooth being wonky after each restart. For me, SRF is stable enough where I don't need to reboot but once a week, if that, unless I'm changing things around.
This. Path of least resistance for Bonsai is definitely ODIN'ing EB13. And 4.1.1 has great battery life in my experience.
Atm, the biggest deciding factor on ROM's to use has to be whether you want to stay on Froyo or do you want to be on Gingerbread.
hayzooos said:
From what I've read, coming from EB13 is the best way to go. Even if you Odin EC05, it still seems to have problems. Their dev, Randy, knows the ins and outs of why, so I would suggest Odining EB13, rooting with with their unlocker, then flashing their newest ROM.
I personally use SRF 1.1.1 w/ the Genocide 1.0 kernel, and don't have any major complaints outside bluetooth being wonky after each restart. For me, SRF is stable enough where I don't need to reboot but once a week, if that, unless I'm changing things around.
Click to expand...
Click to collapse
I would also suggest using Titanium Backup and MyBackUp root sparingly. Not that they don't work but it seems many users troubles always start with restoring old data from Titanium/MBR. I have also found SMS Backup & Restore to be a good option for those wanting to save and restore your txts over using TB/MBR which seems to foul things up when restoring txts.
Don't install any data from previous roms unless it was done by Bonsai during the install. Totally avoid any system data. Old saying: garbage in garbage out...
Sent from Bonsai 7.1.1.1
Looks like I'm not the only one that continues to have issues with Bonsai... everytime I flash Bonsai updates my phone goes wonky and I have to start over again with a factory reset.
After factory resetting to fix my microphone while in a call...now my Slacker will not advance to the next song by itself.
Really looking hard at SRF at this point!
digiblur said:
Looks like I'm not the only one that continues to have issues with Bonsai... everytime I flash Bonsai updates my phone goes wonky and I have to start over again with a factory reset.
After factory resetting to fix my microphone while in a call...now my Slacker will not advance to the next song by itself.
Really looking hard at SRF at this point!
Click to expand...
Click to collapse
You didn't need to reflash to fix the mic, it's a setting in VooDoo.
try EC05 Plus out, quick stable, and good on battery life...
I use Bonsai /w journaling. It is the only ROM that has stayed stable for weeks. Others go bonkers at some point especially w/o jounaling. No offense to ACS but I have yet to have one of their ROMs start and stay stable. Baked stuff is 2nd closest.
Acs srf 1.1.1
Sent from my SPH-D700 using XDA Premium App
I have been on Urban Fury since launch day (March 29 I think) You get 1 FC on the wallpaper app on install and that's it. I have been beta testing themes and kernels and have NEVER had data corruption or force closes other than the one on boot. It comes with Genocide kernel and Wifi Tether 3 pre 14 works great. That being said, all of the ROMs are good. Its just a matter of what you and your phone like the best
Sent from my SPH-D700 using XDA Premium App
Okay folks, if somebody could bring my issue to the attention of anybody who knows what to do about it I would appreciate it.
My issue is twofold:
1)I'm still getting random reboots with RandomROM Thunderhawk 3.3 despite the posting on the thread that says (NO MORE REBOOTS) Is there anything that can be done about this?
2)I checked my baseband version and the modem is still EC05, is there a way to flash or ODIN an EI22 modem for this ROM without getting a black screen when the icons should come up? Could this also be what's causing the reboots?
Thanks for anybody's help that is willing to give it.
Are you using a custom theme? And you have to flash the stickied modem delta. If you are using a theme, I would blame that.
Sent from my ICS NookColor using Tapatalk
I was using thunderhawk too and I had some reboots but onlyyyyy on the lockmod version. When I flashed the regular one I had no problems at all
And for basband I would probably try this
Nandroid backup
Flash "ec05 to ei22" its somewhere in the development section I believe
Reboot
If that doesn't work then a fresh new start is what I would Recommend
Odin back to stock
Root
Install cwm
Flash "eco5 to ei22" modem
Flash thunderhawk 3.3 (without lockmod if you could live without it)
Sent from my SPH-D700 using XDA App
I got the EI22 modem here and flashed it in CWM and it worked well. Only problem I had with thunderhawk is the lockscreen mod, and I'm having data issues on wifi after the phone's been on a while.
I was ec05 but when I flashed the Thunderhawk and it changed to ei22. never had a problem. Got a wild hair up my butt to flash the shadow kernal 1.0.6. Never been happier. no reboots, wifi works perfect, and very responsive. running a live wall paper and still get awesome battery life. give it a try
I saw several posts from folks having some wifi-4g interaction problems...switching back and forth causing one or the other to fail...is that a common problem to all 3.3 users, or are most people not seeing it? I want to give this a try, but I use 4g (at work) and wifi (home) everyday, so I'd like to see how common that issue is. I'm currently on Mostly-stock with Nubernel's latest released kernel...
Sent from my SPH-D700 using XDA App
So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App
You could always try a clean install with doing a factory data reset in CWM and wiping Dalvik, flash ROM, check to see if stuff works, then do an advanced data restore from your last nandroid. If you stll have problems then the best bet is to set everything up fresh after the clean install.
Cluefree said:
So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
The deal with the wifi/4g issue is that 4g will show 0.0.0.0 for ip, baseband, and dns if used after wifi in most cases. This is on official releases of 3.3 and newer. If you turn off wifi, reboot, then turn on 4g it should work. This is oviously annoying. Random provided me with alpha builds of 3.4 and 4.0, and the issue was squashed for me. However, the issue still persists in 3.4.3 official release according to some reports. I have limited access to 4g and can only test on certain days.
Thunderhawk is in a transitional period right now, and 3.4.5 should be released today. Random is hopeful this might solve some issues, including the dialer issues some are reporting with the 3.4 official builds. After that his focus will be on 4.0, which is EL30 based. Consider anything from 3.4 on a beta, and only run it if you want to help find bugs. Obviously you don't mind reporting or I wouldn't be replying lol. Just follow the threads and wait untill it looks stable enough for your usage needs.
Sent from my SPH-D700 using xda premium
Thanks! I certainly wasn't busting on Random's work...and I know he has limited access to 4g for testing, so that makes it harder for him to verify these things. So
I absolutely saw what you describe going from wifi to 4g. Going from
4g to wifi, I had wifi that wouldn't turn on at all (error when trying to enable), and, like you and others have mentioned, a reboot resolved both cases. I will hang out and see if he pushes out a fix soon, and just eagerly await 4.0. If it gets too annoying, I'll restore to my
Mostly Stock... Hmmm... Is there an issue restoring an rfs backup if I am now on ext4? Heh...
Sent from my SPH-D700 using XDA App
Just installed the latest 3.4 revision...I think...Heh. The update was so fast its hard to tell!
Sent from my SPH-D700 using XDA App
And...confirming...the wifi/4g issue persists. 4g ip address is messed up on the first connect after being on wifi...reboot resolves.
Sent from my SPH-D700 using XDA App
I posted this over at rootz earlier today and didn't get any bites so I figured I'd give it a shot over here.
I may be the only one in the world experiencing this problem. Looked around quite a bit and don't see any sign of others having this issue... Anyway, my N7 doesn't seem to like it when I flash a new kernel. I've tried several different kernels and when ever I flash one my display will not wake up once it times out or if I turn the display off manually. Once the screen goes dark i have to hold the power button down and reboot. I have zero issues with custom kernels as long as they are baked into the rom. I typically wipe cache and dalvic after flashing kernels...
Sent from my Galaxy Nexus using xda app-developers app
Little bump here... 130 views and not a peep... :-/
scram99 said:
Little bump here... 130 views and not a peep... :-/
Click to expand...
Click to collapse
youre experiencing "sod", which is a fairly common problem with android 4.2.1 source code(not as common on the n7 as the gnex, but common enough). do you flash the kernel with the rom or do you flash the kernel separately?
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
scram99 said:
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
Click to expand...
Click to collapse
I would just factory reset and start from scratch. Do you have any settings set like UV??
Sent from my Nexus 7 using xda premium
I have tried flashing back to stock, relocking and starting from scratch. I do not undervolt...
A few good folks in the android community had experienced similar happenings and suggested lean kernel... Flashed it earlier this evening and working like a charm.
I was running SlimBean till now, and felt like going back to CM9 (a really old but relatively less leggy build, 0627 to be exact). But everytime i booted up , it said encryption unsuccessful.
I don't know much about this, but does it have something to do with ext4 partitions or something? I don't know what that is either but I think it has something to do with that.
Also, I can't run Quarx's latest builds unless I flash a new sbf I think. Can anyone guide me with that too?
Any help appreciated
Edit: never mind. Fixed it
Sent from my iPad using Tapatalk HD
My son in law just gave me his K1. He got a new Google Nexus. I have successfully rooted my Verizon SGS3 by reading the threads here on XDA and I am happy with that. Now here's my problem. The K1 is a WiFi version running stock 3.2.1. I want to root and load a custom ROM. My main use for this K1 will be streaming video from Wifi to HDTV using HDMI , streaming audio from Wifi to Bluetooth speakers, and using Google video chat over Wifi. After reading through Khanning, Krook1, and Kaschemme threads I am not quite sure where I should start. I would like to use the latest from Kaschemme but I sure not sure if it would be best for uses. Thanks much in advance for any input/guidance.
12/16/2013
I've decided to go ahead and nvflash cm10.1 wifi kaschemme, then flash his latest 10.1.3 release, and finish by flashing gapps jb 20130424 nonneon. Does this sound right?? I hope so. I wish I could get this post moved to Kaschemme's thread. I am a noob and could not start it there. Thanks again to XDADevs for being here. It is a great resource.
12/17/2013
Change of plan!! I am noob so after more reading and digesting I see that the CM ROM's may have problems with both Bluetooth and WiFi. Therefore I am going to start with the latest khanning K1_JB_AOSP nflash and work my way from there. Wish me luck. I hope to pull the trigger today or tomorrow.
fhem said:
My son in law just gave me his K1. He got a new Google Nexus. I have successfully rooted my Verizon SGS3 by reading the threads here on XDA and I am happy with that. Now here's my problem. The K1 is a WiFi version running stock 3.2.1. I want to root and load a custom ROM. My main use for this K1 will be streaming video from Wifi to HDTV using HDMI , streaming audio from Wifi to Bluetooth speakers, and using Google video chat over Wifi. After reading through Khanning, Krook1, and Kaschemme threads I am not quite sure where I should start. I would like to use the latest from Kaschemme but I sure not sure if it would be best for uses. Thanks much in advance for any input/guidance.
12/16/2013
I've decided to go ahead and nvflash cm10.1 wifi kaschemme, then flash his latest 10.1.3 release, and finish by flashing gapps jb 20130424 nonneon. Does this sound right?? I hope so. I wish I could get this post moved to Kaschemme's thread. I am a noob and could not start it there. Thanks again to XDADevs for being here. It is a great resource.
12/17/2013
Change of plan!! I am noob so after more reading and digesting I see that the CM ROM's may have problems with both Bluetooth and WiFi. Therefore I am going to start with the latest khanning K1_JB_AOSP nflash and work my way from there. Wish me luck. I hope to pull the trigger today or tomorrow.
Click to expand...
Click to collapse
CM 10, both Krooks and Kashemme had working Bluetooth and HDMI. That ended with CM 10.1. I WOULD RECCOMMEND kACSHEEMES cm10 you can use his NV flash to run the root and install the recovery. Don't use the non neon gapps with CM 10, you can use the Rootzwiki GAPPS. The other reason to use the Kaschemme is that he is still kind of around.
jerryatherton said:
CM 10, both Krooks and Kashemme had working Bluetooth and HDMI. That ended with CM 10.1. I WOULD RECCOMMEND kACSHEEMES cm10 you can use his NV flash to run the root and install the recovery. Don't use the non neon gapps with CM 10, you can use the Rootzwiki GAPPS. The other reason to use the Kaschemme is that he is still kind of around.
Click to expand...
Click to collapse
I have already flashed Khanning's latest JB AOSP. Can I now simply put Kacshemme's CWM cm10 zip on my extcd and flash it over Khanning's.Should I back up app my apps with TB and restore or can I just flash w/o a wipe. I have also made an android back up of what I got to my extcd. Thanks again for the help.
Sorry I reread both Krook and Kaschemme and I see I do have to go the nFlash route again. No problem. I am curious though. If I use TB to back up all my apps to my extcd can I just then restore them once I get TB reinstalled?
Got it to quote you - "That is not common, i have been running it since September on 4 different k1 tablets an there are no issues. Are you doing a clean flash? Are you using the Neon GAPPS in the OP? I also reflash gapps every time i do an update."
K1 nFlashed K1-WIFI_CM10_JB_07052013
Jerry/anyone,
I nflashed Kaschemme's CM10 in title to replace khanning K1_JB_AOSP and flashed signed gapps-jb-20122111. I really like the ROM but I have a major problem and some general questions. I now have CWM v6.0.2.8 w/ android 4.1.2 and kernel version 2.6.39.4. My major problem is that I have no audio feed with the HDMI. The video is good no audio!!! It worked with JB_AOSP! This is no good I use the K1 to stream NetFlex to HDTV. The audio comes across the K1 speakers, ear buds but no HDMI. Any thoughts help???? Do I need to go back?? Also I thought this ROM provided the option to overclock to 1.4. I can't find this option. Max I can pick is 1.0?? Any and all help is needed and appreciated. Thanks to all and Merry Christmas.
Flashed Kaschemme CM 10.1.3 w/ CWM
OK I decided I can live w/o BT so.........................I used CWM to wipe data/factory reset, wipe cache partition, wipe dalvik cache , flashed CM10.1.3 zip booted up and let things settle down. I rebooted into recovery and flashed the nonneon gapps. Rebooted and logged into my google account. Downloaded TiBU and batch reinstalled missing apps. All went very well and I am happy. I only needed to download a couple apps from the play store. I OC set at min 456 max 1400 and using interactive governor. I have good WiFi, good HDMI, good head phone and video streaming to HDTV. I see my CWM was also updated. So far this is a great performing ROM. Thanks to all and especially Kaschemme for his hard work. Merry Christmas to all. BTW I got 10,501 AnTuTu. Good enough for this ole retired guy
Requesting for ROMs and Drivers for K1
Hello! I am just wondering if you have still saved the other ROMs for this K1, and drivers if in case. I am facing a serious issue on my K1, I just got stuck on APX mode whether I press the vol + and - with power or don't press the 2 volume keys I always get into APX mode. Actually this is the 2nd time it happened to me, but now no luck it has been for todays already. Hope you can help me send all your things (ROMs and drivers) for K1 and I will try to revive my device. Cheers! Merry Christmas and Happy New Year!
johnwilliam_a_k_a_trash said:
Hello! I am just wondering if you have still saved the other ROMs for this K1, and drivers if in case. I am facing a serious issue on my K1, I just got stuck on APX mode whether I press the vol + and - with power or don't press the 2 volume keys I always get into APX mode. Actually this is the 2nd time it happened to me, but now no luck it has been for todays already. Hope you can help me send all your things (ROMs and drivers) for K1 and I will try to revive my device. Cheers! Merry Christmas and Happy New Year!
Click to expand...
Click to collapse
Try one of the NVFlash ROMs while you are in APX.
Sent from my TouchPad using XDA Premium HD app
jerryatherton said:
Try one of the NVFlash ROMs while you are in APX.
Sent from my TouchPad using XDA Premium HD app
Click to expand...
Click to collapse
Just got my K1 revived yesterday using a reimage HC but I have tried using that many times and there was no go. It was a miracle yesterday now I am so happy
Happy all is well
johnwilliam_a_k_a_trash said:
Just got my K1 revived yesterday using a reimage HC but I have tried using that many times and there was no go. It was a miracle yesterday now I am so happy
Click to expand...
Click to collapse
I love CM 10.1.3. It's like having a new tablet. See my post #5 above. Good luck enjoy. Happy New Year
fhem said:
I love CM 10.1.3. It's like having a new tablet. See my post #5 above. Good luck enjoy. Happy New Year
Click to expand...
Click to collapse
I see that you came 1st from unrooted HC. Did you get your K1 rooted first before installing Khanning's & Kaschemme's ROMs? I am still on STOCK HC and I can't remember how to root the K1, of course I want to flash CM10.1.x but I got no root yet. Thanks
Sent from my MT27i using XDA Premium HD app
What I remember
johnwilliam_a_k_a_trash said:
I see that you came 1st from unrooted HC. Did you get your K1 rooted first before installing Khanning's & Kaschemme's ROMs? I am still on STOCK HC and I can't remember how to root the K1, of course I want to flash CM10.1.x but I got no root yet. Thanks
Sent from my MT27i using XDA Premium HD app
Click to expand...
Click to collapse
I came from stock. Just follow the directions on kaschemm's thread. You can get the download from here http://goo.im/devs/kaschemme. You need to download the nvFlash to your pc and run it from there to get root and cwm recovery. If I if remember right the nonneon gapps link is in the thread and you flash that from recovery. Hope this helps. Good luck.