Develop Bugs

[SPRINT][CDMA][FROYO][GUIDE] Overcome/KhasMek 1.4ghz OC FAST (4.30.2011)

First off, this is not for the faint of heart. Backup your junk, don't flash modems or bootloaders if you don't what you're doing, in fact, don't flash anything, if you are not aware of what is what... Read this ENTIRE GUIDE FIRST, THEN DO IT... that way you have a clear understanding of what is suppose to be on your sd card, etc....
Second, none of this is my own work. I take no credit for the development of any of the following, this is more of a guide than
a rom on how to get a Sprint SPH-P100 working with a custom recovery, kernel and rom.
I should note, I have tmobile US, and my interest in this tablet is a secondary device, hence it being a sprint device. It is not meat to be a phone for me... I dont plan to make calls or text, only tether it to my phone, use GPS as well as the other functions. It is, essentially, a laptop replacement with extra goodies...
That being said, if you test this, it is at your own will and I will provide no further instructions on how to undo something you have done... this forum has a search feature, use it. Any contributions to developing it further and providing fixes for the problems listed below are welcomed.
Before I begin, big, BIG thanks to alterbridge for providing me with excellent tips.
Also to Khasmek for his kernel and everyone who helped in the production of heimdall.
Again I say, this guide is meant to give you overclocking features for your tablet. As-well-as the ability to reboot to a custom recovery from the gui (in this case cwm 3.0.0.0).
What works?
Wifi
Camera
Video Recorder
Gallery
all other apps
What does not work?
GPS
What may or may not work?
Calls
MMS
SMS
Voicemail
What's included:
Refer to:
http://forum.xda-developers.com/showthread.php?t=932082
I'm assuming here that you are rooted. If you are not, use superoneclick. Google it...
I'm assuming your are stock also, if you are not, I advise you to get that way using this: http://forum.xda-developers.com/showthread.php?p=9753941#post9753941
Please read it carefully as you can complete bork your tablet if you are not certain. Thanks to gordesky1 for the guide.
When/if you are back to stock you can begin this process. I insist that you do this, because it is the method I started from after flashing various roms/kernels etc...
Now preload your microSD card with the following (i'm assuming you have formatted and can load it with a pc-usb attachement)
[ROM] Overcome 1.6.3
Link: http://www.multiupload.com/8XVZ2JPE4V
Source: http://forum.xda-developers.com/showthread.php?t=932082
[Kernel] KhasMek Voodoo Plus v5
Link:http://gunsforgeeks.com/Tab/kernel/KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip
Source: http://forum.xda-developers.com/showthread.php?t=941781
You will also need a new vold.fstab file, a link is within the instructions.
Lets begin (flashed with Windows 7, sorry mac/linux users, you are on your own):
Step 1: Flash the VZW kernel, as it contains cwm custom recovery and allows you to flash kernels and roms.
Source: http://www.thegalaxytabforum.com/index.php?/topic/1775-clockworkmod-for-sprint-galaxy-tabs/
Download zImage file here: http://www.megaupload.com/?d=SV6IKL1D
Process: (thanks jkurl15)
"To get the zip file containing the zimage download it from here. http://www.megaupload.com/?d=SV6IKL1D
To flash the zimage you will need to use Heimdall which can be downloaded here. http://www.glassechi...ducts/heimdall/ <--------click on the binaries
link for 1.1.1
instruction are below.
Heimdall install instructions
1. Download Heimdall here http://www.glassechi...ducts/heimdall/
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. http://www.microsoft...&displaylang=en <------only if you are using Microsoft widows
2. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe
3. Put you tab into Download mode(while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC and Run Zadig.exe to install the
drivers.
4. From the menu chose Options -> List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
ClockWorkMod Install Instructions
1. First root you tab (use one click root or z4root) then downloaded rom manager.
2. Unzip the flash_image_VZW_zimage.zip. It will have have two files flash_image and zimage. you only need to use the zimage file. Open Heimdall-Frontend.exe and browse to where you unzipped the zimage to and select it. Make sure the box infront of zimage is checked. Hit start and it should flash the zimage and reboot the tab. when it reboots it will get stuck at the samsung screen long hold the power button to shut it off. boot into recovery (cwm) power button plus volume up button it will start backing up to do the fs conversion but it will fail at /data and /cache. it will leave you in recovery.
3. While still in recovery select factory reset/data wipe when finished also do a cache wipe.
4. select reboot system, if you let it try to boot it will loop/hang on the SAMSUNG logo, this is not an issue just hold power key until it powers off.
5. while off hold volume up + power until you see the SAMSUNG logo then release both keys! NOTE: if step 4 does not fully power off and reboots just keep holding the power button until the screen blanks again then let go and quickly hold down only volume up + power until you see the SAMSUNG logo.
6. once it boots back into recovery (cwm) it will start the same backup/conversion process again, this time it will finish and leave you in recovery.
7. select reboot system and wait for it to load the tab back to froyo. (it will be back to factory defaults with the activation screen again)
8. Your tab will still be rooted so install terminal emulator and run "mount" to verify that your partitions are ext4.
9. Power off then boot back into recovery with volume up + power, it will boot back into recovery (cwm)
10. Do a backup and reboot your tab. " - zkurl
Step 2: Your screen should show you cwm 3.0.0.0 and be ready...
1) Wipe Data/Factory reset (for good measure)
2) Wipe Cache
3) Wipe Dalvick
Step 3:
Install the [Kernel]. It will flash and let you know when it is successful.
Step 4:
Install the [ROM]. It will flash and let you know when it is successful.
Step 5:
Install the [Kernel] AGAIN. (i know, it seems retarted, however I've had bootloops otherwise and it didn't matter if i didn't flash it before the rom or not, it would screw up) Anyways, it doesn't hurt.
Step 6:
Wipe again, just for good measure
Step 7:
Reboot device (first boot will take a few but doesn't hang at anything. Which means, if you see the samsung logo for longer than 60 seconds (actually takes right at 30 seconds)... you screwed up. The boot animation of the blue android with astro stars thingies going around it means you are on the path to booting)
Step 8:
The external and internal memory are jacked up. A fix has been provided and you will need to push it to your phone, and reboot.
Download vold.fstab here: http://www.multiupload.com/EKYF3CW39R (thanks to alterbridge)
bring up adb (if you dont know how, stop reading this, re-stock your phone and quit)
adb remount
adb push vold.fstab /system/etc
adb reboot
Your tab will reboot and when it comes back up, no more memory errors.
You've done it! You've flashed a oc'd kernel and a custom rom. From here, you can tinker with fixing the auto-rotate and gps and any other bugs you may encounter. I admit, i'm new to certain things, fixing it isn't my forte
I encourage you to post fixes/bugs here in the thread so that other sprint users can benefit from it all as there is a serious lack of development for them.
Future Updates: I'm assuming we can continue to flash whatever overcome updates come our way, we just have to then reflash the khasmek kernel and re-push the vold.fstab file. If we fix GPS, Screen orientation and it's through pushing means, that will have to continually be redone also. The alternative, someone cooks roms just for us... I myself could probably do it, however have never attempted to. If i get time, I will look into it, however, there are no promises...Maybe gingerbread/honeycomb variants will trickle out soon and we wont have to worry about it.
If you enjoy the rom/kernel, I encourage you to donate to the devs mentioned above, I myself will not require any donations, as this is merely a guide using other peoples materials. A big, big thanks again to the people who contributed to these roms, kernels and tools. Thank you!
Update 1: (4.30.2011 @ 6:49PM CST)
Fix for rotation using a method from the voodoo thread. Can either push it, or copy to usb with pc, then use root explorer or similar to move it into place (requires reboot)
"Try pushing the sensors.default.so file from bauxites thread. I have attached it.
unzip this and place it in /system/lib/hw (backup your old file just in case!)"
Update 2:
When you first boot, your keyboard is selected as "chinese". Simply change it to samsung or whatever else you may want to install...
Thanks to Bauxite!
File: http://forum.xda-developers.com/attachment.php?attachmentid=562977&d=1302188558
Source: http://forum.xda-developers.com/showthread.php?p=12722251&highlight=sensors.default.so#post12722251

Have you tried pushing the sensors.default.so from the v5 thread to /system/lib/hw
Thats what I just did to fix my sensors on the voodoo build
Sent from my SPH-P100 using XDA App

Obama's>god said:
Have you tried pushing the sensors.default.so from the v5 thread to /system/lib/hw
Thats what I just did to fix my sensors on the voodoo build
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
will give that a shot, thank you
Edit: that worked like a charm thank you so much, love XDA!

No problem its one of the last pages. Someone also posted a file gralloc.something.so dont use that. It gave me a weird boot crash where id get the 3 vibrates from a force close over and over again.
Sent from my SPH-P100 using XDA App

just curious, are you using this same setup as myself?
curious if sprint can still make/receive calls send/receive messages... etc...
if you're even utilizing those features... just wondering, thank you again

You mean stock sprint? On stock you can send or recieve messages but no calls
Sent from my SPH-P100 using XDA App

ah no, i meant sprint with the overcome rom and the voodoo kernel. I know there is a lot different so i'm sure it wont work, was just curious

From what I understand its only gsm that can do calling. It's either going to take aosp or some serious serious hacking to get calls on cdma. Im hoping for cyanogen, but I still cant get a stable version of that for my brother's samsung epic.
Sent from my SPH-P100 using XDA App

This worked like an absolute charm!

can anyone of you confirm if you
1. installed on Sprint Tablet
2. have the GPS working?
Thanks soo much!
BTW, great on the write up!

galexandr said:
can anyone of you confirm if you
1. installed on Sprint Tablet
2. have the GPS working?
Thanks soo much!
BTW, great on the write up!
Click to expand...
Click to collapse
1) Yes
2) No.

galexandr said:
Thanks soo much!
BTW, great on the write up!
Click to expand...
Click to collapse
You are very welcome

My Wifi all of a sudden quit working. I turn the Tab on, press the wifi toggle in the notification bar, and then it says "Error" and turns off.

That's interesting. This and Force Closes is why I ended up wanting Overcome over the KhasMek rom....
However, My sprint tab has not encountered this as an error, and I've flashed other modems and everything...
You might try and "fix permissions" from the recovery ... otherwise reflash again just for s's and g's.... I myself haven't seen this as a problem and have used it this way well over a week.

mr2324jgf said:
That's interesting. This and Force Closes is why I ended up wanting Overcome over the KhasMek rom....
However, My sprint tab has not encountered this as an error, and I've flashed other modems and everything...
You might try and "fix permissions" from the recovery ... otherwise reflash again just for s's and g's.... I myself haven't seen this as a problem and have used it this way well over a week.
Click to expand...
Click to collapse
I wiped data from CWM 3.0 and wifi started working again. I wonder what the issue was.
I'm also curious - would this technique work for the GSM CM7 port? Or is CM7 too far away from stock?

I've tried flashing cm7 a few ways and am always unable to get it to work. I'm assuming it's because I need the pit file with it which in heimdall requires the bootloaders also. I haven't messed with oldin or heimdall command prompt...
Last night I attempted again to flash the voodoo kernel over top of the clockwork mod with the stock rom... I then used titanium to clean some junk up, so i'm basically back to stock sprint with a custom OC kernel... it's pretty nice. I'm still not satisifed fully because I know there has to be other options.

mr2324jgf said:
I've tried flashing cm7 a few ways and am always unable to get it to work. I'm assuming it's because I need the pit file with it which in heimdall requires the bootloaders also. I haven't messed with oldin or heimdall command prompt...
Last night I attempted again to flash the voodoo kernel over top of the clockwork mod with the stock rom... I then used titanium to clean some junk up, so i'm basically back to stock sprint with a custom OC kernel... it's pretty nice. I'm still not satisifed fully because I know there has to be other options.
Click to expand...
Click to collapse
Just curious, why did you revert back to stock from this rom?
Sent from my SPH-P100 using XDA App

followed the guide and still stuck at the samsung screen after flashing kernel, rom kernel.

This is going to sound like critisism but I mean it as an honest sincere question. Why would anyone want to follow this guide if it breaks GPS? It's already possible to get the OC with Kazmek or Bauxite's kernels on the stock firmware with EXT4, and GPS also works fine with that other AOSP build, so what's the point of this?

cmoreno911 said:
Just curious, why did you revert back to stock from this rom?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
I've since returned to overcome, I really wouldn't mind having my gps back... but i'm testing different options on it. It's fun to tinker with it, whatever the case, lol
idumych said:
This is going to sound like critisism but I mean it as an honest sincere question. Why would anyone want to follow this guide if it breaks GPS? It's already possible to get the OC with Kazmek or Bauxite's kernels on the stock firmware with EXT4, and GPS also works fine with that other AOSP build, so what's the point of this?
Click to expand...
Click to collapse
the stock firmware has bloatware for any given carrier. the overcome rom is stripped of some of the nonesense without having to go into titanium and delete crap trial and error...
also, in the overcome rom, i can boot into recovery, reboot etc from the power button, whereas with the stock rom i can only power off....
not to mention, i dont have sprint and the sprint branding bothers me... custom boot etc makes me feel like i'm in control of my tablet.
the other benefit of myself and others doing this, is to try and FIX the gps, thus making this the best CDMA/Sprint option for the tablet.
etc etc etc....
thanks.

[Q] Some questions on rooting and flashing a new rom

OK, so my AT&T Note 2 is almost here (FedEx tried to deliver it ye3sterday when I was at work) so I want to make sure I am ready when it gets here. So some questions:
1 I downloaded Odin and understand how to root the phone but where do I get the file to use with Odin to do the rooting?
2 After rooting, what program do I use to flash a new rom?
3 Is there a sticky thread somewhere with this information that I could read?
4 Is there a good program to import all of my contacts from my old Windows phone? I'm not sure what format they are stored in so that is why I mention that it is a Windows phone.
5 (opinion) What is the best rom for an AT&T Note 2? I plan on adding lots of applications later and I really don't like re-installing things often so I'll probably stick with whichever rom I choose for quite a while.

rogerbacon50 said:
OK, so my AT&T Note 2 is almost here (FedEx tried to deliver it ye3sterday when I was at work) so I want to make sure I am ready when it gets here. So some questions:
1 I downloaded Odin and understand how to root the phone but where do I get the file to use with Odin to do the rooting?
2 After rooting, what program do I use to flash a new rom?
3 Is there a sticky thread somewhere with this information that I could read?
4 Is there a good program to import all of my contacts from my old Windows phone? I'm not sure what format they are stored in so that is why I mention that it is a Windows phone.
5 (opinion) What is the best rom for an AT&T Note 2? I plan on adding lots of applications later and I really don't like re-installing things often so I'll probably stick with whichever rom I choose for quite a while.
Click to expand...
Click to collapse
1: http://forum.xda-developers.com/showthread.php?t=2050297 - Does not require Odin to root. Just save to your phone, make sure Unknown Sources is checked in your phone's settings, run the file to install, run the app, make sure the exploit boxes underneath the "root" section are unchecked, then select root.
2: Download GooManager from the Play Store and run it. In menu, select Install OpenRecoveryScript. Follow the prompts, and it will download and install TWRP (custom recovery) for you. It will ask to reboot.
3: Simply do a search at the top of the forum.
4: Try Samsung Kies first. It should transfer all your contacts from most devices. Do this before installing a new ROM. Then make sure the contacts are saved to GMail's contacts.
5: It depends on preference. Each one have their own features and functionality, and varies on the version of Android it's using. I would research each one and see what entices you if I were you. Some ROMs may even have features of certain apps that you like built-in, enhancing the phone's performance due to the fact that it doesn't require an extra app to do what you want it to do. Most ROMs won't require you to "reinstall" things with each update of the ROM if you're just doing an update.

BlackPhantomX said:
1: http://forum.xda-developers.com/showthread.php?t=2050297 - Does not require Odin to root. Just save to your phone, make sure Unknown Sources is checked in your phone's settings, run the file to install, run the app, make sure the exploit boxes underneath the "root" section are unchecked, then select root.
2: Download GooManager from the Play Store and run it. In menu, select Install OpenRecoveryScript. Follow the prompts, and it will download and install TWRP (custom recovery) for you. It will ask to reboot.
3: Simply do a search at the top of the forum.
4: Try Samsung Kies first. It should transfer all your contacts from most devices. Do this before installing a new ROM. Then make sure the contacts are saved to GMail's contacts.
5: It depends on preference. Each one have their own features and functionality, and varies on the version of Android it's using. I would research each one and see what entices you if I were you. Some ROMs may even have features of certain apps that you like built-in, enhancing the phone's performance due to the fact that it doesn't require an extra app to do what you want it to do. Most ROMs won't require you to "reinstall" things with each update of the ROM if you're just doing an update.
Click to expand...
Click to collapse
Thanks.
Maybe I'm making this harder than it needs to be. Looking at some of the roms I notice that some of them say "rooted". If I plan to flash a rooted rom do I have to root first? I assume no, but I thought I should ask.
But to install TWRP I think it has to be rooted and if I use TWRP to flash roms then I guess I'd have to be rooted first even if the rom being flashed is rooted. Now I've confused myself again. I really don't want to turn my $700 phone into a brick by screwing up.

rogerbacon50 said:
Thanks.
Maybe I'm making this harder than it needs to be. Looking at some of the roms I notice that some of them say "rooted". If I plan to flash a rooted rom do I have to root first? I assume no, but I thought I should ask.
But to install TWRP I think it has to be rooted and if I use TWRP to flash roms then I guess I'd have to be rooted first even if the rom being flashed is rooted. Now I've confused myself again. I really don't want to turn my $700 phone into a brick by screwing up.
Click to expand...
Click to collapse
Custom ROMs always require root because it relies on a custom recovery such as TWRP and CWM. So, in short, unless you want to stay stock, you need to root.

This post should help to greatly simplify things for you. (4th post in the thread) Instructions are referring to the jedi rom but they will work for almost any other rom. I am on clean rom and have tried several others. Everything works great on clean rom. My advice would be to download all the ones you want to try, flash them and try each one for a day or two until you figure out which you like the best, then get your phone set up how you want on that rom. Once you get the one you like perfect, make a nandroid backup and then you can always flash any new roms you want to try and if they don't work for you, you can flash your backup and not have to worry about setting everything up on your phone all over again.
http://forum.xda-developers.com/showthread.php?p=35726061
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Trust me, the phone is absolutely worth the wait and the money! Also like he said earlier, every ROM is different and my favorite won't necessarily be your favorite, but if you like the look of Stock, I use Jedix8 which has great battery life and performance and some cool extra features. CleanRom also has a great reputation and I'll probably give it a go soon just to see what it's like. PM me if you have other questions or anything at all

BlackPhantomX said:
Custom ROMs always require root because it relies on a custom recovery such as TWRP and CWM. So, in short, unless you want to stay stock, you need to root.
Click to expand...
Click to collapse
topshelf95 said:
This post should help to greatly simplify things for you. (4th post in the thread) Instructions are referring to the jedi rom but they will work for almost any other rom. I am on clean rom and have tried several others.
Click to expand...
Click to collapse
badler6545 said:
I use Jedix8 which has great battery life and performance and some cool extra features. CleanRom also has a great reputation and I'll probably give it a go soon just to see what it's like. PM me if you have other questions or anything at all
Click to expand...
Click to collapse
Thanks all. I think I have it all figured out (and thanks to FedEx's stupid delivery policies I've had 3 extra days to think about it).
I have downloaded Odin and a rooted img file from http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-easiest-method
It will root and install CWM (although I think I would prefer TWRP from what I've rad.
I've doanloaded both the CleanRom for AT&T and the Jedi roms and will try those out. I think once I get the phone rooted and with hte custom recovery on it the actual flashing of new roms will be comparatively easy.

Well, I got my phone last night and charged it. Today I was able to root it, install TWRP, and flass CleanRom all in under an hour. Thanks to all those who offered help. The only issue I had/have is a lack of internet wit hdefault WAP settings: http://forum.xda-developers.com/showthread.php?p=37478407
I've gotten around it using the Cingular settings but download speed is only 1.9MB. That's OK for now as I consider my options: live with it or talk to AT&T and see is something can be done without losing my unlimited plan.
Overall , this was an easy process thanks to the large databse of information here and friendly helpful people. I would encourage anyone who is thinking of doing this to proceed. It is easy once you start.

S3 Rogers - Looking for ROM/info

I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:

http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

saj222 said:
http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Instead of linking me to something I've already read, how about actually saying something.
I'm finding too many "this might work for rogers, this might not"
Last time i followed a tutorial meant for an AT&T unit, I hard bricked the phone, and ended up tossing it
Sorry if it was in the wrong section before Kenny.

How about me not responding at all next time? I know no one is forcing me but its simple enough to find this info by searching. I understand your hesitance... No one wants an expensive brick.
I'll put something together for you later today unless someone else beats me to it. Deal?

js593 said:
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Click to expand...
Click to collapse
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506

saj222 said:
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506
Click to expand...
Click to collapse
Thank you very much. I';ll be looking this over and attempting this tonight.

js593 said:
I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:
Click to expand...
Click to collapse
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.

thecoach1999 said:
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.
Click to expand...
Click to collapse
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)

js593 said:
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)
Click to expand...
Click to collapse
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.

saj222 said:
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.
Click to expand...
Click to collapse
I believe i ran into the issue blindly.
I forgot to update the bootloader before flashing it. Will try again when i get home and report back with anything.

..

fffft said:
If that sorts your issues, then call it done and thank the people that helped you.
The earlier suggestions were good and not to be faulted. However there is more than one way to do most things. So if you are not happy for whatever reason here is a slightly different approach. There are some very stable custom ROMs that are very snappy and have a similar no lag, fluid feel (Google calls this "butter") to them vis a vis the Nexus. So a simple approach to that result would be:
1. Download and install the Samsung S3 V7.0 toolkit (program)
2. Start the toolkit program
Choose "n" when asked if you want to update the program
Choose your phone version. This is probably "53" for you
Choose option #1 from the main menu to install the necessary USB driver to your PC
After the driver is installed, connect your phone to your PC with the Samsung USB cable.
If your phone is currently stable, you can skip steps #3 + 4.
If you are uncertain, then steps #3 + 4 will restore a stock Rogers firmware as a starting point:
3. Go to Samsung updates and download a stock Rogers firmware
4. Install the stock firmware. This is toolkit menu option #8, 4, 2
5. Download the custom Wicked Aroma ROM v10 (main thread here)
6. Copy the Wicked Aroma ROM to your phone. You can do this in windows by going to file manager and drag and drop the Wicked file (leave it zipped) on the "Samsung Mobile MTP Device - Phone/Data" folder icon.
7. Flash the Wicked ROM from "recovery mode"
Ensure that your battery is at least 80% charged. Then turn your phone off and disconnect the USB cable
Push and hold the home button, volume up and power button at the same time until you feel the phone vibrate and see blue text on screen in the upper left hand corner. Then release the buttons.
On the onscreen phone menu, choose wipe (factory reset)
Then choose install and select the Wicked_v10. zip file
The rest of the install will be automated on your phone screen. It will ask you to select a number of options. If you are uncertain, then just leave them at the default settings. Ensure that you leave the wipe cache setting as is when asked. And I'd recommend the stock theme and stock kernel to start. The rest you can leave as is or change to what sounds attractive to you.
Note that the wicked ROM will change your boot splash screen. Most people won't care and it's not that hard to revert if you don't like the logo for some reason. This is the logo that appears for a few seconds when you first power up a phone.
This is a very snappy, pretty much zero lag and stable ROM. I think that you'd like it.
.
Click to expand...
Click to collapse
Thanks for the lengthy reply.
I tried putting the new bootloader on there, and tried re-flashing, but it did the same thing. So, in the mean time i'm going to use the Dandroid rom (didn't install the Gapps) and it seems to be working okay. I just fear a bit as the phone seems to be running much warmer then it usually does....
In the mean time, ill use this one, and see if it makes a difference (it could still be loading all my settings and whatnot, so we'll see what happens. I love the look of this rom though. Very simple, very clean. Exactly what i was looking for. Those samsung stock themes are terrible.... Thanks a bunch for the help people. Greatly appreciate it!

Personal taste varies a lot and there are a lot of themed ROMs on this site. So you should be able to find something that you like. It sounds like you want something snappy and Spartan looking. If you like your results so far, then no need to go any further.
If you end up trying the Wicked ROM, perhaps choose the Miui or Holo launcher and ASOP lock screen options.
There are an endless variety of home screen themes to be discovered. And no way to know what you might like. A few random screen shots:
http://media02.hongkiat.com/cool-android-homescreens/Clood.jpg
http://media02.hongkiat.com/cool-android-homescreens/evening.jpg
http://main.makeuseoflimited.netdna-cdn.com/wp-content/uploads/2012/09/jb_holo_launcher.jpg
http://i380.photobucket.com/albums/oo248/jb-dan/DroidInc/d4281332.jpg
http://mycolorscreen.com/wp-content/uploads/homescreens_2012/270592/KLPOS7.png
http://desktopspotting.com/wp-content/uploads/2011/12/Minimal-Android-Home-screen.png
.

Just installed the Wicked rom on my S3. NICE! Need to play with the settings a bit to get it configured the way I like, but a definite keeper.
Very nice job.....Kudos!

[ROM][AOSP](8/9/14) Shiny ROM: OTA-Like, Stock Android [4.4.4] [KTU84P]

Shiny ROM: Android 4.4.4, KTU84P for VZW Galaxy Nexus (Toro)
Skip right to the downloads (if you dare )
Hello there XDA GNex community! I'll admit this is a pretty spontaneous post; I've been building ROMs from the Android Open Source (Project) for awhile now, but I've never "published" any of them. I myself own a Verizon Galaxy Nexus, so I've always built from AOSP to make sure I'm as up to date as possible. Well, that's a little background so let's get going with the overview of the ROM itself:
Overview
This ROM is Android KitKat 4.4.4, build KTU84P. The ROM is built directly from source, that is, the Android source code published by Google available for download to all of us developers. The reason I say the ROM is "OTA-like" is because I make VERY few modifications to it, aside from the things that it takes to get the ROM working. I'll go into detail about those things below, but basically I just want the ROM to make your phone feel stable and shiny and new as if it has just received a new OTA update. That being said, it's clear that the landscape of Nexus devices is changing as new ones are released. Therefore, the other primary goal of this ROM is to keep our Galaxy Nexus as close to the modern Nexus design as possible. This means that I will also add in features that will still be stock, but will also make our phones as close to a current Nexus as possible.
As for how I handle the forum side of things, I'm always open to comments, questions, suggestions, requests, etc. I know that most of those things will often be in the form of criticism, but it's okay, I think I can handle it That being said, I do also have a life and am a college student, so I may not get to come on here ALL the time. I will check back as frequently as possible, and I'm hoping that you guys will help each other out as much as possible! Keep it friendly! So now for the details...
Features
Stock Android 4.4.4, build KTU84P
Source (AOSP) built kernel (boot.img)
Easily rootable (see information below)
G-Apps (GMail, Play Store, etc.) included in build along with Nexus apps
Stock browser replaced with Google Chrome
Shiny restart options - access them by holding down the power button and then long pressing on "Power Off"
All the crazy Google proprietary app stuff has been taken care off
Updated frequently
Everything works!
So what do I mean when I say "Everything works!"?
I'm sure by now you all know that when someone says that, it usually ends up not being true. This ROM is not an exception to that rule, but I can say that I've tested most of the things that would be expected to work in stock Android, such as...
WiFi Tethering (no subscription check)
Bluetooth streaming
Google account sign-in and auto-restore of apps and settings
Google Wallet
Location Services (pretty fast GPS lock in my area also)
Photosphere
Android beam
Photo editing with the new filters
Email
Exchange support
Like I said, the normal stuff (data, voice, hardware acceleration, etc.)
More things that aren't important enough to mention here - check out the changelog for a more comprehensive list
Possible Bugs
It's impossible for me to test for and notice EVERY single possible bug in the operating system, so as of right now I can't say that there are any, although I'm sure you will find some. If you do, report them here!
Other IMPORTANT Information
Root
But wait, nothing in this post said anything about root!!!11!!1!1!!! That's right, my ROM does NOT have root built in! (I don't use any root apps, and it's important to the whole "OTA-like" theme). That being said, the ROM is easily rootable; I made sure of this because I know that many, many of you will use root for many useful purposes. If you want to root the ROM, it's as easy as installing Chainfire's new superuser control app/su with this ZIP file. More detailed information can be found in the "Installation Instructions" section. **NOTE** If you are rooted and upgrading to a new build, you should not have to reflash the rooting flashable ZIP because the ROM will keep root for you.
Updates
Now that the ROM has gotten to this stage, the update policy needs a bit of editing Based on the stats I have access to from the website host and data that I collect myself, it seems like Shiny ROM is currently (as of May 27, 2014) stable for at least 80% of the users who have downloaded it. Based on this, and because the ROM is stock, Nexus-like, it doesn't really make sense to update the ROM as frequently as before. The ROM will still be updated as soon as possible after new versions of Android are released. In between Android versions, I will work on making things 100% stable, although that goal isn't always attainable with older devices and aging hardware support. If we decide to explore other paths for the ROM, you will see many more updates If/when the time comes for me to stop updating Shiny ROM, I will let everyone know in a clear way.
Radios
This ROM will (most likely) work with any toro radios; however, I of course recommend using the most recent, Verizon-approved radios which are the FK01 and FK02 radios. My ZIP installation package for these radios can be downloaded here.
Bootloader
Once again, I'm assuming that this ROM will work with all tuna/toro bootloaders; BUT for optimal experience and performance, use the newest Google-approved bootloader, PRIMEMD04. My ZIP installation package for that bootloader can be downloaded here.
ClockworkMod Recovery
I personally recommend using ClockworkMod Recovery as it has always worked well for me with no quirks. Android 4.2 messed up a few aspects of recoveries because of its multi-user system. ClockworkMod Recovery has been updated to correct some of these issues, and I recommend updating to the most recent version, 6.0.4.3. You can flash either the touch recovery or non-touch recovery image through fastboot OR you can download my flashable recovery update ZIP (touch/non-touch) and flash it in recovery. Check out the installation instructions for more details on this.
Some Other Not-so-important Information
Naming Conventions
All of my ROM ZIP files are automatically generated by my build computer. The file name for all builds up to and including the 11/10/13 build always begins with baldwinguy77_toro_aosp so you know that it's my build for toro. All builds after 11/10/13 begin with the prefix ShinyROM_toro_aosp. That prefix is always followed by the date in mmddyy format (e.g. 112212), a hyphen ("-"), and the time in 24-hour, hhmmss format (e.g. 153945). Finally, all builds end with the "signed" suffix - it just helps me know which packages have finished building and which have not. Hopefully this helps everyone to know which update is newest; I stay away from version numbers because I let Google do all of the version control.
Source
In keeping with the spirit of open-source, all relevant Shiny ROM code can be viewed on Github. I'm not extremely experienced with Github, so bear with me as I learn! Thank you!
File Hosting
I've switched over from using Dev-host to a privately hosted site, graciously and generously given to me by user Goofball. Dev-host is still an amazing service, but it's much more convenient for me to use a privately hosted site, plus I get my own suburl and FTP access! HUGE thanks to Goofball! The private hosting will definitely help me deliver a better experience to you guys as far as downloading goes. You can view all of my uploaded, public files here: http://shinyrom.goofball.org/
Also, if anyone ever wants to mirror for me, please feel free so long as you keep the file name and the file itself intact. As for everyone who downloads from a posted mirror: BE CAREFUL! Always use a virus scanner and be careful with what you are putting on your device!
Installation Instructions (VERY IMPORTANT - Note: You can flash all of these ZIPs in CWM or TWRP*)
*Android 4.4 KitKat builds must be installed using the latest version of your preferred recovery!
ROM
1. Download the latest version of the ROM from the download post. (Also download any other files you will need to install, such as Chainfire's SuperSU Root ZIP, the radios installation ZIP, the bootloader installation ZIP, etc.)
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. If you want to be 100% sure there are no problems, wipe data. If you are coming from another ROM or Android version, wipe data. If you do not wipe data and something goes wrong, repeat this process but wipe data - this step is not necessary if you are simply upgrading.
10. If you are updating your radios, flash FK01_FK02_Radios-signed.zip
11. If you are updating your bootloader, flash PRIMEMD04-signed.zip
12. Flash the ROM (ShinyROM_toro_aosp...signed.zip)
13. If you are rooting, flash Chainfire's SuperSU ZIP file - this step is not necessary if you were rooted on the previous build and are simply upgrading.
14. Reboot your phone, and enjoy!
**Note: If you are simply upgrading to a new version of the ROM and want to keep root, follow the exact instructions above, and do not format /system. It really is not necessary to format /system at any time (unless specifically noted), as the ROM installer has this function built in.
Mods
1. Download the latest version of the mod(s) you wish to install from the download post.
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. Install the mod(s) you downloaded in step 1.
10. Fix permissions (not really necessary)
11. Reboot and enjoy!
**Note: You can remove all mods you've installed by dirty flashing the latest version of the ROM.
ClockworkMod Recovery (Fastboot method - must have an unlocked bootloader and fastboot in your path)
1. Download either the CWM touch recovery image or non-touch recovery image to your computer and rename it to "recovery.img".
2. Power off your phone.
3. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
4. Plug your phone into your computer using the standard USB cable.
5. Open the command prompt/terminal and navigate to the folder where your "recovery.img" is saved.
6. Type "fastboot devices" to make sure your phone is recognized; a serial number should show up on the screen.
7. Type "fastboot flash recovery recovery.img" and wait for the process to complete (should be quick).
8. You're done! Use the volume keys to select "Recovery" and boot into your new recovery!
ClockworkMod Recovery (Flashable ZIP method - easier)
If you are updating your recovery before flashing a ROM, these steps should ALL be completed PRIOR to flashing the ROM.
1. Download either the touch recovery flashable ZIP or the non-touch recovery flashable ZIP.
2. Place the ZIP file downloaded in step 1 on your internal storage/sdcard.
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Choose "Install update from sdcard"
7. Select "Choose file from sdcard"
8. Find the flashable recovery ZIP file you downloaded and install it
9. Back up to the root menu of recovery
10. Select "advanced"
11. Select "reboot recovery"
12. The phone should boot up into your new recovery!
Credits
As with most ROMs, I only did a small part to get everything together. Also, a note that should be made here is that when I am using someone else's file, I ALWAYS host files on the Shiny ROM server to ensure that I don't put any unnecessary stress on their servers. Any file, however, still belongs to and is accredited to its original creator as listed below:
Willyjay - For providing us with lots of amazing and innovative mods for the ROM!
Inmanster - Another great modder who we are fortunate to have here in the thread. He works in collaboration with Willyjay and his mods for many things, but also does some of his own unique mods!
Chainfire - For their SuperSU app and su binary, as well as the convenient ZIP update package, which was previously used and recommended. Check out their website, http://www.chainfire.eu/
Groupers - My new buddy who helped me out with a GPS issue that popped up in 4.2.
Google - Without their amazing staff and willingness to share the source code of their operating system, I wouldn't have been able to build this ROM! Of course, all of the Google apps are theirs, along with the Play Store and system apps. They really are the true owners of all of this.
Samsung - We all may have some mixed feelings about them, but in the end they gave us the amazing, hackable phone that is the Galaxy Nexus.
XDA - By providing such a great Android community, ROMs like this one are able to easily connect with users and get their work out there
Dev-Host - The file-sharing service with virtually no limits on sharing - kudos to them and their hard work. d-h.st
Koush and the ClockworkMod/ROM Manager Team - They make the best recovery that's been around for longest, and their constant updates allow us to keep making ROMs! Also, Koush's recently released open source Superuser control app is the best available and the one linked to in the thread. Thanks Koush! clockworkmod.com
Kevdliu - Huge thanks to this dev and their amazing quick settings mod!
The CyanogenMod Team - For a working implementation of DSPManager on Android which can be ported to any AOSP-based ROM! Without them and Bigwavedave25, the DSP manager mod would not be available! Be sure to thank them and to check out the CyanogenMod website! Also, for their feature-filled version of the stock Messaging app which is available as a mod for my ROM!
bouchigo - a user who has helped to make the CM10 Messaging app available as a mod for my ROM in conjunction with Willyjay for bringing it to my attention.
Schoat333 - A user who helped out Willyjay with the bubble styled MMS mods. The credit for the screenshots to go along with the mods goes to him!
Yarly - The most experienced admin I've ever had the pleasure of talking with, who taught me some new debugging tricks and answered some of my questions.
Razorloves - Another admin who helped me out with a few problems and answered a lot of my questions!
Tiny4579 - A kernel dev who also took the time to talk with me and answer a few of my questions.
Thanks to everyone for their hard work and sharing that work with others!
DISCLAIMER
Come on guys, it's a Galaxy Nexus, to what extent could it really get messed up? Nonetheless, in case someone flashes this then puts their phone in the microwave or something and tries to blame it on me, I am not directly responsible for anything that occurs, either negative or positive, from flashing this ROM to your phone. Despite that, I am posting in the spirit of the Android community, a community that I have embraced and belonged to for several years, and I would never try to hurt any of your innocent, beautiful phones. Also, none of the original source for Android belongs to me, nor do any of Google's apps. All preinstalled applications are property of Google, Inc. and I make no claim of ownership to them.
Okay that's about it! THE ROM DOWNLOAD LINK AND A SUMMARY OF ALL FILE DOWNLOADS CAN BE FOUND BELOW!

ROM Download & Changelog
ShinyROM_toro_aosp_080914-125720-signed.zip
MD5: 5844c6e48fb30bbafc976199c5c1effd
Fixes/Changes Included So Far
(older changes)
6/21/14 CHANGES
Updated to Android 4.4.4, KTU84P
8/9/14 CHANGES
Added system-side support for native screen casting
Added Italian translations for the Shiny restart menu (courtesy of XDA user lparcshinoda)
Switched to prebuilt version of CellBroadcastReceiver in an attempt to fix issues with it on toro
Mods
Before installing any of the packages below, please be sure to check out the mod installation instructions in the OP!
Key
To make mod installation more convenient, all mod links will now be color-coded based on the files they change. The key shows what each color corresponds with:
Red - SystemUI.apk
Blue - framework-res.apk
Purple - SystemUI.apk & framework-res.apk
Green - Other
If you install mods that are in the same color group, it is likely that they will overwrite each other. It is OK to overwrite a previously installed mod, but please note that the originally installed mod will no longer be there. If you want to completely revert to stock, flash the "Back to Stock ZIP" mod under the baldwinguy77 mod section. This mod replaces your SystemUI.apk and framework-res.apk files with ones from the stock ROM.
Developer-specific Mods
All of these mods have been provided by some really awesome mod developers who take the time to continue to make updated mods for my newest ROM builds. That being said, they have lives and can't always get the mods out right away, so make sure the date next to their name matches the build you're running! They usually are around the thread and are open to doing custom mods if you ask Be sure to thank them and check out the credits section for more info!
Baldwinguy77 (Updated for 8/9/14 build)
Back to Stock ZIP - Returns you to the stock version of the ROM by removing SystemUI and framework-res mods.
Stock kernel flashable ZIP - Overwrites any custom kernel you have installed with the stock kernel normally packaged with the ROM.
Inmanster (Updated for 3/9/14 build)
36 DPI Nav. Bar - Replaces the stock navigation bar with a smaller (height-wise), 36 DPI version.
Black Dash-style Softkeys - Replaces the stock navigation bar buttons with black, dash-style ones.
Blue Stock Softkeys - Replaces the stock navigation bar buttons with blue-colored ones.
Carrier Text Replacement - Replaces the carrier text on the lockscreen and pulldown notification shade with "Galaxy Nexus".
Extended Battery Framework Mods - Improve accuracy of battery level reporting for those using extended batteries.
2100 mAh (with Carrier Text Replacement mod)
3050 mAh
3800 mAh
5900 mAh (with No CRT-off Animation mod)
Grey Battery Percentage - Enables display of the current battery percentage in the status bar with grey-colored font.
InmanMod - A combination of the 2100 mAh battery, no CRT-off animation, carrier text, 36 DPI nav. bar, and white zenyth softkeys mods.
No CRT-off Animation - Removes the stock, default CRT-like screen off animation.
White Zenyth-style Softkeys - Replaces the stock navigation bar buttons with white, zenyth-style ones.
Universal Mods & Downloads
These mods have been compiled by myself, sometimes in conjunction with the modders above, to always work with any version of the ROM (but not necessarily any device). Therefore, you don't have to worry so much about these being up-to-date because they should always work. If that is ever not the case, simply PM me and we'll get it fixed This section also includes some other Verizon Galaxy Nexus related downloads such as the latest radios and bootloader. You can use these according to the installation instructions in the OP.
Universal Mods
AOSP Web Browser (for Android 4.4) - Installs the AOSP web browser with Chrome bookmark syncing for Android 4.4.
DSP Manager(for Android 4.4) -Installs the DSP Manager app along with the audio libs and configs important to running the service, allowing you to customize the audio equalizer of your device. At the moment, certain apps on Android 4.4 do not work with the modular DSP service.
ClockworkMod Images
Touch 6.0.4.3
Non-touch 6.0.4.3
ClockworkMod Recovery Flashable ZIPs
Touch 6.0.4.3
Non-touch 6.0.4.3
Chainfire's SuperSU Root Control App and ROOT Flashable ZIP (Works with 4.3 & 4.4)
Download (Latest version, v2.02)
Toro Radios[/size]
FK01 & FK02 Radios Flashable ZIP (Latest)
FF02 & FG02 Radios Flashable ZIP
Tuna Bootloaders[/size]
PRIMEMD04 Bootloader Flashable ZIP (Latest)
PRIMELC03 Bootloader Flashable ZIP

Thanks for your roms, they have been the daily driver on my wifes GN since you started posted them way back when.

I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?

kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
Are you sure it's only when plugged into a wall charger? If that's true, it sounds like a hardware issue, but I think you probably just happened to notice it at that time. You may want to try out the 1/4 build as that one seems to work well for people with mobile data-related problems in the newer builds.

kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.

hotrodwinston said:
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
Click to expand...
Click to collapse
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.

kielby said:
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.
Click to expand...
Click to collapse
By the way I reflashed the 4.1.1 (JRO03O) radios from radio thread without changing anything else and the problem seems to have gone away.

What kernel should I use with this ROM to get the best performance/battery life combo. Link please!
Sent from my 2013 Kindle Fire HD

Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.

RoxRedEye said:
Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
Click to expand...
Click to collapse
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds

3/9/14 Build Information
Hey there everyone! It seems like it's been awhile since the last time I got make one of these new build posts, and I have to say it feels good to be able to do it again! I first have to apologize for my absence both in terms of development and communication in the thread. I'm getting close to the end of my sophomore year in college, and let's just say it has been keeping me extremely busy. I don't mind it, but I just wish it still left more time for me to do Android-related things! Luckily, I had a whole week off to catch up on a lot of things, including Shiny ROM development. So with that, we have a new build ready to go that includes a very minor update to the AOSP base of the ROM as well as some not so minor updates to the telephony stack. What this means is that mobile data and voice performance/reliability may have some big improvements in this build. We didn't get a chance to do a wide-scale test with these changes, and they're only in the master branch of AOSP, but after reviewing the code I'm hopeful that they'll bring improvements for us. That being said, be sure to leave your feedback here on the thread so we know how it's working! If you experience any problems, try to grab a logcat and let us know about them so we can try to get everything straightened out! So after reviewing the other information and installation instructions below, head over to the download post to grab the new build!
I also want to take this opportunity to point out that Shiny ROM has a new website! For now, the URL/domain is still http://shinyrom.goofball.org/ to stay consistent. The website has a lot of information about Shiny ROM as well as some future plans. It also lists details for the newest build of Shiny ROM along with download links, etc. I'm hoping that this website serves as a good platform for Shiny ROM to grow as we can now deliver a lot of information without having to worry about it getting buried in the forum and whatnot. So check that site frequently for Shiny ROM news and updates as well as information about new builds! There is also a contact form there for everyone to leave their suggestions, report bugs, etc. I hope you all like it!
(You can still access all of the Shiny ROM files here.)
Thanks to everyone for your continued support of myself and Shiny ROM!
Installation Instructions
Download desired ZIP files (ROM, SuperSU*, mods, etc.) and place on internal storage.
Reboot to the latest version of your preferred custom recovery (CWM or TWRP).
Wipe cache.
Wipe dalvik cache.
**OPTIONAL** Wipe data/factory reset (will erase user data like apps and saved games, etc., but may fix strange bugs).
Flash ROM.
**OPTIONAL** Flash other desired ZIPs (SuperSU, mods, etc.).
Reboot.
Enjoy!
*As of 3/9/14, the latest version of SuperSU is v1.93.

baldwinguy77 said:
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds
Click to expand...
Click to collapse
No worries. Thanks for the reply and thank you for your hard work bringing us a stable stock KitKat. Glad I have extra batteries with me - gonna download and flash asap.

Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx

ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk

asilentcivilian said:
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk

klobkelosh said:
Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
Click to expand...
Click to collapse
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
asilentcivilian said:
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Glad to hear it! Thanks for your support!

baldwinguy77 said:
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
Click to expand...
Click to collapse
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery

klobkelosh said:
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery
Click to expand...
Click to collapse
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs

baldwinguy77 said:
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs
Click to expand...
Click to collapse
I'll take that under consideration, but man it was really killing me. Following new rom flash, for everything set up, charged up to 100 percent. Good. Drive to dinner, 30 mins, in and out of 4g and 3g, battery at 80 percent. After 2 hour dinner on 3g, 60 percent. Back home 40 percent, lots of hand offs. She's nearly dead now and I haven't even used her tonight. I love this ROM, but she's not right...

Most recent and stable ROM for the Gio GT-S5660

What is the most recent and stable ROM for the Gio GT-S5660M ?
Importantly it would be to have a ROM that is new enough to work with modern apps, which often require at least android 4 or 5. Also, I would prefer to avoid GApps and go with F-Droid and Aurora Store, and the latter seems to require android 5+.
I have a couple of these lying around and thought they might make good WiFi IP phones with a SIP client. With a modern ROM and a new replacement battery (remember those?!) they could have new life.
Is this workable? This phone is so cute and compact that I really don't want to get rid of it if it can be used for something.

It has an armv6 cpu wich is no longer supported on android the last supported version was kitkat 4.4.4, this is the latest rom available for the device: https://forum.xda-developers.com/t/rom-cyanogenmod-11-final-05-08-2015.3066771/
It can still be used to listen to fm radio etc, although it no longer has browser support, so it won't work on all sites. I have one too and think it is a very nice tiny phone but I am affraid you are going to have to buy a newer phone for daily usage.

@J.V.B. Thank you for your reply!
Does that rom work well? There is some conflicting feedback in the thread. Which is the correct rom (msm vs msm7x27)?
How can the rom be flashed from the stock non-rooted state? There aren't instructions in that thread, though there is a post saying to use this CWM recovery (requires root?): https://forum.xda-developers.com/t/...-11-wip-alpha-1.2582642/page-27#post-54754255
Good point, the browsers all seem to require android 5+.
Currently on stock (android 2.3.4) I am using CSipSimple and that's working reasonably well. A newer rom might give a bit more flexibility in settings (eg. I can't figure out how to enable wifi on boot and autostart CSipSimple on 2.3.4), and maybe just maybe a few apps through F-Droid.

Both versions work they are just different kernels, I forgot what the advantages over each other were, I think the 7x27 version was more buggy but I am not sure, I recommend checking out both.
That cwm is indeed the only correct version, newer or older ones can't install this rom. I think to install the cwm you just have to boot to recovery (home button + power button and keep the home button pressed in.) and apply update from sd card and select that cwm(wrong: see edit). After this you boot to recovery again and now you factory reset and flash the rom. You also need to flash the camera patch after you flash the rom, otherwise you won't be able to record using the camera. I am not responsible for anything that happens, custom roms are always a risk. Hope it works for you
edit: You need to be rooted and on android version 2.3.3 or higher to install cwm: https://forum.xda-developers.com/t/...mwares-mods-tips-tricks.1397120/post-20397988

I also recommend using link2sd:
https://www.apkmirror.com/apk/bulent-akpinar/link2sd/ .
For instructions, follow this guide but scroll all the way down to the for cwm only users method: https://awanstuff.wordpress.com/201...ink2sd-in-any-android-phone-with-screenshots/
Link2sd will fully transfer apps to sd card instead of only the package. I changed the settings to make sure auto link is on and install location is set to sd. You can also transfer already installed apps to the sd and a lot more.
After this maybe post about how well the gio is running for documentation.
Some extra tips: the built in root is handy and if you enable developer options in the rom you will also get a performance menu in settings where you can make it run faster.

Thanks, I plan to try installing CWM and the CM11 rom soon. From searching it looks like "MSM7x27" refers to the Snapdragon S1 processor version:
List of Qualcomm Snapdragon systems on chips - Wikipedia
en.wikipedia.org
The Gio has a MSM7227 https://www.gsmarena.com/samsung_galaxy_gio_s5660-3741.php so maybe the MXM7x27 version is the correct one? I don't know if the plain "MSM" version rom is referring to a specific or generic designation.
Thanks for the tip about link2sd. It's nice to have that option since the very limited storage on this phone is maybe the biggest weakness. I'll see if I need it, since I don't plan to install many apps at all, rather I want to maximize battery life.
I got 1500 mAh batteries from Polarcell and in airplane mode with wifi and just CSipSimple running on the stock rom it lasts over 7 days in "standby". Let's see a modern phone do that!

I think this is the msm7x27: https://github.com/androidarmv6/android_kernel_samsung_msm
and this is the msm: https://github.com/HerroYou/android_kernel_samsung_msm/commits/cm-11.0
The msm just adds overclocking but might be more unstable and it also breaks the backlights. I don't know which is the best one. I recommend if the msm7x27 doesn't work well enough to try the msm and see if that gives you better results.
Also just so you know I have not found any gapps that work yet.

Also when you before you reset your device and flash the rom. Right after the cwm install I recommend fully backing up your device to an sd card so you can just go back any time you want.

I tested csipsimple and it works. If you want better battery life, the power menu that gets enabled after you unlock dev mode might allow you to downclock the cpu to get even more battery.

HerroYou has a mxm7x27 repo too: https://github.com/HerroYou/android_kernel_samsung_msm7x27
It would have been so helpful for them to leave a couple of notes about the difference. It seems like these terms might be common enough in the dev circles that they didn't think it needed explanation.
About gapps, I wasn't interested anyway, so I'll take its lack as a "feature". Not sure if microg is feasible. In any case, side-loading and F-Droid are ok for me on this device.
And yes, a backup after installing CWM but before the rom installation is essential. No intention to skip that.

oh I see the msm2x27 kernel is based on linux kernel 2.6.37 and the msm kernel is based on linux kernel 3.0

I have been reading up on things and see that most threads say you must be rooted and above version 2.3.3 to flash the cwm recovery: https://forum.xda-developers.com/t/...mwares-mods-tips-tricks.1397120/post-20397988
I am sorry I forgot about it. It really has been a long time since I installed it

Nice catch. In that case it is tempting to try msm with the more recent kernel 3.0.
Is there no way to flash CWM without root?
If not, is this post on rooting still valid? https://forum.xda-developers.com/t/...wares-mods-tips-tricks.1397120/#post-20397899

It is to root the stock rom so it should still work since the stock rom hasn't been updated in forever. I would also recommend reading the rest of the beginning of that thread to make sure you didn't miss anything because while mostly outdated, the things like rooting the stock rom and installing cwm is still the same.

I would also just to be sure use the cwm version in the thread: https://forum.xda-developers.com/t/...mwares-mods-tips-tricks.1397120/post-20397988 and then update it to the new version.

I started downloading the resources needed for this project, but the link (actually the whole hosting site) is dead for the root gb updated.zip hmm...
There are a few other files for rooting uploaded by random forum members:
Big thread For New Users (Rooting , Flashing,Firmwares,Mods,Tips, Tricks)
This thread is collection of all available data/tutorials about samsung galaxy gio,so it may save time for you guys. -------------------------------------------- For Simpilfication each post will contain single tutorial, Main post will only used...
forum.xda-developers.com
Big thread For New Users (Rooting , Flashing,Firmwares,Mods,Tips, Tricks)
This thread is collection of all available data/tutorials about samsung galaxy gio,so it may save time for you guys. -------------------------------------------- For Simpilfication each post will contain single tutorial, Main post will only used...
forum.xda-developers.com
A bit scary, but not sure there's another choice. It would be ideal if the recovery and rom could be flashed without root.

I found a rooting tutorial with a download on this post: https://forum.xda-developers.com/t/...kernels-recoveries-scripts-tutorials.1623393/
It is under the tutorials section.
Again I am not sure if you have to root to be able to install cwm but I wouldn't take any risks.
Also before you install anything is there anything you want me to confirm whether it's working or not on this rom?

I got youtube to work through newpipe and mx player although you have to download the videos because at low resolutions newpipe loses audio when sending to external video player.

Thanks, that's a nice resource thread. In the second page of the rooting thread someone has a modified version of the file for Bell S5660M variant, which is what I have, so I suppose I'll use that. I would prefer to go with CWM and CM11 without rooting, since I don't need or want root, but as you say it could be risky...
Oh, it would be great if you could verify on CM11 if 1) wifi can start automatically on (re)boot (eg. if it was on when powering off or rebooting, 2) if programs like CSipSimple can be autostarted on boot. That's all I really need right now to make it useful as an wifi IP phone.

I don't know how I would go about autostarting apps on boot. Is there a setting or a test for that? The wifi stays enabled after reboot.