Database Users

[HOWTO] Universal CSC & recover product code [ANY ROM] (I5801 supported)

As you should have noted I'm not supporting this topic anymore. Nowadays most ROMs have this integrated, you only have to change to your CSC of choice in case of need.
(My links were from "pre-Megaupload BOOM" era, so... Not really uploading them again as they aren't needed!)
Before anything, I hope you have an /efs folder backup, you should have done it even before flashing!
NOTICE: This method does a reset, your SGS only maintains your personal files (sdcard & external sdcard). I'm not responsible at all for any problem that you get for following this procedure.
This procedure must bee done after flashing and before installing "anything" ("only" root and a program like Root Explorer are allowed ). If you do this after you'll likely have problems!
You need root access so this can work! You may do this with commands via ADB or terminal, or else in a easy way with a program like Root Explorer (notice this is a paid app).
NOTICE: It seems this process, as it uses older CSC versions, disables the "voice input abilities", you may have to reinstall "voice apks" (if you use them...). I will confirm this today or during this weekend. (this issue was related to a problem on the French CSC)
MANUAL METHOD:
First, get the right folder for your country (available at the bottom of this topic or else ask me) and copy it to /system/csc.*
After, open an ADB shell, and use the following command:
Code:
am start -a android.intent.action.MAIN -n com.android.Preconfig/com.android.Preconfig.Preconfig
After this, select on your SGS, your CSC country code. Then it'll reboot, you'll have to do the initial configuration, and it's done!
"AUTOMATIC" METHOD (firmwares dated to september (or newer)): (Thanks for Richthofen, for this info!)
First, get the right folder for your country (available at the bottom of this topic or else ask me) and copy it to /system/csc.*
After, check your IMEI with this code on the dialer, *#06#, and save it as you'll need.
Then, type on the dialer, *#272*???????????????# (??????????????? it's your IMEI, it must have 15 digits), after you can chose your CSC, then it'll reboot (it may take some time, you'll see bootloader applying the changes), you'll have to do the initial configuration and it's done!
For your country you'll need a specific folder. If you don't find it were, give me an CSC file for your country (any firmware version, I just need the file "cache.rfs" or the "CSC_I9000------.tar.md5") and I will make the folder for your country available.
* If you're on JPK (probably on every new version of Froyo), you'll need the following commands to be able to copy the CSC folder to the /system/csc.
Code:
adb shell
su
busybox mount -o remount,rw /system
This process is fully functional, it changes your CSC and recover your original product code! (to have your product code recovered your nv_data.bak should be compatible with the CSC you apply)
PS: You can check your product code with SGS ToolBox.
PS2: I did some search and didn't see this method posted were on XDA. If I'm wrong, sorry!
Universal CSC Pack said:
EXPERIMENTAL (Tested on I9000 with JPA, but it should work on all ROMs)
Download the pack, put it on sdcard, go to ClockworkMod Recovery mode, choose "install zip from sdcard" and install the pack. Then reboot and follow steps 2 and 3 of "Automatic method" explained above! (check your CSC code on the list bellow)
I've to test this some more time and I also expect some feedback from you After that I'll turn this pack the most "universal" possible.
Thanks to on.one on the info on this process.
Click to expand...
Click to collapse
OPS - Australia (YES OPTUS)
VAU - Australia (Vodafone) BRANDED
XSA - Australia (Telstra, YES OPTUS, Vodafone AU, Virgin Mobile, 3, Crazy Johns)
HUT - Australia (3) BRANDED
ATO - Austria
SEB - Baltic (LMT GSM, LV TELE2, LV BITE, LT Omnitel, LT Bite, LT TELE2, EE EMT, EE ELISA, EE TELE2)
ETR - Bangladesh
TML - Bangladesh (TML and ETR seem equal, same version, same network operators)
PRO - Belgium
VVT - Bulgaria (vivacom)
MTL - Bulgaria (MTEL)
BMC - Canada (Bell)
BWA - Canada (SaskTel)
BMF - Canada (Fido) UNBRANDED [provided by Idan73, not checked by me]
XEZ - Czech Republic
VIP - Croatia (HR VIP)
SFR - France (F SFR, SFR RU) BRANDED
XEF - France
DBT - Germany
CYO - Greece (MTN, CYTAVODA)
EUR - Greece (WIND GR, vodafone GR, COSMOTE)
TGY - Hong Kong [provided by rickylcp, not checked by me]
INS - India (CSCEdition > ED006)
INU - India (CSCEdition > ED009 | I think INU is an updated version of INS, as they seem to have the same network operators)
XSE - Indonesia
MET - Ireland (Meteor)
ITV - Italy [UPDATED 02/11]
XME - Malaysia
NPL - Nepal
XEE - Nordic (Denmark, Finland, Iceland, Norway, Sweden)
XTC - Philippines
XEO - Poland (Plus, Era, Heyah, Orange, Play)
ERA - Poland (ERA) BRANDED
TPH - Portugal
CNX - Romania (Vodafone RO)
COA - Romania (Cosmote)
ORO - Romania (RO Orange)
HAT - Romania (RO Orange, Vodafone RO, Cosmote)
SER - Russia (MTS, Beeline, Megafon, TELE2)
TOP - Serbia
XSP - Singapore
XSP - Singapore UNBRANDED
XSO - Singapore (Singtel)
MOT - Slovenia (Mobitel)
SIM - Slovenia (Si.mobil)
XEC - Spain (Movistar) BRANDED
FOP - Spain (Movistar, Vodafone ES, Orange, Yoigo, Mobil R, EUSKALTEL, TeleCable, Blau, Simyo)
SLK - Sri Lanka
AUT - Switzerland (Sunrise, Swisscom, Orange CH)
MOZ - Switzerland (Sunrise, Swisscom, Orange CH)
SWC - Switzerland (Swisscom) BRANDED
CPW - United Kingdom & Ireland
XEU - United Kingdom & Ireland
This process also works on the I5801, thanks to gazski!
I5801 said:
Hello mate,
I managed to change the csc on my GT-i5801.
I have the firmware I5800XWJH2 and is rooted.
I had to plug my external sd card into my laptop, i then downloaded the CPW csc and then transfered the zipped file to my sd card, i then unzipped the file in the sd card.
I put the card back into the phone then used ROOT EXPLOYER and changed the permissions of the file to READ, WRITE, EXECUTE... i then followed your instructions on your thread and it worked..yippee
You are more than welcome to use this explanation.
Thanks for all your help and i hope you understand my explanation
Regards
Gary
Click to expand...
Click to collapse

I already mentioned this, but its good to have in a separate thread , here is the old post
http://forum.xda-developers.com/showpost.php?p=8184498&postcount=74
-Pramod

Now aside from perhaps entering automatically any APN settings to your phone, rather than doing it manually.
What actual advantage is there to change/select the correct CSC? I've flashed JM7 and JM8 and I never changed the product code, which I think puts you on KOR as the default, and never encountered any noticeable advantage or disadvantage in running the phone as such.
All I had to do was to enter "internet" under APN and my 3G connection was restored.
Is there anything to gain by choosing the right CSC for your provider/country?

Have a look at the csc files, there are application specific to the Country/Region too, some settings are also there for region, mostly the GSM 3G frequency is also set from the CSC setting, even the GPS settings are also there.
These files are not jsut operator and APN they are more than that!!
-Pramod

bloodrider said:
I upgraded to JPH and for my country there isn't a ROM available with Multi-CSC, for the moment...
NOTICE: This method does a reset, your SGS only maintains your personal files (sdcard & external sdcard). I'm not responsible at all for any problem that you get for following this procedure.
So I needed an alternative method and after some research and guessing, here it is:
Get the right folder for your country (Portugal) and copy it to /system/csc.
After, open an ADB shell, and use the following command:
Code:
am start -a android.intent.action.MAIN -n com.android.Preconfig/com.android.Preconfig.Preconfig
After this, select on your SGS, your CSC country code. Then it'll reboot, you'll have to do the initial configuration, and it's done!
In these procedure the folder that I use it's for Portugal (TPH CSC). For other countries you'll need other specific folder. If you need it, give me an CSC file for your country (any firmware version, I just need the file "cache.rfs") and I will make the folder for your country available.
This changed my sale code, that was my goal, as a bonus it changed also my product code, but notice that my .nv_data.bak was the older one with the right product code.
PS: I did some search and didn't see these method posted were on XDA. If I'm wrong, sorry!
Click to expand...
Click to collapse
I have a I9000T which is equal to I9000M
And if you are not a nuisance
I wanted to ask if you can make the folder BMC
Link CSC
http://www.multiupload.com/O3FSEGLHT5
Thank you very much for your great work

pramods said:
Have a look at the csc files, there are application specific to the Country/Region too, some settings are also there for region, mostly the GSM 3G frequency is also set from the CSC setting, even the GPS settings are also there.
These files are not jsut operator and APN they are more than that!!
-Pramod
Click to expand...
Click to collapse
so is there any noticable difference by choosing a CSC designated for your region/telco? signal strength and GPS tracking in particular.
'cause froyo is (HOPEFULLY) 3 days away and y'know. lazy to reconfigure stuff all over again. lol. thanks!

pramods said:
Have a look at the csc files, there are application specific to the Country/Region too, some settings are also there for region, mostly the GSM 3G frequency is also set from the CSC setting, even the GPS settings are also there.
These files are not jsut operator and APN they are more than that!!
-Pramod
Click to expand...
Click to collapse
I'll give it a whirl I guess, but I haven't noticed any 'disadvantages' by not using the specific CSC for my provider/region.

criskelo said:
I have a I9000T which is equal to I9000M
And if you are not a nuisance
I wanted to ask if you can make the folder BMC
Link CSC
http://www.multiupload.com/O3FSEGLHT5
Thank you very much for your great work
Click to expand...
Click to collapse
No problem, just give me some time

If you have a wrong product code, you won't have the correct firmware via Kies.
For the sale code, it depends on the country, some may not have many information to configure. But it's as pramods said, and it also configure your language, your GMT, SOS numbers, specific aplications for your country or mobile operator,...
For example, if I'm not mistake the Bell SGS are from Canada, right? If you upgrade them to JPC or JPH it seems they may not work well cause they need a frequency adjust, automatically available on CSC

I agree that this method changes Sales code, but I'm quite sure that it does not change your Product code, because I've tried several times. For example yesterday I flased JPH which totally screwed up my .nv_data.bak files (hopefully I have them on my PC), then I went back to JM8 which is a lot better firmware. I had to change my Product code by myself, overwriting my .bak files with the original ones, and deleting nv_data.bin files Even when I had my original .bak files, your method via adb shell didn't change my Product code only Sales code

criskelo, there you have your CSC folders. I made for the two mobile operators. The Sasktell CSC didn't have the apps, as they seem equal to the Bell apps, I ad them to the Sasktell CSC.
The CSC file you provided me seemed modified, so I may overlooked something, warn me if there's any problem
STATUS: Canada added

celeronix said:
I agree that this method changes Sales code, but I'm quite sure that it does not change your Product code, because I've tried several times. For example yesterday I flased JPH which totally screwed up my .nv_data.bak files (hopefully I have them on my PC), then I went back to JM8 which is a lot better firmware. I had to change my Product code by myself, overwriting my .bak files with the original ones, and deleting nv_data.bin files Even when I had my original .bak files, your method via adb shell didn't change my Product code only Sales code
Click to expand...
Click to collapse
I have a Portuguese friend that used my method and he said that everything went OK...
I'm thinking the only different thing I did was editing the mps_code.dat, but I though it didn't had interfered/helped in the process.
I will ad this as a first step, it won't do any warm, that way someone who tries can tell us if that step is really needed.

bloodrider said:
I have a Portuguese friend that used my method and he said that everything went OK...
I'm thinking the only different thing I did was editing the mps_code.dat, but I though it didn't had interfered/helped in the process.
I will ad this as a first step, it won't do any warm, that way someone who tries can tell us if that step is really needed.
Click to expand...
Click to collapse
Probably it's gonna work that way - with editing mps_code.dat, otherwise it won't change your Product code, because it does not interfere with nv_data.bin files in any way

celeronix said:
Probably it's gonna work that way - with editing mps_code.dat, otherwise it won't change your Product code, because it does not interfere with nv_data.bin files in any way
Click to expand...
Click to collapse
Editing the mps_code.dat will change the nv_data.bin too?
My nv_data.bin was KOR and after this CSC process it changed back to the original.
The system after the change on mps_code.dat needs a reboot to alter the nv_data.bin? As it's strange I though it was this CSC procedure that corrected the issue.

Thank you very much
I'll test as soon as the method
then comment

bloodrider said:
Editing the mps_code.dat will change the nv_data.bin too?
My nv_data.bin was KOR and after this CSC process it changed back to the original.
The system after the change on mps_code.dat needs a reboot to alter the nv_data.bin? As it's strange I though it was this CSC procedure that corrected the issue.
Click to expand...
Click to collapse
No, I'm not sure about this at all I'm sure for one thing - CSC procedure can't change nv_data.bin It may read some data from this file, but it surely doesn't write anything in it.

STATUS: Bulgaria added

I need Colombia added. Where do I find the file?
Sent from my GT-I9000 using XDA App

You need to find a I9000UR--- ROM or else if you still have your original ROM check the folders that you have on /system/csc.

STATUS: Romania added

[GUIDE] My Bell Canada flashing/rooting procedure

Update: I upgraded my phone with XXKI3 2.3.5 firmware, from XXKH3.
The lag is gone, definitely a big improvement compared to XXKH3 version. The phone is very responsive and fast. Quadrant shows 4200+, pretty impressive:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The bootloader was updated, you cannot reset anymore your phone with a download jig. However, Intratech uploaded the old bootloader:
Intratech said:
If you've already flashed a full package from elsewhere and cannot reset your binary counter using the Jig just flash this package in the PDA or Bootloader (Yes both will work) section of Odin to replace the bootloaders and then you can reset the counter: http://www.multiupload.com/LQQBRQVJUD
Click to expand...
Click to collapse
Personally, I flashed the file with Odin (PDA).
The phone ring is set to silent, instead of default "Over the horizon" ringtone. Make sure you change it, your phone is not broken. See the complete list of changes, related to previous ROM.
Guide
I'm posting this procedure in a separate thread, as is easier to be linked into different forum posts. My Bell Canada phone came originally with the UGKG2 firmware, so everything listed below is based on my own experience with this version, I do not know or confirm it will work with other firmware. I currently run the official (?) XXKI3 Gingerbread 2.3.5 firmware, downloaded from samfirmware.com site (see details below). This is a wipe device release.
Personally, I read that other people flashed their phones with a different firmware... but I did not wanted to do it on my phone. I sticked with the same family XXKGx, just to be safe. Please read Electroz's explanation below.
There are 3 types of release builds: leaked, Frankenstein (compiled and tested by devs, based on demand) and official (Kies updates).
The procedure is simple (I presume you are familiar with Odin, Download Mode &Co.):
1) Get yourself the stock firmware and kernel (thank you Intratech)
2) Setup your drivers properly, avoid the Kies insanity (see below)
3) Flash the new firmware (my flash procedure, you can/should skip Re-Partition/PIT as Intratech explained)
4) Flash phone with CF-Root (I used the CF-Root-SGS2_XX_OXA_KI3-v4.1-CWM4.zip file)
5) Wipe (cache + factory reset)
6) Uninstall all Samsung crap and install additional system apps (i.e. Car Home)
7) Flash back the stock KI3 kernel (thank you Intratech, password: [email protected])
8) Wipe (cache + factory reset)
9) Connect your device to a download jig, to reset the flash counter (old bootloader needed)
Phone & Modem Drivers Setup
Note: This procedure was tested with Windows 7 Ultimate 64bits. If you already installed Kies, uninstall all related software/drivers and clean your registry. Or do a clean Windows install just to be safe.
1) With your anti-virus off, put your phone in Download mode and connect the USB cable. Windows Update will start to download right away the modem and USB drivers. Make sure you select the Windows Update option, when asked into driver install window.
2) Once the modem drivers installed, disconnect the cable, reboot the phone in normal mode and reconnect the cable again. A new set of drivers will be installed for the rest of USB interface.
Important: You need do it in the SPECIFIC order mentioned above, or else the modem drivers will not be installed and you will not be able to use properly Odin. I know this because I tried the other way around.
Initial Phone Setup
Once the phone rebooted, you will be welcomed to the Android Setup.
1) First, set the language from English UK to whatever you like.
A Network warning related to Date and Time will pop, tap on Cancel.
2) Tap the Android robot and setup your phone.
There is NO need to change any other settings, the phone will automatically detect the Bell network.
If for some reason it does not, once you completed your basic setup go to:
Settings > Wireless and Network > Mobile networks > Network operators
It will start the scanning and pop 3 Bell networks, pick the first one. Again, this is in case your phone does not work with calls, voicemail or SMS.
Notes
You should uninstall the CWM app once you flashed back the stock kernel, is half useless. I tested the new Superuser app from Android Market, it will properly upgrade to latest version and also upgrade the su binary on XXKI3 firmware. If you plan to poke around your phone with the Terminal, you will lose all the fancy Linux commands. (grep etc.)
Personally, I purchased ChainsDD's Superuser Elite key. It will allow you to pin protect your rooted device, among other useful things that are planned to be added (built-in terminal). I upgraded Superuser to version 3 and everything works properly.
Battery Power Savings
I always leave my phone with all default options, including screen auto-adjust. The only options I turn off are:
Settings > About phone > Software update > Auto update Disabled
Settings > Applications > Samsung Apps > Off
Personally, I have no idea who started the battery calibration myth in S2. It is useless to "overcharge" the battery, as the software has a check to stop automatically the charge once the battery is 100% while the battery itself has a build-in controller that can't be wiped.
Example of battery stats with the phone in idle mode for approx. 18hrs (86%) and 109hrs (2%):
Running Services
I use Wifi N with a Cisco E4200 DD-WRT (phone at 20"), these are my running services:
Code:
PID USER VSZ STAT COMMAND
1 root 508 S /init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [migration/0]
5 root 0 SW [watchdog/0]
9 root 0 SW [events/0]
11 root 0 SW [khelper]
15 root 0 SW [async/mgr]
16 root 0 SW [pm]
19 root 0 SW [suspend]
20 root 0 SW [sync_system_wor]
151 root 0 SW [s5p-tmu]
337 root 0 SW [sync_supers]
339 root 0 SW [bdi-default]
341 root 0 SW [kblockd/0]
356 root 0 SW [khubd]
359 root 0 SW [kseriod]
394 root 0 SW [irq/331-max8997]
434 root 0 SW [kmmcd]
527 root 0 SW [kondemand/0]
540 root 0 SW [pet_watchdog/0]
549 root 0 SW [khungtaskd]
550 root 0 SW [kswapd0]
599 root 0 SW [aio/0]
612 root 0 SW [crypto/0]
1237 root 0 SW [sec_jack_wq]
1240 root 0 SW [irq/350-sec_hea]
1245 root 0 SW [spi_gpio.3]
1262 root 0 SW [svnet_txq]
1274 root 0 SW [file-storage]
1300 root 0 SW [irq/328-mxt224_]
1306 root 0 SW [irq/325-k3g]
1312 root 0 SW [irq/326-proximi]
1315 root 0 SW [cm3663_light_wq]
1316 root 0 SW [cm3663_prox_wq]
1366 root 0 SW [mali_dvfs]
1369 root 0 SW [mali-pmm-wq]
1378 root 0 SW [sii9234_wq]
1379 root 0 SW [irq/481-mhl_int]
1380 root 0 SW [irq/496-mhl_wak]
1383 root 0 SW [irq/343-max1704]
1394 root 0 SW [kstriped]
1396 root 0 SW [kmpathd/0]
1398 root 0 SW [kmpath_handlerd]
1399 root 0 SW [ksnapd]
1400 root 0 SW [kconservative/0]
1414 root 0 SW [ktflash_requlat]
1429 root 0 SW [usbhid_resumer]
1432 root 0 SW [binder]
1441 root 0 SW [irq/333-IPC_HOS]
1452 root 0 SW [mmcqd]
1481 root 0 SW [l2cap]
1482 root 0 SW< [krfcommd]
1488 root 0 SW [dynamic hotplug]
1501 root 0 SW [melfas_touchkey]
1506 root 0 SW [fimc0_iqr_wq_na]
1509 root 0 SW [fimc1_iqr_wq_na]
1512 root 0 SW [fimc2_iqr_wq_na]
1515 root 0 SW [fimc3_iqr_wq_na]
1518 root 0 SW [hdcp work]
1529 root 0 SW [tvout resume wo]
1535 root 0 SW [sec-battery]
1538 root 384 S /sbin/ueventd
1761 root 0 SW [Si4709_wq]
1782 root 0 SW [jbd2/mmcblk0p9-]
1784 root 0 SW [ext4-dio-unwrit]
2563 root 0 SW [jbd2/mmcblk0p7-]
2564 root 0 SW [ext4-dio-unwrit]
2566 root 0 SW [jbd2/mmcblk0p1-]
2567 root 0 SW [ext4-dio-unwrit]
2570 root 0 SW [jbd2/mmcblk0p10]
2571 root 0 SW [ext4-dio-unwrit]
2579 system 868 S /system/bin/servicemanager
2580 root 6616 S /system/bin/vold
2581 system 1972 S /system/bin/notified_event
2583 root 732 S /system/bin/debuggerd
2584 radio 9512 S /system/bin/rild
2585 system 4624 S /system/bin/npsmobex
2586 system 8476 S /system/bin/drexe
2590 bluetoot 1372 S /system/bin/dbus-daemon --system --nofork
2591 root 932 S /system/bin/installd
2592 keystore 1804 S /system/bin/keystore /data/misc/keystore
2594 system 14192 S /system/bin/tvoutserver
2595 shell 800 S /system/bin/sh /system/bin/rtc_log.sh
2612 shell 780 S /system/bin/immvibed
2907 wifi 2644 S /system/bin/wpa_supplicant -Dwext -ieth0 -c/data/wifi/bcm_su
3374 media 56536 S < /system/bin/mediaserver
3375 root 15472 S /system/bin/netd
3376 root 126m S zygote /bin/app_process -Xzygote /system/bin --zygote --star
3391 system 276m S system_server
3496 root 0 SW [iscan_sysioc]
3497 root 0 SW [dhd_watchdog]
3498 root 0 SW [dhd_dpc]
3499 root 0 SW [dhd_sysioc]
3502 system 152m S com.android.systemui
3511 app_99 168m S com.sec.android.inputmethod.axt9
3521 radio 155m S com.android.phone
3522 app_66 148m S android.process.media
3528 app_53 134m S com.sec.pcw.device
3532 system 134m S com.samsung.bt.avrcp
3536 bluetoot 134m S com.broadcom.bt.app.system
3544 app_12 176m S com.sec.android.app.twlauncher
3604 app_54 173m S com.google.process.gapps
3631 app_12 148m S android.process.acore
3688 app_84 135m S com.sec.android.app.FileTransferManager
3777 app_36 137m S com.sec.android.widgetapp.weatherclock
3927 app_38 136m S com.sec.android.widgetapp.apnews
4193 app_91 137m S com.sec.android.app.clockpackage
4220 app_16 137m S com.android.providers.calendar
4234 app_100 134m S com.sec.android.daemonapp.accuweather
4255 app_78 159m S com.google.android.gm
4333 app_81 174m S com.cooliris.media
4366 app_119 144m S com.google.android.apps.reader
4376 app_103 170m S com.levelup.beautifulwidgets
4435 app_37 138m S com.sec.android.widgetapp.stockclock
4453 app_16 138m S com.android.calendar
4476 system 156m S com.android.settings
4486 app_112 177m S com.google.android.music
4633 app_82 137m S com.sec.android.app.fm
4752 app_40 135m S com.sec.android.app.samsungapps.una
6623 app_68 185m S < com.google.android.apps.maps
9014 dhcp 916 S /system/bin/dhcpcd -ABK eth0
10732 graphics 139m S com.sec.android.app.screencapture
11958 system 138m S com.wssyncmldm
11989 system 135m S com.sec.android.providers.drm
11997 app_1 139m S com.smlds
12037 app_102 139m S com.skype.raider
13094 app_5 141m S jackpal.androidterm
13136 app_115 135m S com.noshufou.android.su
13170 app_68 149m S com.google.android.apps.maps:NetworkLocationService
13180 app_68 144m S com.google.android.apps.maps:FriendService
13503 app_83 141m S com.sec.android.app.FileTransferServer
13579 root 0 SW [flush-179:0]
13646 shell 1684 S /sbin/ext/busybox sh /sbin/sleep 3600
13651 shell 1676 S /sbin/ext/busybox /sbin/sleep 3600
13707 app_68 154m S com.google.android.apps.maps:HotpotService
13788 system 135m S com.android.MtpApplication
13825 app_5 796 S /system/bin/sh -
13858 root 796 S sh -
13966 root 1684 S /sbin/ext/busybox sh /sbin/ps
13971 root 1716 R /sbin/ext/busybox /sbin/ps
CSC (Cell Site Controller)
The default CSC setting in XXKI3 is KOR. You can check it with: *#272*{IMEI}#
where the {IMEI} value represents the 15 digits of your IMEI (International Mobile Equipment Identity).
I personally used the default option (KOR) and the phone works perfect, with great reception:
There are some people who wonder if they should change the CSC. I will quote Intratech on this matter as he answered perfectly to my question:
Intratech said:
Some people do and some just use the CSC packaged with whichever firmware they flash. As long as your APN and SMS/MMS settings are ok there is no need to flash another CSC package.
Click to expand...
Click to collapse
Fast Dormancy
Some people noticed that their network idle on 3G, instead of HSPA+. That is absolutely normal, because of the "fast dormancy" feature. If enabled, HSPA+ will rapidly disconnect from the network once the information is sent or received. That will penalize the actual network you are on, unless the carrier network and your phone talk to each other in a way that takes battery life as well as network congestion into consideration. For this to work, both networks and smartphones have to implement a standardized version of the fast dormancy feature. Bell Canada supports this feature and by default Fast Dormancy is enabled into XXKI3 firmware.
You can check it with: *#9900#
You should call your carrier to see if they have it implemented. Probably your tech support will look like you are speaking Chinese and escalate it to a more knowledgeable guy. This is the average download speed I get on XXKI3 (network is switching automatically on HSPA+):
There are some reports where people confirmed that the UGKG2 build allowed you to reach faster download speeds (up to 9MB). Personally I think 6MB over a cell network is already more than perfect for tethering, not to mention that there are many factors to be taken into consideration when you deal with a wireless transmission. (location, tower antenna, weather, etc.)
Random Restart
The screen needs minimum 500Mhz to get out of Sleep Mode. Some custom ROM's use a low voltage or "underclock" feature that reduces the power consumption but also the number of CPU steps. That is what makes your phone crash and reboot randomly. If you use an external sdcard, do a sd wipe just to be safe. It should take several hours, so do it over the night. Personally, I did not experienced any random reboots using neither the XXKH3 or XXKI3 firmware.
Some people might have bad battery contacts on their S2. Basically, the phone shuts down while in your pocket. Clean the battery terminals with some audio head tape cleaner and cotton swabs, than make sure the contacts are proper.
You could also have a RAM (hardware) issue. Bad memory degrades fast so you will see your random reboots pop at a faster frequency. If you did all the above and still experience random reboots, run adb logcat to see what is going on at that specific moment. If you get error codes like:
Code:
code 1 (SEGV_MAPERR), fault addr 00000000
you are dealing with bad memory unfortunately and need to service your phone.
Manage system apps with Terminal
Personally, I decided to stick with a terminal for now, I feel more comfortable to see what is going on with my own eyes in my phone. A good alternative to Terminal would be the SystemApp Remover, is faster and more robust compared to Titanium Backup as it does only one task (backup/remove system apps).
I did an output list of all the packages:
Code:
$ pm list packages -f >> /sdcard/packages 2>&1
so I know now where each package is located and what is the associated name.
All I have to do is run:
Code:
$ su
# rm -f /system/app/package.{apk,odex}
# pm clear PACKAGE
# pm uninstall PACKAGE
Running "mount | grep system" tells me right away where and how /system is mounted:
Code:
/dev/block/mmcblk0p9 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
so all I have to do is change the mount perms to write, instead of read:
Code:
# mount -o remount,rw /dev/block/mmcblk0p9 /system
Package Manager commands:
Code:
# pm
usage: pm [list|path|install|uninstall]
pm list packages [-f] [-d] [-e] [-u] [FILTER]
pm list permission-groups
pm list permissions [-g] [-f] [-d] [-u] [GROUP]
pm list instrumentation [-f] [TARGET-PACKAGE]
pm list features
pm list libraries
pm path PACKAGE
pm install [-l] [-r] [-t] [-i INSTALLER_PACKAGE_NAME] [-s] [-f] PATH
pm uninstall [-k] PACKAGE
pm clear PACKAGE
pm enable PACKAGE_OR_COMPONENT
pm disable PACKAGE_OR_COMPONENT
pm setInstallLocation [0/auto] [1/internal] [2/external]
The list packages command prints all packages, optionally only
those whose package name contains the text in FILTER. Options:
-f: see their associated file.
-d: filter to include disbled packages.
-e: filter to include enabled packages.
-u: also include uninstalled packages.
The list permission-groups command prints all known
permission groups.
The list permissions command prints all known
permissions, optionally only those in GROUP. Options:
-g: organize by group.
-f: print all information.
-s: short summary.
-d: only list dangerous permissions.
-u: list only the permissions users will see.
The list instrumentation command prints all instrumentations,
or only those that target a specified package. Options:
-f: see their associated file.
The list features command prints all features of the system.
The path command prints the path to the .apk of a package.
The install command installs a package to the system. Options:
-l: install the package with FORWARD_LOCK.
-r: reinstall an exisiting app, keeping its data.
-t: allow test .apks to be installed.
-i: specify the installer package name.
-s: install package on sdcard.
-f: install package on internal flash.
The uninstall command removes a package from the system. Options:
-k: keep the data and cache directories around.
after the package removal.
The clear command deletes all data associated with a package.
The enable and disable commands change the enabled state of
a given package or component (written as "package/class").
The getInstallLocation command gets the current install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
The setInstallLocation command changes the default install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
Removed System Apps
This is the list of /system apps I removed from XXKI3 firmware:
BuddiesNow.apk
Days.apk
DigitalClock.apk (I use Beautiful Widgets instead)
Email.apk (I use Gmail only)
EmailWidget.apk
GameHub.apk
GenieWidget.apk
install_flash_player.apk
Kies.apk
KiesAir.apk
kieswifi.apk
Kobo.apk
MiniDiary.apk
MusicHub_U1.apk
MusicPlayer.apk (I use Google Music instead)
PolarisOffice.apk
PressReader.apk
ReadersHub.apk
SamsungApps.apk
SamsungAppsUNA3.apk
SamsungIM.apk
SecretWallpaper1.apk
SecretWallpaper2.apk
SevenEngine.apk
ShareApp.apk
SnsAccountFb.apk
SnsAccountLi.apk
SnsAccountMy.apk
SnsAccountTw.apk
SnsDisclaimer.apk
SnsImageCache.apk
SnsProvider.apk
SocialHub.apk
VoiceToGo.apk (I use Car Home instead)
Zinio.apk
Apps ported to Galaxy S2
Some of my favorite apps, not available into Market and ported to Galaxy S2:
Google Car Home
Market Access
Google+ 2.0 (works with a Google Apps account)
Terms
ROM - software stored into read-only memory. ROM retains its contents even when the phone is turned off. ROM is referred to as being nonvolatile, whereas RAM is volatile.
Kernel - portion of the OS that handles drivers, hardware control and access for the rest of the OS.
Modem - handles the communication with your carrier.
Root - superuser privileges in any Linux OS.

yqed said:
I'm posting this procedure in a separate thread, as is easier to be linked into different forum posts. My Bell Canada phone came originally with the UGKG2 firmware, so everything listed below is based on my own experience with this version, I do not know or confirm it will work with other firmware. I currently run the official (?) XXKG3 Gingerbread 2.3.4 firmware, downloaded from samfirmware.com site (see details below).
Personally, I read that other people flashed their phones with a different firmware... but I did not wanted to do it on my phone. I sticked with the same family XXKGx, just to be safe.
Click to expand...
Click to collapse
This is wrong. I'm not sure where you got that XXKG3 is remotely the same as UGKG2, but here's an explanation of the firmware version numbers:
This is standard across most Samsung Phones.
I9000 = Model #
UG = Carrier/Area code. For example, XX = Europe, UG = Bell Mobility Canada.
K = Year = 2011
G = Month = July (H = August, I = September)
2 = Revisions that month for the specific region (aka. UG, XX, XW).
A lot of people on here think the last 3 digits are important and that if you have 2 KG3 firmware that they are the same. However, this is not the case.
You need to go by all 5 letters due to the fact that each firmware is customized by different groups at Samsung. And to prove this, just look at KG2. There are 2.3.3 KG2's and there are 2.3.4 KG2's.
It's actually possible that one area's KG2 could have been newer than another area's KG4. The best way to check, is to look at the build date in the Build.prop for each firmware.
But your assuming that KGx means they're the same is wrong. All that those numbers mean is what month/revision the firmware is. Samsung has several different teams producing firmware independently of each other for different regions. The only letters that mean the firmwares are similar are the country/carrier code (ie. UG, XX, XW).
Also, your idea of what Official firmware is, is flawed. Just because it's on samfirmware, DOES NOT make it official. Most of their firmwares are leaked test builds. If it's not released on Kies, it's not official.

Thanks for the great explanation, much appreciated. It should help many people understand better how the versioning works. About the "official" part, that's the reason why I mark it with a (?). As you said very well, it is official once is released by Samsung through updates.
The thread is related to my own experiences with the Europe MULTI firmware, based on the fact that a Bell phone specs are identical to the Europe model.
Edit: I upgraded to XXKH3 firmware successfully just now, everything works great.

I currently have a Bell branded SGSII with baseband version UGKG2.
I originally flashed it with CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip and then I re-flashed it with the original UGKG2 Stock Kernel from Bell.
Now my phone is rooted and stock.
Any positive/negative feedback from users running XXKH3 firmware (2.3.4) would be very much appreciated.

thvpham said:
I currently have a Bell branded SGSII with baseband version UGKG2.
I originally flashed it with CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip and then I re-flashed it with the original UGKG2 Stock Kernel from Bell.
Now my phone is rooted and stock.
Any positive/negative feedback from users running XXKH3 firmware (2.3.4) would be very much appreciated.
Click to expand...
Click to collapse
I ran the KH3 firmware briefly with no issues. The only annoying this was when using the program monitor widget I would experience some lag or choppiness when switching homescreens(same on KG6/KH4). On the positive side the gps accuracy and lock time was greatly improved.

Aha, I had no idea as I don't use that widget... thanks for the tip.
I usually hold the Home button until the Task Manager pops, to see the running apps. But I got used already to press the Back key every time I deal with an app... that automatically closes it.
About the GPS, the accuracy is greatly improved indeed. It takes me 1-3secs max to get a lock (with wireless networks disabled) and the accuracy is always 5meters.
Edit: There is a new Digital Clock service running now... I have no idea what makes it start, please let me know. I use Beautiful Widgets on my home screen.

The digital clock service should be part of the digital clock widget. You can try to end the process under running services and see if it stops it.

I downloaded the XXKH3 firmware but I'm not sure which files I should be using with Odin (Bootloader, PDA, Phone & CSC).

KayvinM said:
The digital clock service should be part of the digital clock widget. You can try to end the process under running services and see if it stops it.
Click to expand...
Click to collapse
I use Beautiful Widgets, so DigitalClock.apk should not be starting... Weird.
I just uninstalled the system app, no more running services. It was wasting my battery for nothing.
thvpham said:
I downloaded the XXKH3 firmware but I'm not sure which files I should be using with Odin (Bootloader, PDA, Phone & CSC).
Click to expand...
Click to collapse
See step 3 and skip the PIT file (re-partition unchecked). Also see the Update note into OP.

thvpham said:
I downloaded the XXKH3 firmware but I'm not sure which files I should be using with Odin (Bootloader, PDA, Phone & CSC).
Click to expand...
Click to collapse
I ended up re-downloading the XXKH3 from Intratech's thread and it was much easier flashing the one PDA file.
Now do I need to flash the XXKH3 stock kernel or my default stock Bell kernel?

You need the XXKH3 stock kernel, Intratech has it linked below the actual firmware link.

does it matter if CSC changes?
right now, (before root + update firmware), I still have BMC....
but once it's changed, would that create problems? If yes, what kind of problems. If no, then why do we care about CSC?

Personally, I used the samfirmware files and the phone works great. The pda.bell.ca info is present into ASN also.

Thanks for the responses everyone.
I ended flashing the stock XXKH3 kernel with the firmware. So far the upgrade has been good to me, I noticed improved battery life for the first 18 hours of usage. I will continue to use this build until I find something that is more stable and efficient then this.

A BIG THANK YOU!!!! I finally rooted and unlocked.
Originally: UGKF6
Now: XXKG5
Thanks for the guide!!!
Just 1 question though, do I HAVE TO do a factory after root? Any problem if I don't?

One thing is sure, the battery life degraded compared to XXKG3 firmware.
XXKG3 | XXKH3 (about 4hrs lost)
When I took the screenshot on KG3, I was using the phone for about 2 hours to read a book (notice the sudden drops because of the white screen), while the KH3 was always in sleep mode. So ya, there is a significant change in battery life with a tradeoff for the GPS gains.
I updated the OP.
clb09 said:
A BIG THANK YOU!!!! I finally rooted and unlocked.
Originally: UGKF6
Now: XXKG5
Thanks for the guide!!!
Just 1 question though, do I HAVE TO do a factory after root? Any problem if I don't?
Click to expand...
Click to collapse
Just curious, why you did not used the KH3 to take advantage of amazing GPS? The battery life should be a bit better also, compared to KG5. What do you mean by "do a factory"? You will lose root only if you flash back the firmware, flashing the kernel will not delete the su binary. You want to keep your phone rooted.
I strongly recommend you to spend $1 and get ChainsDD's Superuser Elite key, it will allow you to pin protect your rooted device. I upgraded to 3.0 Beta4 and everything works properly. Worth the dollar in so many ways, not just for securing the su access.

What you use to remove system app.
Thanks

Fizwiz said:
What you use to remove system app.
Thanks
Click to expand...
Click to collapse
I use Titanium Backup PRO. It allows me to backup, freeze and uninstall the unwanted apps.

One thing i have see with the XXKH3. With the KG2 im stable on H+, now im switching between 3G and H+.
Anyone else?

See Fast Dormancy info in OP. Is normal and the intended way to save you battery and bandwidth congestion.

Regulatory domain, Wifi channels 12 and 13

Hi all!
I have noticed that my Arc S does not receive AP on channels 12 and 13. After doing some searches I concluded that the Regulatory domain must be set to US which is incorrect in my case, as I live in Europe.
I tried following this guide http://forum.xda-developers.com/showthread.php?t=1067944 to enable these channels, of couse doing the necessary modifications for this to work on a SE, but with no results unfortunatly.
My phone still has a locked bootloader and I cannot try custom roms, but will a custom rom solve this problem?
Moveover I am curious to know if this is a problem of the kernel module used which is locked to 11 channels or if it is because of some setting hardcoded in android itself.
Thank you!

as i can see, for the european area the only restriction is the signal power<20db, channels 11-13 are allowed and are working in Europe! My arc S is also locked but i can see channels 11-13.

Tkx for you reply labrok!
Then I cannot understand. I verified this using an app on the market called "Wifi Analyser", and the fact is that even in the wifi connect menu, all AP with these channels are not visible.
Also in the sqllite database available with the command
# /system/bin/sqlite3 /data/data/com.android.providers.settings/databases/settin
gs.db "select * from secure"
I can see:
wifi_num_allowed_channels|11
If I try to change this number to 13, it allows the change, but whenever I deactivate/activate the wifi, the number goes back to 11..
What is the version of the firmware that you are running?
I have 4.0.2.A.0.42.
Tkx!

same version, phone is European like yous so it uses same region settings,router TP-link TL-WR1043ND WITH ddwrt and router`s region set to Canada (to gain an extra 3db of power) i can set it till channel 13 and i can see it and i can connect too, to use channel 14 i must change region to japan but channel 14 is not usable from my arc s! but channels 12-13 working, they are not so good for an N network but my phone can see them an connect to them, maybe you should try to reflash your phone!

It's good to know that it works ok and that the problem lies only in software. I have asked some other users of the Arc S/Neo and they report the same problem
Maybe with your help we can solve this problem once and for all for everyone.
If your phone is rooted all I need you to do, is send me your Wifi drivers, running the following commands on the adb shell. Adb comes with the android sdk and is located at C:\Program Files (x86)\Android\android-sdk\platform-tools and then run "adb shell" command on a command line. You also need to activate the usb debugging on your phone.
Code:
su
cp /system/lib/modules/tiwlan_drv.ko /mnt/sdcard
cp /system/lib/modules/sdio.ko /mnt/sdcard
You now should have 2 files on the root of your sdcard, sdio.ko and tiwlan_drv.ko.
Can you please send these files to me?
I will then replace them on my phone and effectively determine if the problem is actually caused by the drivers or by the Android system itself.
Thank you so much for your help!!

My friend my phone is not rooted, if there is a way to help you, but because my phone is new I cannot root it and avoid my guarrantee.
Sent from my LT18i using XDA App

Thank you anyway labrok! I will keep searching for someone that has this working and with root to see if I can solve my problem

Ok, actually I found out how you can do this without root and without touching the warranty.
I will guide you through the process.
Install the Android SDK available at http://developer.android.com/sdk/index.html
Activate the USB debugging on "Applications"->"Development"->"USB Debugging"
Then open a command line prompt on windows and go to the directory where you installed android, typically C:\Program Files\Android\android-sdk\platform-tools, with the command
Code:
cd "C:\Program Files\Android\android-sdk\platform-tools"
Copy the driver files now from the phone with the commands
Code:
adb pull /system/lib/modules/tiwlan_drv.ko
adb pull /system/lib/modules/sdio.ko
The command prompt should look like this
Code:
C:\Program Files\Android\android-sdk\platform-tools>adb pull /system/lib/modules
/tiwlan_drv.ko
4636 KB/s (973324 bytes in 0.205s)
C:\Program Files\Android\android-sdk\platform-tools>adb pull /system/lib/modules
/sdio.ko
1618 KB/s (26520 bytes in 0.016s)
Files tiwlan_drv.ko and sdio.ko should be on C:\Program Files\Android\android-sdk\platform-tools folder now. Zip them and send them to me plz

i will try, but i think is not drivers problem.More likely its region restrictions, in Greece its allowed channels from 1-13, maybe in your is different than Greece! but i will send you the drivers as soon as possible!

I'm having the same issues with Xperia Arc S in Bulgaria. The phone has set it's wifi radio to operate on channels 1-11 so any networks on channels 12, 13 and 14 aren't visible to me.
Pure Android has the option to set the regulatory domain, but SE has decided to disable (or hide) it.
Here you can see how to set it on a non-SE Android: firdouss.com/2011/07/wifi-network-android-reason/
I've asked SE to check this on their forum too:
talk.sonyericsson.com/message/127760

Thank you the_mouse_bg!
I have bootloader unlocked my Arc S and tried a few roms like CM7.2, MIUI where I can see all 13 channels fine, so from this I have concluded that the problem is really from the firmware as due to the lack of answers on this topic, I was getting really worried this could be a hardware problem from my phone..phewwww
I now have stock firmware .42 with DooMKernel installed and the regulatory domain does appear in the menu but fails to be changed
I asked in the DooMLord's kernel topic to see if I can in any way debug this problem to try to solve it as I'm still little experienced with linux android workings.
Let's see if we can solve this issue asap!!

Regulatory domain (Wi-Fi channels 12 and 13) fix for the factory (default) ROM
I managed to fix the regulatory domain in order to be able to use the wireless channels 12 and 13 in the factory ROM. I only tested this procedure in the Xperia Pro (MK16a) and using the factory GingerBread ROM, although the procedure should be similar for other Xperia models and for the ICS ROM.
Well, it still needs rooting, but for those worried about the warranty it should be better than unlocking the bootloader or installing another ROMs, because you can root your phone, apply the fix, then unroot it, and nobody will ever know the phone was once rooted unless they do a deep forensic analysis.
How the regulatory domain works in Xperia devices
Sony added a class named "com/android/server/WifiService$RegulatoryDomain" which isn't part of standard AOSP. This class checks in which country you currently are based on the current MCC (Mobile Country Code), extracted from the first 3 digits of the current PLMN. Then there is a list of MCCs of countries on which 13 Wi-Fi channels are allowed. If your MCC is on the list, it enables 13 channels, otherwise it only enables 11 channels.
If your current MCC is not on the list, your wifi_num_allowed_channels setting has no effect. It is always reseted to 11.
Note that this is an "Android framework-level lock", not a "Linux-level or driver-level lock", because if you try to run iwlist (you can build yours from this svn repo) it shows channel 12 and 13 Wi-Fi networks even without any modification to the factory ROM.
The problem
The problem is that not all countries which allow 13 Wi-Fi channels are listed in the "WifiService$RegulatoryDomain" class. Apparently, there are typo errors in some MCCs.
For example, Brazil is MCC 724, but the class lists MCC 742, which according to this listing is a non-existent MCC. So it's apparently a typo error. They typed 742 instead of 724.
Fixing it
First, root your device. I used FlashTool for this.
Then, copy /system/framework/services.jar from your device to your computer using adb. Then unpack it (unzip or 7zip or whatever), use baksmali for disassembling classes.dex, and open "com/android/server/WifiService$RegulatoryDomain.smali" in a text editor.
Look for something like:
Code:
const/16 v7, 0x24
const-string v8, "742"
aput-object v8, v6, v7
iput-object v6, p0, Lcom/android/server/WifiService$RegulatoryDomain;->mHighChannelsMccs:[Ljava/lang/String;
This is where the 13-channels-allowed MCC list is being built. The "742" is the apparently non-existent MCC. Just replace it by the MCC of your country. Look at this listing or look at the first 3 digits of the PLMN:
Code:
$ adb logcat | grep PLMN
E/WifiService( 241): Could not get PLMN!
E/WifiService( 241): Could not get PLMN!
E/WifiService( 241): Could not get PLMN!
I/WifiService( 241): PLMN = 72410
I/WifiService( 241): PLMN = 72410
In my case I just replaced "742" by "724".
Then use smali for assembling the code back to the classes.dex file, and repack the services.jar file using jar, zip or another tool.
Finally, copy your modified services.jar to your device's /system/framework/services.jar using adb, and reboot your phone. Now everything should work.
About the attached file
My modified services.jar is attached for reference. Remember it is for the Xperia Pro factory GB ROM. If you use ICS or if you have another Xperia device, you need to baksmali/modify/smali your own jar file as described above.

wifi.supplicant_scan_interval not found in build.prop

i need to change wifi scan interval but i can't find wifi.supplicant_scan_interval anywhere in root level ,
i tired to add it in build.prop but nothing changed .
any dev can help ?

I got the same problem.
Wi-Fi keeps scanning while im already connected. Why, O, why?!
My mind has never been more baffled.
GT-i9505 on WanamLite ROM v3.1.

How to get region lock status?

Hello. I want to get region lock status on Galaxy A5. I tried to edit customer.xml unfortunately I don't know how to get lock status. Maybe some AT command, or shell command, or internal api... Thanks very much.

BTW, code *#7465625# does not executing.