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.

which of the custom ROMs are you liking best?

I've been following the ROM dev daily but I've been stuck in the hospital and not been able to flash any of them yet.
I'm getting out today and plan on checking one out asap and am curious as to which one I should go with.
I would appreciate any feedback on them that you can provide!!

scott0 said:
I've been following the ROM dev daily but I've been stuck in the hospital and not been able to flash any of them yet.
I'm getting out today and plan on checking one out asap and am curious as to which one I should go with.
I would appreciate any feedback on them that you can provide!!
Click to expand...
Click to collapse
I am still running rooted stock. One of the ROMs that had K9 Mail wouldn't work for me on Exchange 2K10. You could also look at the # of posts in each of the threads, that may ID where most of the peeps are headed.
I really wanted to say that I hope you are doing better. My phone haxoring started with a long hospital stay back during the Razor days.
I do like LG's native e-mail client. Only Samsung's e-mail client is better.

scott0 said:
I've been following the ROM dev daily but I've been stuck in the hospital and not been able to flash any of them yet.
I'm getting out today and plan on checking one out asap and am curious as to which one I should go with.
I would appreciate any feedback on them that you can provide!!
Click to expand...
Click to collapse
I currently only used the Domination HD ROM, and it has its goods n bads.
the Goods:
1) Lag is virtually gone! Phone runs really smooth and fast, with almost no stuttering.
2) Some extra visual improvements, like the Roboto Fonts and ICS wallpapers included (although it didn't show up on mine for some reason)
3) ICS sounds/notifications
the Bads:
1) Video Recording (camcorder) is borked as for now. You cannot record a video, the app just freezes at 00:00:00
2) Bootup time is significantly longer (might be closer to 2-3 min bootup time) but someone said that it might be due to the deodexing of files in the phone.
3) the claimed Bravia Engine and Xloud features implemented in the ROM just cannot be seen/heard. Supposedly it is there and running, but to some, nothing looks any different than the usual HD look of the phone and the sound is no louder than default. So those 2 features either are not working or just not noticeable enough.
That's my small review on the Domination HD ROM. I might have missed something and if I did, hopefully the next person will add to it.

SnoopDawg said:
I am still running rooted stock. One of the ROMs that had K9 Mail wouldn't work for me on Exchange 2K10. You could also look at the # of posts in each of the threads, that may ID where most of the peeps are headed.
I really wanted to say that I hope you are doing better. My phone haxoring started with a long hospital stay back during the Razor days.
I do like LG's native e-mail client. Only Samsung's e-mail client is better.
Click to expand...
Click to collapse
hey thanks Amigo! I hope all is well with you now as well.
I took your advice and flashed the kernalpan1c ROM and am checking it out now.
aquariuz23 said:
I currently only used the Domination HD ROM, and it has its goods n bads.
the Goods:
1) Lag is virtually gone! Phone runs really smooth and fast, with almost no stuttering.
2) Some extra visual improvements, like the Roboto Fonts and ICS wallpapers included (although it didn't show up on mine for some reason)
3) ICS sounds/notifications
the Bads:
1) Video Recording (camcorder) is borked as for now. You cannot record a video, the app just freezes at 00:00:00
2) Bootup time is significantly longer (might be closer to 2-3 min bootup time) but someone said that it might be due to the deodexing of files in the phone.
3) the claimed Bravia Engine and Xloud features implemented in the ROM just cannot be seen/heard. Supposedly it is there and running, but to some, nothing looks any different than the usual HD look of the phone and the sound is no louder than default. So those 2 features either are not working or just not noticeable enough.
That's my small review on the Domination HD ROM. I might have missed something and if I did, hopefully the next person will add to it.
Click to expand...
Click to collapse
super, Thank you eh. nice. I really want to try this one too. I got the impression from following the thread that the video cam issue can't be resolved. Perhaps I read it wrong, I will go back through the posts. I too want that vid cam on this phone. But I am very curious about that Bravia engine and Xloud and if/how much they make a difference on my device.
I am liking the kernalpani1c ROM, it does seem smooth, I uninstalled the GO launcher, sticking with Zeam after comparing the 2 with the new ROM, Zeam is noticeably faster & smoother for me.
The best thing about the custom ROMs for me is I had to use Malninion's unbricking method to fix this phone several weeks ago which uses the SU640, now I am back to the proper one.
I think I'll check out that Domination ROM next.

scott0 said:
hey thanks Amigo! I hope all is well with you now as well.
I took your advice and flashed the kernalpan1c ROM and am checking it out now.
super, Thank you eh. nice. I really want to try this one too. I got the impression from following the thread that the video cam issue can't be resolved. Perhaps I read it wrong, I will go back through the posts. I too want that vid cam on this phone. But I am very curious about that Bravia engine and Xloud and if/how much they make a difference on my device.
I am liking the kernalpani1c ROM, it does seem smooth, I uninstalled the GO launcher, sticking with Zeam after comparing the 2 with the new ROM, Zeam is noticeably faster & smoother for me.
The best thing about the custom ROMs for me is I had to use Malninion's unbricking method to fix this phone several weeks ago which uses the SU640, now I am back to the proper one.
I think I'll check out that Domination ROM next.
Click to expand...
Click to collapse
I might switch to kernelpanic's rom next week or so when I have the time to start fresh. I'm gonna format the /data partition so it will a be clean slate.
Well, like i've mentioned, me and some others don't really see any difference either the bravia engine or Xloud is doing to the phone. The image quality on the phone is the same, and the loudness is just as loud as stock. Shrugs, it might just be me I dont know lol. Feel free to try it and let us know what you think about it

aquariuz23 said:
I might switch to kernelpanic's rom next week or so when I have the time to start fresh. I'm gonna format the /data partition so it will a be clean slate.
Well, like i've mentioned, me and some others don't really see any difference either the bravia engine or Xloud is doing to the phone. The image quality on the phone is the same, and the loudness is just as loud as stock. Shrugs, it might just be me I dont know lol. Feel free to try it and let us know what you think about it
Click to expand...
Click to collapse
I was wondering about the clean slate starting fresh myself, does that make a difference?
I went to get the other ROMs and such but noticed their instructions were different than kernalpan1c, they did not state to clear caches and wipe system, etc so I stopped there.
so a question- it's safe and correct to always do the following 2 steps when flashing any ROM
3. Format /system in Mounts and Storage
4. Then "wipe cache partition" and "advanced > wipe dalvik cache"
thanks for the inputs

aquariuz23 said:
3) the claimed Bravia Engine and Xloud features implemented in the ROM just cannot be seen/heard. Supposedly it is there and running, but to some, nothing looks any different than the usual HD look of the phone and the sound is no louder than default. So those 2 features either are not working or just not noticeable enough.
Click to expand...
Click to collapse
why on earth would anybody need some st1nk'n bravia engine while there already is lg mobile engine in stock ROM? ther U go http://www.youtube.com/watch?v=KD3GSzOBuUo

scott0 said:
I was wondering about the clean slate starting fresh myself, does that make a difference?
I went to get the other ROMs and such but noticed their instructions were different than kernalpan1c, they did not state to clear caches and wipe system, etc so I stopped there.
so a question- it's safe and correct to always do the following 2 steps when flashing any ROM
3. Format /system in Mounts and Storage
4. Then "wipe cache partition" and "advanced > wipe dalvik cache"
thanks for the inputs
Click to expand...
Click to collapse
So far from what I have followed, the 2 steps you've mentioned are safe to follow. The only thing they've all mentioned is: "DO NOT WIPE/FORMAT /Data Partition" Just making it big, bold and bright so you don't miss it LOL. Kernelpanic figured out that it is some kind of a glitch in CWM that causes data corruption when you wipe/format the /Data partition.
Domination's ROM also states to wipe /system and dalvik cache, it's a standard thing i'm guessing. The only reason I want to start from a clean slate is that I don't want any bugs or system clash when I flash a new ROM over an existing ROM, so I think wiping /data will be essential.
Btw, Kernelpanic has suggested that if you do need to wipe /data, to please first flash back LG's default recovery using the image you've backed up prior to flashing CWM on the phone, and then formatting the phone back to factory settings using it. When factory reset is complete (which means /data is also wiped), you can then flash back CWM and then flash the new ROM.
Hopefully this will help you decide on your steps. Again, wiping /data is not necessary at all, it's just an option that technically should be done but right now is not so safe to do. Be careful and as always, we are not responsible for a gorgeous brick on your desk lol.
---------- Post added at 05:06 PM ---------- Previous post was at 04:58 PM ----------
Billy Madison said:
why on earth would anybody need some st1nk'n bravia engine while there already is lg mobile engine in stock ROM? ther U go http://www.youtube.com/watch?v=KD3GSzOBuUo
Click to expand...
Click to collapse
I like that commercial lol. That is very informative and interesting to watch. Very true wat you said about the Bravia engine. Tbh, like I previously mentioned, I do not see any benefit of the Bravia engine on this phone, and definitely not the Xloud feature. Thus, I'm thinking of trying another ROM that has all capabilities functioning, thus the Camcorder.
Just wondering, if you truly can replace the "visual engine (e.g. LG's engine with Bravia Engine), could that be the reason why the camcorder won't work? It's kinda weird that the camera works but the recording function doesnt.

well,
i flashed the domination ROM and it installed, I poked around and decided I needed the video camera, so shut down, booted in to CWM and flashed the other ROM, it said it installed, i rebooted it would not open, stuck on boot, so i shutdown, booted into cwm and restored the 1st ROM but now i am stuck on a boot loop and cannot access cwm.
derp.
update: flashed the su640 ROM so I am back in biz, gotta root and flash CWM.
so i guess this is a fresh flash after all!
i'm at 32% batt, superoneclick does not want to root atm , letting it charge a bit and will try to reroot.

scott0 said:
well,
i flashed the domination ROM and it installed, I poked around and decided I needed the video camera, so shut down, booted in to CWM and flashed the other ROM, it said it installed, i rebooted it would not open, stuck on boot, so i shutdown, booted into cwm and restored the 1st ROM but now i am stuck on a boot loop and cannot access cwm.
derp.
update: flashed the su640 ROM so I am back in biz, gotta root and flash CWM.
so i guess this is a fresh flash after all!
i'm at 32% batt, superoneclick does not want to root atm , letting it charge a bit and will try to reroot.
Click to expand...
Click to collapse
Yeah, that's what I feared, that when flashing another ROM over existing rom and not deleting /data might give an error. Which other Rom were you attempting to flash over Domination?

aquariuz23 said:
Yeah, that's what I feared, that when flashing another ROM over existing rom and not deleting /data might give an error. Which other Rom were you attempting to flash over Domination?
Click to expand...
Click to collapse
was trying to flash the RebelRom after the Domination. the switch from kernalpanic to domination went fine but the switch from Domination to Rebel FUBARed the phone, same exact steps followed. it also messes up the phone where a restore does not work then cwm is not accessible.
yup, serious issue that is not pointed out very well anywhere. the phone was ruined. in fact it's now stuck on the su640 ROM rooted but not recognized by adb so no su access, adb shell command returns a dollar sign and stalls, and the su640 wireless issue means no internet access on the phone so I can't get terminal emulator on it to move img files in to place.
ATT is sending me a replacement under the warranty.
my opinion atm on the custom CWM and the available ROMs is the ROI is not there.
The Roms don't perform any better than a rooted and debloated stocker IMO to justify the risk it takes checking them out.

scott0 said:
was trying to flash the RebelRom after the Domination. the switch from kernalpanic to domination went fine but the switch from Domination to Rebel FUBARed the phone, same exact steps followed. it also messes up the phone where a restore does not work then cwm is not accessible.
yup, serious issue that is not pointed out very well anywhere. the phone was ruined. in fact it's now stuck on the su640 ROM rooted but not recognized by adb so no su access, adb shell command returns a dollar sign and stalls, and the su640 wireless issue means no internet access on the phone so I can't get terminal emulator on it to move img files in to place.
ATT is sending me a replacement under the warranty.
my opinion atm on the custom CWM and the available ROMs is the ROI is not there.
The Roms don't perform any better than a rooted and debloated stocker IMO to justify the risk it takes checking them out.
Click to expand...
Click to collapse
Damn, seems like there is still some figuring out to do. A lot of the troubles keep pointing to CWM. What did you tell AT&T to get them to send you a warranted phone?

Kaiser_Beef said:
Damn, seems like there is still some figuring out to do. A lot of the troubles keep pointing to CWM. What did you tell AT&T to get them to send you a warranted phone?
Click to expand...
Click to collapse
i told them the phone was stuck on the LG boot screen and it would not turn off entirely. if I hold the power button down long enough the screen would flash off but it would instantly reboot itself again. the phone did finally fully boot to the su640 ROM but no data/internet access. then they had me do a factory reset which failed as well, after the reset the phone would still boot to main screen instead of to the setup screen.
It was a long telephone call. but ultimately I was transferred to the warranty dept, the 1st tech agent filled that warranty person in who then just checked a cople things and then agreed to ship me a replacement expedited, scheduled delivery is Monday.

scott0 said:
was trying to flash the RebelRom after the Domination. the switch from kernalpanic to domination went fine but the switch from Domination to Rebel FUBARed the phone, same exact steps followed. it also messes up the phone where a restore does not work then cwm is not accessible.
yup, serious issue that is not pointed out very well anywhere. the phone was ruined. in fact it's now stuck on the su640 ROM rooted but not recognized by adb so no su access, adb shell command returns a dollar sign and stalls, and the su640 wireless issue means no internet access on the phone so I can't get terminal emulator on it to move img files in to place.
ATT is sending me a replacement under the warranty.
my opinion atm on the custom CWM and the available ROMs is the ROI is not there.
The Roms don't perform any better than a rooted and debloated stocker IMO to justify the risk it takes checking them out.
Click to expand...
Click to collapse
So out of all the 3 ROMs you've tried which one did you like the most? Well, of course the rebelrom doesn't count cuz it borked your phone lol. Sorry to hear that though. I had this bad feeling when you mentioned that it froze after flashing that you flashed rebelrom, and yup that's what you did lol. Didn't you read through the thread though? Many of them got stuck in boot loops and not being able to recover after it.

yes, of course I read through the thread. I had the time to read through all the threads many times and did, even jotted notes down. I was fully aware of the risks involved and don't recall *****ing. I am patiently awaiting my replacement phone generously provided by ATT.
my conclusion was that none of the ROMs are worth the risk. The first one doesn't perform any better than a stock phone debloated + a better launcher, the second one has a very long boot time, then performs no better than a debloated stocker minus the video recorder.

scott0 said:
my conclusion was that none of the ROMs are worth the risk. The first one doesn't perform any better than a stock phone debloated + a better launcher, the second one has a very long boot time, then performs no better than a debloated stocker minus the video recorder.
Click to expand...
Click to collapse
I will say upfront to anyone looking at using my ROM, it is a de-odexed ROM minus bloat, a better launcher, some optimizations (ie ICS app process and system server, build.prop tweaks), and the carrier text removed from the status bar. With that said, de-odexed does run smoother than stock (odexed). CF-Bench scores are for example higher on my ROM than on stock.
We're not going to see dramatic speed improvements past that without custom kernels or CM/AOSP.

scott0 said:
yes, of course I read through the thread. I had the time to read through all the threads many times and did, even jotted notes down. I was fully aware of the risks involved and don't recall *****ing. I am patiently awaiting my replacement phone generously provided by ATT.
my conclusion was that none of the ROMs are worth the risk. The first one doesn't perform any better than a stock phone debloated + a better launcher, the second one has a very long boot time, then performs no better than a debloated stocker minus the video recorder.
Click to expand...
Click to collapse
lol scott, I never said anywhere that you were *****ing about bricking. I was just wondering why try when you know you have 80% of bricking? But anyways, it's great that you are getting a replacement from AT&T.

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!

[Q] Clarify graphical glitches on [ROM] [4.4] [KRT16M] A taste of KitKat [Alpha]?

Following this thread http://forum.xda-developers.com/showthread.php?t=2507846&page=36 many people are saying pretty much every problem is solved given enough effort/luck, other than supposed graphical glitches. Does anybody have any further comments on how these glitches look, are they animated, common, annoying or are they easy to ignore?

If you browse through some of the 4.4 threads there are screenshots and videos. I think it would be very annoying.

cupfulloflol said:
If you browse through some of the 4.4 threads there are screenshots and videos. I think it would be very annoying.
Click to expand...
Click to collapse
Oh I was unable to find a video, I've seen the screenshots which on their own look fairly annoying for sure.

carn1x said:
Oh I was unable to find a video, I've seen the screenshots which on their own look fairly annoying for sure.
Click to expand...
Click to collapse
They don't occur in normal usage. They occur in screenshots, but that doesn't mean your screen looks like that - the glitches you see in the screenshots aren't really there. In fact, they are so minor these ROMs are usable as a daily driver.

carn1x said:
Following this thread http://forum.xda-developers.com/showthread.php?t=2507846&page=36 many people are saying pretty much every problem is solved given enough effort/luck, other than supposed graphical glitches. Does anybody have any further comments on how these glitches look, are they animated, common, annoying or are they easy to ignore?
Click to expand...
Click to collapse
I just Flashed A taste of kitkat and it killed my gps function. are you experiencing the same issue?

McDuffSmith said:
I just Flashed A taste of kitkat and it killed my gps function. are you experiencing the same issue?
Click to expand...
Click to collapse
I haven't flashed yet, hence this thread, I was worried the graphical issues were too severe. However it still seems a number of people are having problems so I'll give it a few more days until the best installation routine is better known and documented. I can't really afford to lose Wifi or GPS and those seem a bit hit and miss.

From my time using it, it only occurs when rotating and sometimes when locking the screen (But I haven't noticed it, so I'm not too sure). There isn't anything wrong with it under normal use and is only briefly seen when rotating. As much as it annoys me, it's a small price to pay to have kitkat. The only sever issue is a big black box covering the Google Search results which renders Google Search kinda obsolete :/
As for GPS I'm not experiencing anything abnormal except maybe a few meters off.
Wi-fi works fine too.
But do note that I'm not running Slimkat or A taste of Android, I'm using the Toro plus version but converted to Maguro. And IMO it works much better than the ones that were built for maguro.

lonehangman said:
The only sever issue is a big black box covering the Google Search results which renders Google Search kinda obsolete :/
Click to expand...
Click to collapse
That is the only thing that really is an issue for me with "A taste of KitKat". It's happening sometimes in the e-mail application too, and in AOSP browsers. Chrome is fine, thought.
So my guess is everything that the OS render from HTML (GNow, e-mails, browser) is broken with the anoying black box !

Hi, I'm a noob here at xda, but, I bought GNex due it's "always" up to date OS and now it's no more up to date.
I'd like very much to test this ROM, but, I can't figure out some things posted here. Can someone help me?
Can you tell the meaning of:
Gapps
To flash something
CMW
TWRP
Maguro
This full sentence "format system, factory reset, flash rom and gapps again"
I have rooted my Gnex, installed Google services, google search, camera, gallery, hangouts and launcher .apks from 4.4. I have replaced ligoogle_recognizer_jni.so, libfiltershow_filters.so, libjni_mosaic.so and liblightcycle.so files at /system/lib as told in this topic http://forum.xda-developers.com/showthread.php?t=2506344
I'd like a walkthrough to install this version of 4.4, if possible. I have no clue of what to do after downloading the files^^
Well, tanks for any help I can get and thanks to Garak for spending his time to help us. I never thought it would happen so fast!

ericmas001 said:
That is the only thing that really is an issue for me with "A taste of KitKat". It's happening sometimes in the e-mail application too, and in AOSP browsers. Chrome is fine, thought.
So my guess is everything that the OS render from HTML (GNow, e-mails, browser) is broken with the anoying black box !
Click to expand...
Click to collapse
All that stuff as of 4.4 is now rendered by Chromium I think? I suppose this is what people complaining about Feedly being broken refers to as well.

ericmas001 said:
So my guess is everything that the OS render from HTML (GNow, e-mails, browser) is broken with the anoying black box !
Click to expand...
Click to collapse
I said GNow but I meant GoogleSearch, GNow is fine

I have some questions about the referred topic aswell. Do you think here is the best topic to ask or should I ask it in another topic?
Hi, I'm a noob here at xda, but, I bought GNex due it's "always" up to date OS and now it's no more up to date.
I'd like very much to test this ROM, but, I can't figure out some things posted here. Can someone help me?
Can you tell the meaning of:
Gapps
To flash something
CMW
TWRP
Maguro
This full sentence "format system, factory reset, flash rom and gapps again"
I have rooted my Gnex, installed Google services, google search, camera, gallery, hangouts and launcher .apks from 4.4. I have replaced ligoogle_recognizer_jni.so, libfiltershow_filters.so, libjni_mosaic.so and liblightcycle.so files at /system/lib as told in this topic http://forum.xda-developers.com/show....php?t=2506344
I'd like a walkthrough to install this version of 4.4, if possible. I have no clue of what to do after downloading the files^^
Well, tanks for any help I can get and thanks to Garak for spending his time to help us. I never thought it would happen so fast!
Click to expand...
Click to collapse

ericmas001 said:
That is the only thing that really is an issue for me with "A taste of KitKat". It's happening sometimes in the e-mail application too, and in AOSP browsers. Chrome is fine, thought.
So my guess is everything that the OS render from HTML (GNow, e-mails, browser) is broken with the anoying black box !
Click to expand...
Click to collapse
Not everything, I'm guessing only a few things? My app renders perfectly, but it could be because I'm not using the new WebView.
Torieth said:
Hi, I'm a noob here at xda, but, I bought GNex due it's "always" up to date OS and now it's no more up to date.
I'd like very much to test this ROM, but, I can't figure out some things posted here. Can someone help me?
Can you tell the meaning of:
Gapps
To flash something
CMW
TWRP
Maguro
This full sentence "format system, factory reset, flash rom and gapps again"
I have rooted my Gnex, installed Google services, google search, camera, gallery, hangouts and launcher .apks from 4.4. I have replaced ligoogle_recognizer_jni.so, libfiltershow_filters.so, libjni_mosaic.so and liblightcycle.so files at /system/lib as told in this topic http://forum.xda-developers.com/showthread.php?t=2506344
I'd like a walkthrough to install this version of 4.4, if possible. I have no clue of what to do after downloading the files^^
Well, tanks for any help I can get and thanks to Garak for spending his time to help us. I never thought it would happen so fast!
Click to expand...
Click to collapse
This probably isn't the best thread to ask this, but I'll go over it.
To flash something means to flash a zip through your Recovery (See below) which will directly modify your phone. So for example, if you want to flash a new boot animation, it'll 'install' that animation and 'apply' it.
CWM and TWRP are both recoveries, they allow you to do things like format certain partitions, wipe all user data, and flash zips (as mentioned above). They are pretty vital to doing this sort of thing.
Maguro is the codename for the international version of the Galaxy Nexus, the other code names are TORO and TORO PLUS which are the American variants (I'm not too sure about the TORO/TORO PLUS, but I'm fairly certain that this is correct).
format system, factory reset, flash rom and gapps again. From what I've said above, you should now be able to figure this out. Firstly, this is all done in recovery (Remember how I said it was vital?)
Format System format the System 'partition'
Factory Reset wipe all user data/return the phone back to a fresh state
Flash ROM obviously flash the rom
Flash GAPPS GAPPS stands for Google Apps which are the standard apps which come with most Android installs. I'm assuming it's a separate package to make the ROM size smaller and allow the users to use different system apps.
Hope this helped, but most of this information can be found by a few quick Google searches

lonehangman said:
Not everything, I'm guessing only a few things? My app renders perfectly, but it could be because I'm not using the new WebView.
This probably isn't the best thread to ask this, but I'll go over it.
To flash something means to flash a zip through your Recovery (See below) which will directly modify your phone. So for example, if you want to flash a new boot animation, it'll 'install' that animation and 'apply' it.
CWM and TWRP are both recoveries, they allow you to do things like format certain partitions, wipe all user data, and flash zips (as mentioned above). They are pretty vital to doing this sort of thing.
Maguro is the codename for the international version of the Galaxy Nexus, the other code names are TORO and TORO PLUS which are the American variants (I'm not too sure about the TORO/TORO PLUS, but I'm fairly certain that this is correct).
format system, factory reset, flash rom and gapps again. From what I've said above, you should now be able to figure this out. Firstly, this is all done in recovery (Remember how I said it was vital?)
Format System format the System 'partition'
Factory Reset wipe all user data/return the phone back to a fresh state
Flash ROM obviously flash the rom
Flash GAPPS GAPPS stands for Google Apps which are the standard apps which come with most Android installs. I'm assuming it's a separate package to make the ROM size smaller and allow the users to use different system apps.
Hope this helped, but most of this information can be found by a few quick Google searches
Click to expand...
Click to collapse
It helped a lot! Thank you!
Sorry for asking this kind of questions, they seem very basic given how often I read these words here. I already had an idea, but, before changing such things in my phone, I needed some straight answers. Thanks again! ^^
I don't want to abuse, but, are you aware of the topic "A taste of Kitkat" ? Which recovery is best to use to flash this ROM? CWM or TWRP? Both are mentioned several times, so, I'd like some directions, if possible.
So, I have to:
> Install a Recovery;
> Download the ROM zip file and Gapps;
> bootload into recovery mode;
> Format system;
> Factory reset;
> Flash the ROM zip file;
> Install Gapps.
Right?!
Thanks in advance!

Torieth said:
It helped a lot! Thank you!
Sorry for asking this kind of questions, they seem very basic given how often I read these words here. I already had an idea, but, before changing such things in my phone, I needed some straight answers. Thanks again! ^^
I don't want to abuse, but, are you aware of the topic "A taste of Kitkat" ? Which recovery is best to use to flash this ROM? CWM or TWRP? Both are mentioned several times, so, I'd like some directions, if possible.
So, I have to:
> Install a Recovery;
> Download the ROM zip file and Gapps;
> bootload into recovery mode;
> Format system;
> Factory reset;
> Flash the ROM zip file;
> Install Gapps.
Right?!
Thanks in advance!
Click to expand...
Click to collapse
Yep that seems about right! As for the best recovery, I personally recommend CWM. Also, don't forget to backup! Before you format go to backup/restore and do a backup. This will take your phone's current state save it, so if you ever stuff up, you can just restore it and your phone will be exactly how you backed it up.

Torieth said:
Hi, I'm a noob here at xda, but, I bought GNex due it's "always" up to date OS and now it's no more up to date.
I'd like very much to test this ROM, but, I can't figure out some things posted here. Can someone help me?
Can you tell the meaning of:
Gapps
To flash something
CMW
TWRP
Maguro
This full sentence "format system, factory reset, flash rom and gapps again"
I have rooted my Gnex, installed Google services, google search, camera, gallery, hangouts and launcher .apks from 4.4. I have replaced ligoogle_recognizer_jni.so, libfiltershow_filters.so, libjni_mosaic.so and liblightcycle.so files at /system/lib as told in this topic http://forum.xda-developers.com/showthread.php?t=2506344
I'd like a walkthrough to install this version of 4.4, if possible. I have no clue of what to do after downloading the files^^
Well, tanks for any help I can get and thanks to Garak for spending his time to help us. I never thought it would happen so fast!
Click to expand...
Click to collapse
Hello, welcome!
Gapps
Google - apps. You need to flash them to get Play Store, and other google services.
flashing
Flashing a ROM means deleting your partitions and getting other software on it. Like deleting windows 7 and 'flashing' windows 8 on it.
CWM & TWRP
CWM ( ClockworkMod ) and TWRP ( Team Win Recovery Project ) are 'recovery's you can install them and use them to install ROM's , backup, format partitions etc.
maguro
Marguro is the codename for the Samsung Galaxy Nexus GSM. so if you see 'maguro' you know they are talking about your device.

[Q] Is my Galaxy S3 possibly bricked?

Hello everyone,
I want to start by saying that this is my first post on xda, having just signed up a few minutes ago. I tried to search for any inquiries that were similar to mine, and couldn’t find any, but I may have missed them so I apologize if that’s the case, and I’m really not even sure if this is the correct area to post this in. Once again, I’m sorry if it’s not right. I also should say that I’m not very knowledgeable in the area of rooting, and flashing roms, and I’m sure that you guys know much more than me. That having been said, you’ll have to bear with me and my lack of understanding if that’s okay, as I’m pretty limited. I've encountered a problem with my GS3 (Galaxy S3) today, where it now gets stuck in a boot-loop every time I try to turn it on. Prior to that happening, I was running the stock, unrooted AT&T android version that was released in May (4.4.2 I believe?), and I had been having a lot of problems with performance and battery life. But as I had had the phone for over two years (I bought it in November 2012), I simply thought that it was slowing down and I thought it could possibly stop working, but as I said, I’m no expert. Back to earlier today, I was using the phone as I normally do (texting, light web-browsing, etc.), when I heard the notification tone indicating I had received a text. I picked up my phone, pushed the lock/power button to turn the screen on, and it said something to the effect of (I wish I had written it down, but I didn’t think to at the time) “software broken, you’ll need to factory reset your device” (that’s very much just my recollection, so I may have it completely wrong), along with a prompt to reset it. I touched that, and it just shut off. I tried to turn it back on, and it would keep shutting off after about 15-20 seconds. But I was able to get it into both recovery and download mode – just not booted up. So I thought to (probably stupidly) try to flash a rom, and I’ve tried several since that time (my phone won’t mount as a device on my laptop, thus preventing transfers, though I was able to get around this by using a micro sd card adapter and putting the card in that, then transferring the files to the card). But the first I tried – and was successful in flashing was called AOKP 4.4.4 (Kitkat) made by Task650 from 9-10-14. I’ll try to post the link to the thread that I used to research it. http://forum.xda-developers.com/showthread.php?t=1766684. As I’ve always been on touchwiz, I found out after I flashed it that I had to download the gapps package, which I tried to do from this link https://plus.google.com/+SeanHacker/posts/AGq2b8YwjXB . I downloaded that and tried to flash it by following this guide http://android.stackexchange.com/qu...he-gapps-package-after-installing-cyanogenmod . I’m sorry if I’m not organizing this in the right manner, but I’m doing my best! So anyway, I installed it from zip within clockwork mod recovery and then cleared the cache and dalvik cache afterwards, as the person in the above link said to. Then, I tried to reboot and that’s what I got stuck in the boot-loop. I left my phone for 30-35 minutes thinking it might’ve been taking awhile because I’d just tried to install the google apps. But it never did seem to do anything. Since that time, I’ve tried installing the stock rom (which I downloaded here: http://stockroms.net/file/GalaxyS3/SGH-I747/StockROMS.net-SGH-I747_ATT_1_20120522193451.zip) through odin and the recovery mode installation, cyanogenmod 10.2.1, and synergy r484 ( http://downloadandroidrom.com/file/GalaxyS3Verizon/roms/Synergy/Synergy-S3_19Apr13_1622_r484_s.zip ), all of which have been unsuccessful. The closest I got to being complete was going through the aroma installer for synergy, before trying to install and getting the message “Something was not successful during rom install. You will likely have a non-booter if you see this. If it constantly happens press save log in aroma and report this in xda thread.” (I didn’t know how to save the log and post it here). So that’s about everything that’s happened up until this point, and I apologize if my rambling is hard to follow lol. I just didn’t know what else to do. I’m very scared that I’ve bricked my device and that it won’t work anymore. I’m out of ideas, so I would greatly appreciate any and all help and/or input! Thank you very much for your time!
* Here is the link for the multi-window guide: http://www.howtogeek.com/189345/how-to-get-multi-window-multitasking-on-any-android-phone-or-tablet/

ok , let me get the ball rolling but not real knowledgeable myself.
1) do you know your bootloader and modem version.?
2) not bricked as long as it still can get in a bootloop.
3) sometimes (if were lucky) you can do the 'pull-battery' trick., pull battery out , wait a minute or so , put back in , do the button thing to get to recovery (power, volume up and home at same time).
(i , personally , would probably do a complete wipe and try to install the CM 10.2.1 zip to at least have my phone up and running. you still wont have gapps but you can get that after your phone is back up).
hopefully (!!!) someone more knowledgeable will chyme in , cause the battery pull trick is a maybe/maybe not. sorry dont have more right now. good luck.
"all i can really do , is stay out of my own way and let the will of heaven be done"

Since your phone was running 4.4.2, do not attempt to flash any ROMs using that attempt to downgrade your bootloader to anything prior to 4.4.2.
Try this to get your phone up and running:
download the latest CM11 for the d2lte and save it to an external SD card: https://download.cyanogenmod.org/?device=d2lte
dowload the latest tar.md5 version of Philz Touch for the d2lte from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/
boot phone in download mode, open Odin 3.07, do not check anything except f.reset.time, flash Philz via PDA box, remove USB cable when you see the word Reset appear in the status window, remove battery, replace battery, boot into recovery, format system, Dalvik, data, and cache, flash cm11, and reboot.

thank you audit13 , i was really reaching. lol. to heck with mighty mouse. its "mighty-aidit13 here to save the day". :good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

Thank you both so much!
I'm sorry, but I don't know my bootloader or my kernel version, unfortunately. I've got a lot to learn, and this happening clearly proves that lol. I will try that with cm right now, and let you know how it goes! Should I download the latest nightly or the latest stable version? I'm sorry for all of the questions!

questions are o.k. its how we learn. (& keep from jacking up our phones.lol).
get the latest nightly.
"all i can really do , is stay out of my own way and let the will of heaven be done"

Thank you
mrrocketdog said:
questions are o.k. its how we learn. (& keep from jacking up our phones.lol).
get the latest nightly.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
I appreciate your patience. I don't know if I could be so kind and forgiving if I was in your shoes right now. I just feel like a total idiot for not seeking advice before I flashed the initial rom.

The latest nightly or stable will do. You just want to get your phone up and running with a ROM.

It was successful!
I flashed cm and it worked! It is seemingly fully-functioning right now (I haven't noticed anything that isn't working), but I have two more things I'd like to ask about, if you don't mind. First, and this is the more important one to me, is getting the gapps if that's at all possible (though I'm a little hesitant about it), though I can live without them. I would post the link to the aforementioned gapps guide, but I cannot post links in replies right now as I do not yet have 10 posts, but I will try to edit the initial post. Since that’s where I ran into the problem initially, it’s may not a good idea to follow that link’s instructions. Secondly, one thing I'd like to do – seeing as this is my first non-touchwiz rom – is get multi-window installed on this rom, if I can do that. There was a link I was reading up on, though I don’t know how accurate or “safe” it is. I will edit the initial post with the link if I can. I feel bad for having all of these different problems and questions, but you guys are lifesavers. For all I knew, I’d be stuck with an expensive paperweight from this point on, so you guys really helped me so much!

http://wiki.cyanogenmod.org/w/Google_Apps
here is a link for CM 11 gapps.
dont know about multi-window , my phone is very bare bones (not even gapps).
"all i can really do , is stay out of my own way and let the will of heaven be done"

Confirm the bootloader and modem on your phone using the Samsung Info App from the Play store. Once you have this information, you can look for TW-based ROMs in the development threads that are compatible with your bootloader and modem.
I haven't had an s3 for over 10 months so I can't comment on the availability of the multiwindow function in CM ROMs.

That's very much appreciated!
Thank you so much! Would you mind looking at that link that was edited into the first post to tell me if the procedure itself is correct? I just don't want to take any chances!

Okay, I will do that as soon as I get the gapps installed Thank you so much again for all of your help!

chevrolet1234 said:
Thank you so much! Would you mind looking at that link that was edited into the first post to tell me if the procedure itself is correct? I just don't want to take any chances!
Click to expand...
Click to collapse
if your talking about the flashing guide for gapps , it looks correct. you flash gapps from recovery just like you did the CM11 rom.
"all i can really do , is stay out of my own way and let the will of heaven be done"

The Xposed Framework will do what you want to do. If you want to try CM12, Xposed will not work as it has not been updated to work with Android 5.0.
I recommend setting up your ROM with all of the apps and settings you like. Once you have done that, boot into recovery, create a nandroid backup, boot into the ROM, install Xposed Framework and play with it. If something goes wrong, boot back into recovery and restore your nandroid backup which will undo everything you did since you create your backup.

audit13 said:
The Xposed Framework will do what you want to do. If you want to try CM12, Xposed will not work as it has not been updated to work with Android 5.0.
I recommend setting up your ROM with all of the apps and settings you like. Once you have done that, boot into recovery, create a nandroid backup, boot into the ROM, install Xposed Framework and play with it. If something goes wrong, boot back into recovery and restore your nandroid backup which will undo everything you did since you create your backup.
Click to expand...
Click to collapse
audit , are you on the right thread ? just askin. lol.
poor audit , spread thin !
"all i can really do , is stay out of my own way and let the will of heaven be done"

audit13 said:
The Xposed Framework will do what you want to do. If you want to try CM12, Xposed will not work as it has not been updated to work with Android 5.0.
I recommend setting up your ROM with all of the apps and settings you like. Once you have done that, boot into recovery, create a nandroid backup, boot into the ROM, install Xposed Framework and play with it. If something goes wrong, boot back into recovery and restore your nandroid backup which will undo everything you did since you create your backup.
Click to expand...
Click to collapse
Okay, thank you so much, and I'm fine with staying on CM11, I think. Yes, I was talking about the gapps guide in the last post; sorry I didn't clarify it better haha. Is there a way to create the nandroid backup onto my micro sd card?

there is in twrp. dont know about cwm , but should be though.
"all i can really do , is stay out of my own way and let the will of heaven be done"

chevrolet1234 said:
Okay, thank you so much, and I'm fine with staying on CM11, I think. Yes, I was talking about the gapps guide in the last post; sorry I didn't clarify it better haha. Is there a way to create the nandroid backup onto my micro sd card?
Click to expand...
Click to collapse
You should be able to specify the backup location in recovery. For me, I tend to save it to an external SD card and make a copy on your computer for safekeeping.

Thank you and I'm sorry! This is just all so confusing to me, and I'd be completely lost without both of you helping me!