Database Info

Looking for a stable rom

so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!

nvertigo said:
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
Click to expand...
Click to collapse
Yes, you can use the one-click to put KJ6 on there then flash a different ROM via CWM.

Personally I've had the best experience with Valhalla ROMs. Last night I just flashed RAVERX3X latest Valhalla Black build. Its low profile so it's quick and responsive, and even better, not a single instability issue.
Sent from my SGH-T959V using XDA App

thanks for the advice guys!

I did the first flash step, which worked successfully and rebooted my phone. then i tried to flash the bootloaders that came with it, but uploading PIT 1/10 failed, and it froze trying to end session. i pulled the battery and the phone seemed bricked, but i connected the cable and oneclick said it was connected (no download mode screen, no lights at all). so i did the initial one-click flash and let it reboot again, then flashed valhalla black.
nothing SEEMS to be wrong, but i'm a little scared. can anyone weigh in on what happened?

You're ok. I can't explain what happened but people have reported similar issues, nothing on the screen but it can be seen in ODIN, and were able to recover (as you did) just fine.
Sent from my SGH-T959V using XDA App

This section of XDA is small, but good in terms of quality.
I just flashed Raver's Cyanogenmod/Valhalla hybrid and it is smooth and stable.

One-Click...
At the beginning of the week, I still had Froyo on my device.
I used Bryan's one-click (SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar)...
(I had a scare, too... which involved the so-called "Rainbow screen" -- but FB suggested I run the one-click, again and also to do the Bootloaders -- and everything turned out ok).
But, I needed to get CWM 5 (and, that particular one-click had CWM 3.0.2.8x)
So, I flashed an update of Bryan's kernel (sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip)
And, because I was feeling overjoyed at all the goodness that I'd seen so far, I flashed RaverX3X's rc3.zip (from Team Acid's Source Forge site)...
And, life is really, really, really... good.

yep
+1 Valhalla black edition! Installed today and love love love.

ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!

nvertigo said:
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
Click to expand...
Click to collapse
Not sure about the crashing but I experienced reboots because of the kernel Valhalla Black uses. There are fixes out there for that part of the problem but what you should really is perform a factory data reset, do the one to get a ROM with CWM on it, then use CWM to install Valhalla Black per the instructions on the page for it. I've a feeling you'll be much more stable after that.
As for the 10 minutes, that's basically to allow your phone to rebuild the Davlik cache (cache with optimizations for your apps). Definitely let it sit while it does that just to be safe.

thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.

nvertigo said:
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
Click to expand...
Click to collapse
If it was fully booting and you weren't getting the "rainbow" screen, then your boot loaders are fine. If in doubt, go check out bhundven's one-clicks, and run one of them - twice. The first time it doesn't let you check the boot loader box but the 2nd time it does.
Valhalla Final comes with bundven's beta 2c kernel. I believe people are running that without issue. Keep in mind Valhalla Final and Valhalla Black are two different ROMs with two different kernels.
I did a one-click back to stock (factory reset, cache wipes, etc.) & am running bhundven's latest beta kernel with no problems (thus far).

[Q] Planning to root and put a custom rom on a friends phone

Hi there, my friend is coming round soon and I was planning to give it a custom rom
Now, I've done this type of stuff before (on my nexus) I just want to see how you would do it for this samsung phone
Now, what recoveries can you get? I use 4EXT on mine
And, can anybody send me to a stable and up-to-date rom that can be used everyday and has nearly no issues? I need one without all the samsung stuff, just a normal default android one
And, how would I go by rooting the phone?
On mine, I used the zergrush exploit, does it work for this phone??

If you want one with everything working, then use the Froyo roms. CM7 is under development. The major bugs are bluetooth and youtube hq. Leaving that, even thats useable. It's even better than Froyo.
I suggest you to try either Kyorarom or Kyrillos v9.6. Both of them are froyo based, pre-rooted, and have other mods to make it even more faster than a stock one.
Happy flashing!

ak700 said:
If you want one with everything working, then use the Froyo roms. CM7 is under development. The major bugs are bluetooth and youtube hq. Leaving that, even thats useable. It's even better than Froyo.
I suggest you to try either Kyorarom or Kyrillos v9.6. Both of them are froyo based, pre-rooted, and have other mods to make it even more faster than a stock one.
Happy flashing!
Click to expand...
Click to collapse
Thanks, and how do I go about flashing the rom, would I have to root it first?

No need.
This is something to good to read http://forum.xda-developers.com/showthread.php?t=1372414
BTW to root the phone use super one click root (or sth like that )

Ah, I get it now, thanks
Just one more question, does ODIN delete the phones data before installing the rom?

You have to wipe all your data after flashing(or not if from Froyo to Froyo)
I mean from recovery. ODIN don't delete user data

I exactly I don't know the working of odin, but after flashing you are directly taken to the recovery and advised to wipe data and factory reset.

Choosing an ICS/Jelly Bean ROM

Just sharing my experience in upgrading to Jelly Bean on the Captivate.
Before you begin:
Before you begin, back up your efs partition.
Some ICS and JB ROMS have issues where they will forget your IMEI. If this is the case you'll need to restore your efs partition. If you don't already have a back up, you'll have to reflash to stock (pain in the butt) so that you can back up your efs so that you can restore it on your shiny new ROM. Without an IMEI, you won't be able to make calls or access wireless networks.
How to Backup/restore EFS: http://forum.xda-developers.com/showthread.php?t=859914
General Process
ICS and Jelly Bean are too big to put the entire rom in /system, so the current practice is to break up the ROM into 2 or more zip files (the ROM itself and a second zip that has essential apps like the Market). Both have to be flashed.
The ROMs have upgraded CWM (Recovery Modules) so you have to flash the ROM twice. The first time installs the CWM, the second time installs the ROM.
My journey
I had been using Mosaic, which is now defunct. When I started seeing posts from Studacris (former Mosaic developer) from several months ago saying "Gingerbread? What is this the stone age?" I decided perhaps is was time to upgrade to ICS.
Of course when I started looking at ICS ROMS, it turns out that now there are Jelly Bean ROMS available as well. Some people say the JB ROMS solve several problems with ICS. Others say the ICS are more stable for now.
Moral of the story. Your Captivate is unique. You won't know which is which until you try them, but my journey may help you.
1. I want to try Slim Bean, but coming from Gingerbread, it's recommended to start on Cynanogen (CM)
2. So I might as well try CM, but do I try CM9 (ICS) or CM10 (JB)?
3. Ah what the heck, let's go CM10!!!
4. Okay, there's at least four versions. The official, three unofficials of varying "v" releases, the Devil version with datadata (what the heck is datadata?), some guy's custom rolled ROM which he says is likely to brick your phone.
5. Okay, I'll try the latest V8 version with the Devil kernel (note, you should use the version with datadata).
6. Flash goes fine, but now it hangs on black screen with the word Android. After 30 minutes, I figured it really was hanged. Reflashing and rewiping solved that problem.
7. I had a lot of issues with it (see below), so I decided to try Slim ICS.
8. I had other issues with SlimICS (see below), so what the heck, let's try Slim Bean.
9. Slim Bean seems like a keeper to me: Fast; great feautures; decent launcher (vastly better than SlimICS). Only real problem I'm finding is that the Market won't let me install (or even see) Astro Player, which is one of my absolute must have apps. Still trying the dev's workaround.
CM 10 Issues:
Outdated:
1. The home key and back key are reversed.
2. My IMEI was wrong, and restoring EFS didn't help
3. I experienced intermittent lag on the launcher
Update CM10
Everything works fine in CM10 Helly Bean (29.07.2012). Faster than Slim.
http://forum.xda-developers.com/showthread.php?t=1783064.
Slim ICS Issues
The first thing the Slim ICS installer does is install its own CWM and in the process it will erase your sdcard (internal memory)
SO....
1. Back up your internal SDCARD before you start
2. To save time, put the zip files on your external card also (the newer CWM will let you install from the external card)
3. I hate the launcher
4. I still couldn't make phone calls.
Slim Bean issues
Works great except for the market issue. Seems to be a problem with the DPI. Still waiting to see if it resolves. Alternatively, I could try to restore my Mosaic version of Astro Player with Titanium back up.
Update:
1. Market issue resolved after about 36 hours of following the fix on the website.
2. Internal card and sdcard were reversed, (/sdcard and /emmc)
Conclusion
I hope my journey helps someone out there.

patrokov said:
Slim Bean issues
Works great except for the market issue. Seems to be a problem with the DPI. Still waiting to see if it resolves. Alternatively, I could try to restore my Mosaic version of Astro Player with Titanium back up.
Click to expand...
Click to collapse
Apps still aren't showing up in the market, but the TiBu restored apps work fine.

patrokov said:
Slim ICS Issues
The first thing the Slim ICS installer does is install its own CWM and in the process it will erase your sdcard (internal memory)
SO....
1. Back up your internal SDCARD before you start
2. To save time, put the zip files on your external card also (the newer CWM will let you install from the external card)
3. I hate the launcher
4. I still couldn't make phone calls.
Click to expand...
Click to collapse
I initially had that issue of not being able to make any calls. I didn't even have ANY service. Then I went to check which baseband/modem I had and sure enough I found the rom didn't flash a modem. I had to go find one and flash it. After that it worked perfectly.
I also didn't like the new Lightning Launcher so I went back to the old launcher they used - Zeam Launcher.

Ravenmtx said:
I initially had that issue of not being able to make any calls. I didn't even have ANY service. Then I went to check which baseband/modem I had and sure enough I found the rom didn't flash a modem. I had to go find one and flash it. After that it worked perfectly.
I also didn't like the new Lightning Launcher so I went back to the old launcher they used - Zeam Launcher.
Click to expand...
Click to collapse
Which modem did you end up flashing?

CM 10 Issues:
1. The home key and back key are reversed.
2. My IMEI was wrong, and restoring EFS didn't help
3. I experienced intermittent lag on the launcher
Click to expand...
Click to collapse
1 sounds like you did not flash a proper kernel
2 no imei troubles here
3 NO LAG WHAT SO EVER

CheesyNutz said:
1 sounds like you did not flash a proper kernel
2 no imei troubles here
3 NO LAG WHAT SO EVER
Click to expand...
Click to collapse
CM10 comes with the Devil kernel. Flashing another kernel is not part of their installation instructions.

patrokov said:
CM10 comes with the Devil kernel. Flashing another kernel is not part of their installation instructions.
Click to expand...
Click to collapse
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.

patrokov said:
Which modem did you end up flashing?
Click to expand...
Click to collapse
I tried most of them. I live in the Washington DC area and I found the latest XXJVU worked best for me. You'll just have to find out which one works best for you.

takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
I flashed the CM10 that was to be renamed Helly Bean, following these directions: http://hellybean.site11.com/help.html
(at the time the url was something like cm10.site11.com but the directions are the same.)

takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
Exactly
Sent from my SGH-I897 using Tapatalk 2

CheesyNutz said:
Exactly
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
This is what I originally flashed and had all the issues with. Is this the wrong one?
http://rootaxbox.no-ip.org/divers/devil_jellybean/rom/v8/
Tonight I flashed this one, and everything works perfectly.
http://rootaxbox.no-ip.org/divers/devil_jellybean/rom/20120729/
The reason I ask is that I'm trying to find out whether it was my error or some weirdness on my cappy's part.

patrokov said:
I flashed the CM10 that was to be renamed Helly Bean, following these directions: http://hellybean.site11.com/help.html
(at the time the url was something like cm10.site11.com but the directions are the same.)
Click to expand...
Click to collapse
I don't personally recommend that page because it was not actually tested yet by porters it means that the file in that site was raw JB. Recently derteufel uploaded a version that is "busted". So I would suggest to pay a visit to the HellBean thread and test a version that has already ported.

I just installed the stable CM9 and I don't really like what I am seeing. The lag on the home screen is unbearable and sometimes the notification bar splits into two when I am pulling it down. I will definitely try a CM10 rom and see how well it functions but I want to use the most stable version, or better yet the one with the least issues that I can use as my day to day rom. I really don't want to go through the trouble of installing every single JB rom.

droyd666 said:
I will definitely try a CM10 rom and see how well it functions but I want to use the most stable version, or better yet the one with the least issues that I can use as my day to day rom. I really don't want to go through the trouble of installing every single JB rom.
Click to expand...
Click to collapse
I'd definitely recommend Helly Bean first, in that case.

helly bean all the way. the only problem i have with it is when flashing a new rom (whether its the same to re-flash or upgrading to latest) you lose google now.

I'm running the 8/11 build OF CM10 KANG builds "JELLYBRO" by Makelegs, it's running great! Here's the link below.
http://forum.xda-developers.com/showthread.php?t=1803709
Sent from my SGH-I897 using Tapatalk 2

Definitely Helly Bean. Make sure to do a solid master clear and format of your phone first, then flash the latest helly bean. Long time user of slimics then slimbean and just switched over.
Only jellybean rom I've found that works FAST right out of the box, and even better when changing a few settings with devil kernel config. Only rom in which devil config settings actually stick after reboot as well!

VashTS said:
helly bean all the way. the only problem i have with it is when flashing a new rom (whether its the same to re-flash or upgrading to latest) you lose google now.
Click to expand...
Click to collapse
Not if you flash the add-on like you are supposed to...
Sent from a jelly bean

So far the latest cm9 nightly is the only ics that has worked well for me. All the jb roms I tried have me a lot of issues (sd card switch, no modem-couldn't even flash a modem, etc) so I haven't built up the confidence to try again.
My problems aren't with ROM behavior, but rather the newer versions of system apps. The phone app on gb had a feature at the end of a phone call to redial or text the person you just called. Miss that. Also the clock app doesn't have the world clock. Not a fan of that one. Over all everything is smooth but a lot of features I had with apex 12 are greatly missed.
Sent from my SGH-I897 using xda premium

simple man said:
I'm running the 8/11 build OF CM10 KANG builds "JELLYBRO" by Makelegs, it's running great! Here's the link below.
http://forum.xda-developers.com/showthread.php?t=1803709
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
I also applaud jellybro on my phone and flash each day with new builds as they come. Remeber to have a quick read thro the cherry picks to see what was changed/added/fixed. Runs great!
I do use the devil kernel with it tho - http://rootaxbox.no-ip.org/derteufel/jellybean/Cappy/113/. I use the CMC one.
Matt/eg.

Stable Daily Carry ROM?

I know this isn't the first thread of this kind to be made but everything seems out of date, a month marks a lot of updates fixing old bugs and making new ones. Anyway, I'm looking for a custom ROM and possibly a separate kernel that is "stable" (as stable as a custom ROM could be) and battery friendly. I was going to do AOKP or paranoid android but I hear in later updates they got buggy from using newer radios and some people are getting the sleep of death. I'm also interested in the Siyah kernel for the lulzactiveq governor but I question its stability and compatibility with other ROMs. I'm a noob and this is going to be my first flashing of a ROM aside from the massively fail attempts on my old Droid Pro. I'm already rooted and unlocked and made a NANDroid with clockwork recovery but advice on flashing and software is cool. I hear with Odin the yellow triangle pops up when you download boot but with cwr it doesn't which is why I plan on using it. Also, exactly how does one clean flash? I know dirty is just clearing caches so which should I do?
Using the latest OTA with the G7 baseband, still ICS.
TL;DR Stable bettery-friendly ROM, advice on flashing, possibly a kernel for ROM for better battery life?
Thanks a lot, sorry again for making the millionth thread on this matter!

Big fan of CleanRom here. I've tried different JB-based roms but keep coming back. I'm on CR 2.5 now with the HD radio, but have been on 2.1 with CleanKernel previously, along with the stock and G7 radios.
A "clean" flash will have you wipe data/factory reset as well. You should do this when switching Rom bases. I dirty flashed from CR 2.1 up to 2.5 and haven't had issues though.
Edit: FWIW, I can routinely see over 24hrs on a charge under normal/low usage.
Edit 2: If you care about your apps' data, you might want to go ahead and run a backup with something like Titanium Backup before doing a clean flash.

I'm no expert but I will answer a few of your questions. I rooted a month ago and have flashed every rom I can find, every rom I used has its own quirks and nothing is absolutely perfect.
It wouldnt hurt to just flash a few roms and see what you like best. As long as you have your backup and you can boot into recovery I dont see how it could hurt right?
At this moment I am using LiquidSmooth-JellyBean v2.0 RC3. Its quick and really clean but I have to manually cycle WiFi to get it working after I leave a routers range (i'm sure theres a fix but I havent looked yet)
A Clean Flash- Wipe your dalvik cache from recovery>advanced and data wipe/factory reset . This is wiping all your phone settings/data. Backup before this point since theres no going back unless you have a backup.
A Dirty Flash- you are installing on top of an old ROM without clearing all of your cache- you can retain settings but will have a high possibility of problems.
GoodLuck!

Thanks, I'm looking at cleanROM now. Is it ICS or JB? Usually it's either mentioned or there's a [JB]/[Jelly Bean] thing in the title but it's got nothing.
Also, does anything not work like wifi-direct or NFC? I know sometimes it's a per-person thing and other times there's a bunch of stuff you have to do to get things working properly.
If it doesn't have wifi or NFC and is ICS based I may as well play with other ROMs then. I don't want my phone OOC for too long though b/c I'm looking for work and lack a house phone.

Touchwiz ICS is the most stable at this time! It does not matter if its Beans, Synergy, or Clean Rom...they all are based off of VRALG1 Touchwiz... anything different between those are just additional mods baked into a stock rom. AOSP still has RIL issues, meaning the data handoff between 4g/3g is bad. Alot of times when Im on the outskirts of a solid 4g area the device's data connection flakes out.

CleanRom is using VRALG7 base and that is ICS. From what I remember CleanRom was pretty stable.

Quick definition:
Anytime you do not format your system, your not doing a true clean install.
Factory reset/data, cache, dalvik is a considered a clean install only when running the same base version (4.0 or 4.1 for example).
When changing base versions you should be doing all that + formatting your system (cwm under mounts and storage) or your just flashing a jb rom on top of an ICS rom. Issues arise because of this. Most devs are calling for this too.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises

Synergy R73 seems to be the best so far. No reboots. Fast stable. Had Clean Rom Prior to it which was also great. Tried Jellywiz but kept having issues.

So only ICS roms are stable? I kinda want jelly though, which ROM seems the most stable? I hear older versions of AOKP and Paranoid work better then the newer ones. Siyah + AOKP might be neat, alternatively Euroskanks CM Kang project with the same Siyah kernel. I've read some great things about lulzpowerq which is why I want that kernel so much, probably with SIO or NOOP for i/o since I hear they're wonderful for battery life. The main battery problem is from using the HD radio though, right? So just flash to G1 and it should be good?

MasterPoppy said:
So only ICS roms are stable? I kinda want jelly though, which ROM seems the most stable? I hear older versions of AOKP and Paranoid work better then the newer ones. Siyah + AOKP might be neat, alternatively Euroskanks CM Kang project with the same Siyah kernel. I've read some great things about lulzpowerq which is why I want that kernel so much, probably with SIO or NOOP for i/o since I hear they're wonderful for battery life. The main battery problem is from using the HD radio though, right? So just flash to G1 and it should be good?
Click to expand...
Click to collapse
Just experiment its the only way you'll find out what works best for you.
Sent from my Galaxy SIII

Alrighty, thanks for the help! When I watched the noob video I was a bit afraid people would be mean. You guys are really helpful and awesome though. :highfive:

Synergy .r73 and KT747 ...
Most of the issues you hear about are caused by overclocking (anything above 1728 MHz is just for bragging rights or quadrant scores), underclocking (anything under 384 MHz is asking for trouble) undervolting (don't get ridiculous here ... your CPU needs power), using a task killer and/or applying unnecessary tweaks (e.g., V6 Supercharger ... totally unnecessary).
My phone, wifi and GPS work flawlessly, and my 4g speeds are off the charts.
The theme support is pretty good, too.
Sent from my SCH-I535 using xda premium

Jb rom's will not come close to the stability of ics until the official release from samsung/vzw. Data issues being reported as well. I suggest reading for a day before doing anything. AND BACK UP YOUR IMEI BEFORE FLASHING ANYTHING!
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises

annoyingduck said:
Jb rom's will not come close to the stability of ics until the official release from samsung/vzw. Data issues being reported as well. I suggest reading for a day before doing anything. AND BACK UP YOUR IMEI BEFORE FLASHING ANYTHING!
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Click to expand...
Click to collapse
I've been reading, seems the main problem is the modem being used in some of the ROMs. Apparently they updated to HD and everything works fine after G7. I also heard about IMEI issues, how do I back-up? A lot of the instructions are confusing...

Go here:
http://forum.xda-developers.com/showthread.php?t=1852255
Read the entire first page min. Do the terminal method A, and the synergy method B if you plan on running a rom other than synergy. (if you flash synergy it does it for you.)
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises

pdinphx said:
Synergy .r73 and KT747 ...
Most of the issues you hear about are caused by overclocking (anything above 1728 MHz is just for bragging rights or quadrant scores), underclocking (anything under 384 MHz is asking for trouble) undervolting (don't get ridiculous here ... your CPU needs power), using a task killer and/or applying unnecessary tweaks (e.g., V6 Supercharger ... totally unnecessary).
My phone, wifi and GPS work flawlessly, and my 4g speeds are off the charts.
The theme support is pretty good, too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I agree with this.
I've used Synergy r73 with Imo's kernel and KT747 kernel. I'm currently using Ziggy's kernel, which is the default on Synergy r73. So far so good and smooth!!

annoyingduck said:
Go here:
http://forum.xda-developers.com/showthread.php?t=1852255
Read the entire first page min. Do the terminal method A, and the synergy method B if you plan on running a rom other than synergy. (if you flash synergy it does it for you.)
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Click to expand...
Click to collapse
I tried reboot nvbackup but it just rebooted normally and didn't go to the bootloader thingy. Does that mean it didn't work? I had superuser access and everything, am I supposed to do the vol down + pwr + home thing you usually do to get into the bootloader or something?

MasterPoppy said:
I tried reboot nvbackup but it just rebooted normally and didn't go to the bootloader thingy. Does that mean it didn't work? I had superuser access and everything, am I supposed to do the vol down + pwr + home thing you usually do to get into the bootloader or something?
Click to expand...
Click to collapse
Did you see tiny blue text at the top left when it was rebooting?

yeah, a quick flash before it booted. is that it? and do I have to do the other backup thing with the program after it or should nvbackup do the trick?

MasterPoppy said:
yeah, a quick flash before it booted. is that it? and do I have to do the other backup thing with the program after it or should nvbackup do the trick?
Click to expand...
Click to collapse
Well according to that thread "You may see tiny blue text on the bootloader screen indicating that it is copying." So I would assume that's it.
To be honest, when researching this whole lost IMEI issue, I was so paranoid that I did EVERY type of backup that was discussed in these forums. I saved every backup file to my dropbox account, my phone, and my computer just in case. I'll admit, I'm a bit more care free when flashing now, but I have yet to experience a lost IMEI issue.
If you're paranoid like me then it never hurts to do the other backup methods.

[Q] Help - Touchwiz vs AOSP on S3

I dont know if its my phone or what but I haven't had any luck with AOSP ROMS on this phone. It seems like there's always some sort of bug that just kills it. I flashed a CM10.2 rom that felt like speed of lightning but was bugging out. I tried ecilpse and some others but all were to buggy for me. I recently tried to flash liquid cause I wanted to run something else other than touchwiz but it ruined my phone and now I cant flash custom ROMS(i have a help thread up..feel free).. Anyone else having bad luck on these AOSP ROMS

Not what you want to hear, but I'm having no issues with flashing new ROMs. I'm only using LiquidSmooth and waiting/hoping for a 'complete' 4.3 version, but again, no problems with flashing to a new ROM. I have been running LS2.9 (4.2.2) for several weeks and on Sunday flashed up to LS2.10 (4.3) but went back to 2.9 because when I mirror my phone on my AppRadio3, it doesn't auto-rotate my screen to landscape, so I have a portrait orientation of my phone on the radio display, which makes it so small as to be unusable.
I don't recall what method I used to root my phone, but I'm using TWRP 2.6.3 to perform a) a clean wipe every time (Factory Reset + System), then b) install the new ROM, and c) a final reboot back in to recovery and flash the latest gapps image. Does it take a little longer to follow this process? Sure, but it's a reliable process that means I don't have issues afterwards to mess with, so the extra time spent on the front end is worth it to me.

I've had moderate success with the AOSP ROMS. Each one seems to have it's own small bugs, but the AOSP ROMs that I've tried didn't have anything that ruined functionality. Been running Dirty Unicorn ROM for the past couple days and it is really solid. Haven't noticed any issues at all with it yet.

It's got to be your downloads or install process. Do you check MD5? If no then start. Remember just wipe data for each install. Updater-script in ROM zip wipes system for you. Cache resides in data. Do NOT restore system data using TiBu. Other than that I don't know what else to tell ya bud :/
Sent from my SCH-I535 using Tapatalk

Haven;t had any trouble with AOSP flashes, but many of the ROMs or maybe most have some bugs. All the so called AOSP ROMs are built off the same base, CM10. None of them support all the hardware and software features that Tocuhwiz supports. I find the custom TW ROMs far superior in features and as good or better in speed as well.
Make sure you are flashing a compatible Kernel when you switch between CM based ROMs and TW based