Database Users

[ROM] Eris_Official 1.0 Alpha With Controllable Overclocking! [5/9/2010]

Updated:
Changelog:
1.0
remove amazon apk
optimize all png's
optimize zips
based on new build
added su and superuser.apk
apps2SD enabled (requires FAT32 and EXT3 partitions on SD)
Wireless Tethering
Wired Tethering
added task killer tweak for speed
removed OTA
added systemro and systemrw - thanks jamezelle
Changed permissions for ADB to root
USB debugging on by default
Added Terminal
Added flash_image (for future ease when upgrading recovery images)
Added sqlite3
Added Market fix - thanks jcase
Added Overclocked kernel to 710mhz (767 didn't seem stable on everyone's phone)
Added SetCPU
Modified kernel to work with SetCPU's Autodetect
Warning: This is alpha. I don't have an eris to test this on.
Also, some phones won't be able to handle the speeds.
0.8T2
All changes from 0.7 but based on bugless 0.5.5 build (that was never released) without the De-odexing so no more FC's and other bugs.
Added systemro and systemrw - thanks jamezelle
Added wireless and wired tether apps
http://www.multiupload.com/4JGKZHXT40
0.7 Since 0.5.4:
Optimized all the pgn's in all the apk's
De-odex'd all apk's and frameworks
Zipaligned all apk's
Changed permissions for adb to root
Changed symlink to bin/ifconfig busybox
The png's and zipaligning will minimize the RAM usage of all preinstalled apps.
0.7 - http://www.multiupload.com/GN6IUOVU5G
Thank you Wes Garner for the tips on deodexing.
Based on the newest 2.1 leak - A lot of fixes by HTC
USB Debugging on by default in ramdisk
fixed su/superuser issues
Updated busybox and moved busybox symlinks to /system/xbin/bb
Removed su from xbin since it's already in bin
Added TERMINFO and libcurses to fix nano
Added flash_image for future ease when upgrading recovery images
Added sqlite3
Disable OTA (rm SystemUpdater.apk)
Changes to init.rc in ramdisk for busybox and TERMINFO
Build number now shows version number but not showing in Settings
Kill amazonmp3 app (it sucks up RAM like nobody's business)
Downloads
http://www.multiupload.com/VT874ICFFX
Don't have time to really give you a thorough intro at the moment, sorry.
Make sure to WIPE before you flash from another ROM.

Downlaoding now will flash to it tomarrow sometime thanks

Lol as soon as you put it someone put in on the irc.
Question:after this it shouldn't be full flashes and be just minor updates to the rom?
Or are they going to be full flashes? I think I asked you before but don't know if you answered.

will this unroot my phone

ivanmmj said:
Make sure to WIPE before you flash from another ROM.
Click to expand...
Click to collapse
what will happen if didn't WIPE?

Ivannmj will you allow your rom to be used as a base for other roms?

acually flashing now... so far so good ill edit the post when im done
ok, installed and working so good thanks

so ummm... ::squint:: how... do... u... wipe?

...
tonyfiasco said:
so ummm... ::squint:: how... do... u... wipe?
Click to expand...
Click to collapse
A) do you have root access on your eris?
and
B) have you put a recovery image on your eris?

tonyfiasco said:
so ummm... ::squint:: how... do... u... wipe?
Click to expand...
Click to collapse
no comment.
from recovery img, select wipe, choose factory reset, and wipe dalvik

jcase said:
no comment.
from recovery img, select wipe, choose factory reset, and wipe dalvik
Click to expand...
Click to collapse
I'll assume you have root and Recovery already.....

Does anyone have the md5 hash for this?

pkopalek said:
Does anyone have the md5 hash for this?
Click to expand...
Click to collapse
MD5: 182ACEC321A44D14F8734E249D0ED1D7
I have updated this rom, works great!

I am going to cry! I found this download yesterday
androidforums.com/htc-droid-eris/55898-you-dont-need-root-new-leak.html
This is the one you are speaking of here right? I wake up, get a call... wait for it... no sound
o
M
F
G
I could scream. Is anyone else still having this bug?

Morkai Almandragon said:
I am going to cry! I found this download yesterday
androidforums.com/htc-droid-eris/55898-you-dont-need-root-new-leak.html
This is the one you are speaking of here right? I wake up, get a call... wait for it... no sound
o
M
F
G
I could scream. Is anyone else still having this bug?
Click to expand...
Click to collapse
No this rom is for root users. and i dont know about that issue, i havent heard of that issue, im running the newest 2.1 leak and everything seems fine to me

Morkai Almandragon said:
I am going to cry! I found this download yesterday
androidforums.com/htc-droid-eris/55898-you-dont-need-root-new-leak.html
This is the one you are speaking of here right? I wake up, get a call... wait for it... no sound
o
M
F
G
I could scream. Is anyone else still having this bug?
Click to expand...
Click to collapse
Not at all. There is similar data in this one, to the one you're referring to.
The image of the one you're referring to is NOT a Root image.
it's a normal image. If you have a problem like that, try reflashing it, checking the md5 hash on that - making sure it matches someone else's that works AND/OR, just re-download the file.
Either way, you probably want to re-flash that PB00IMG.zip. But if you reflash it and the same problem happens, you will want to re-download it, or check to make sure the file is 100% intact.

<sigh> I am flashing more now than with my 6800, 6950, and Omnia combined

Can anyone verify which information is missing from Settings > About Phone > Software information?
Is it Kernel version? Build number? Software number?

pkopalek said:
Can anyone verify which information is missing from Settings > About Phone > Software information?
Is it Kernel version? Build number? Software number?
Click to expand...
Click to collapse
No information is missing in my phone, all fields are filled. Just flashed this ROM this morning and so far so good....

how does this compare to the 2.1 OTA root ROM?
I'm running evil eris right now, starting to get fed up with the bugs interfering with the necessary usage of my phone.
I am on the forums daily, but I'm getting confused with all the updates coming out and which one(s) are better than others.

[HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!]

Dear xda'er from the USA: To the disappointment of some in this forum, the xda-team has decided to split the sections on the Samsung Galaxy S i9000 and its US-counterparts into SEPARATE sections! You will be able to get some help here but you will likely be better helped/supported/suited in the forums that belong to your specific device!
Note: Many of the FAQs may still apply to you and you are welcome to make use of our setup. However, if you have open questions I suggest directing them to the above mentioned forums.
IP-Notice: You are welcome to use the information in this thread! If you do, please link the original source.
I try to give credit where due. If you feel I am using your content without your authorization or proper credits, please contact me!
General Note: There are now four official models of the Samsung Galaxy S outside the US: the GT-I9000 (International), GT-I9000M (Canada), GT-I9000B (Brazil), GT-I9000T (Mexico). All information in this FAQ is based on the GT-I9000 International version. Most of them also apply to the other models. The I9000M and I9000T are virtually identical to the I9000 and are mostly compatible with I9000 software. The I9000B has an added digital television receiver and is generally not as compatible. Please check carefully before starting to mess with the firmware on your device, check for possible compatibility issues beforehand and ALWAYS make sure you have three button recovery (see FAQ#A12)
Note: The I9000B has a separate FAQ
Note2: For the Korean Galaxy S SHW-M110S, please see this separate FAQ
Disclaimer: This FAQ is provided as-is without any warranties to completeness/correctness. I will take no responsibility if you break/brick/damage your phone.
Contents:
Post#1: Frequently Asked Questions
Post#2: HOWTO Section
Post#3: ADB Tutorial
Post#4: Tutorials and Fixes
Post#5: Tips & Tricks
Post#6: Firmware Selection Guide
FAQ Sections:
A. General
B. Firmware
C. Modding
D. Applications
E. Recovery
(A) General:
1.How can I reset my phone?
2.I have flashed a new firmware and now my phone won't connect to 3G. What's wrong?
3.Can I disable 2G broadband like on the Desire/N1?
4.I flashed a new firmware and now I cannot download protected apps and Market-enabler doesn't work. How can I still install protected apps?
5.My phone takes forever to get a GPS-fix? Is there a solution to this problem?
6.I am experiencing long loading times when opening apps/intermittent lags when switching screens. What is the problem?
7.My G-sensor seems to be off. How can I calibrate it?
8.I have a SIM-Locked phone. Is there anything I need to look out for?
9.When will Ice Cream Sandwich be released for my shiny new phone?
10.I'm running Linux. Can I still flash my firmware? Do I need to install Windows?
11.Most phones have a bunch of codes that can be entered in the dialer for special functions. What are they on the SGS?
12.My phone cannot enter download mode or recovery mode using the buttons combos. What can I do?
13.I live in Canada/Mexico (The Americas in general). Can I get my phone to use the 850Mhz bands with I9000 Modems?
1.How can I reset my phone?
On the Galaxy S the soft-reset is achieved by pressing and holding the power button. A hard-reset can executed by pressing and holding VolumeUP+Home+Power. There you will find the options "reboot", "apply sdcard:update.zip", "wipe data/factory reset" and "wipe cache partition". (Note: The list of options can vary considerably after installing modified firmware/kernels)
The "wipe data/factory reset" option will restore your phone to the original configuration of the firmware YOU LAST INSTALLED (including any updates made via update.zip). This will NOT bring your phone back to the firmware installed when you originally bought it unless you haven't flashed your phone.
You can navigate the recovery screen using VolumeUp & VolumeDown and use the Home button to select.
2.I have flashed a new firmware and now my phone won't connect to 3G. What's wrong?
The CSC you used is most likely not intended for your area. This means that the broadband provider settings are not included and need to be configured manually. To do this, go to Settings->Wireless and Networks->Mobile Networks->Access Point Names, press the settings-button and select "New APN". You will then need to enter the respective data as provided by you mobile operator. APN settings can usually be found on the operators website.
3.Can I disable 2G broadband like on the Desire/N1?
As of firmware XWJM1 (July 2010), this function is available in the wireless settings. All current firmwares now have this feature.
4.I flashed a new firmware and now I cannot download protected apps and Market-enabler doesn't work. How can I still install protected apps?
This is done by google to protect commercial applications from piracy. This usually only happens on internal beta firmwares. Use Eris Market Fix from the Market or the tutorial in P#4,T#1. Both fixes require root privileges (See FAQ#C1)
5.My phone takes forever to get a GPS-fix? Is there a solution to this problem?
It appears that the XWJM1 and XWJM2 firmwares have mostly fixed the major GPS issues and the general consensus is that these firmwares deliver consistently better GPS results than previous firmwares. The usability, however, still varies per location and sometimes the software gets no fix despite seeing plenty of satellites.
To date, there appear to be no better fixes available. There are still many reports that GPS is flaky and it appears as if Samsung is no longer working on improvements in this area.
6.I am experiencing long loading times when opening apps/intermittent lags when switching screens. What is the problem?
The Samsung Galaxy S uses the internal SD to store cache data by default. This storage uses the severely outdated RFS (FAT-related) filesystem. Next the to poor performance in a good state, RFS appears to rapidly manifest massive amounts of filesystem errors which cause the experience on the SGS to degrade over time.
Currently almost all custom kernels fix the problem by replacing the RFS filesystem with ext4 on (virtually) all partitions (some do not touch the /efs partition). Original credit for the discovery that the filesystem was the problem belongs to mimocan and the fix has since been refined by RyanZA, z4ziggy, sztupy and most notably supercurio.
7.My G-sensor seems to be off. How can I calibrate it?
The G-sensor calibration appears to be off in a lot of shipped devices. Current firmwares can calibrate the accelerometer in the Display menu.
8.I have a SIM-Locked phone. Is there anything I need to look out for?
As of now there are several reports of successfully flashed SIM-locked phones and no reports of any (related) problems.
This means that as of now (there seem) to be no specific restrictions for SIM-locked phone except the lock itself. However, the lock on the Galaxy S can be easily removed. Please refer to T&T#20 for unlocking your phone.
9.When will Ice Cream Sandwich be released for my shiny new phone?
At the moment, there are no indications that Samsung will release a fully featured Android 4.0 firmware for the Galaxy S. They are, however, porting several ICS features to Android 2.3. While this is very disappointing, there are several ICS ports based (in part) on the sources for the Nexus S available already which will probably result in a relatively stable build in the long term.
10.I'm running Linux/OSX. Can I still flash my firmware? Do I need to install windows?
If you are running Linux or OSX you do not need to install Windows. You can either run Odin in a virtual machine or alternatively use Heimdall by Benjamin Dobell. Heimdall runs natively on Linux and OSX and has reached a well tested release state.
11.Most phones have a bunch of codes that can be entered in the dialer for special functions. What are they on the SGS?
There is a list of "secret codes" here. There are also several apps in the market with these features in the market.
12.My phone cannot enter download mode or recovery mode using the buttons combos. What can I do?
Some batches in various countries seem to not have this feature. However, Samsung Canada has released a fix via Kies (for the I9000M) and it has been adopted to suit a larger audience (I9000 and I9000M). Instructions on how to update your phone to get the three-button-combo can be found here or here. Note: Follow the instructions in that post CAREFULLY and read it completely BEFORE attempting to do anything on your phone. If done improperly, this can still brick your device!!!
13.I live in Canada/Mexico (The Americas in general). Can I get my phone to use the 850Mhz bands with I9000 Modems?
Users in the Americas will find that the I9000 modems use the 900Mhz band which is not used in the Americas. However, since the I9000 is virtually hardware-identical to the I9000M and others which do use the 850Mhz band, the band can enabled on the I9000 modems. There is a guide here.
(B) Firmware:
1.What is a ROM/firmware?
2.Can I update my firmware?
3.Why are there sometimes multiple files in the firmware archive/folder?/Why do I get three different versions when using *#1234#?
4.Can I mix PDA/Modem/CSC files from different firmwares without bricking my phone?
5.My phones software version says I9000XXJF3/XXJF5/xxxxx. What does this mean?
6.I want to install new firmware but I want to have a backup of my original firmware to go back to in case I need to go back for warranty reasons. Can I backup my original firmware somehow?
7.Can I flash an Asian ROM on my European device or vice versa?
8.What is the .pit file? Why are there different versions?
9.I flashed a new firmware using Odin (or Kies) and now my phone is acting weird (force closes etc)? Also, my settings are also still there.
1.What is a ROM/firmware?
The firmware/ROM is the software that runs on the phone. In case of the Galaxy S this is (currently) Android 2.3.5 Gingerbread. The Galaxy S was initially released with Android 2.1 Eclair and will most likely not receive any major firmware upgrades anymore. Samsung is porting several features from newer Android versions but has refused to bring a fully-featured Android 4.0 release on the grounds that the TouchWiz UI together with ICS would be to big for the normal system partition.
2.Can I update my firmware?
Most likely: Yes. You can update your firmware through Samsungs official application (Kies) and with firmwares that have been leaked or otherwise been obtained for installation without using the Samsung Kies software. You can find firmwares made by Samsung for phones all over the world, here. You will also find a guide to the installation in HOWTO#1 in the second post of this thread.
Note: Please also keep in mind that not all firmwares that come with phones are available. Reflashing to stock may not be possible because the specific firmware isn't available!
3.Why are there sometimes multiple files in the firmware archive/folder?/Why do I get three different versions when using *#1234#?
Galaxy S firmware updates come in three parts (which are sometimes packaged as one file):
-The CODE itself (called PDA). This is android and all the applications that come with it. (The archives/folders will be named after the version of this file)
-The MODEM (called Phone). This is the firmware of the wireless chipset of the device and will operate you WiFi, Blutooth and 3G/2G/GSM connections. (ie Radio ROM)
-The CSC (short for Customer Specific Customization). This includes connection data for the broadband networks as well as apps that are only available in certain languages/intended for a specific area.
If we ask for your firmware, we want to know all three!
Since not all of these require updates simultaneously, often then CSC and MODEM files will have lower version numbers.
(Also when packaged in one file the repartition option should NEVER be checked in Odin because it will mess up your partition layout and will require a reflash with three-part firmware!)
Most firmwares that are currently available are no longer split up into the three parts and instead delivered as one which can be flashed by entering it as the PDA/CODE in Odin.
4.Can I mix PDA/Modem/CSC files from different firmwares without bricking my phone?
Yes. Most Modem/CSC files will work with any PDA. However, there may be compatibility issues which may force you to reflash your phone. Note also that newer CSCs usually include newer versions of the software that comes with them (Some of which may not be upgradable via the market or other means).
5.My phones software version says I9000XXJF3/XXJF5/xxxxx. What does this mean?
The first two letters describe the country while the third gives the year, the fourth gives the month and the last number/letter is the version of the firmware (from that specific month. Numbering starts at 1-9 and then uses letters from A-Z). For an extensive list of the country codes, see this thread.
Note: To better distinguish the firmware releases based on a new Android version (2.1 vs 2.2 vs 2.3 etc), Samsung has shifted the use of the third and forth letter and these are now no longer coherent with the year and month according to Samsung's old system.
6.I want to install new firmware but I want to have a backup of my original firmware to go back to in case I need to go back for warranty reasons. Can I backup my original firmware somehow?
You can backup most of your firmware through Clockwork Recovery, however, since this already requires root it is not suitable for a warranty return. Nevertheless virtually all firmwares that are currently being shipped with the phone are available and thus a restoration is almost always possible.
7.Can I flash an Asian ROM on my European device or vice versa?
Flashing firmwares between several areas is easily possible. Please make sure you have the correct model before flashing. The international SGS has the model I9000. The Korean version and the US variants have significantly different model numbers and firmwares for those phones should NEVER be flashed on the I9000 or vice versa.
8.What is the .pit file? Why are there different versions?
There are now three different versions of the .pit file. 513.pit, 512.pit and 803.pit. Most firmwares since the end of 2010 do not require a .pit file to be selected. Generally only the 512 version is used. The .pit file is only necessary if you intend to repartition the phone. If you do, you inadvertently wipe all your data (not the internal SDcard). Since the partitioning of the device has not changed for more than a year, repartitioning is almost never necessary unless you used a custom firmware like cyanogenmod, which changes the partition sizes.
The .pit file maps partitions on the NAND storage.
9.I flashed a new firmware using Odin (or Kies) and now my phone is acting weird (force closes etc)? Also, my settings are also still there.
Some firmwares that can be flashed via Odin and the firmwares that are flashed using Kies, do not touch your settings and they do not empty your cache and appdata partitions. As a results, there is data there from previous firmwares which may lead to unforseen complications. Especially so, if your previous firmware was based on a different android version (i.e. flashing from XWJM6(android 2.1) to XXJPC(android 2.2)). You can attempt to overcome this by wiping the cache. Usually, to resolve this, you have to do a factory reset according to FAQ#A1
(C) Modding:
1.What is root/rooting?
2.What are customROMs? How do I get them?
1.What is root/rooting?
root is the user account in Linux with all privileges. The root user can edit anything on the system. For safety reasons, users do not have all those privileges. When you root your phone, you will gain write access to areas of the phone you couldn't previously access and are allowed to run more commands in the terminal. Because applications do not get a lot of priviledges, some of them require you to root the device in order for them to function properly (or fully). There is a tutorial for rooting in the Post #2 and there is a Chainfire Root that works most firmwares. CF-Root essentially is a kernel that is flashed over the original kernel.
If all of this means nothing to you then you are probably wise to NOT root your phone. Mistakes using root can break your phone very easily. (Usually, but not always, these can be solved with a reflash)
2.What are customROMs? How do I get them?
Custom ROMs are modified versions of the Samsung firmware or complete rewrites of the Android OS for the Galaxy S such as Cyanogenmod (and the derivative MIUI). Almost all current custom ROMs are based on Android 2.3 with some now being based Android 4. They can be found in the Android Development Subforum.
(D) Applications:
1.I tried using Allshare/DLNA but it will not recognize my device/play any files?
2.Can I change the default homescreen of the Touchwiz Launcher?
1.I tried using Allshare/DLNA but it will not recognize my device/play any files?
As of now a lot of DLNA certified devices/software do not work with Allshare. However, Samsung TVs should work and Windows Media Player 12 as well as Samsung's PC Share Manager work in most cases.
2.Can I change the default homescreen of the Touchwiz Launcher?
You cannot change the default Homescreen in the settings. However, if you are rooted, there is a way to change the default homescreen. See T&T#5 for more info.
(E) Recovery:
1.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
1.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
Most likely: YES! In almost any case, you should still be able to turn off the device (if necessary by removing the battery) and start into download-mode (VolumeDown+Home+Power) or recovery-mode (VolumeUp+Home+Power). After (for example) an unsuccessful flash, you can retry the flash in download-mode (same steps as when flashing a functioning device). If a flash to a functioning f/w (without applying any update.zip) doesn't help or you cannot get your PC to flash at all, you can ask for help here.
If you see a symbol asking you to connect to the PC, depending on how you arrived at this point, it may be sufficient to connect to the PC and run Odin (i.e. press "start" when the phone is recognized) without adding any files. This may, however, leave some residual issues if (for example) had an incorrect/incomplete flash so you may want to do a normal flash after this!
If you do not have download mode and for some ludicrous reason felt the need to go ahead and modify your firmware regardless of this lacking, there is now a guide on creating a home-made JIG which will force your device into download mode without the actual button combo here. Also pre-fabricated JIG dongles can be purchased on ebay for a couple of EUR/USD.
-----------------------------------------------------------
Changelog:
[12th July] FAQ created.
[12th July] Added Flash HOWTOs in Post#2
[13th July] Added list of CustomROMs in FAQ#10
[16th July] Added notification for US phone users
[18th July] Added rooting to HOWTOs
[18th July] Added ADB tutorial in Post#2
[19th July] Moved ADB tutorial to Post#3
[19th July] Added Tutorial/Fix section in Post#4
[19th July] Added "Protected Apps Market Fix" in Post#4, Tutorial#1
[24th July] Removed SIM-Unlocked as a requirement from flash HOWTO (Post#2, HOWTO#1).
[24th July] Added Tags for categorizing the FAQ
[26th July] Added Tip&Tricks section in Post#5
[20th August] Added a ROM-Selection Guide in Post#6
[30th August] Major Rework of the FAQ section
[8th October] Added "Installing any official firmware using Kies" in Post#4, Tutorial#2
[17th October '10] Added "Extracting Samsung Phone Drivers from Kies Installer" in Post#4, Tutorial#3
[2nd March '11] Began Major Update
[5th November '11] Updated to recent release of Android 2.3 and other changes
[7th January '12] Some updates to reflect recent changes regarding software and Android 4.
[6th April '12] More updates regarding Android 4.0 and some other updates.

Flash/Update Guides
!!!READ THE GUIDES AND NOTES COMPLETELY!!!
General Note:Flashing may refer to both methods. However, Method 2 requires files to already be on the phone. Therefore if you semi-bricked your phone, method 1 is usually the preferred way to fix it.
General Note 2: Flashing firmware and/or factory resets will WIPE your APN settings. Make sure you are using the right APN if that is a possible issue with your provider.
Important General Note: Several batches of phones that were sold have the download-mode button combo disabled (VolumeDown+Home+Power or alternatively Home+Power on some phones). Check if the download-mode combo works BEFORE flashing! Please refer to FAQ#A12 and T&T#23 for a fix for the download mode if it doesn't work on your phone!
HOW TO:
1.Flash Firmware and kernels using Odin.
Note: This will in (almost) all cases erase all your data and applications (includind root!). It will NOT touch the internal or external SD card.
Requirements:
-Odin3 version 1.82 (Note: Odin should be on the system partition (the partition where windows is installed) to avoid possible issues)
-".PIT" file for the Samsung Galaxy S (See FAQ#B9 or the source of the FW for the version to use! Not needed for kernel flashes.) .PIT files are usually not necessary anymore since the partition layout of the SGS hasn't changed since the end of 2010
-USB cable
-Desired firmware package or desired kernel package
Procedure:
1.Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connecting the phone via USB!)
2.Select the PDA/Modem/CSC/.PIT files in Odin. (For kernel flashes, only PDA is required. For FW flashes, at least a PDA is required. Some PDAs have Modem and CSC integrated. If you decide to repartition, make sure you choose the right file, currently almost always the one with the ending 512.PIT)
[Optional]3.Check the "Re-Partition" checkbox. (Only do this if you have separate packages for PDA, Modem and CSC AND you have a .PIT file selected! Don't do this for single PDA flashes or kernel flashes!)
4.Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.
5.Connect your phone with your computer and wait until the drivers are installed.
6.When the drivers are installed, click Start.
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
8.You have successfully flashed your phone.
2.Update to CustomROMs/Mods/Root using .zip files
Note: Depending on the firmware you selected, this may or may not wipe your applications and the respective data. In any case, it will not touch your internal and external SDcards!
Requirements:
-ADB (from the Android Software Development Kit) -- Optional
-CustomROM File
-USB-cable
-2e recovery, Clockwork recovery (can be installed using HOWTO#1 and an appropriate kernel) (Note: 3e recovery will not allow the installation of .zip files that aren't signed by Samsung and is as such not usable for this procedure)
There are two methods for applying the update. Procedure A requires some basics in using a terminal (and ADB). Procedure B can be carried out by anybody but usually isn't available if the bootloader does not have download mode. See FAQ#A12 for more information on download mode using the button combo.
Note: The recovery screen can be navigated using the Volume Up and Volume Down Buttons (Up and Down) and the Home Button (To Select)
Procedure A: (Requires ADB)
1.Copy the CustomROM/root file to the "/sdcard/" folder on the phone and (if not already the case) rename to "update.zip"
2.On the phone go to Settings->Applications->Development and check "USB debugging"
3.Extract the Android SDK and navigate to the /tools/ subfolder of the SDK folder using cmd.exe.
4.Run "adb reboot recovery" to enter recovery mode
5.Wait for the recovery screen en select "apply: /sdcard/update.zip"
6.Wait for it to finish and reboot.
Procedure B: (Does NOT require ADB)
1.Copy the CustomROM/root file to the "/sdcard/" folder on the phone and (if not already the case) rename to "update.zip"
2.Restart in Recovery Mode by pressing an holding VolumeUP+Home+Power.
3.Wait for the recovery screen en select "apply: /sdcard/update.zip"
4.Wait for it to finish and reboot.
If you encounter trouble with the ROM afterwards, enter recovery mode again and select "factory reset/wipe data/cache" and confirm before seeking help.

ADB Tutorial
ADB Tutorial
Many tutorials, fixes and mods are written assuming a basic knowledge of ADB. ADB is a command-line tool that is part of the Android Software Development Kit (a.k.a. Android SDK or ADK). This tutorial is aimed at getting you acquainted with the basic functions/workings of the ADB tool.
(Note: I do not currently use/have Linux installed. For now, this tutorial will be Windows-only. However, I suspect Linux users are versed in command-lines already and do not need a tutorial like this to open adb)
Requirements:
-Android Software Development Kit (you do not need to run "SDK Setup.exe" to use ADB!)
-Rooted Samsung Galaxy S
-Busybox (installed from market and updated!)
Basic Setup:
In order to use ADB you will first need to decompress the Android SDK. For simplicity, decompress the folder "android-sdk-windows" into the root of one of your partitions. (I am using the root folder of my D: partition for the purpose of this tutorial)
You now need to start the Windows Command-Line tool "cmd". This differs per Windows version:
XP: Go to the start menu and click "Run", type "cmd.exe" and confirm with "Run"
Windows Vista/7: Go to the start menu, type "cmd.exe" and hit enter.
You will now see a command-prompt open (I erased my username):
As stated before, my "android-sdk-windows" folder is located on my D: partition. You will now need to navigate to the "platform-tools" subfolder of the "android-sdk-windows" folder:
Before we go any further we will now have to complete some steps on our phone:
-Make sure the phone is rooted (find the application "Superuser Permission")/has the latest version of busybox installed (Run "BusyBox installer" and make sure it says, that the latest version is installed). If not, root your phone according to the HOWTO in Post#2 and install busybox from the market (and follow the instructions in the description) respectively.
-Put your phone in USB debugging mode: "Settings"->"Applications"->"Development" and check "USB debugging"
-Close all other applications on your phone and go back to the TouchWiz Launcher Home Screen
-Connect the phone to your PC
Now, we are ready to run ADB:
I hope this helps all those who were clueless so far on all the adb-based tutorials for fixes etc.

Tutorial for Market Fix
Note: This section is strictly a work in progress and new tutorials will be added when they become available and have been confirmed as working!
Content:
1.Market Protected Application Fix
2.Installing any official firmware using Kies
3.Extracting Samsung Phone Drivers from Kies Installer
4.Backing up the /efs folder
Tutorials/Fixes:
1.Market Protected Applications Fix
Background: In order to prevent the illegal copying of copyrighted applications google has integrated what are called protected apps. These applications have some copying protection which means they cannot be backup-ed without root. In order to prevent rooted/modified phones from getting those applications, google market checks the build.prop file in the /system/ folder against a verified list to see if the version of your firmware is an official release. This tutorial will show you the steps to replacing the build.prop of the firmware you installed with that of a firmware that is verifiedand accepted by google.
Note: MoDaCo's r2 and the derivatives thereof have a fix included for this in the ROM (can be found in "MCR Scripts").
NOTE: As of now, "Eris Market Fix" from the android market seems to work on the SGS. It uses a similar procedure and should achieve identical results (for now). The app itself can be uninstalled after the fix is working.
Requirements:
-Rooted Samsung Galaxy S
-ADB (from the Android Software Development Kit)
-build.prop from a recognized official firmware
Procedure:
1.Download and extract "build.prop".
2.Copy the "build.prop" to the root of your internal SD card (to the folder "/sdcard")
3.Make sure the phone is rooted (find the application "Superuser Permission")/has the latest version of busybox installed (Run "BusyBox installer" and make sure it says, that the latest version is installed). If not, root your phone according to the HOWTO in Post#2 and install busybox from the market (and follow the instructions in the description) respectively.
4.Run the following commands in ADB (for a tutorial on ADB, see Post#3):
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
busybox mv /sdcard/build.prop /system/build.prop
reboot
5.Wait for the phone to reboot. Check if can see protected apps (for example the paid version of tapatalk)
6.If you cannot see protected apps, you may have to wait a while in order for market to recheck the build.prop. This process can be helped bu setting the system time (manually) to 23:59 (i.e. 11:59PM) and wait for it to pass the 0:00 (i.e. 12:00AM) mark. Then return the time to the correct time setting and reboot. (You may still need to wait a few minutes before you can actually see protected applications)
7.If you still can't see protected applications, restart in recovery mode ("Volume Up"+"Home"+"Start") and wipe the cache of your phone. (You may still need to wait a few minutes before you can actually see protected applications)
For the interested, here a explanation of the code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount is the linux routine to mount a device to a specific path
-o will allow you to issue several commands to the mount routine, separated by commas
remount will unmount and then mount the filesystem again
rw will cause the filesystem to be mounted with read/write permissions
-t is the parameter used to define the filesystem
yaffs2 is "yet another flash file system 2"
/dev/block/mtdblock3 is the hardware-location of the system path
/system is the path to which you want to remount the hardware location
busybox mv /sdcard/build.prop /system/build.prop
busybox causes the following commands to be executed by busybox instead of default android
mv moves files from one location to another
/sdcard/build.prop is the path to the file that is being moved
/system/build.prop is the path where the file gets moved to
2.Installing any official firmware using Kies
Background: In August 2010 Samsung started (if only scarcely) to release official and test updates for the i9000 firmware. Since many users have flashed different firmware and the ways of backing up original product codes were not know at the time, most people who flashed their phones do not have the original settings from their country and/or provider and can thus not get the official updates for their area. Forthermore, some updates were only released in one or a few areas and people outside those areas wanted access. Consequently, Zangieff figured out a way to fake the phone information for Kies in order for it to find and install updates from a specific area. This is a slightly adapted version of his fix.
NOTE: There have been no firmware releases for some areas and providers through Kies. This fix is only able to upgrade to versions that have actually been released on Kies.
Requirements:
-Samsung Galaxy S
-Samsung Kies
-Basic knowledge of regedit
Procedure:
1.Run Kies, connect the phone and make sure it is properly recognized.
1.1.If you have never before opened the firmware upgrade widget with your phone connected before, open it now and then close it again (Do NOT close Kies!)
1.2.Optional: (Only do this if you are looking for experimental updates!)
1.2a. Open the firmware upgrade widget in Kies
1.2b. Press Ctrl+Alt+U+P simultaneously. Kies will confirm the correct sequence with "Test Mode is ON".
1.2c. Close the firmware upgrade widget of Kies
2.Run regedit (Start-->Run...-->Type "regedit"-->Press Ok) (Windows XP)/(Start-->Type "regedit"-->Press Enter) (Windows Vista/7)
3.Use regedit to navigate to "HKEY_CURRENT_USER/Software/Samsung/Kies/DeviceDB/". You will find a number of folders in numerical order (usually) starting from 1. Find the folder with the relevant keys (see below) and make sure it is the one currently in use. [If you find several folders with the keys and don't know which are the right ones, delete all of them, repeat step 1 and 1.1 and find the folder with the lowest value. (You may have to use F5 or View--->Refresh to get to see the new folders)]
4.Find the registry keys "HIDSWVER" and "ProductCode"
5.Replace them with the appropriate keys as needed for your desired upgrade.
6.Open the upgrade widget in Kies and enjoy updating.
To find the appropriate values for HIDSWVER and ProductCode, check this thread for an extensive list of codes.
Note: If you close Kies, you will have to repeat the process.
Note2: You can upgrade to the most recent official firmware version from any firmware version even if you already have the same version or a newer one installed
3.Extracting Samsung Phone Drivers from Kies Installer
Background: Not all users are interested in installing the full software package Kies in order to get to flash their phone via Odin or Heimdall. The Kies installer turns out to be extractable using 7-zip and the phone drivers have a separate installer. This allows for installing only the phone USB drivers and lets you avoid installing Kies and the included bloatware.
Requirements:
-Samsung Kies installer package (found here)
-7-zip (found here)
Procedure:
1.Install 7-zip
2.Right click the Kies installer and Find 7-zip->Extract to "Kies_x.x.x.xxxxx_xx\"
3.Navigate to "Kies_x.x.x.xxxxx_xx-->CabFile-->USB Driver"
4.Right click the "SAMSUNG_USB_Driver_for_Mobile_Phones.exe.cab" file and 7-zip->Extract to "SAMSUNG_USB_Driver_for_Mobile_Phones.exe\"
5.Open the folder SAMSUNG_USB_Driver_for_Mobile_Phones.exe\ and execute SAMSUNG_USB_Driver_for_Mobile_Phones.exe and follow the installer instructions.
6.Enjoy connecting your phone without the full Kies install.
4.Backing up the /efs folder
Background: Some experimental firmwares modify the /efs folder. This can cause IMEI corruption and/or change the product code your phone reports.
Requirements:
-Rooted Phone
Either (A):
-ADB (from the Android Software Development Kit)
Or (B):
-Root Explorer (from market)
Procedure:
1.Make sure your phone is rooted (and busybox is installed for ADB procedure)
A:
1A.Enable USB debugging mode (Settings-->Application-->Development-->USB debugging)
2A.Connect the phone to USB
3A.Open a command prompt and enter adb (see tutorial)
4A.Acquire root privileges (type "su"). (Make sure you accept the root-prompt on the phone)
5A.Execute "busybox cp -a /efs /sdcard/"
6A.Disconnect the phone, deactivate USB debugging, reconnect the phone and backup the copy of the efs folder to your PC
B:
1B.Use root explorer and navigate to the root of the filesystem /
2B.Press "Mount R/W"
3B.Copy the efs folder to your sdcard
4B.Connect the phone to the PC and backup the copy of the efs folder to your PC.
2. Restore the backup if your IMEI gets corrupted or your product code is changed by a firmware.

Tips&Tricks
Handy Tip&Tricks
by Forum Members
This is for all Samsung Galaxy S users (GT-i9000 only. Some might work on US versions). It is a collection of handy tutorials that were posted in the development section but that do not need to be on the first page constantly.
Note: These links are provided as-is and most are untested by me! All credit for the procedure goes to the respecitve poster/involved parties.
1. Changing Fonts (for free) by socket84
2. Replacing Samsung Media Player with Android default by aditya_t90
3. Generating TUN.KO for OpenVPN on SGS by newmail
4. Replacing TouchWiz calendar with Android default by tommy34
5. Setting default homescreen in TouchWiz launcher by socket84 or the derived SGS Screen Changer by pedrodh
6. Installing Samsung Phone drivers WITHOUT Kies
7. OneClick Lagfix by RyanZA
8. CFLagFix by Chainfire
9. LagFix using update.zip by Tayutama
10. SuperOneClick Root by CLShortFuse
11. Headphone SoundQuality Fix or MixGet from Market by gilsken
12. AMOLED Screen for Notifications App by madmack
13. Using LED-Button Backlights for notifications by neldar
14. Comparing Firmwares on Packages by GAda
15. Stopping automatic media scan & scan on demand by aditya_t90
16. Overclocking/UnderVoltaging the CPU by raspdeep
17. Creating FlipFont APKs by ritalin
18. Circle Battery Indicator Mod by Fightspit (ported to SGS by designgears)
19. Official Firmware Update without running Kies by miki4242
20. Unlocking/Unfreezing Samsung Galaxy S for Free (collaboration, see thread for credits)
21. Choosing between GlassLock and Android's stock lock screen by Ateisti or Android Stock Lockscreen for JM8,JPH,JPK,JM9,JPM,JPA,JP6 by Project1.exe
22. Flashing under Linux and MacOS X using Heimdall by Benjamin Dobell
23. Restoring the three button recovery/download combo by Richthofen
24. ADB filesystem plugin for Total Commander by sztupy
25. Enabling Landscape Mode in TouchWiz Launcher by scheichuwe

Firmware and LagFix Selection Guide
Last Updated: April 3, 2010. Up-to-date as of April 3, 2011 15:53 CEST
As you may have noticed, there are a lot of firmwares on samfirmware.com and it's not very clear which ones are best/least buggy etc.
In this section, I will give a general guide to which firmware to use depending on your preferences:
If you like the stock Samsung Galaxy S experience and are looking for the most stable/bugfree version:
-Flash I9000ZSJPK or I9000XWJS8 according to HOWTO#1.
-Install the one of the kernels below or one of the lagfixes from FAQ#A6.
If you would like have the latest firmware and are willing to tolerate some bugs (this is beta firmware):
-Flash I9000XWJVK according to HOWTO#1.
For a list of current custom ROMs, see this thread
Lagfixes and Kernels:
In FAQ#A6 the currently used methods for lagfixes are described. There are a number of enhanced kernels (most of which use at least one of the lagfixes) that add features such as more accessible RAM, enhanced compiling, Clockwork Recovery, Blacklight Notification and several various features depending on the Kernel. Here is a list of the popular, well tested, optimized kernels (Note: Some of them include an overclock):
-hardcore's speedmod Froyo
-laststufo's Super Optimized Kernel
-supercurio's Voodoo Lagfix
-DamianGto's Ultimate Kernel
-tegrak's lagfix build Kernel
There is a frequently updated list here
General Note:
If you want to take the modding further, look at FAQ#D2 in Post#1 for a list of Custom ROMs and chose one you like. Depending on whether or not there is a lagfix integrated, you should then apply one of the lagfixes from the first suggestion. I would also suggest avoiding loop-mount fixes like OCLF and CFLF (see FAQ#A6) because performance rapidly declines over time.
Note: None of the available ROMs completely fix the poor GPS. Most of the ROMs noted above are provide roughly the same GPS performance. Samsung is hoping to release a full GPS fix in september (hopefully with the froyo release) It is not clear if or when Samsung will release a full fix for the GPS issues. However, it is doubtful since there are now many indications that the issue is in fact hardware related and even the final Froyo release doesn't completely fix the GPS.

For us coming from HTC devices if we hose the recovery partition is there a way to recover the phone. It was HBOOT (FastBoot) in the HTCs. Does ODIN provide the ultimate "debricking" feature. I realize there are ways to brick that are unrecoverable, but if I hose the recovery and I am done I will be very hands off on modding.

thanks for this. a good starting point to gather all the info!
should sticky this

I think we are still out of a mod for this forum...

might wanna add this for calibration of the orientation sensor:
http://forum.xda-developers.com/showpost.php?p=6999499&postcount=8

tommy34 said:
might wanna add this for calibration of the orientation sensor:
http://forum.xda-developers.com/showpost.php?p=6999499&postcount=8
Click to expand...
Click to collapse
Added! Thanks =)

can this be a sticky, its very informative?

Great! I've acctually been waiting for a thread like this!
In Sweden one operator(Tele2) seems to have issues with the device not switching to 3G even when available. Does anybody else have these issues with their operators?

FrezoreR said:
Great! I've acctually been waiting for a thread like this!
In Sweden one operator(Tele2) seems to have issues with the device not switching to 3G even when available. Does anybody else have these issues with their operators?
Click to expand...
Click to collapse
Did you check your APN settings? Did you contact the provider concerning the issue?

Darkstriker said:
It appears it doesn't take long for this reserved post to become useful. I'll post short guides on flashing firmware here. (...)
Click to expand...
Click to collapse
In the Flash Firmware using Odin guide didn't you forget to add "SIM unlocked phone" as a requirement?

Akerfeldt said:
In the Flash Firmware using Odin guide didn't you forget to add "SIM unlocked phone" as a requirement?
Click to expand...
Click to collapse
I know it says so in the guide but I recall having read that SIM-locked phones can be flashed as well. Don't quote me on that!
Added it as a requirement for now.
Edit: I did read it here. However, it seems that those phones aren't actually SIM-locked, so for now, SIM-Unlocked is definitely a requirement.
Thanks for pointing it out! =)

Darkstriker said:
Did you check your APN settings? Did you contact the provider concerning the issue?
Click to expand...
Click to collapse
The APN settings should be fine, the phone works on both 2G, 3G and HSPDA, but when it at some point have switched to 2G it will stay in 2G and you would have to manually set it to 3G.
Yeah we are a group on a Swedish android forum where someone have contacted both samsung and tele2 about the problem. But if not anyone here has the same problem it surely must be tied to the operator, which is what I have thought all along.

efbenson said:
For us coming from HTC devices if we hose the recovery partition is there a way to recover the phone. It was HBOOT (FastBoot) in the HTCs. Does ODIN provide the ultimate "debricking" feature. I realize there are ways to brick that are unrecoverable, but if I hose the recovery and I am done I will be very hands off on modding.
Click to expand...
Click to collapse
I'm sorry efbenson, I seem to completely have missed your post.
I'm not sure how this works on HTC android devices since I have only had a Windows-mobile version. What seems to be the equivalent of the features you are "describing" is the download-mode (VolDown+Home+Power) which can be reached even after interrupted firmware-flashed (experienced it myself. Still scary as hell!)
However, I don't think I'm fully qualified to answer your question. Maybe you could reformulate it, since it's not very clear right now.

This definitely deserves a sticky, thanks for this DS

FrezoreR said:
The APN settings should be fine, the phone works on both 2G, 3G and HSPDA, but when it at some point have switched to 2G it will stay in 2G and you would have to manually set it to 3G.
Yeah we are a group on a Swedish android forum where someone have contacted both samsung and tele2 about the problem. But if not anyone here has the same problem it surely must be tied to the operator, which is what I have thought all along.
Click to expand...
Click to collapse
I haven't had such problems and I dont remember reading anything of the kind so far so this likely is an issue with your provider. Maybe you can check if this occurs everywhere or only in specific areas (like cities) or something like that.

[Kernel] Voodoo (lagfix_3.0) + Backlight notification for Captivate. It works!

THIS IS FOR CAPTIVATE ONLY
I am not responsible for any damage caused to your device
BACKUP BACKUP BACKUP with Nandroid and Titanium Backup before installing this.​
What this is:
Voodoo lagfix beta 4 from supercurio
Backlight notification patches from neldar
Vanilla Captivate kernel built from Samsung sources.​
What this is *not*:
Unhelpful OC/UV kernel. I did start from his github repository, and cherry picked the changes I wanted while leaving the OC/UV out for now.
Voodoo color fix.​
How to install
Download captivate-voodoo3.0_bln_v1.10.zip. (You can also install captivate-voodoo_lagfix_3.0_v1.10_nobln.zip if you do not want backlight notification).
Did I say backup first yet? Backup in case something fails and you need to recover!
Rename the downloaded file to update.zip, put it on the root of your built in sd card (not the removable one!), reboot into stock recovery mode, select reinstall packages. The first conversion takes a long time depending on how much data needs to be converted (the white AT&T screen). The phone will tell you as it progresses through the different stages ("please wait", "step 1", "step 2" and if all goes well "conversion successful"). Important: You have to install via recovery using the update.zip if you want the backlights to work because this also needs /system/lib/hw/lights.default.so to be updated for BLN support. Either that, or install the file yourself by pulling it out of the update.zip and putting it in /system/lib/hw, overwriting the stock version. If you do not want backlight notification, install captivate-voodoo_lagfix_3.0_v1.10_nobln.zip instead.
Important
If you have installed v1.2 or below or installed v1.4 or installed v1.5 while I had it up, you need captivate-voodoo-beta4-v1.5a.zip to clean up the sound configuration first. Then install the latest release. You do not need v1.5a if this is the first time you are installing this (or are coming from stock), you just need the latest release.
Nandroid, ClockworkMod
Disable the lagfix as above before using Nandroid, Clockworkmod because they do not understand EXT4 yet and will not backup correctly.
More details on the voodoo lagfix on http://project-voodoo.org/installation as it is basically the same as the Galaxy S (international).
Enjoy!​
HSUPA (optional, bluetooth mic does not work):
Install Captivate Voodoo+BLN+HSUPA kernel+ I9000 JH2 modem: Before you flash this, first install the Captivate Voodoo+BLN kernel above. Then use ROM Manager to flash i897_hsupa_v1.10.zip. This will install a new Captivate Voodoo+BLN+HSUPA kernel that allows us to use the I9000 JH2 modem that enables HSUPA for us. There is no need to disable-lagfix if you already have Voodoo lagfix working, but it is a good idea to make backups in any case. Note: Bluetooth mic does not work with this yet.
Revert back to Captivate Voodoo+BLN+JH7modem:
Use ROM Manager to flash i897-captivate_v1.10-revert.zip. This will flash back to the Captivate Voodoo+BLN kernel without HSUPA and will also flash the Captivate JH7 modem. No need to disable lagfix if you are already running it.​
Uninstall:
Disable lagfix
1. Mount phone on computer (connect it so that you see its two card, one internal, one external if you have one).
2. Navigate to the Voodo folder on the internal SDCARD (there should be only one of the two cards that has this folder)
3. Create a file (or folder) named "disable-lagfix", no extensions. (right click -> new-> new file or folder)
4. Unmount your cards from the computer.
5. Shut phone OFF.
6. Turn back on.
You should hear the "Converting EXT4 back to RFS".
Scary way to get original kernel back
If you really really want to go back to the kernel you had before applying the lagfix kernel (why?), first disable the lagfix as explained above. Then you will need to get into adb shell, with root.
Code:
thor$ adb shell
$ su
# redbend_ua restore bml7-zImage-kernel-backup.img /dev/block/bml7
Be very very careful with this command. If you make a mistake, you can brick you phone for good.
If *I* wanted my original kernel back, I would just disable-lagfix, make a backup and then use Odin One-click to go to stock and then restore from backup. Much less scary and no danger of killing the phone.​
Changelog:
1.10 Added backlight notification. Changed to use stock sbin/init because the previous init might have been the cause of some ppl losing sdcard or usb (might have been!). captivate-voodoo3.0_bln_v1.10.zip captivate-voodoo_lagfix_3.0_v1.10_nobln.zip
1.9 Same as 1.8, but with a different method for handling init.d scripts so it uses the standard busybox run-parts. captivate-voodoo_lagfix_3.0_v1.9.zip
1.8 Make sure /data is mounted noatime, nodiratime - better performance and fewer writes to flash. Was an oversight that these were dropped. captivate-voodoo_lagfix_3.0_v1.8.zip
1.7 Cleaned up /system so nothing is left there after the phone comes up fully. No change in behavior. captivate-voodoo_lagfix_3.0_v1.7.zip
1.6 Clean voodoo installation with stock Captivate kernel (actually the same as v1.3, but to avoid confusion for ppl coming to this from stock). captivate-voodoo-beta4-v1.6.zip
1.5a Bugfix release that cleans up the mess from any previous voodoo installs that disabled sound for you. captivate-voodoo-beta4-v1.5a.zip
1.4 There is no 1.4 anymore. If you installed it, you need 1.5a above.
1.3 Fixed headphones problem (configuration problem for sound in general) captivate-voodoo-beta4-1.3.zip
1.2 Added init.d support to allow things like mobileAP etc to work. Do not use.
1.1 Totally vanilla update.zip - has nothing but lagfix. Do not use.
1.0 Left some pieces from my SRE installation on the update.zip - fixed in 1.1​
Credits:
Francois Simond, supercurio on XDA (Voodoo lagfix)
[email protected] (Backlight notification patch)
[email protected] (kernel help)​
Github repositories:
Voodoo initramfs used to build the kernel initramfs
Linux kernel sources, configs for Captivate to build this release
Toolchain used
Clone the repos, change the CONFIG_INITRAMFS_SOURCE to point to the voodoo initramfs in the i897_defconfig file under arch/arm/configs of the kernel and build with the build_kernel.sh in the top level of the linux kernel directory. The build_kernel.sh has to be edited to change CROSS_COMPILE to point to the toolchain and the AOSP variable has to point to the place where it can find the signing tools under the eclair build from AOSP.​
Donate:
I am a liver transplant survivor and I would not be here if not for the generosity of the person who was thoughtful enough to have signed up to donate his organs before he passed away.
And if you are feeling cash rich, you could also support supercurio for the voodoo lagfix and support neldar for the backlight notification. ​I have tried to keep the kernel as vanilla as I could so that I could isolate the changes to just the ext4 lagfix. I will include more things as I work on this and if I have the time!
I am putting everything on github so others can continue on this if I am lax
-Atin

oooo nice! 10 chars

my sweet jebus yes

Installing now. Lets see what all this talk has been about.
My phone is talking to me!

Great. Another reason to flash. Thanks. )
Sent from my f5 hitter.

GOD DAMMIT! literally 5 minutes after i flash SRE this comes out. how should i flash over, just head back to stock?

DOAlaboratories said:
GOD DAMMIT! literally 5 minutes after i flash SRE this comes out. how should i flash over, just head back to stock?
Click to expand...
Click to collapse
you can flash on top. you'll lose some of the things from SRE until I have the two merged fully.

Should I just Odin myself back to stock then do this or will it work over my root, lag fix, etc?

After a really bad experience with SRE and sleeping death, this is much needed. Thanks much

Ah.. so this is where everyone seems to be tonight lol.. going under my USER CP i see the vanilla/SRE/Capti-VibHybrid always refreshed!
Great to hear this I'm excited to see if anyone finds poquito bugs!

I just flashed this on top of SRE running jH7 and my
Phone is talking to me while
It's on the Att white screen! Crazy but it's sexy ahahahA

why not have this simply as a lagfix, and incorporate it into SRE, instead of trying to make yet another all-in-one tool?? It will be nice to just have one tool (SRE), and have the voodoo lagfix incorporated into that instead of the other way around.
Oh and btw, if you do incorporate unhelpfuls oc/uv kernal...PLEASE keep a version with stock clock speeds/voltages. Some of us have no desire for this, and as of now, it seems to be the source of most of the problems.

I have one request. I see that u are planning to incorporate oc/uv in this mod. Can u make a non-oc/uv version as well? My experie ce with it has been nightmarish

Just finished!
Got 1533 quadrant score with all my stuff intact. No fresh install! Loving this so far!
Edit: ran quadrant second time and I got 1785

Hey, looks like someone stole my thread layout... pshhhhh
this is going to be in SRE
the fix, not this...

designgears said:
Hey, looks like someone stole my thread layout... pshhhhh
Click to expand...
Click to collapse
I thought I felt strangely familiar reading the OP.... lol
Can we get a lagfix only update like on the main voodoo page? This one messed up my theme and that's gonna be a deal breaker. lolz jk
EDIT: Ahhhh and removed my overclock!!

wow, just downloaded the zip, not very happy about this...
that is SRE with a few edits to add voodoo...
shame on you
THIS IS SRE WITH VOODOO
ha, and this is the I9000 kernel, its not even for captivate.

designgears said:
wow, just downloaded the zip, not very happy about this...
that is SRE with a few edits to add voodoo...
shame on you
THIS IS SRE WITH VOODOO
Click to expand...
Click to collapse
first the thread layout, and now SRE! You should take this as a compliment, that means you are doing something right!

wow really DG?! dang .. something is very wrong with this IMO. :/ .. is this going to be another cyanogen type drama Dx ..
at least he mentioned your name in credentials..
lol it's written designgears(SRE) .. it's openly written he literally used your code .. X__x.. not as bad as the cyanogen drama.. D: .. >_>..
am i making this too dramatic than it is o_o?

1726 quadrant and no sleeping death yet. Im keeping a copy of this version

[REF] Nexus S ROM&Kernel Survival Guide

Introduction:
Please read and try to do some research instead of bombarding the developers with the same questions over and over, cluttering the threads with useless and recursive information. I will try to include terms for all the ROMs and Kernels in the Development Section, and remove the obvious things as much as possible. That doesn’t mean it will be perfect! I hope this will be useful for beginners, because it provides most of the basic information you need to get started. From now on, it’s up to you what you do.
I am fully aware that the information included here is for one time use, enough to get you started. Some of these things ARE well known by many of you, but they are still useful for others that are just beginning to learn about their NS. Besides definitions and explanations, I’ll also link to useful posts around xda and other sites, which provide further information on the respective subject.
ROMs​(ROM: a firmware that contains the Android operating system, and at least critical apps necessary for running your phone (but usually more apps than just those); can be stock or custom, and comes packaged in a *.zip file, flashable under recovery)
AOSP-built ROMs
Features: these are built from source code, from the Android Open Source Project, delivered free of bloatware and with rich customizations.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyanogenMod 9 (still in alpha stages for now)
IML74K Android 4.0.3 Build 4 - Quad Lockscreen + More MODS (1/15/12)
nuhetri- v1.0.0
Slim ICS
AOSP+ V2.3|ICS 4.0.3|Source Built|Status Bar Widgets + Nice Mods
4G VERSION
vhgomez36-ICS-NXS-4G-4.0.3 r2.0
IML74K Android 4.0.3 Build 3 - Quad Lockscreen+More MODS
Crossbones v0.1.3
CyanogenMod 9 v4.0.3 - Alpha 20
Click to expand...
Click to collapse
Moddified ROMs
Features: these are modified versions of stock/AOSP ROMs/other custom ROMs, that keep the look of the base ROM up to a certain point. Also generally free of bloatware and with some additional modifications.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyberGR-MOD|NS.NGN ver. 4.0 Ultimate
NSCollab 1.0.60
Ultimate ICS v4.0
-=Nexus MV 1.12.09=-
KANGY6 | ICS | AOKP |
NexusBeam 4.2.3
CyberGR-MOD|NS.NGN ver. 3.0 Hybrid ICS
Click to expand...
Click to collapse
MIUI-style ROMs
Features: unique type of ROM, developed by the Chinese. Has a strong iOS feel, highly customizable.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
◄ ▌ [09.Jan.12] [ROM] Brainmaster's MIUI 2.1.6 ICS | Stable 2.3.7b v2 GB ▌►
DianXin OS (DX ROM) ICS | GB ROM
4G VERSION
◄ ▌ [28.Nov.11] [ROM] brainmaster's MIUI NS4G 1.11.25 | OTA ▌►
Click to expand...
Click to collapse
Stock ROM
Official releases from Google. The reasons most people here flash a stock ROM are: they want to update/ are bored of custom ROMs/ want to start over with their phone/ warranty reasons.
If you want to go back to stock for some reason, check this thread and read carefully, so you get the correct version for you.
Click to expand...
Click to collapse
Once we decide for a type or ROM (except stock), we head over to the ROMs thread and begin reading the list of features. Now would be a good time to PANIC! No, no, just kidding Those words do exist in some kind of language (not necessarily English). So here’s a very basic list of the most common terms found in our ROM threads:
Code:
[B]AOSP[/B]
[quote]Short for [url=http://source.android.com/]Android Open Source Project[/url]. Its purpose is to maintain the development
of the Android platform. Anyone can use the Android source code for
any purpose, and this is when custom ROMs come in. The [AOSP]
tag is used here to signal a ROM built from Google’s source, a pure
ROM, free of bloatware, with very good performance (generally)
and a very extended degree of customization. [/quote]
[B]Build.prop[/B]
[quote]This file is located in /system/build.prop. It holds the majority
of the runtime flags that are used when Android boots. Basically, it
lists specific information about your device, for applications to use.
You can also edit lines, with a file manager that has access to
/system, in order to change LCD density, build number, device
model and many more. [/quote]
[B]Busybox(ed)[/B]
[quote]Busybox is a collection of simple, but powerful Linux
utilities, that Android doesn't come with by default. It is used
by applications like MetaMorph and Titanium backup in order
to do special operations. You can manage ther version installed
on your phone with various apps from the [url=https://market.android.com/search?q=busybox&c=apps]market[/url] [/quote]
[B]/boot partition[/B]
[quote]This partition includes the bootloader and kernel, and
it enables the phone to boot. Wiping it must be done only if
requested, and the phone must not be rebooted after this operation.
Instalation of a new one is done by flashing a ROM that includes
the /boot partition. [/quote]
[B]/cache partition[/B]
[quote]Inside this partition, Android stores frequently accessed
data and app components. Performing a wipe of the /cache does
not affect personal settings or files, but simply gets rid of existing
data there, which gets automatically rebuilt in time. [/quote]
[B]Dalvik cache[/B]
[quote]Dalvik cache collects the information about the installed
applications and frameworks, and organizes them into a writeable
cache. Under this writeable cache, it stores the “optimized”
bytecode of the applications which is used by the applications
themselves later for a smoother operation. This dalvik cache can
grow as more applications are installed on your phone. It is safe
to wipe dalvik-cache. It will be rebuilt again when the phone
boots. This also explains why your phone takes ages to start up
for the first time. [/quote]
[B]/data partition[/B]
[quote]Also called userdata, the data partition contains the user’s
data – this is where your contacts, messages, settings and apps
that you have installed go. Wiping this partition essentially performs
a factory reset on your device, restoring it to the way it was
when you first booted it, or the way it was after the last official
or custom ROM installation. When you perform a wipe data/factory
reset from recovery, it is this partition that you are wiping. [/quote]
[B]Deodex(ed)[/B]
[quote]In Android file system, applications come in packages with
the extension .apk. These application packages, or APKs contain
certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application
that are optimized before booting. Doing so speeds up the boot
process, as it preloads part of an application. Deodexing is basically
repackaging of these APKs in a certain way, such that they are
reassembled into classes.dex files. By doing that, all pieces of an
application package are put together back in one place, thus
eliminating the worry of a modified APK conflicting with some
separate odexed parts. The advantage of deodexing is in modification possibilities. On the other hand, since the .odex files were supposed
to quickly build the dalvik cache, removing them would mean
longer initial boot times. However, this is true only for the first
ever boot after deodexing, since the cache would still get built
over time as applications are used. [/quote]
[B]EFS folder[/B]
[quote]This is a VERY important folder. It contains phone-specific
information, like IMEI (encrypted in the nv_data.bin), wireless
devices MAC addresses, product code (also in the nv_data.bin)
and more. I advise you to make a backup of this folder, and keep
it safe. Remember, backup BEFORE flashing anything. Use [url=http://forum.xda-developers.com/showthread.php?t=1138873]this tool from forum member Borky_16[/url]. [/quote]
[B]Init.d[/B]
[quote]Init.d is very useful because it runs scripts that you can
just delete or replace in the /system/etc/init.d folder. The scripts
are also very flexible and can be used to call other scripts or set
a variety of system settings. [/quote]
[B]G-apps/Gapps[/B]
[quote]A long time ago, in a galaxy far far away, there was a
developer. And he used the Force for developing something called
CyanogenMod. For the happiness of the other folks in the galaxy,
he included some applications from Google. But the Emperor…
oh, sorry… But Google didn’t agree with him including these
proprietary apps, so they sent him a cease and desist letter.
Long story short, the Google Applications are provided separately
via a flashable .zip file. This is the case for pure AOSP ROMs,
and theoretically this is how it should be done. Theoretically. [/quote]
[B]Host File[/B]
[quote]Located in the /etc/ folder, it is used to block ads.
Most ROMs come with a “blocks ~95% of ads” statement. You
can also manage it with apps from the [url=https://market.android.com/search?q=ad+block&c=apps]market[/url]. [/quote]
[B]Logcat[/B]
[quote]The Android logging system provides a mechanism for
collecting and viewing system debug output. Logs from various
applications and portions of the system are collected in a series
of circular buffers, which then can be viewed and filtered by
the logcat command. You can use logcat from an ADB shell to view
the log messages.[/quote]
[B]NANDroid[/B]
[quote]When you take NANDroid backup, it means you are
backing up entire ROM. It’s basically a picture of the ROMs’
state . So when something goes wrong, you have the
chance to restore your phone to the backup state using the NANDroid. [/quote]
[B]NSTools[/B]
[quote]An essential tool that manages tweaks like BLN,
BLD, BLX, Liveoc, OC, CPU Governor, Deep idle and so on.
Written by arifhn, available in the [url=https://market.android.com/details?id=mobi.cyann.nstools&feature=search_result#?t=W251bGwsMSwyLDEsIm1vYmkuY3lhbm4ubnN0b29scyJd]market[/url] and on [url=http://forum.xda-developers.com/showthread.php?t=1333696]xda[/url],
this is a must have application for managing these various options. [/quote]
[B]Odex[/B]
[quote]These ‘odex’ files are actually collections of parts
of an application that are optimized before booting. Also explained at deodex(ed). [/quote]
[B]Power Menu[/B]
[quote]A multiple choice menu that appears when long pressing
the power button. In stock, these are critical options,
such as powering down the device. Developers have also
added options for taking snapshots,
rebooting normally/into bootloader/into recovery and so on. [/quote]
[B]Radio[/B]
[quote]The radio controls basic low-level functions like
network connectivity, Wi-Fi, and GPS. It comes as a radio.img file,
and generally, developers try to leave this out of their
ROMs because different areas require different radios. Pay attention
to this when choosing to flash a new ROM. There is a reference
thread with all the radios [url=http://forum.xda-developers.com/showthread.php?t=1116884]HERE[/url]. [/quote]
[B]Ramdisk[/B]
[quote]Ramdisk.img is a small partition image that is mounted
read-only by the kernel at boot time. It only contains /init
and a few config files. It is used to start init, which will
mount the rest of the system images properly and run the
init procedure. A Ramdisk is a standard Linux feature. [/quote]
[B]Recovery[/B]
[quote]Recovery mode in Android provides an environment for
users to wipe cache, data, factory reset the phone or update
it with a .zip file. There are custom recoveries like [url=http://www.clockworkmod.com/rommanager]ClockworkMod[/url] or [url=http://forum.xda-developers.com/showthread.php?t=1399565]TWRP[/url], which provide additional functionality,
and are very popular for this reason. [/quote]
[B]RTL[/B]
[quote]Short for Right-to-Left and refers to support for languages requiring this type of writing. [/quote]
[B]SetCPU[/B]
[quote]An application built by coolbho3000, which allows CPU speed tweaking and management, allows overclocking, and sets CPU governors. Available on [url=http://forum.xda-developers.com/showthread.php?t=505419]xda[/url] and the [url=https://market.android.com/details?id=com.mhuang.overclocking&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5taHVhbmcub3ZlcmNsb2NraW5nIl0.]market[/url] (try to buy from the market if you want to support his work). [/quote]
[B]SIM Toolkit (STK)[/B]
[quote]Now if you live in the States, you might not even know what
the STK is, so a bit of explaining is in order. Put simply, the STK
allows carriers to load a simple set of menus and 'applications' on
your SIM card. Earlier versions of Android, up to 1.6, actually
included a rather rough, but functional Sim Toolkit application, but
at some point it was dropped. [/quote]
[B]/system Partition[/B]
[quote]This partition basically contains the entire operating system,
except the kernel and the bootloader. This includes the Android
user interface as well as all the system applications that come
pre-installed on the device. Wiping this partition will remove Android
from the device without rendering it unbootable, and you will
still be able to put the phone into recovery or bootloader mode
to install a new ROM. [/quote]
[B]Unsecured Boot.img[/B]
[quote]Used for adb remount, gets you root by default on a shell. (ro.secure=0) [/quote]
[B]V6 Supercharger Script[/B]
[quote]A more technical explanation could be done here, but
the bottom line is that this is used to make your phone run
faster, by better management of memory. [/quote]
[B]Zipaling[/B]
[quote]Zipalign is an archive alignment tool introduced first
time with 1.6 Android SDK (software development kit). It
optimizes the way an Android application package (APK) is
packaged. Doing so enables the Android operating system to
interact with the application more efficiently, and hence has
the potential to make the application and overall the whole
system much faster. Execution time is minimized for zipaligned
applications, resulting is lesser amount of RAM consumption
when running the APK. [/quote]

Kernels​
(Kernel: provides the most basic level of control over all of the phone's hardware; consider them a link between the hardware components and the ROM)
With kernels it’s a little bit easier. At least this is how it may seem. Right after rooting the device, many choose to first flash a kernel (including me) mostly because it gives the opportunity to flash something while not modifying the appearance of the phone. Furthermore, it gives you the ability to change things like CPU clock speed, internal and ARM voltages, and also have different patches and mods designed to prolong battery life/improve speed/provide stability.
Kernels are abundant for the NS, so I’ll be naming the most popular:
GLaDOS
ICUP Kernel Edition
*Matr1x*
SG-NS-ICS - 14-01-2012 - 11UV|Voodoo|BFQ|BIGMEM|BLN|BLD|BLX|TW|Lazy|3.0.15
Netarchy Nexus
NS+4G Trinity (E)UV and OC CM9 + m(any) roms
Click to expand...
Click to collapse
Many users ask around about which could be the best kernel. For this, xda member bedalus decided to set up a thread where he benchmarked ICS kernels (accurately enough). This should give you an idea where to start from.
Also, there are terms which appear frequently in the features list of kernels, so here’s a very basic list of the most common terms found in our kernel threads:
Code:
[B]BFS[/B]
[quote]A Brain F**ked Scheduler will perform better on CPU intensive
process, which usually cause them to get higher benchmark scores.
However because it only dedicates minimal CPU to background
processes you may experience lag when switching quickly between
different tasks. [/quote]
[B]BLD[/B]
[quote]Backlight Dimmer provides an option for the lights of the
touchkeys to be turned off after a certain period. This can be
tweaked from NStools. [/quote]
[B]BLN[/B]
[quote]Backlight Notification is a mod developed by neldar,
which converts the touchkey backlights into a notification led. [/quote]
[B]BLX[/B]
[quote]Battery Life eXtender, from Ezekeel, manages the maximum
percentage to which the battery is being charged. By default,
the Nexus S is charged to about 95% capacity. [/quote]
[B]CFS[/B]
[quote]A Completely Fair Scheduler is more suited for multitasking.
You may notice performance issues when using CPU heavy
activities like HD games because it is trying to keep the other
processes in the background equal to the one that is hogging the
CPU. It should also be noted that, as designed, this type of
kernel should handle going from listening to music to sending a
text to surfing the web with minimal lag. [/quote]
[B]Deep IDLE[/B]
[quote]Another mod by Ezekeel, which allows the phone to
enter a “deep idle” state while performing tasks when the screen is
off. For example, listening to music with the screen off and
Deep Idle turned on, you should get better battery life than
without Deep Idle. [/quote]
[B]Governors [/B]
[quote]There is a much to be said here, and this would stretch
this dictionary too much. I recommend reading [url=https://github.com/CyanogenMod/cm-kernel/blob/android-msm-2.6.37/Documentation/cpu-freq/governors.txt]THIS[/url], a very good explanation of
governors—from CyanogenMod. [/quote]
[B]OC (Overclock)[/B]
[quote]An overclock is usually one of the first things users
figure out after gaining root access on a new phone. If you
want to push your smartphone's CPU to run more clock cycles,
you have to know that extra power isn't coming from nowhere.
However, it is generally considered good practice, but it
depends on your handset. Some phones may be able to support
overclocking to 1.4 GHz, while others may never get past
1.2 GHz. Just proceed with caution. [/quote]
[B]Touch Wake[/B]
[quote]Yes, yes, Ezekeel again. This mod allows the user to
wake the device after a set amount of time, just by touching
the screen or the capacitive buttons. The time after which the
screen no longer responds to a touch is set with NStools. [/quote]
[B]UV (Undervolt)[/B]
[quote]This refers to lowering the voltage to conserve power while
still achieving the same performance, assuming your settings
remain stable. Both SetCPU and NStools allow the user to change
voltages. Like overclocking, this is also a trial and error process,
because each phone is different. The benefits are low energy
consumption and less thermal output. [/quote]

Tools & Mods​
So you have a rooted phone. Maybe even a custom Kernel or ROM, whatever works for you. But you still want to be a tad different from the other guys using the same configuration as yours. So here's a small selection of mods and apps developed by members of the community, enough to get you started. Feel free to experiment, and remember: read before flashing, search before asking and you should be alright!
Mods for AOSP+ Rom
[BOOTANIMATION] Plain, Simple & Colorful + color variants
Nova Launcher
Flavours for stock OTA ICS 4.0.3
Search key to ICS recent apps [add CM9 version]
[NS][NS4G]FaceLock for ICS 4.0.3
Enable on-screen buttons in ICS roms
Click to expand...
Click to collapse
NOTES:
I am hoping this little survival guide is useful FOR BEGINNERS in understanding the basic terminology used here in the Nexus S sections. As the title suggests, it was made with beginners in mind, so I don’t want posts of so called “experts” saying how they already knew this.
IMPORTANT: I do NOT guarantee the explanations written here are completely accurate or complete, FOR NOW. I will keep working on this, correcting mistakes as I continue to read.
If you find something that you think is not correct, or consider something must be added, please post here, together with a link to a credible source.
All of this came from sources off the internet, so please bear with me. Also, sorry for any typing mistakes. If you see any, please be sure to signal them
If I have helped you in any way, or if you appreciate the work invested in this (now and for the future), press the THANKS button.
Thank you! (Hoping to see this stick) And many thanks to all the great devs working on ROMs and Kernels for us. Keep up the great work!
W O R K - I N - P R O G R E S S
(I will be sure to notify you when I believe this is complete)​

Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk

ljordan2 said:
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Thank you! I'm just worried it is a little bit long... but in the next couple of days I will be making it more reader friendly
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.

nice thread! thanks

Hey great post, i still haven't rooted my nexus s but you just made me flash a kernal. I was tkinking about it but never too serious.
thanks!

Love it!!! Cleared so much up (you recieved my first Thanks button click!)
Just wanted to clarify something about the Kernel. My Rom is stock 2.3.6 that was received OTA when I unboxed the phone (Nexus S GSM i9020A, I'm in Canada). The bootloader is unlocked, phone rooted with CWM recovery via one click (QBKing's Video). Am I able to flash a custom Kernel to a stock Rom? Reading the above seems to lean towards the "yes", but wanted to make sure first.
Also, do not use the one click method on the Nexus S GSM if you want to easily return to stock. The one click stock only supports the 4G, which is extremely silly and inconvenient IMO. I'm currently still trying to figure out how to return to stock, incase something does happen and the phone needs warranty work. Let's just say, I'm not making much progress and this is extremely uncomfortable ATM..

Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.

Thanks so much for taking the time to do this
Sent from my Nexus S using XDA App

Harbb said:
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Click to expand...
Click to collapse
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.

very useful for us newbie, thanks for sharing

heX79 said:
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
Click to expand...
Click to collapse
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...

great post OP

Nice thread! Great Work ,Thanks

Hey thanks! Happy to see good feedback on this.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.

Great beginners guide, and thanks for the link!
For kernel benchmarks and more, see here: http://goo.gl/mpeHI

Thanks very much! I will give it a try shortly, just to confirm if I recieve any issues. I've also installed the recommended CWM version for my model, not sure if it makes a difference, but I flashed 5.0.2.0 anyway as the version I was getting an error with had a higher build number.
Right now I'm enjoying AndroidME 1.2.3 with Speedy 6 kernel and have no complaints so far! (Kernel updated this morning from Speedy 5)
I will report back with any issues once I have some time to do a Nandroid backup and test the stock Rom.
Thanks for your help!
It's nice to know there's a way to revert back to stock, should anything need servicing! I've also started reading up on Odin
flodb113 said:
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
Click to expand...
Click to collapse

You're welcome! Looking forward to an update with your stock flashing situation. I also used ClockworkMod 5.0.2.0 a long time. I'm now on 5.0.2.3 only for the better menu layout.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.

just one question...
can i install more than one kernel at a time...
for eg.like one i installed for battery usage and othr for sound..
can i do tht

Google Wallet working for I-9300 in US

Hey guys, I just got GW working for my unlocked and rooted SGS3 i9300 by combining the how-to from GW for US variants (HERE) and MoDaCo latest patched GW (HERE). So here are the steps (obviously your phone has to be rooted and is using TW; not sure about other roms; I'm using the latest JB leak LI8):
1. Nandroid backup
2. Using Root Explorer (ES will not work as reported from other source), modify the /system/build.prop:
LOOK FOR THESE LINES:​
Code:
ro.build.model=GT-I9300
ro.product.name=m0xx
ro.product.device=m0
TO​
Code:
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
Then save it. RE will automatically backup the old one as build.prop.bak.
3. Download the latest GW from HERE to sd card
4. Move the GW.apk to system/app
5. Restart the phone
6. Start GW, sign in, add your cards, etc
7. Back to RE, delete the new build.prop, and then change the old build.prop.bak to build.prop, so S-voice can work properly (or else you'll get network error)
8. Restart the phone again
9. Enjoy your GW at 711 or elsewhere (I had it work at 711)
10. Another nandroid backup would be useful
11. Don't restore this GW by Titanium Backup whenever installing a new TW-based rom. Instead, reset (in-app setting) and delete GW from the phone. Flash a TW rom, then follow the steps again.
PS: I assume most of you know how to work with RE and nandroid; you can search xda for instructions.
Disclaimer: I'm not sure if this method works with other JB leaks, ICS, or other custom roms (don't mention CM, since it's another whole world )
Credit: ogdobber (GW for US variants), PaulOBrien (Patched GW)

No replies? Wow.
Thanks for posting this. I'm running the latest Wanamlite ROM, which is based on Touchwiz JB. I know that one of the modifications is a "modified build.prop" file for increased market compatibility. Do you think that it not being 100% stock ROM will prevent me from trying this?

Maybe because there's similar thread in themes and apps section.
And I think its even older than oggdober thread and op has been the first to figure out HTC_jewel thingy.
Sure it dealt with UK customers in the title, but the rest is identical. Then they blacklisted us (the test of the world) and we stopped caring.
All said it does not mean in its current form it is not usefull for us customers (only).
Testing JKay alpha on GT-I9300

got this set up yesterday but haven't had a chance to test it out yet at a store.

I have done the procedure similar to this with my S2 so I figured this shouldnt be that hard. Well I follow the Instructions and it gets all set up however when i got o add my debit card it says "Request Failed, Please try again" and no mat7ter how many times i try to do it it still wont go through. Any ideas as to why?