Database Info

Android 4.0.1 by Samsung for SGS2

interesting....
http://www.sammobile.com/2011/12/14/exclsuive-android-4-0-1-by-samsung-for-sgs2-custom/
Originally Posted by bocautrang.pt
After a long wait Samsung has finally started testing Android 4.0.
Last week our “insider” presented us with XXKP1.
The Android version of this ROM is Android 4.0.1.
The build date is 7 december 2011.
As you may know of us we often get these leaks prior to release.
After we did some checks on it we can confirm that we’re dealing with a “CUSTOM” Samsung build.
We strongly advise people who only flash stock ROMs to not flash this.
As you all may know we only offer stock ROMs so you will not find this firmware on our usual firmware page.
We at Sammobile offcourse have tested this ROM in all curiousity.
Samsung uses Android 4.0 with their own TW-Launcher and Android 4.0 tweaks.
Below you will find a video review of this ROM.
http://www.youtube.com/watch?v=ISAI6qbQm6U">http://www.youtube.com/watch?v=ISAI6qbQm6U" type="application/x-shockwave-flash" width="425" height="350">
What works in I9100XXKP1?
All the Basics work like calling , sms , internet and more.
Some applications havent been worked out correct so they will force close on stress.Because we are dealing with a “CUSTOM” ROM here it can occur that the phone will react very slow from time to time.There is also the chance of some “RANDOM REBOOTS”We at Sammobile advise people to not use thhis ROM for daily usage.If you want to download this firmware then you can do so via the provided link below.DOWNLOAD
Password: samfirmware.com
Again if you only flash STOCK ROMs then dont flash this.
Because you flash this rom with “unsecure” kernel the phone thinks its “CUSTOM”and will start counting on your custom counter.
You will loose your warranty because of this.

Indeed.
I know our Infuses could run ICS. Hell, my Nexus S runs it beautifully. It's just a matter of the right libs. I think the hardware is more than sufficient.

im curious to see how the hard key/soft key issue is going to be worked out. Also since ive been using GoLauncher to get rid of my status bar, it will be interesting to see how the new menu button works.

tazbo28 said:
im curious to see how the hard key/soft key issue is going to be worked out. Also since ive been using GoLauncher to get rid of my status bar, it will be interesting to see how the new menu button works.
Click to expand...
Click to collapse
Well the custom ROMs to come out so far for the Nexus S have either left them in (which some people prefer) or taken them out. The hard buttons would obviously still need to work (they do on the Nexus S) so you'd just get a bit more real estate at the bottom of the screen. Rumor has it that the official ICS update for the NS will not have the software buttons but as it hasn't been officially released yet, nobody knows for sure. It's a good bet though.

jvanlew said:
Well the custom ROMs to come out so far for the Nexus S have either left them in (which some people prefer) or taken them out. The hard buttons would obviously still need to work (they do on the Nexus S) so you'd just get a bit more real estate at the bottom of the screen. Rumor has it that the official ICS update for the NS will not have the software buttons but as it hasn't been officially released yet, nobody knows for sure. It's a good bet though.
Click to expand...
Click to collapse
I wouldnt doubt it. It would seem redundant to leave them in. Hopefully google is really making an effort at unification with ICS. It would be awesome to not have a fragmented app store and dev.

My 2 Cent's
There is no question that the Infuse is capable of running ICS, other lesser devices are running it. I have a mostly stable beta running on my Inspire that has very similar hardware specs. (slower processor clock too 1ghz vs 1.2ghz) it really boils down to the correct drivers & libs/kernel I think ICS would be awesome on the Infuse.
Cheers
BR

After a long wait Samsung has finally started testing Android 4.0.
Last week our “insider” presented us with XXKP1.
The Android version of this ROM is Android 4.0.1.
The build date is 7 december 2011.
As you may know of us we often get these leaks prior to release.
After we did some checks on it we can confirm that we’re dealing with a “CUSTOM” Samsung build.
We strongly advise people who only flash stock ROMs to not flash this.
As you all may know we only offer stock ROMs so you will not find this firmware on our usual firmware page.
We at Sammobile offcourse have tested this ROM in all curiousity.
Samsung uses Android 4.0 with their own TW-Launcher and Android 4.0 tweaks.
Below you will find a video review of this ROM.
What works in I9100XXKP1?
All the Basics work like calling , sms , internet and more.
Some applications havent been worked out correct so they will force close on stress.
Because we are dealing with a “CUSTOM” ROM here it can occur that the phone will react very slow from time to time.
There is also the chance of some “RANDOM REBOOTS”
We at Sammobile advise people to not use thhis ROM for daily usage.
If you want to download this firmware then you can do so via the provided link below.
DOWNLOAD
Password: samfirmware.com
Again if you only flash STOCK ROMs then dont flash this.
Because you flash this rom with “unsecure” kernel the phone thinks its “CUSTOM”and will start counting on your custom counter.
You will loose your warranty because of this.

bocautrang.pt said:
After a long wait Samsung has finally started testing Android 4.0.
Last week our “insider” presented us with XXKP1.
The Android version of this ROM is Android 4.0.1.
The build date is 7 december 2011.
As you may know of us we often get these leaks prior to release.
After we did some checks on it we can confirm that we’re dealing with a “CUSTOM” Samsung build.
We strongly advise people who only flash stock ROMs to not flash this.
As you all may know we only offer stock ROMs so you will not find this firmware on our usual firmware page.
We at Sammobile offcourse have tested this ROM in all curiousity.
Samsung uses Android 4.0 with their own TW-Launcher and Android 4.0 tweaks.
Below you will find a video review of this ROM.
What works in I9100XXKP1?
All the Basics work like calling , sms , internet and more.
Some applications havent been worked out correct so they will force close on stress.Because we are dealing with a “CUSTOM” ROM here it can occur that the phone will react very slow from time to time.There is also the chance of some “RANDOM REBOOTS”We at Sammobile advise people to not use thhis ROM for daily usage.If you want to download this firmware then you can do so via the provided link below.DOWNLOAD
Password: samfirmware.com
Again if you only flash STOCK ROMs then dont flash this.
Because you flash this rom with “unsecure” kernel the phone thinks its “CUSTOM”and will start counting on your custom counter.
You will loose your warranty because of this.
Click to expand...
Click to collapse
Thanks ill include the text in the main post.

Ahhh stupid att they want their new devices to have it only . Guys our only hope will be cm9. After that, then chances of having pur own rom will be high.

Does this work on infuse
Sent from my SGH-I997 using xda premium

rboone18 said:
Does this work on infuse
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Lol
Sent from my SGH-I997 using Tapatalk

I thought it was a valid question, it seems missleading how post is wrote.
Sent from my SGH-I997 using xda premium

rboone18 said:
I thought it was a valid question, it seems missleading how post is wrote.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
lol.........

No
Sent from my SAMSUNG-SGH-I997 using xda premium

Theres nothing misleading about "for sgs2".
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

[OFFICIAL]CM10 Official Nightlies for D2VZW GSIII

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
See the 9-11-12 Cyanogenmod Announcement at bottom of post! There are now regular Nightlies you are used to and now the M-Series Roms, I will let the CM Team speak for it themselves as to what it is, see quote and link at bottom of post.
As of 8-18-12, the Verizon Galaxy S III, yes the one with the formerly locked bootloader that everyone loved to hate, has now been accepted into the Official CM10 Jelly Bean Nightly builds. Bookmark THIS PAGE to check for the latest nightlies. Many thanks to everyone involved in getting the d2vzw this far including you, African Canadian Sock Monkey!
Official Announcement from Cyanogenmod 8-18-12
Today we kick off the nightly builds of the CM10 JellyBean code branch, builds will show up later this evening.
CM9 nightly builds for devices that don't receive a CM10 nightly will continue (for the meantime) but we are changing the timing on them to be once a week instead (aka weeklies). This will allow a means for us to test bug fixes and the like as they get merged into the ICS branch - as stated before, the CM9 branch is in an otherwise perpetual code-freeze.
The devices receiving CM10 nightlies this evening include (but aren't limited to):
# The US SGS3 variants
# The Galaxy Nexus variants
# The Nexus S varaints
# The Nexus 7
# The Transformer and Transformer Prime
# The SGS1 variants (Vibrant, Captivate, International, and i9000b)
# The SGS2 i9100g
# P3 and P5 tablets
Other devices will join the roster as they become ready and gain their maintainers blessing for nightlies.
Edit d2vzw nightlies will require the insecure bootloader. See http://goo.gl/CST0K
Click to expand...
Click to collapse
Source
I didn't see a thread for this so I figured I would go ahead and create this thread for the discussion and following of the d2vzw Official CM10 Jelly Bean Nightlies. Our maintainer cvpcs has stated that the initial official nightlies may not have all of the fixes such as MMS fix in them until those fixes are merged into the official tree.
YOU MUST BE ROOTED:
I recommend using the Casual app from Adam in THIS THREAD.
YOU MUST BE UNLOCKED:
As stated the official version of CM10 nightlies for d2vzw requires you be on an unlocked Verizon GSIII. As an alternative to the Casual method Adam posted up, you can now unlock your device using a simple one-click app made by fellow dev mmmeff called VZW GS3 EZ-Unlock on the play store.
YOU MUST BE RUNNING A CUSTOM RECOVERY:
Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want. Please note the Touch CWM 5.8.4.9 available in the app doesn't play nice with CM10. Don't use it. I personally recommend using the CWM (non-touch) versions such as 6.0.1.2. If you prefer 6.0.1.2 Touch and want to flash it using the EZ-Recovery app using the "custom" option, simply flash this file using the app.
If you would rather not use that app, see THIS THREAD for CWM 6.0.1.2 files and install instructions.
blade7840 said:
Can I use TWRP recovery to flash this Rom?
Click to expand...
Click to collapse
Don't see why not. As usual, make sure you have a nandroid just in case. I previously stated TWRP Data Wipe was broken. Which is only partially true, because it FAILS for a REASON. If it worked it would format our internal sdcard! Proper use of TWRP would be to use the Factory Reset option which should take care of things. The Format Data option would be rather dangerous if it worked. So there you go.. It should work as well as CWM. More of a preference thing. You can find TWRP 2.2.2.0 in THIS THREAD. If you like using mmmeff's EZ-Recovery app and want to flash TWRP 2.2.2.0 using the custom option, use this file.
BECAUSE WE ARE NOW UNLOCKED, WE NO LONGER REQUIRE OR USE ANYTHING KEXEC
* In case anyone is still running CWM 6.0.1.0 from the kexec kernel days it is fine to use still. It functions as a standard custom recovery but had the additional ability to run kexec enabled kernels. So you can continue to use it or upgrade to another version. Because we are unlocked you are free to use any recovery now and Kexec is no longer applied.
So now all you need to do is root your phone, load up those two apps, load the recovery (i recommend the newest TWRP 2.2.2.0), unlock the device, and download and install the latest nightly in recovery.
GOOGLE APPS (including Play Store) ARE NOT INCLUDED IN OFFICIAL CM:
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Google Apps by default.
If you do a complete wipe and install an official CM10 build clean and you still have gapps remaining without having ever installed a gapps package, you likely didn't get a clean wipe. Recommend rebooting and wiping again and re-install.
WILL I LOSE MY IMEI IF I FLASH THIS?:
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Click to expand...
Click to collapse
There is a chance you will lose your IMEI on these devices any time you flash anything. If you are not willing to accept the risk inherent in flashing your device, regardless of what you are flashing or what you are worried about, then DONT FLASH ANYTHING, remain stock, and locked. If you want to read more on the "how to" for IMEI backup and restore, see THIS THREAD for latest IMEI discussions and detailed methods for backup and restore.
CM OFFICIAL NIGHTLIES DO INCLUDE A KERNEL:
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Click to expand...
Click to collapse
Yes. If you want to try custom kernels on CM10, it is of course at your own risk.
Flash, MMS, NFC or Native Tethering work on these builds?
Let's put it this way. They have all worked at some point or another. Then you have the fact that so many people posting here are contaminating the results with comments about unofficial builds and people that are flashing using different methods, etc......There's no good way for me to track and update this portion accurately. If you rely on any single feature to work properly, you are using the wrong ROM. Go back to stock. If you are flashing Nightlies of anykind you should expect things that have worked all along, some days will be broken. So the best thing to do is try it yourself and report here for others to see. These might be official nightlies but it's still very BETA and WIP (Work In Progress) and should be treated as such.
MMS WORKS
I can confirm personally as of the 8-20 build MMS is working and persistent after a reboot!
NFC WORKS
NFC fix found here.
WPA/WPA2 Native Tethering WORKS
You can flash the file in THIS POST to fix native tethering with WPA/WPA2 security intact.
FLASH WORKS
Sideload the newest Adobe Flash app found in THIS THREAD to get Flash on Jelly Bean. Of course you must have "Unknown Sources" enabled in Settings->Security to sideload any apk
If things change, let me know via PM, I'll try to update the OP.
UNOFFICIAL ALPHA BUILD THREAD IS OVER HERE.
In that thread you can find discussion and info on the unofficial alpha builds by people such as cvpcs, invisiblek, dhacker and others who have been part of the efforts to get us to where we are today. Their contributions are invaluable. Those builds right now may actually run smoother and have less bugs because they are UNOFFICIAL which means they can do what's called "cherry picking" and include code that has not been committed into the OFFICIAL builds yet. The official build may or may not have all those features. They are sometimes different ROMs functionally.
Now that we have an Official Nightly build in order to not confuse people please take Alpha Unofficial talk to that thread. Please keep posts here on topic and relevant to the Official Nightly builds. Things that work on those doesn't work on these and vice-versa.
CHANGELOG IS HERE and UnOfficial CM10 Bugtracker is HERE
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
UPDATE, Official Announcement from Cyanogen Mod, M-Series Roms Announcement 9-11-12
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Tonight’s M1 build is available for these devices:
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S (crespo)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
In standard CM style, we will continue to add devices as time goes on up until our stable release.
Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.
Happy flashing!
Click to expand...
Click to collapse
Source
If you need a more general "all things GSIII guide" to bail out of a problem, or to do other things that aren't necessarily CM10 specific, I highly recommend THIS THREAD

So to start it off I'd like to know if anyone is running the cm-10-20120818-NIGHTLY-d2vzw.zip build from early this morning? Does it have the MMS fix? Is it significantly different from the alpha builds we have been running for a couple weeks?

Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've unlocked your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.

Do these include google now, if not where can I get it?

ilogik said:
Do these include google now, if not where can I get it?
Click to expand...
Click to collapse
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Play Store by default.
Click to expand...
Click to collapse

Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium

Immolate said:
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've disabled your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Click to expand...
Click to collapse
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies

WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
YES. Op updated.

Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2

Schaweet said:
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
Yeah yeah, acknowledged. I'm sure if you can disable your bootloader, I'll figure out a way.

ive had one random reboot hopefully it was just a once time thing cause im loving this rom..much better than touchwiz
hopefully that flickering thing when texting gets fixed soon cause it gets a bit annoying..(ive also noticed that my widgets flicker)

neyenlives said:
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Click to expand...
Click to collapse
I think he's talking about Google now(voice search assistant), Not Google apps. It should be built into the ROM but you should still flash gapps anyways
Sent from my SCH-I535 using Tapatalk

Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The ROM comes with a kernel, but you can flash any non-kexec kernel for AOSP ROMs that you want. I'm currently running an AT&T kernel.
Sent from my Galaxy S III

TheBiles said:
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
Click to expand...
Click to collapse
mms is working for me with the latest build:good:

XTRoRDiNAiRE said:
mms is working for me with the latest build:good:
Click to expand...
Click to collapse
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III

Can I use TWRP recovery to flash this Rom?

TheBiles said:
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Click to expand...
Click to collapse
Phone number and MIN are blank for me (after a few reboots). Also, the LTE toggle doesn't seem to function properly. Everything else is working flawlessly; this ROM is definitely a daily-driver. Enjoy!
EDIT: I just realized that MMS isn't working for me....I can live without it for now but those that need it, may want to wait for another build.

neyenlives said:
YES. Op updated.
Click to expand...
Click to collapse
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium

Nice. I was just thinking about flashing this
Sent from my Verizon Samsung Galaxy S 3 running SynergyROM v1.6

WizeGuyDezignz said:
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The IMEI issue from my personal standpoint and based off of the opinions of the smart guys in IRC, is that it is very possibly a hardware design issue. Samsung could have put the EFS data which contains the IMEI in a non-volatile un-changable part of the memory but it looks as though they left it writable. This means we can try to write it back if we lose it but it also means bad data could be written to it thus erasing it.......that's what I have gotten out of it so far. So every time you flash you take the risk. I seriously doubt any fix will ever officially come because as long as you buy the phone and use it in stock form, you would never see the issue. It's an issue that only affects custom flashers, so don't expect to see a fix.

Former Droid X User Needs Help Transitioning

I'm making the transition from my old Droid X to the VZW Galaxy S3, and I have a few questions. The flashing process between these two phones are quite different and perhaps another ex-Droid X user (or just an all around knowledgeable person) could help me out.
1. To my knowledge, we were never able to flash Kernels on the Droid X because of its locked bootloader. So how does Kernel flashing work? Are there certain kernels that only pair with certain roms, or can you flash any kernel you like with any rom? I have a feeling it's the former, as I've already seen kernels categorized i.e. Touchwiz Kernels or CM10 based kernels.
2. With the Droid X, all roms were flashed using CWM. But with this phone that's not always the case right? Some may require a kexec method or even a custom recovery image, correct?
3. I've seen a few roms recommend backing up IMEI / MEID / EFS data before flashing. Is something I should consider doing whenever I flash, just as one would do a nandroid backup?
4. I've seen a few threads mentioning flash count, resetting flash count, etc. Should I be concerned with flash count? If so, why?
5. With the Droid X, before you could flash a rom, you had to make sure the firmware you were on was compatible with whatever rom you were trying out. For example, if you wanted to try cm7 you had to flash over the stock froyo kernel. If you wanted to try miui you had to flash over a stock gingerbread kernel. However, it would seem, with the S3 you can flash any rom (whether it be an ics rom or a jb rom) over stock 4.0.4. Is this correct? Can you flash an ics rom over the top of a jb rom? Or do you always have to revert back to ics stock?
6. Is Odin the Samsung equivalent of rsd lite?

D-meist said:
I'm making the transition from my old Droid X to the VZW Galaxy S3, and I have a few questions. The flashing process between these two phones are quite different and perhaps another ex-Droid X user (or just an all around knowledgeable person) could help me out.
1. To my knowledge, we were never able to flash Kernels on the Droid X because of its locked bootloader. So how does Kernel flashing work? Are there certain kernels that only pair with certain roms, or can you flash any kernel you like with any rom? I have a feeling it's the former, as I've already seen kernels categorized i.e. Touchwiz Kernels or CM10 based kernels.
2. With the Droid X, all roms were flashed using CWM. But with this phone that's not always the case right? Some may require a kexec method or even a custom recovery image, correct?
3. I've seen a few roms recommend backing up IMEI / MEID / EFS data before flashing. Is something I should consider doing whenever I flash, just as one would do a nandroid backup?
4. I've seen a few threads mentioning flash count, resetting flash count, etc. Should I be concerned with flash count? If so, why?
5. With the Droid X, before you could flash a rom, you had to make sure the firmware you were on was compatible with whatever rom you were trying out. For example, if you wanted to try cm7 you had to flash over the stock froyo kernel. If you wanted to try miui you had to flash over a stock gingerbread kernel. However, it would seem, with the S3 you can flash any rom (whether it be an ics rom or a jb rom) over stock 4.0.4. Is this correct? Can you flash an ics rom over the top of a jb rom? Or do you always have to revert back to ics stock?
6. Is Odin the Samsung equivalent of rsd lite?
Click to expand...
Click to collapse
1. Flashing kernels has been made as simple as flashing ROMs
2. kexec is outdated since the bootloader got unlocked. You can also still use CWM on this or there's another recovery that people like called TWRP (Download an app called EZ-Recovery from the play store, youll need it to flash any recovery)
3. Losing IMEI is a royal paiin in the arse, but it's rare. Either way you want to back it up. I believe the guide on how to do so is in the Development Forum.
4. I haven't tripped the flash count. Basically all it is is a way for Verizon to tell if you been f'in with your phone. I Believe that only AOSP/AOKP ROMs can trip it, not stock ROMS
5. It's a bit simpler flashing between ROMs on this phone. Just wipe data/factory reset and flash away. For the most part.
6. Yes it is basically.
Check the guide out in my sig, it'll explain how to do most everything in detail.

Brian Gove said:
1. Flashing kernels has been made as simple as flashing ROMs
Click to expand...
Click to collapse
To Elaborate on this just a bit, yes it is as easy as flashing roms but you were correct in saying that there are aosp kernels and there are tw kernels. just make sure the os version (ICS, JB) and the framework (TW, AOSP) match your rom and you are good to go!

Relentless D said:
To Elaborate on this just a bit, yes it is as easy as flashing roms but you were correct in saying that there are aosp kernels and there are tw kernels. just make sure the os version (ICS, JB) and the framework (TW, AOSP) match your rom and you are good to go!
Click to expand...
Click to collapse
Thanks Brian and Relentless. Going to cut my teeth on an easy TW rom for starters, probably Synergy.

D-meist said:
Thanks Brian and Relentless. Going to cut my teeth on an easy TW rom for starters, probably Synergy.
Click to expand...
Click to collapse
If you are just getting your feet wet with tw roms, you might consider giving Bean's a try. I've been using Build 9 since it dropped and it's smooth.
imo, it's themed just enough to not look like a straight tw rom, the performance is great and the battery life is fantastic as well.
I've tried synergy once or twice and was never quite completely satisfied with it.

D-meist said:
Thanks Brian and Relentless. Going to cut my teeth on an easy TW rom for starters, probably Synergy.
Click to expand...
Click to collapse
I haven't run CM or MIUI or any other AOSP ROM on this phone so take this with a grain of salt;
If you want cool stuff and constant bugs/lack of normal features go with the AOSP....
If you want some cool stuff and a nice stable daily driver... go with the TW ROMs. I've been running Synergy since 1.2(or 3 I cant remember lol) and I love it. Everything works on it, it's stable, and it's currently being ported to Jelly Bean so I can't wait for that shtuff. Eschelon and the rest of his team are good about listening to feature suggestions/requests too when they got time so more and more will be added.

Brian Gove said:
I haven't run CM or MIUI or any other AOSP ROM on this phone so take this with a grain of salt;
If you want cool stuff and constant bugs/lack of normal features go with the AOSP....
If you want some cool stuff and a nice stable daily driver... go with the TW ROMs. I've been running Synergy since 1.2(or 3 I cant remember lol) and I love it. Everything works on it, it's stable, and it's currently being ported to Jelly Bean so I can't wait for that shtuff. Eschelon and the rest of his team are good about listening to feature suggestions/requests too when they got time so more and more will be added.
Click to expand...
Click to collapse
Relentless D said:
If you are just getting your feet wet with tw roms, you might consider giving Bean's a try. I've been using Build 9 since it dropped and it's smooth.
imo, it's themed just enough to not look like a straight tw rom, the performance is great and the battery life is fantastic as well.
I've tried synergy once or twice and was never quite completely satisfied with it.
Click to expand...
Click to collapse
The moral of the story...Try out a few different roms What is amazing for one person might not be for the next. I'm flashing new roms every few days because I always want to see what else is out there.

Relentless D said:
The moral of the story...Try out a few different roms What is amazing for one person might not be for the next. I'm flashing new roms every few days because I always want to see what else is out there.
Click to expand...
Click to collapse
Yea I had beans for a little while... I honestly cant remember why I switched. I was just suggesting he stick with the TW ROMs period cuz I dont feel the AOSP ROMs are anywhere near stable enough yet.

Don't want to hijack OP's thread, but do any of you know how to check flash counter?
I will be getting my FOURTH sg3 this week, and this is the first time I will be returning a phone that I had rooted/unlocked/rommed. I'm all back to stock, just want to make sure I don't get a bill for $600.

Kreeker said:
Don't want to hijack OP's thread, but do any of you know how to check flash counter?
I will be getting my FOURTH sg3 this week, and this is the first time I will be returning a phone that I had rooted/unlocked/rommed. I'm all back to stock, just want to make sure I don't get a bill for $600.
Click to expand...
Click to collapse
haven't tried it but this is the best I've found searching around real quick.
http://forum.xda-developers.com/showthread.php?t=1781471

Brian Gove said:
3. Losing IMEI is a royal paiin in the arse, but it's rare. Either way you want to back it up. I believe the guide on how to do so is in the Development Forum.
How "rare" is it to lose the IMEI after flashing? And is losing your IMEI a possibility flashing any ROM or just certain ones like CM10 or AOSP, or are TW and Stock roms susceptible to this as well?
Click to expand...
Click to collapse

davefields3 said:
How "rare" is it to lose the IMEI after flashing? And is losing your IMEI a possibility flashing any ROM or just certain ones like CM10 or AOSP, or are TW and Stock roms susceptible to this as well?
Click to expand...
Click to collapse
I honestly don't know. One of the devs for Synergy ROM said something to the effect its "a weird Samsung reboot code and so the phone automatically restores a bad backup of your IMEI. It's a fluke thing"
It's 100% random when flashing anything I believe.

If u use the synergy Rom to flash it automatically has a script to back up your meid number and stuff. I've flashed synergy official cm10 nightlies without a hitch. Just make sure that u obtain root and unlock the bootloader and flash recovery. Thus far I've had no problems. Btw synergy Rom is the best one out there. Jellywiz is a jb Rom it is awesome but only thing that doesn't work is sms at the present time. If u want to back up ur meid best tool to use is qpst just Google it. Also all in one tool that has been great for me unlocking obtaining root and stuff is Verizon gs3 casual tool. In order to use that tool u mist have java se framework which u can find at the java website. Any questions feel free to shoot me a message! Good luck!
Sent from my SCH-I535 using xda app-developers app

chrisharper9643 said:
If u use the synergy Rom to flash it automatically has a script to back up your meid number and stuff. I've flashed synergy official cm10 nightlies without a hitch. Just make sure that u obtain root and unlock the bootloader and flash recovery. Thus far I've had no problems. Btw synergy Rom is the best one out there. Jellywiz is a jb Rom it is awesome but only thing that doesn't work is sms at the present time. If u want to back up ur meid best tool to use is qpst just Google it. Also all in one tool that has been great for me unlocking obtaining root and stuff is Verizon gs3 casual tool. In order to use that tool u mist have java se framework which u can find at the java website. Any questions feel free to shoot me a message! Good luck!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Just to clarify. Synergy is a stock tw based rom and CM10 is well a cm based rom. Two different monsters and roms entirely.
Sent from my SCH-I535 using Tapatalk 2

U r right but both can be flashed the same way
Sent from my SPH-L710 using xda app-developers app

davefields3 said:
Brian Gove said:
3. Losing IMEI is a royal paiin in the arse, but it's rare. Either way you want to back it up. I believe the guide on how to do so is in the Development Forum.
How "rare" is it to lose the IMEI after flashing? And is losing your IMEI a possibility flashing any ROM or just certain ones like CM10 or AOSP, or are TW and Stock roms susceptible to this as well?
Click to expand...
Click to collapse
I found this thread which looks like the Synergy guys made a script to backup IMEI. I gave it a go and was succesful in backing it up. Seemed much easier than the QPST method. Don't know if it will actually restore, but hopefully I'll never have to find out.
Click to expand...
Click to collapse

[Q] Confused about installing ICS ROM into an existing GB ROM

It has been a long day of researching on unlocking my aunts SGH-T959W . I have finally finished rooting the phone http://forum.xda-developers.com/showthread.php?t=1956025
My phone has the following status atm:
Firmware:2.3.6
Build no.: Gingerbread.WUQL86
kernel: 2.6.35.7-blastoff-v2
Blastoff does not detect any network signal, and hence I have to install another ROM
However, I am having a bit problem making a decision which ROM to install, since this is not even my phone and I am not sure.I was looking at this list http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V/List_of_ROMs
Basically I just want a stable ROM for her phone, and something fast.
One thing particularly confusing is, how can I install ICS kernels into a Gingerbread ROM, that is just not compatible. And if you guys can provide links that would be useful, THANKS ! :laugh:

With blast off kernel you can flash any ics or jb roms. Ics is solid except for wifi calling and the battery won't go for days...maybe one day. Jb needs some work still gps doesn't work and wifi is broke on 4.2.2. If you're after something stable and wifi calling isn't a deal breaker go with any ics and proton kernel. O and the latest cm9 has broken video but proton kernel fixes it.

I can vouch for CM9 with the Proton kernel. Ultragen is supposed to be good too. If the JB ROMs haven't got GPS and WiFi working when I get The Urge, I'm trying that combo.
Btw, Google Voice works for WiFi calling. It doesn't show as the cell phone number at the recipient's phone tho.
Sent from my SGH-T959V using xda app-developers app

4.1.2 is jellybean and WiFi works on that actually it all does now except for gps and 4.2.2 is the one with the borked WiFi
Sent from my Galaxy Nexus using xda premium

TwitchyEye said:
With blast off kernel you can flash any ics or jb roms. Ics is solid except for wifi calling and the battery won't go for days...maybe one day. Jb needs some work still gps doesn't work and wifi is broke on 4.2.2. If you're after something stable and wifi calling isn't a deal breaker go with any ics and proton kernel. O and the latest cm9 has broken video but proton kernel fixes it.
Click to expand...
Click to collapse
Thanks, so I was looking at this http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V/Installing_a_ROM
in the upgrade/downgrade path section, it says I have to go CM9 to upgrade, am I am still in GB (MTD) or (BML) ? And why is I can't find blastoff kernel in the list. What I am confused about is how can I get proton kernel in CM9, in the list it doesnt seem to have it in the list. Okay wait is this what you mean, go to follow the instructions of flashing to CM9, then flash to CM10 ,slim bean 3.1 or paranoid andriod 2.99

Stuck on hold said:
I can vouch for CM9 with the Proton kernel. Ultragen is supposed to be good too. If the JB ROMs haven't got GPS and WiFi working when I get The Urge, I'm trying that combo.
Btw, Google Voice works for WiFi calling. It doesn't show as the cell phone number at the recipient's phone tho.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Thanks for the response, so if custom ROMS still have problem should I just go back to the stock ROM, and if I go to the Stock ROM would I lose my rooting ? .What will be the pros and cons in this case ?

Beastmode said:
4.1.2 is jellybean and WiFi works on that actually it all does now except for gps and 4.2.2 is the one with the borked WiFi
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ahh I don't need gps xD.

There are some interface changes going from gb to ics I like. Valhalla Black and CM7 were the, two GB ROMs I used other than stock, and I liked them both for different reasons.
Usually I try a different ROM because the one I'm on flakes due to a bad app, sun spots or sumthin'. If I gotta wipe and reflash, I figure may as well try something new.
I miss swype and the office app from the stock ROMs, but I like the overall experience better with the custom ROMs.
From a security standpoint, you really have no idea if the devs can be trusted, but that's not to say SAMSUNG or Google are implicitly trustworthy either. Just saying... For that matter, having private info on a smart phone isn't probably the most secure idea either. You pick the risks you find acceptable.
One of those risks is taking on the tech support for a phone you don't own
Sent from my SGH-T959V using xda app-developers app
---------- Post added at 09:17 AM ---------- Previous post was at 09:14 AM ----------
Oh, and I believe unlocking and rooting are two totally different things. The former relates to being able to use other service providers and the later gives more access to the device's software 'innards'.
Sent from my SGH-T959V using xda app-developers app

meekazhu said:
Thanks, so I was looking at this http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V/Installing_a_ROM
in the upgrade/downgrade path section, it says I have to go CM9 to upgrade, am I am still in GB (MTD) or (BML) ? And why is I can't find blastoff kernel in the list. I am still confuse
Click to expand...
Click to collapse
It's probably because our wiki is outdated. Forgive us.
What matters is the version of cwm that you're using. Blastoff has 5.0.xx I forget which exact version is in the kernel. Anyway then you should be good to go. I'm not sure you still have to go to cm9 first. I think all our roms have the right stuff to take you from blastoff to wherever.

Stuck on hold said:
There are some interface changes going from gb to ics I like. Valhalla Black and CM7 were the, two GB ROMs I used other than stock, and I liked them both for different reasons.
Usually I try a different ROM because the one I'm on flakes due to a bad app, sun spots or sumthin'. If I gotta wipe and reflash, I figure may as well try something new.
I miss swype and the office app from the stock ROMs, but I like the overall experience better with the custom ROMs.
From a security standpoint, you really have no idea if the devs can be trusted, but that's not to say SAMSUNG or Google are implicitly trustworthy either. Just saying... For that matter, having private info on a smart phone isn't probably the most secure idea either. You pick the risks you find acceptable.
One of those risks is taking on the tech support for a phone you don't own
Sent from my SGH-T959V using xda app-developers app
---------- Post added at 09:17 AM ---------- Previous post was at 09:14 AM ----------
Oh, and I believe unlocking and rooting are two totally different things. The former relates to being able to use other service providers and the later gives more access to the device's software 'innards'.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Lol, I am just trying to save my aunts 20$, and also I get to learn something new. what method do u usually do to change custom roms is it flashing from CWM or is there a software ?. I have been really careful regarding what i do to the phone since yesterday as it is not my phone, that is why I have been asking all possible questions before starting anything . I know unlocking and rooting are two different things , but in order to unlock you need to root.
Ok so I am flashing to CM9 now , after that should flash to a different ROM, like CM10 or should I just stick to CM9 or move to Ultragen. blastoff is a battery drainer, i got up this morning it went from 100% to 30% O_O

TwitchyEye said:
It's probably because our wiki is outdated. Forgive us.
What matters is the version of cwm that you're using. Blastoff has 5.0.xx I forget which exact version is in the kernel. Anyway then you should be good to go. I'm not sure you still have to go to cm9 first. I think all our roms have the right stuff to take you from blastoff to wherever.
Click to expand...
Click to collapse
okay cool .I am rewriting this question, i think it did not get updated in my previous response. What I am confused about is how can I get proton kernel in CM9, in the list it doesnt seem to have it in the list. Okay wait is this what you mean, go to follow the instructions of flashing to CM9, then flash to CM10 ,slim bean 3.1 or paranoid andriod 2.99

You'll be able to flash any MTD rom from any other MTD/BML rom. The problem will be going from MTD back to BML but you probably won't want to do that.
As was mentioned, you will need a kernel with CWM 5.x+. You can find the blastoff kernel if you go back a few pages in the development forum.
As for which ROM to install? I recommend Team Acid's AOKP (link in my signature) using the Proton ICS kernel (by beastmode). It's been a very stable combination for me.

FBis251 said:
You'll be able to flash any MTD rom from any other MTD/BML rom. The problem will be going from MTD back to BML but you probably won't want to do that.
As was mentioned, you will need a kernel with CWM 5.x+. You can find the blastoff kernel if you go back a few pages in the development forum.
As for which ROM to install? I recommend Team Acid's AOKP (link in my signature) using the Proton ICS kernel (by beastmode). It's been a very stable combination for me.
Click to expand...
Click to collapse
what are the chances of me going back to BML rom, so once I upgrade to custom ICS based roms, I can flash different roms that are only related to ICS and JB, and not Gingerbread, since it a version behind? So if I went to CM9 , i can easily switch AOKP with proton ics kernel or ICBINB ?
Thanks FB , I followed your post for rooting it was really useful. Also I thought BML and MTD, are just file systems or type of mapping, why are they supported in kernel level and not ROM level?

[Q] What is the best way to match up a custom kernel to the ROM I'm currently running

I have flashed ROMs before on this device, but in all honesty, I just did it going by what other people were flashing. I always flashed the "latest ROMs" in tandem with the "latest kernels" that separate developers were building.
Now I would actually like to go back in time and try to find the smoothest and most stable combination I can get on 4.3 now that everyone's moving onto 4.4
I'm currently running PA with the stock kernel of 3.4.62-CM
So does that mean if a separate developer is building their kernel do I have to match the same exact kernel version of CM? (And yes I understand that AOSP and TW kernels are completely different, and I don't cross flash at all, lol)
I'm asking this to try to get a more thorough understanding of what is exactly going on when I'm changing a kernel, and how different versions matter.
Thanks everyone!
Sent from my SCH-I535 using Tapatalk

i cant go into detail about kernels since i dont know coding and all the other fun stuff
but they are fone depended.i personally use BMS kernel im on liquidsmooth 4.4 rom but have used BMS on 4.3 liquidsmooth rom . ive tried KT kernel but did not play nice with my fone it wasnt letting me change settings on it . i suggest from my personal experience try out different kernels run them for couple days to see how it plays with ur fone .