[Kernel/RECOVERY] Sony Xperia Go ST27i, Kernel, CWM, GB KK v5.1 and ICS KKv6 - Sony Xperia P, U, Sola, Go

NOTE: Use at Own Risk, I am not Responsible for any damages...... Hit Thanks if it works for you
NOTE: Do not turn on Battery Save mode when you have flashed KK v6.x Kernel, then phone will go into a bootloop immidiatly
Prerequesites:
Sony Firmware: 6.0.B.184 for GB and 6.1.1.B.1.10 for ICS
Installed Andoid SDK with platform-tools included, http://developer.android.com/sdk/index.html
Correctly installed modifed USB Drivers from Sony, follow this Thread if you got problems http://forum.xda-developers.com/showthread.php?t=1527159
Unlocked Bootloader, which implies the correct installation of the USB Drivers follow this Process http://unlockbootloader.sonymobile.com/unlocking-boot-loader
Get SU and Superuser from here http://androidsu.com/superuser/
Know how to put the phone into Fastboot mode
How too:
Now lets get started, these are the steps to get to the latest kernel with the recovery installed.
1. Flash the unlocked stock kernel "Kernel 6.0.B.184 ro.secure=0.elf" from the Android SDK Folder:
fastboot.exe -i 0x0fce flash boot Kernel 6.0.B.184 ro.secure=0.elf
fastboot.exe reboot
2. Install SU and Superuser to gain permanent Root
NOTE: This step is only needed once, you can flash a new kernel without the need to root the device again.
extract SU and Superuser from the downloaded zip files and push those via ADB to the unlocked /system folders from the SDK dir with the commadn below.
adb root
adb shell id (to see if you are root)
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb remount
adb install Superuser.apk
reboot the phone and check with a Rootchecker app if you successfully gained root.
3. Install Busybox From the Market.
Touch the Play Store icon and wait for ...... ...... ok just kidding
NOTE: Please check the Correct file size of the su file with ls -l /system/xbin/ it should be around 380 K in size or compare with the file from the zip archive
4. Flash the latest Custom Kernel "kernel.elf".
fastboot.exe -i 0x0fce flash boot Kernel with CWM gows io sio.elf
fastboot.exe reboot
5. Enter Recovery
Hit Vol+ after it vibrates on the Sony Logo , the Home Touchkey is the Enter Button......
Finally go for a full backup, yeah !!!!
NOTE: I never had to wipe or factory reset my phone while swapping kernels back and forth, trust me i flashed the phone a lot of times with a lot of self compiled kernels...
Appendix:
I build a Custom Kernel from this source http://developer.sonymobile.com/wpor...ads/opensource Open source archive for build 6.0.B.3.184 for KK v5.x and 6.1.1.B.1.10 for KK v6.x
here is my git https://github.com/krachlatte/
Thanks to the makers of the Android Kernel Kitchen 0.2.3, Flashtool, Superuser, aso....just to mention a few:
KeiranFTW for CWM
DOOMLORD for govenours
Championschwimmer For the Kernel Kitchen
jozinek
driversax
.... a s o i hope i did not forget anyone...
Thanks
Release Notes
Krachlattes Kernel (KK) v5.1
SSHTunnel Support
Iptables Support
Droidwall Support
I/O Schedulers added:
sio
Governours added:
interactive
minmax
smartass
smartass2
Krachlattes Kernel (KK) v6.3
gcc upgrade from 4.3.3 to 4.6
http://gcc.gnu.org/gcc-4.6/changes.html
SSA loop prefetching is enabled by default for the Cortex-A9 at -O3
Kernel Source code update to 6.1.1.B.1.10 found at sony dev page
Bootlogo fixed
I/O Scheduler added:
Simple I/O Scheduler (SIO)
Governour added:
smartassv2
Hotplug
The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."
Obviously, this governor is only available on multi-core devices.
Screenshot showing up time, Juice defender installed, normal usage.....for 1 hour 10 minutes music via bluetooth and gps track recording at the same time yesterday, with kernel v6.2.
NOTE: Do not turn on Battery Save mode when you have flashed KK v6.x Kernel, then phone will go into a bootloop immidiatly
Flash it with:
fastboot.exe flash boot boot.img

---

Hi! If I use this will the contents on my phone ve deleted or will it stay intact? Tia!
Sent from my ST27i using Tapatalk 2

---

pls delete this
btw couldn't get a real root ...
i seem to have root but not working properly ... titanium wont get root privileges for example ..

---

hi guys,
for me it is still working fine as done in the thread above, just post your errors and I will try to look into it. NO SD Card issues at all. got this phone on friday morning and rooted it on friday at around 10pm.
Class 10 SD Card is much faster then with my old defy, when reading an writing files to the phone when it is connected to pc.
Titanium backup running fine....
Something to consider:
1. You need to extract the SU file and Superuser.apk from the zip file and install it via ADB, not push the whole zip via ADB.
2. Did you really unlock the bootloader as described on the sony pages?
3. Is the Android SDK and the modified SONY USB Driver installed correctly? the Dirver installation to get the phone into fastboot correctly was a bit frustrating.

---

krachlatte said:
hi guys,
for me it is still working fine as done in the thread above, just post your errors and I will try to look into it. NO SD Card issues at all. got this phone on friday morning and rooted it on friday at around 10pm.
Class 10 SD Card is much faster then with my old defy, when reading an writing files to the phone when it is connected to pc.
Titanium backup running fine....
Something to consider:
1. You need to extract the SU file and Superuser.apk from the zip file and install it via ADB, not push the whole zip via ADB.
2. Did you really unlock the bootloader as described on the sony pages?
3. Is the Android SDK and the modified SONY USB Driver installed correctly? the Dirver installation to get the phone into fastboot correctly was a bit frustrating.
Click to expand...
Click to collapse
Hello - yeap - pushed it from the extracted folder - no error messages received in the cmd prompt. all went fine.
2. also yes - the phone is unlocked - actually when tried unlocking for the second time it told me it's already locked
3. I have all the sdk's installed for android and am running the fastboot from the platform-tools directory so all should be there ...
yet - root checker says I have root - but titanium backup or any other program seem to run at first but then I get an error that The phone was not granted with root privileges. Also I cannot install busybox - starts installing and fails at the end for some reason ...
Any ideas?

---

could you post your screenshot?
did you start with a clean install, i mean did you flash another kernel before installing this one?
where are you from, means what build do you have installed?
could you create a ftf file with flashtool, if it is different from my build ?

---

krachlatte said:
could you post your screenshot?
did you start with a clean install, i mean did you flash another kernel before installing this one?
where are you from, means what build do you have installed?
could you create a ftf file with flashtool, if it is different from my build ?
Click to expand...
Click to collapse
Will post a screenshot later on tonight as I am not at home with my laptop and phone.
I created an ftf file using the downloaded files from pc companion, decrypted them and made a new ftf file, which was flashed onto the device. I believe this is considered a clean install ?
I am located in Bulgaria but need to check the build version exactly. Just confirmed that the details on the screenshot match all 100% with what the phone.
I have tried flashing another kernel indeed again prepared for .184 from this thread here : http://forum.xda-developers.com/showthread.php?t=1829729 but without any luck - at the end I managed to flash the kernel from this thread here, and then followed the procedure as described above - all seems good and superuser seems to be giving permission to applications - alas no luck.
I can even upload the ftf file if needed. all else seems to be running fine (some slowdowns though - lag or smth - was not present with 162.)

---

krachlatte said:
Hi Guys,
here is what i did, i just bought a Sony Xperia Go, i am coming from a defy running cm7 and cm9 with root.
i just extracted the kernel from the official Sony update that i graped from the cache folder and converted that file via flashtool to a working ftf file, followed by extracting the kernel and ramdisk and modified the default.prop file to ro.secure=0, afterwards i repacked the the extracted zimage and ramdisk to a working kernel this file is attached to this post "Kernel 6.0.B.184 ro.secure=0.elf". the kernel is complete stock nothing included. just flash it via fastboot with: (unlocked Bootloader needed, see sonys pages for this also for usb driver installation)
fastboot.exe -i 0x0fce flash boot Kernel 6.0.B.184 ro.secure=0.elf
fastboot.exe reboot
next I included SU and Superuser via ADB, you can download an extract SU and Superuser from here http://androidsu.com/superuser/
adb root
adb shell id (to see if you are root)
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb remount
adb install Superuser.apk
Thanks to the makers of the Android Kernel Kitchen 0.2.2, Flashtool, Superuser, aso....
my major question is when will we see CM9 or CM10 ported to this device.
Click to expand...
Click to collapse
Im on .184 now with so many apps installed.. Do I have to flash a clean .184 before flashing this kernel or its ok to just flash it? What would I lose if I flash this?
Sent from my ST27i using Tapatalk 2

---

wbgenetic said:
Will post a screenshot later on tonight as I am not at home with my laptop and phone.
I created an ftf file using the downloaded files from pc companion, decrypted them and made a new ftf file, which was flashed onto the device. I believe this is considered a clean install ?
I am located in Bulgaria but need to check the build version exactly. Just confirmed that the details on the screenshot match all 100% with what the phone.
I have tried flashing another kernel indeed again prepared for .184 from this thread here : http://forum.xda-developers.com/showthread.php?t=1829729 but without any luck - at the end I managed to flash the kernel from this thread here, and then followed the procedure as described above - all seems good and superuser seems to be giving permission to applications - alas no luck.
I can even upload the ftf file if needed. all else seems to be running fine (some slowdowns though - lag or smth - was not present with 162.)
Click to expand...
Click to collapse
i would recommend to flash the ftf file you generated from the cache and then flash the kernel i provided. had serveral issues with the kernel you are referencing to, my sd card corrupted with it and i had to start from scratch

---

krachlatte said:
i would recommend to flash the ftf file you generated from the cache and then flash the kernel i provided. had serveral issues with the kernel you are referencing to, my sd card corrupted with it and i had to start from scratch
Click to expand...
Click to collapse
will backup first (since it's my fiancee's phone I don't really wanna lose all contact photos (again)) and then will post results. Thanks.

---

wbgenetic said:
I can even upload the ftf file if needed.
Click to expand...
Click to collapse
Here are the checksums for the FTF I got from decrypting the firmware downloaded by PC Companion:
CRC-32: d65b0f0f
MD4: e2b001459ef3818cb68c323b6c8fdc38
MD5: 3a35a92ff63c13701637dff2a9019d7c
SHA-1: 310b4b677666ce8a0074ac48b3f29673cc61409d
It would be interesting to know if yours is different. If yes, maybe the reason for your problems is that you got a different regional firmware which is not perfectly compatible with the kernel from this thread.
Does anyone know where I can upload a 270 MB file without registering? I could try uploading my FTF (not sure it would go through, though).

---

I will run a md5 over mine later,
root checker screenshot
Gesendet von meinem Iconia A500 mit Tapatalk

---

when thinking about hashing, it does not work because the files have got a different name so the hashes will be different.
here is a screenshot with what i got from the 3 cached files when i have decrypted them with flashtool
cheers

---

krachlatte said:
I will run a md5 over mine later,
root checker screenshot
Gesendet von meinem Iconia A500 mit Tapatalk
Click to expand...
Click to collapse
when I run the root checker it runs fine - try installing busybox or try to uninstall something with root uninstaller for example

---

Lebenita said:
Here are the checksums for the FTF I got from decrypting the firmware downloaded by PC Companion:
CRC-32: d65b0f0f
MD4: e2b001459ef3818cb68c323b6c8fdc38
MD5: 3a35a92ff63c13701637dff2a9019d7c
SHA-1: 310b4b677666ce8a0074ac48b3f29673cc61409d
It would be interesting to know if yours is different. If yes, maybe the reason for your problems is that you got a different regional firmware which is not perfectly compatible with the kernel from this thread.
Does anyone know where I can upload a 270 MB file without registering? I could try uploading my FTF (not sure it would go through, though).
Click to expand...
Click to collapse
flashed it clean, followed the instructions to the point - and still - cant even run titanum backup. root checker however still says i'm root! tell me what the problem is now ... grrrr! all that happened was that I now need to rearrange all data ...
---------- Post added at 09:34 PM ---------- Previous post was at 09:30 PM ----------
here's what I get from the superuser trying to update itself or whatever to give you an example... at first it seeems to grant user rights but then ... http://a6.sphotos.ak.fbcdn.net/hphotos-ak-ash4/418841_4289626354485_1820163401_n.jpg
+ here's the folder cache I used (see attached)

---

here I hope this will help as well :
all seems fine but Root Access : no access
am I pushing a wrong SU :? what could be the reason for this ?

---

Hi,
i think i found your problem, it loosk like you did not include the loader.sin
20/014/2012 19:14:46 - INFO - Decrypting FILE_279161669
20/014/2012 19:14:59 - INFO - Decrypting FILE_279160643
20/015/2012 19:15:00 - INFO - Decrypting FILE_279066729
20/015/2012 19:15:00 - INFO - Decryption finished
20/016/2012 19:16:30 - INFO - Starting bundle creation
20/016/2012 19:16:30 - INFO - Adding loader.sin to the bundle
20/016/2012 19:16:30 - INFO - Adding kernel.sin to the bundle
20/016/2012 19:16:31 - INFO - Adding system.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding fotakernel.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding modemfs.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding partition-image.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding simlock.ta to the bundle
20/016/2012 19:16:40 - INFO - Adding prcmu.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding apps_log.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding modem.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding userdata.sin to the bundle
20/016/2012 19:16:41 - INFO - Adding cache.sin to the bundle
20/016/2012 19:16:41 - INFO - Finished bundle creation
cheers

---

krachlatte said:
Hi,
i think i found your problem, it loosk like you did not include the loader.sin
20/014/2012 19:14:46 - INFO - Decrypting FILE_279161669
20/014/2012 19:14:59 - INFO - Decrypting FILE_279160643
20/015/2012 19:15:00 - INFO - Decrypting FILE_279066729
20/015/2012 19:15:00 - INFO - Decryption finished
20/016/2012 19:16:30 - INFO - Starting bundle creation
20/016/2012 19:16:30 - INFO - Adding loader.sin to the bundle
20/016/2012 19:16:30 - INFO - Adding kernel.sin to the bundle
20/016/2012 19:16:31 - INFO - Adding system.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding fotakernel.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding modemfs.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding partition-image.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding simlock.ta to the bundle
20/016/2012 19:16:40 - INFO - Adding prcmu.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding apps_log.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding modem.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding userdata.sin to the bundle
20/016/2012 19:16:41 - INFO - Adding cache.sin to the bundle
20/016/2012 19:16:41 - INFO - Finished bundle creation
cheers
Click to expand...
Click to collapse
here we go step by step :
could be it - flashing now with all 3 files selected and making sure loader.sin is on ..
here is the log :
21/017/2012 00:17:28 - INFO - Device connected in flash mode
21/017/2012 00:17:42 - INFO - Selected Xperia GO ST27i_6.0.B.3.184_Bulgaria.ftf
21/017/2012 00:17:42 - INFO - Preparing files for flashing
21/017/2012 00:17:47 - INFO - Please connect your device into flashmode.
21/017/2012 00:17:48 - INFO - Opening device for R/W
21/017/2012 00:17:48 - INFO - Reading device information
21/017/2012 00:17:48 - INFO - Phone ready for flashmode operations.
21/017/2012 00:17:48 - INFO - Start Flashing
21/017/2012 00:17:48 - INFO - Flashing loader
21/017/2012 00:17:49 - INFO - Loader : S1_Root_3065 - Version : R5E006 / Bootloader status : ROOTED
21/017/2012 00:17:49 - INFO - Flashing partition-image.sin
21/017/2012 00:17:49 - WARN - This file is ignored : simlock.ta
21/017/2012 00:17:49 - INFO - Flashing kernel.sin
21/017/2012 00:17:50 - INFO - Flashing fotakernel.sin
21/017/2012 00:17:52 - INFO - Flashing modemfs.sin
21/017/2012 00:17:53 - INFO - Flashing prcmu.sin
21/017/2012 00:17:53 - INFO - Flashing modem.sin
21/017/2012 00:17:55 - INFO - Flashing apps_log.sin
21/017/2012 00:17:55 - INFO - Flashing system.sin
21/019/2012 00:19:36 - INFO - Log written to C:\Flashtool\flashtool_2012-08-20_12-06-56.log
21/019/2012 00:19:51 - INFO - Flashing userdata.sin
21/020/2012 00:20:02 - INFO - Flashing cache.sin
21/020/2012 00:20:03 - INFO - Ending flash session
21/020/2012 00:20:03 - INFO - Flashing finished.
21/020/2012 00:20:03 - INFO - Please wait. Phone will reboot
21/020/2012 00:20:03 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
21/020/2012 00:20:04 - INFO - Device connected in flash mode
Phone reboots after cable is unplugged and plugged in .. Once loaded I directly reboot into fastboot mode and ..time for some kernel loading ...
Fastboot mode on :
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe -i 0x0fce flash
boot "Kernel 6.0.B.184 ro.secure=0.elf"
sending 'boot' (4708 KB)...
(bootloader) USB download speed was 20606kB/s
OKAY [ 0.251s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.374s]
finished. total time: 0.636s
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe reboot
rebooting...
finished. total time: 0.005s
C:\Program Files\Android\android-sdk\platform-tools>
Phone reboots and now time to push the SU ...
I switch on USB debugging and wait till device is recognized with adb devices ....
C:\Program Files\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
CB5A1KS3PC device
Then I start running the required commands (now trying with SU 3.1.3 for arm devices). (last time it was with 3.2).
C:\Program Files\Android\android-sdk\platform-tools>adb root
adbd is already running as root
C:\Program Files\Android\android-sdk\platform-tools>adb shell id
uid=0(root) gid=0(root)
C:\Program Files\Android\android-sdk\platform-tools>adb remount
remount succeeded
C:\Program Files\Android\android-sdk\platform-tools>adb push su /system/xbin/su
2596 KB/s (85096 bytes in 0.032s)
C:\Program Files\Android\android-sdk\platform-tools>adb shell chown 0.0 /system/
xbin/su
C:\Program Files\Android\android-sdk\platform-tools>adb shell chmod 06755 /syste
m/xbin/su
C:\Program Files\Android\android-sdk\platform-tools>adb remount
remount succeeded
C:\Program Files\Android\android-sdk\platform-tools>adb install Superuser.apk
2801 KB/s (1500526 bytes in 0.523s)
pkg: /data/local/tmp/Superuser.apk
Success
C:\Program Files\Android\android-sdk\platform-tools>
Then I start testing to see If I have root or not ...
Same thing - phone says rooted -all points to rooted phone - but: in root checker I get : like on the screenshot : Root access : no access ... what could be the reason ? btw after testing with root checker - phone starts running slow as hell .. ...
(oh and here is the budle creation log:
21/011/2012 00:11:20 - INFO - Decrypting FILE_279166356
21/012/2012 00:12:01 - INFO - Decrypting FILE_279160643
21/012/2012 00:12:07 - INFO - Decrypting FILE_279066729
21/012/2012 00:12:07 - INFO - Decryption finished
21/012/2012 00:12:58 - INFO - Starting bundle creation
21/012/2012 00:12:58 - INFO - Adding loader.sin to the bundle
21/012/2012 00:12:58 - INFO - Adding kernel.sin to the bundle
21/012/2012 00:12:58 - INFO - Adding system.sin to the bundle
21/013/2012 00:13:12 - INFO - Adding fotakernel.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding modemfs.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding partition-image.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding simlock.ta to the bundle
21/013/2012 00:13:13 - INFO - Adding prcmu.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding apps_log.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding modem.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding userdata.sin to the bundle
21/013/2012 00:13:14 - INFO - Adding cache.sin to the bundle
21/013/2012 00:13:15 - INFO - Finished bundle creation
))

---

i used this su binary http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
could you upload your ftf file somewere so that i could extract your stock kernel and unlock it for you?
it looks like you got a diffrent regional image....
i also compiled a Customer kernel from sony source for the phone, i will upload this kernel later in the evening today.

---

krachlatte said:
i used this su binary http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
could you upload your ftf file somewere so that i could extract your stock kernel and unlock it for you?
it looks like you got a diffrent regional image....
i also compiled a Customer kernel from sony source for the phone, i will upload this kernel later in the evening today.
Click to expand...
Click to collapse
no problem - will upload the ftf in the evening as well - as I am not in front of the home PC right now.
** also any suggestion on backuping all settings on the phone :? I am tired of losing all settings with each flash ... and unfortunately the best backup tool I know (titanium) requires a proper root