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.
Related
{
"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"
}
Cognition Rom FAQ's
Check it out here!
Come chat with us!
Get Cognition Here
If you like this, buy me a beer!!
for OP.... OUT
Cognition Captivate ROMs - Tips & Tricks
Lets get started !!!!
The items in this post are not my work, I am just collecting them and posting here. They are also dangerous and may brick your phone. Please use at your own risk. No warrenties
Please donate to appropriate talented individuals who do this wonderful work
Installation
Install Using Clockwork Recovery
Caution: If you are running Cognition 6.X or below you must install using ODIN.
If you are not already rooted, root with the tools here. http://forum.xda-developers.com/showthread.php?t=739304
Go to the xda thread located here http://forum.xda-developers.com/showthread.php?t=786532. Download the latest version of the ROM. Move it to your internal SD card on your phone. DO NOT RENAME THE FILE.
Download ROM Manager (available in the market, more info here) and choose "Flash Clockwork Mod" which will put an update.zip (holding clockwork recovery) on the root of your internal SD card.
Open Rom Manager, choose "Install ROM from SD Card", navigate to your Cognition2.x.zip, and check “Wipe Data”. Watch the magic happen!
Note: if this is your first time installing clockwork, it may fail at stock recovery and reboot. Simply choose "reinstall packages" once more, and it should work properly.
Install Using ODIN
Caution: Use this method only for ODIN FLASHABLE DOWNLOAD! Download link will say “Download Cognition v2.2 BETA X.X.X ODIN”. This .zip contains everything you need to flash a ROM using ODIN. It includes:
• Odin.exe
• PIT.pit
• PDA.tar
• PHONE.tar
• CSC.tar
1. Put your phone into Download Mode (See below for Instructions)
2. Set-up ODIN with the appropriate files and click Start. (One-click versions just click Start). Note: Not all files listed above will be included.
3. Watch the magic.
How TO's
HOW TO: Put your phone in Download Mode
Make sure you phone is powered off, unplugged and charged. Remove SIM, External SD and Battery
Right Click ODIN Exe and click “Run as administrator”
Click Vol Up/Vol Down at the same time and insert USB into phone (other end must be plugged into the PC).
Note: This is extremely important: your phone screen should display a large yellow triangular icon with a shovel wielding droid in it. The text "Downloading... Do not turn off Target!!!!" appears below the icon. If you do not see this screen, you are likely in Recovery Mode.
HOW TO: Flash To JF6 Stock
Use How to Flash ODIN method above. Get Stock ODIN files from here
http://forum.xda-developers.com/showthread.php?t=731989
Caution: If your build is 1008 then you should use STOCK JF6 with 3 button fix from here
http://forum.xda-developers.com/showthread.php?t=818439
Where are archived ROMS?
http://www.ponack.net/designgears/OLD/
Lock Screen Mods, Battery Indicators
http://forum.xda-developers.com/showthread.php?t=799511
HOW TO: Reconfigure Battery Stats
When you flash a new ROM it may be necessary to reconfigure your battery stats.
Signs you may need to re configure:
1. . Using more then 10% battery in an hour or less
2. . While plugged into the charger you lock screen shows a different percentage charge then the battery icon
3. . After a full charge your battery icon only shows 99% and quickly drains.
4. . Any general weird battery activity
Step by step battery reconfigure process: (This is the process that has worked for me time and time again with ROM after ROM)
1. . Flash the Rom on a full battery. (skip to step 6)
2. . If you flashed on less then full plug into AC charger asap and charge to full while the phone is powered on
3. . Once the phone blinks full 2.1-battfull popup shows 2.2-battery sign shows on left of notification bar power off
4. . Charge till full while powered off. the phone will vibrate and the green battery will show 100% in white text
5. . Unplug phone and power on.
6. . Using Root Explorer or a comparable program navigate to (Mount R/W first): data>system> and delete file batterystats.bin
7. . Reboot
8. . While the phone reboots it will rebuild that file and the software and phone should now match.
9. . If any of the symptoms persist start at step 2 and repeat.
10. . As with any rechargeable battery fully discharging the battery once in a while isn't a bad idea
HOW TO: BATTERY Calibrate
1. Connect the phone to the charger with the phone powered on, and allow the phone to charge until it shows 100%
2. Disconnect the phone from the charger, and power it off.
3. Reconnect the phone to the charger with the phone powered off, and allow the phone to charge until the battery indicator shows 100% (you can use vol-up/vol-down to make the indicator come back up when the screen goes to sleep).
4. Disconnect the phone from the charger and power it on.
5. Once the phone is powered completely on, power it off again and reconnect it to the charger until the battery indicator shows 100%.
6. Disconnect the phone, power it on, and use it.
You should only need to use this sequence one time.
HOW TO: Enable/disable Voodoo
To Disable: Create a folder in /sdcard/Voodoo named "disable-lagfix" (without the quotes; capitalization is important). To Enable just remove this folder
Now reboot the phone.
Tips & Tricks/Missing Apps/Walpapers & Other Stuff
(11/16/2010) Con 2.3bv4: HOW TO: Install Missing Wallpapers & Keyboard
Live Wallpapers & SOme keyboards were removed from this ROM. Here is how to get them. Credit pinoymutt
http://forum.xda-developers.com/show...postcount=9095
(11/17/2010) Android Keyboard
http://forum.xda-developers.com/showpost.php?p=8431641&postcount=2
(11/18/2010)MMS Fix
Credit: mmoorman12
http://forum.xda-developers.com/showpost.php?p=8830645&postcount=4081
(11/18/2010)Some Google goodies for Froyo (Desk Clock, Genie Widget, Car Home, Music)
Might or not be compatible with all ROMS - Please try at your own risk
Credit: frauhottelmann http://forum.xda-developers.com/showthread.php?t=817092
(11/18/2010)androidIMATIONS | Custom Boot Animations for Android
Might or not be compatible with all ROMS - Please try at your own risk
Credit: cmbrougham http://forum.xda-developers.com/showthread.php?t=822955
(11/22/2010) 2.3b6 if you cannot get signal after flashing flash jj4 modem
http://forum.xda-developers.com/showthread.php?t=835272&highlight=modem
Credits:
Cognition Wiki
Many Many posts in XDA Captivate section
Other Stuff from Quoted from Cog Thread
GPS Settings:
To get to LbsTestMode: *#*#3214789650#*#* from your dialer
Originally Posted by cnewsgrp 1. Disable “Use Wireless Networks”
1. Navigate to Settings > Location & Security > uncheck the box next to “Use Wireless Networks”
2. Go to the phone and dial *#3214789650#
1. This step throws you into LBSTestMode menu
3. In the LBSTestMode menu change “Operation Mode” to MS Based
4. In the LBSTestMode menu, find “SUPL/CP Settings” and change the SERVER & PORT to supl.google.com and port 7276 (DO NOT use www. in front of supl)
5. REBOOT
6. Enable “Use Wireless Networks”
* Navigate to Settings > Location & Security > check the box next to “Use Wireless Networks”
Update: When using MS based, tracking is terrible, the gps often misses the fact that i have turned and thinks i am continuing forward.
Using standalone is a bit better, but still has times where it misses the fact that i have turned
Should you want to revert back to your original GPS settings, you’ll need to re-enter you factory specs:
Original settings:
Operation Mode: Standalone
SERVER: www.spirent-lcs.com
PORT: 7275MMS Settings:
Name: AT&T
APN: wap.cingular
Proxy: leave blank
Port: leave blank
Username:[email protected]
Password:CINGULAR1
Server: leave blank
MMSC: http://mmsc.cingular.com
MMS Proxy: wireless.cingular.com
MMS Port: 80
MCC:310
MNC:410
APN Type: leave blankEmail fix if you have that "issue"
APK Download Here
adb pull /system/app/Email.apk
adb pull /system/app/Email.odex
adb push ./Email.apk /sdcard/
adb shell
su (at this point tell superuser to allow permissions if prompted)
rm /system/app/Email.apk
rm /system/app/Email.odex
cp /sdcard/Email.apk /system/app/Email.apk
chown root.root /system/app/Email.apk
chmod 644 /system/app/Email.apk
exit
exit
adb rebootCisco VPN Issue Fix:
VPN Links:
http://code.google.com/p/get-a-robot...9.apk&can=2&q=
http://code.google.com/p/get-a-robot...un.ko&can=2&q=
Simply follow these steps. ALL CREDIT GOES TO SUKKUBUS06 from another topic here on XDA. I modified a few steps that I think help the clarity of the instructions.
* Download the correct tun.ko for Android 2.2 here (it says Nexus One but works perfect with my Cognition ROM on Captivate): http://code.google.com/p/get-a-robot...un.ko&can=2&q=
Copy the tun.ko file to the ROOT of your internal SD Card.
Un-install any OpenVPN Settings, OpenVPN Installer, or OpenVPNC applications if they are installed. Perform these steps from scratch...TRUST ME.
You must have the Busy Box installer downloaded and install Busy Box. This app is availabe in the app store. use 1.17.
For the next step you must have the android SDK files on your computer. Open a command prompt, change directories to the C:\android-sdk-windows\tools directory then start the code commands.
Code:
adb shell
su(ALLOW ACCESS ON YOUR PHONE WHEN SUPER USER PROMPTS YOU)
mount -o remount,rw /dev/block/stl6 /system
cp /sdcard/tun.ko /system/xbin/
* create symlinks for busybox route and ifconfig (required by openvpn)
Code:
cd /system/xbin
mkdir bb
cd bb
ln -s ../busybox ./ifconfig
ln -s ../busybox ./route
* create directory for openvpn config files
Code:
mkdir /sdcard/openvpn
* create symlink for cp (unix command for copy). otherwise the install-script of the OpenVPNInstaller (see below) will fail!!!
Code:
ln -s /system/xbin/busybox /system/xbin/cp
* download OpenVPNInstaller from Android Market
run and configure OpenVPNInstaller
specify directories: busybox is in /system/xbin, ifconfig and route are in /system/xbin/bb
* copy vpn-config files (config, certs, key) to /sdcard/openvpn (i.e. via adb push or mounting the phone as a mass-storage unit)
* download OpenVPN Settings from Android Market
run and configure OpenVPN Settings
activate "load tun kernel module"
Tun module settings:
- Load module using insmod (instead of modprobe!!)
- Path to tun module: /system/xbin/tun.ko
Path to configurations:
/sdcard/openvpn
Path to openvpn binary
/system/xbin/openvpn
Now install the latest VPNC found here: http://code.google.com/p/get-a-robot...9.apk&can=2&q=
I rebooted my device at this point. I set up my connection in VPNC and it worked perfectly. Oddly enough when performing a lsmod command in the terminal, I see NO tun.ko module running but hey who cares! It works!
GOOD LUCK!
How to edit notification bar/battery mods/transparent drawer:
http://forum.xda-developers.com/showthread.php?t=812541
Pirateghost said:
YEP
but if you already had everything setup the way you wanted....
Click to expand...
Click to collapse
With TiBu it really doesn't take too long to get back there,
Sorry if this is a dumb question but what is hsupa?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yeah i got HSUPA but i had to do the harder way. That going to be a real treat for everybody.
Now we just need a kernal that can do it all, then there will be roms coming out everyone's ass we wont be able to keep up
TheTodFather said:
Yeah i got HSUPA but i had to do the harder way. That going to be a real treat for everybody.
Now we just need a kernal that can do it all, then there will be roms coming out everyone's ass we wont be able to keep up
Click to expand...
Click to collapse
this for sure
does the ugjh2 modem go into the pda spot in odin?? Never flashed just the modem
mauriciorubio said:
Sorry if this is a dumb question but what is hsupa?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
http://www.google.com/#hl=en&expIds...l=&oq=hsup&gs_rfai=&pbx=1&fp=1de331493393b8ab
buddy17 said:
does the ugjh2 modem go into the pda spot in odin?? Never flashed just the modem
Click to expand...
Click to collapse
nope, Phone slot. Kernel goes in PDA
wait....i think i meant to say kernal....unless i need to flash the modem AND the kernal?? I downloaded the reoriented kernal from the other thread that includes voodoo, is that all i need to get hsupa if i already have cognition?
im on sre2b6, if i flash to this cognitive will i need to mess with odin for the modem or is included...can i just rom manager over to this, i dont mind if it wipes everything
buddy17 said:
wait....i think i meant to say kernal....unless i need to flash the modem AND the kernal?? I downloaded the reoriented kernal from the other thread that includes voodoo, is that all i need to get hsupa if i already have cognition?
Click to expand...
Click to collapse
nope, you need the JH2 modem. it's hiding somewhere in the kernel thread. Zilch needs to be here tonight, he's usually on top of this ****
HSUPA is high speed uplink packet access and that with download makes HSPA or 3.5g.
or http://en.wikipedia.org/wiki/High-Speed_Uplink_Packet_Access
NOW Gears we need to optimize MTU settings!!!!
Maxium Transmition Units--------currently we are pegged at 1400 and with header it even lower i think 1352 to be exact.
1500 The biggest sized IP packet that can normally traverse the internet without getting fragmented. Typical MTU for non PPPoE, non VPN connections.
1492 The maximum MTU recommended for internet PPPoE implementations
1472 The maximum ping data payload before fragmentation errors are received on non-PPPoE non VPN connections
1460 TCP Data size (MSS) when MTU is 1500 and not using PPPoE
1464 The maximum ping data payload before fragmentation errors are received when using a PPPoE connected machine
1452 TCP Data size (MSS) when MTU is 1492 and using PPPoE
576 Typically recommended as the MTU for dialup type applications .. leaving 536 bytes of TCP data.
48 The sum of IP, TCP, and PPPoE headers
40 The sum of IP, and TCP headers
28 The sum of IP, ICMP headers
Clicking this link will show you your MTU and other important settings http://www.speedguide.net/analyzer...._TOS=0&IP=24.236.120.106×tamp=1284959054
SO we can either have a max of 1500 or 1400 but when downloading a package that is a 10mbs it adds up real quick!
AT&T pegged us at 1400 for a reason we don't know if it will work unless we test for packet loss. If anyone can point me in the right settings I would love to play with it.
darkamikaze said:
I rather do that I think.. links to both D: ?
and which goes to where? like phone? pda? D:
Click to expand...
Click to collapse
extract the .tar file out of the zip and the .bin file out of the modem zip
tar goes in PDA
modem goes in PHONE
i had to flash them separately to get it to work 100%
OK, I am trying to disable the lagfix using the disable-lagfix file in the voodoo directory, but it doesn't seem to be doing anything(usually you hear the robot voice saying it is reverting back to RFS). I'm going to try removing the file, and see what happens.
EDIT: Hmm, removing it I hear the voice telling me it is applying the voodoo ext4 lagfix. Maybe I just missed it when I added the file before. There were a couple of drunk idiots I had to help at my job...
Demented71 said:
OK, I am trying to disable the lagfix using the disable-lagfix file in the voodoo directory, but it doesn't seem to be doing anything(usually you hear the robot voice saying it is reverting back to RFS). I'm going to try removing the file, and see what happens.
EDIT: Hmm, removing it I hear the voice telling me it is applying the voodoo ext4 lagfix. Maybe I just missed it when I added the file before. There were a couple of drunk idiots I had to help at my job...
Click to expand...
Click to collapse
Hey demented, deleting the files wont revert you back to rfs. Create a folder called "disable lagfix" with no quotes or hyphens
Sent from my SAMSUNG-SGH-I897 using XDA
wuxingwarrior3 said:
Hey demented, deleting the files wont revert you back to rfs. Create a folder called "disable lagfix" with no quotes or hyphens
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
I know. I created the file via ES File Explorer, but I think I was outside my booth when it removed the lagfix, so I thought that it didn't do it.
EDIT: Just created it again, and it's reverting back to RFS.
TheTodFather said:
HSUPA is high speed uplink packet access and that with download makes HSPA or 3.5g.
or http://en.wikipedia.org/wiki/High-Speed_Uplink_Packet_Access
NOW Gears we need to optimize MTU settings!!!!
Maxium Transmition Units--------currently we are pegged at 1400 and with header it even lower i think 1352 to be exact.
1500 The biggest sized IP packet that can normally traverse the internet without getting fragmented. Typical MTU for non PPPoE, non VPN connections.
1492 The maximum MTU recommended for internet PPPoE implementations
1472 The maximum ping data payload before fragmentation errors are received on non-PPPoE non VPN connections
1460 TCP Data size (MSS) when MTU is 1500 and not using PPPoE
1464 The maximum ping data payload before fragmentation errors are received when using a PPPoE connected machine
1452 TCP Data size (MSS) when MTU is 1492 and using PPPoE
576 Typically recommended as the MTU for dialup type applications .. leaving 536 bytes of TCP data.
48 The sum of IP, TCP, and PPPoE headers
40 The sum of IP, and TCP headers
28 The sum of IP, ICMP headers
Clicking this link will show you your MTU and other important settings http://www.speedguide.net/analyzer...._TOS=0&IP=24.236.120.106×tamp=1284959054
SO we can either have a max of 1500 or 1400 but when downloading a package that is a 10mbs it adds up real quick!
Click to expand...
Click to collapse
where is the MTU settings at in android
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.
I recently purchased a China Telecom Galaxy Grand 2 SM-g7109 (G7109KEUBNC1) Android version 4.3.
I would really like to be able to install the Google Play Store on this phone.
I have tried a number of different efforts to do this, including those described here:
http://forum.xda-developers.com/showthread.php?t=2689312 (but needs root permission ... which I can't seem to get)
http://www.dashi.com/guide/7755.html ... installed the recovery ... but the root failed
Tried, Towelroot ... but the phone simply reboots
Tried, Root Master (mgyun.com/romastersu) ... but it failed
Also tried pulling the .apk from my Galaxy Nexus phone and installing them, GMAIL, Google Contacts both worked and sync OK, but Google Play and everything else does not (installs, but the never connects ... even on VPN [I am in China, behind the Great Firewall]).
After all that I have done the phone will now no longer get updates "Your device has been modified. Software updates are not available." I also have to now deal with the "Unfortunately, Google Play Store has stopped - OK" dialogue popping up every 10 - 30 seconds!!!
I have done the factory reset/wipe several times, but this does not give back the ability to update ;(
Please help me root or at LEAST install the Google Play Store (in a way that functions)!
UPDATE:
I have managed to root the China Telecom Gaxay Grand 2 SM-G7109!!!
Many thanks to @mjcaballero on this thread: http://forum.xda-developers.com/galaxy-grand-2/help/how-to-root-flash-ittowelroot-v3-t2802021#post54618106
Using Towelroot v3 (https://towelroot.com/) and the modstrings functionality (https://towelroot.com/modstrings.html), I was able to input the modstring:
Code:
1337 0 0 0 4 0
and boom the device was rooted!
Here is the text from https://towelroot.com/modstrings.html if you do not feel like clicking:
== Introducing modstrings! ==
Modstrings are a way to modify the exploit parameters for your obscure phone.
This is only if your device can't be towelrooted.
Click "welcome to towelroot v3" 3 times and enter text.
1337 method(0-3), align(0-1), limit_offset(0-8191), hit_iov(0-7), temp_root(0-1)
method: which syscall is used in the blocking thread, try them all
align: which alignment to use for the iovs, try them all
limit_offset: 0 is probably the right value here, otherwise close to the samsung value and a multiple of 4
hit_iov: which iov to overwrite to cause block
temp_root: do a temp root putting su and daemonsu in /sbin, good for HTC and Motorola, doesn't fix exploit
To fix, align and method are probably your best bet(4*2=8 values), hit_iov maybe, limit_offset if you are desperate.
== Examples ==
Most phones: "1337 0 1 0 4 0"
New Samsung: "1337 0 1 7380 4 0"
Temp root: "1337 0 1 0 4 1"
Click to expand...
Click to collapse
Then I went ahead and used Smart GApps v1.0 (http://forum.xda-developers.com/showthread.php?t=2689312) to add the Google Play store and such and well now I am a very happy customer!!!
Many thanks to the xda-developers community!
Only fresh flashed bootloader locked XT1058 AT&T - ROM LPAS23.12-21.7-1, and XT1060 VZW - ROM LPAS23.12-39.7-1 are supported!
See archive content for instructions. Time to install ~20 min. If you experience problems after Android boot, like not working buttons or quick settings, wipe cache + data partitions. Don't update SuperSU (disable auto updates), it won't work. Later I'll post complete debloated ROMs with fresh SuperSU version, and simplify instructions. Be informed also, that this method doesn't give you read-write rights like unlocked bootloader. You may read and write having root-rights, but only till a restart or shutdown occurs, and every change will be undo by the Qualcomm protection (like HTC' s=on).
At the moment patch includes:
SuperSU 2.65 Free
Xposed Framework v86 (installer, modules)
Busybox 1.25.0.YDS, path /system/xbin/busybox
Download
P.S. Install only on indicated above ROM versions, and it's obvious that you must have enough theory knowledge and practical experience to make use of 9008 patch, so I'm not responsible for any consequences, etc. Greets go to: CrashXXL (method inventor), Sabissimo (our former OP), and serg_gangubas (ROM guru).
==============================================================================================
31.07.2017 - Full ROM Patch for Bootloader Locked Moto X ATT/VZW/etc
Based on the same principle, and not depend on system partition content, so it suits any bootloader locked Moto X Gen1 ATT/VZW (possibly any model, besides 1049 RepW / 1055 US Cell), but takes about 4 hours to be done - prepare for that, 100% battery level only!
This full ROM patch includes:
SuperSU 2.82 Free
Xposed Framework v87 (installer, modules)
Busybox 1.26.2, path /system/xbin/busybox
ViperFX 2.5.0.5 - sorry needs polishing, removed now (
Gallery and Camera not depend on Moto services
Gboard instead AOSP Keyboard. If it eats too much RAM, see Simple Keyboard
GAPPSes updated. Use command like adb shell pm uninstall --user 0 com.blahblah.blah to block any unwanted app or service
ES File Explorer Free Edition (a clone, you can disable and install yours )
"Jedy" gesture
AdBlock support (effect lasts till the 1st reboot yet, I'll think about make it constant). Please, choose /data/hosts instead of /system/etc/hosts
ROM debloated, but not deodexed.
Download
Instruction
Be careful, phone will be WIPED then flashed in 9008 "brick" mode (CrashXXL idea). Before you start install Moto drivers, latest RSD Lite, and fully charge the battery.
1) Download and unpack zip on С: (or any), open Python27, launch RUN_path.bat (needs to be launched only single time), install driver QHSUSB_driver.exe, and launch file _Moto.X.BootLocked.*.exe (where * - is desired ROM).
2) Go into fastboot mode, execute RUN_blbroke.bat. Screen gets black, Device Manager in Windows finds "QHSUSB_DLOAD", and installs it as "Qualcomm HS-USB QDLoader 9008 (COM*)". If it doesn't install, google for Windows driver digital signature disable.
3) Now launch RUN_root.bat, and see that patching process took start.
4) A small patch *SPEAKERS.BOOST.exe (if exists) boosts both speakers' volume.
P.S. Please, don't flash anything extra into the phone. In case of trouble, all you need is inside this folder. Just make it work.
To make "Battery OK" in fastboot use fastboot_cyclecharge.bat
Completely drained out battery causing "USB input device" needs disassembly of the phone to charge externally.
In case Titanium Backup shows error "Batch backup interrupted: insufficient free storage space", delete default backup folder, and make a new:
Titanium Backup > Menu > Preferences > Backup folder location > Storage Provider > DocumentProvider storage > Show Internal Storage > Internal Storage > Select Internal Storage > Create the folder > Use the current folder. Done!
Notes for myself: Viper, force wipe, readme.txt, volume patch, Adblock, advanced debloat
Debloated, rooted, lightweight ROM - soon! )
PUBLISHED. Sorry, took long time.
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
This method is working on locked BL.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
Wait wait... If you can have now possibility to unlock bootloader - go for it immediately! You will have normal FULL root-rights (SuperSU 2.49). Don't install 5.1, if you plan to unlock, because Sunshine app (25$) works only on 4.4.2 Android.
This topic is to help those AT&T users that are boot locked forever (who missed out possibility to unlock on 4.4.2 by proceed to 5.1) to give them READ-ONLY root. Yes, it's limited, but anything at least.
s5610 said:
If you can have now possibility to unlock bootloader...
Click to expand...
Click to collapse
I guess anyone on 4.4.4 today. There is no possibility to use Sunshine anymore.
Anyway spasibo za method
Ahh, if I don't have to be BL unlocked that's great lol.
I haven't read too much into the 5.1 updates or sunshine for that matter.
I've been on krypton 1.4.1 since it was released, and I haven't been able to successfully upgrade to any 5.1 roms yet.
Works great!
Works great for me on Windows 10 RTM 64-bit! Thanks a ton, I was waiting for a post like this.
I only had 3 minor hiccups:
1. RSD Lite gave me an error about "getvar", so I had to go into flashfile.xml in the ROM zip and remove the line that said getvar
2. I had to reboot to disable driver signature enforcement twice for some reason because Windows Update
3. The run-root.bat got stuck on "Executing..." because I installed the wrong driver (the correct file is qcusb.inf when installed from device manager -> browse my computer for driver software -> let me pick from a list -> all devices -> have disk)
Otherwise, everything runs just as well as KitKat, including Xposed.
Hehe got to love step 9
System Write
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
Click to expand...
Click to collapse
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Need some help, I did all steps until step 9. I installed the QHSUSB_DLOAD driver manually, and I can see 'Qualcomm HS-USB QDLoader 9008 (COM4)' showed in my Device Manager, but when I run 'RUN_Root.bat', I got this
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending SBL Reset...
Done
c:\Python27>pause
Press any key to continue . . .
Then I tried to run 'RUN_Root.bat' again, then I got
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
c:\Python27>pause
Press any key to continue . . .
any suggestions? Thanks
jahrule said:
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Click to expand...
Click to collapse
Ill put the files here
Fantastic!!! I was looking this. All the last week I was sleeping about 3 hours per day trying to root my phone.
----
I scream "Victory" before the process finish.
Damn! My phone reboot and stay in the android doll fallen screen.
DejanPet said:
Ill put the files here
Click to expand...
Click to collapse
What to do with these files?
Those files are needed by Jahrule
Sabissimo
Hello.
I did everything as instructed, but eventually got the screen "no command".
The only thing I did not flash rom - a month ago updated by an OTA to 5.1, thought it was not necessary.
Factory reset does not help.
Advise something.
In the end, everything worked, thank you))
It works
It works great! Thank you very much! ATT xt1058.
eze_cba17 said:
Damn! My phone reboot and stay in the android doll fallen screen.
Click to expand...
Click to collapse
Follow the OP instruction EXACTLY, no exceptions!
If you got your current 5.1 through AT&T OTA, it's not enough for root patching procedure. A full RSD 5.1 official SBF flash over is required.
Could someone please do a video on this. I'm having a little trouble.
Hi all, hi tim,
I'm new in smartphone world but I am "hacking" lover and want to play with my girlfriend old Core Plus.
I enabled debugger mode, Installed TWRP and lineage-13.0-20170524-UNOFFICIAL-cs02.zip ROM (tim's 3.4.5+, Android 6.0.1).
I tried many ROMs but other have problem at boot ("trebuchet" loops chash).
Maybe it's because data and system were not correctly wiped (error during ROMs deployment, I had to manually delete /data and /system using ADB)...
Is there a way to install new rom without loosing data ?
Using OTA updates ? Currently it does not found any update ("No items available").
My main problem is GPS does not work:
(I want to use it for walking, so without internet location providers)
Code:
[email protected]:/ # settings put secure location_providers_allowed +gps
[email protected]:/ # dumpsys location
Current Location Manager state:
Location Listeners:
Reciever[f571137 listener UpdateRecord[passive android(1000) Request[POWER_NONE passive fastest=0]]]
Reciever[6db46a4 listener UpdateRecord[passive android(1000) Request[POWER_NONE passive fastest=0]]]
Active Records by Provider:
passive:
UpdateRecord[passive android(1000) Request[POWER_NONE passive fastest=0]]
UpdateRecord[passive android(1000) Request[POWER_NONE passive fastest=0]]
Historical Records by Provider:
android: passive: Interval 0 seconds: Duration requested 177 out of the last 177 minutes: Currently active
Last Known Locations:
Last Known Locations Coarse Intervals:
Geofences:
Enabled Providers:
fused
passive
mWhitelist=[] mBlacklist=[]
fudger: offset: -276, 1160 (meters)
passive Internal State:
mReportLocation=true
gps Internal State:
mFixInterval=1000
mDisableGps (battery saver mode)=false
mEngineCapabilities=0x6 (MSB MSA )
fused Internal State (com.android.location.fused):
REMOTE SERVICE name=fused pkg=com.android.location.fused version=0
mEnabled=false null
fused=null
gps Location[ 0,000000,0,000000 acc=340282346638529000000000000000000000000 t=?!? et=?!?]
---
net Location[ 0,000000,0,000000 acc=340282346638529000000000000000000000000 t=?!? et=?!?]
---
It there an hardware problem or a OS problem ? How to check ?
I'am also looking for a tutorial to build Lineage from scratch, for my interest.
Any link welcome.
Last request: I didn't find any reliable FM radio tuner apk. Device have a tuner, it works with samsung ROM.
Have a nice day.
Can You send me this rom?
Because source link is dead.
EDIT: Nevermind, sorry 'bout that.