[Q] Flashtools SIN header verification failed in Ubuntu

[Q] Flashtools SIN header verification failed in Ubuntu - Sony Ericsson XPERIA X10 Mini

Hey,
I downloaded and extracted Flashtools 0.9.1.0 in my Ubuntu 12.04 LTS. here is my uname:
Code:
$ uname -a
Linux danial-HP 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Then I installed both architectures packages of libusb-1.0-0
Code:
$ sudo apt-get install libusb-1.0-0 libusb-1.0-0:i386
[sudo] password for danialbehzadi:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libusb-1.0-0 is already the newest version.
libusb-1.0-0:i386 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Then I made the udev rule for usb flasher
Code:
$ cat /etc/udev/rules.d/Flashtool.rules
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
When I run the Flashtool/Flashtoolconsole as my own user there is no permission:
Code:
$ ./FlashToolConsole --action=flash --file=/home/danialbehzadi/Downloads/E10_nAa-14_2.6.29.6-nAa-14.ftf --kernel=yes --system=yes
JAVA_HOME not set. Using default value : ./x10flasher_lib/linjre64
02/016/2012 16:16:55 - INFO - <- This level is successfully initialized
02/016/2012 16:16:55 - INFO - Flashtool Version 0.9.1.0 built on 2012-08-31 00:17:29
02/016/2012 16:16:55 - INFO - Choosed /home/danialbehzadi/Downloads/E10_nAa-14_2.6.29.6-nAa-14.ftf
02/016/2012 16:16:55 - INFO - Preparing files for flashing
02/016/2012 16:16:55 - INFO - Please connect your phone in flash mode
02/017/2012 16:17:02 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:03 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:04 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:04 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:05 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:05 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:06 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:06 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:07 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:07 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:08 - ERROR - No permission on device. Add valid udev rules
.
.
.
And when i run them as root here is the output:
Code:
$ sudo ./FlashToolConsole --action=flash --file=/home/danialbehzadi/Downloads/E10_nAa-14_2.6.29.6-nAa-14.ftf --kernel=yes --system=yes
[sudo] password for danialbehzadi:
JAVA_HOME not set. Using default value : ./x10flasher_lib/linjre64
02/056/2012 15:56:48 - INFO - <- This level is successfully initialized
02/056/2012 15:56:48 - INFO - Flashtool Version 0.9.1.0 built on 2012-08-31 00:17:29
02/056/2012 15:56:48 - INFO - Choosed /home/danialbehzadi/Downloads/E10_nAa-14_2.6.29.6-nAa-14.ftf
02/056/2012 15:56:48 - INFO - Preparing files for flashing
02/056/2012 15:56:48 - INFO - Please connect your phone in flash mode
02/056/2012 15:56:56 - INFO - Opening device for R/W
02/056/2012 15:56:56 - INFO - Reading device information
[=> ] 2%
02/056/2012 15:56:56 - INFO - Phone ready for flashmode operations.
[==> ] 5%
02/056/2012 15:56:56 - INFO - Start Flashing
02/056/2012 15:56:56 - INFO - Processing loader
02/056/2012 15:56:56 - INFO - Checking header
[=====> ] 10% flashsystem.X10FlashException: ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
at flashsystem.Command.send(Command.java:129)
at flashsystem.X10flash.processHeader(X10flash.java:168)
at flashsystem.X10flash.uploadImage(X10flash.java:183)
at flashsystem.X10flash.sendLoader(X10flash.java:203)
at flashsystem.X10flash.flashDevice(X10flash.java:321)
at flashsystem.FlasherConsole.doFlash(FlasherConsole.java:201)
at gui.FlasherGUI.main(FlasherGUI.java:187)
flashsystem.X10FlashException: ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
at flashsystem.X10flash.uploadImage(X10flash.java:193)
at flashsystem.X10flash.sendLoader(X10flash.java:203)
at flashsystem.X10flash.flashDevice(X10flash.java:321)
at flashsystem.FlasherConsole.doFlash(FlasherConsole.java:201)
at gui.FlasherGUI.main(FlasherGUI.java:187)
02/056/2012 15:56:56 - INFO - Ending flash session
[======> ] 13%
02/056/2012 15:56:56 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
02/056/2012 15:56:56 - ERROR - Error flashing. Aborted
02/056/2012 15:56:56 - INFO - Log written to /home/danialbehzadi/Downloads/Programs/FlashTool/flashtool_2012-09-02_03-56-48.log
And this is the Log file /home/danialbehzadi/Downloads/Programs/FlashTool/flashtool_2012-09-02_03-56-48.log:
Code:
$ cat ~/Downloads/Programs/FlashTool/flashtool_2012-09-02_03-56-48.log
02/056/2012 15:56:48 - INFO - <- This level is successfully initialized
02/056/2012 15:56:48 - INFO - Flashtool Version 0.9.1.0 built on 2012-08-31 00:17:29
02/056/2012 15:56:48 - INFO - Choosed /home/danialbehzadi/Downloads/E10_nAa-14_2.6.29.6-nAa-14.ftf
02/056/2012 15:56:48 - INFO - Preparing files for flashing
02/056/2012 15:56:48 - INFO - Please connect your phone in flash mode
02/056/2012 15:56:56 - INFO - Opening device for R/W
02/056/2012 15:56:56 - INFO - Reading device information
02/056/2012 15:56:56 - INFO - Phone ready for flashmode operations.
02/056/2012 15:56:56 - INFO - Start Flashing
02/056/2012 15:56:56 - INFO - Processing loader
02/056/2012 15:56:56 - INFO - Checking header
02/056/2012 15:56:56 - INFO - Ending flash session
02/056/2012 15:56:56 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
02/056/2012 15:56:56 - ERROR - Error flashing. Aborted
I just searched for that and couldn't find suitable solution for this situation. In most of the cases the handset was bricked and they couldn't access the phone. but in my case, I'm using my phone without any problem, so I don't believe in un-bricking as a good solution.
My handset details are:
Code:
Model number:
X10mini
Android version:
2.3.4
Baseband version:
M76XX-TSNCJOLYM-53404015
kERNEL VERSION:
2.6.29
[email protected] #1
Mod version:
MiniCM7-2.0.2
Recovery version:
ClockworkMod v3.2.0.0.-r3 x10mini
Build number:
GRJ22
Any idea?

danialbehzadi said:
Hey,
I downloaded and extracted Flashtools 0.9.1.0 in my Ubuntu 12.04 LTS. here is my uname:
...
Any idea?
Click to expand...
Click to collapse
Did you unlock your bootloader?

SmG67 said:
Did you unlock your bootloader?
Click to expand...
Click to collapse
I don't know. Is here a way to find out that?
I'm on Minicm7 and I have ClockworkMod Recovery. Is that mean my bootloader is unlocked? If not how can I unlock that via Ubuntu?

No, you're on the stock kernel, and you have an old version of MiniCM7, from 2.1 onwards they were built on top of the nAa-gb kernel.
You can unlock your bootloader with flashtool, in the plugins section, but you have to check whether it's safe to do:
If you take the back-cover of your phone off, there's a sticker with info about your phone-model on it. It should have a timestamp on it, saying something like 10w49. the first number is the manufacturing year, the second one the manufacturing week. If it's lower than 11w29, it should be ok.
Secondly: You have to check your sim-lock certificate with S1tool, by clicking the 'identify' button in that program and following the instructions.
If at the bottom of the info-screen it says: SEMC Simlock Certificate you should be all ok. If it says Certificate not recognised, you might end up with a brick if you try the unlock.
Good luck

Tick no final verification box before flashing using flashtool
Sent from my R800i using xda premium

SmG67 said:
No, you're on the stock kernel, and you have an old version of MiniCM7, from 2.1 onwards they were built on top of the nAa-gb kernel.
You can unlock your bootloader with flashtool, in the plugins section, but you have to check whether it's safe to do:
If you take the back-cover of your phone off, there's a sticker with info about your phone-model on it. It should have a timestamp on it, saying something like 10w49. the first number is the manufacturing year, the second one the manufacturing week. If it's lower than 11w29, it should be ok.
Secondly: You have to check your sim-lock certificate with S1tool, by clicking the 'identify' button in that program and following the instructions.
If at the bottom of the info-screen it says: SEMC Simlock Certificate you should be all ok. If it says Certificate not recognised, you might end up with a brick if you try the unlock.
Good luck
Click to expand...
Click to collapse
Thanks dude
My handset's timestamp was 10w50 and it was OK, but I couldn't find S1tool for Ubuntu to check your sim-lock certificate, So I risked my phone and unlocked bootloader via the plugins menu of Flashtool Everything worked fine and I flashed the kernel and then the MiniCM7-2.2.1 ROM without any problem.
But there is sth I wonder about that. After I upgraded the ROM, When I connect the handset to my computer with USB, The Flashtool says:
07/012/2012 04:12:52 - INFO - Device connected with USB debugging off
07/012/2012 04:12:52 - INFO - For 2011 devices line, be sure you are not in MTP mode
Click to expand...
Click to collapse
But I am sure USB debugging is checked on the phone. I tried my sister's phone (Xperia mini without any changes) and it gave me the same message.
How can I fix that?

add your user group in udev rules
Then I made the udev rule for usb flasher
Code:
$ cat /etc/udev/rules.d/Flashtool.rules
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
When I run the Flashtool/Flashtoolconsole as my own user there is no permission:
Code:
$ ./FlashToolConsole --action=flash --file=/home/danialbehzadi/Downloads/E10_nAa-14_2.6.29.6-nAa-14.ftf --kernel=yes --system=yes
JAVA_HOME not set. Using default value : ./x10flasher_lib/linjre64
02/016/2012 16:16:55 - INFO - <- This level is successfully initialized
02/016/2012 16:16:55 - INFO - Flashtool Version 0.9.1.0 built on 2012-08-31 00:17:29
02/016/2012 16:16:55 - INFO - Choosed /home/danialbehzadi/Downloads/E10_nAa-14_2.6.29.6-nAa-14.ftf
02/016/2012 16:16:55 - INFO - Preparing files for flashing
02/016/2012 16:16:55 - INFO - Please connect your phone in flash mode
02/017/2012 16:17:02 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:03 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:04 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:04 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:05 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:05 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:06 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:06 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:07 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:07 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:08 - ERROR - No permission on device. Add valid udev rules
Any idea? :confused
Hi, try to add your user group in your udev rules file in :/etc/udev/rules.d/"your usb here is=Flashtool.rules ".rules
should be like this : ", GROUP="your username"
Code:
$ sudo gedit /etc/udev/rules.d/Flashtool.rules
# USB device 0x0fce:0x* (usb) Sony Ericsson devices
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce",SYSFS{idProduct}=="*", MODE="0777", GROUP="your username"
Then restart udev:
Code:
$: sudo service udev restart
udev stop/waiting
udev start/running, process 30009
that should fix it, have a try, sory for my english
Regards.

problems with bootloader and flashtool
SmG67 said:
No, you're on the stock kernel, and you have an old version of MiniCM7, from 2.1 onwards they were built on top of the nAa-gb kernel.
You can unlock your bootloader with flashtool, in the plugins section, but you have to check whether it's safe to do:
If you take the back-cover of your phone off, there's a sticker with info about your phone-model on it. It should have a timestamp on it, saying something like 10w49. the first number is the manufacturing year, the second one the manufacturing week. If it's lower than 11w29, it should be ok.
Secondly: You have to check your sim-lock certificate with S1tool, by clicking the 'identify' button in that program and following the instructions.
If at the bottom of the info-screen it says: SEMC Simlock Certificate you should be all ok. If it says Certificate not recognised, you might end up with a brick if you try the unlock.
Good luck
Click to expand...
Click to collapse
Hi i have read your explanation about the solution to that problem and i have some problems ( i wanna your help, if you can,plz) with flash other kernel and verify if i have unblocked may bootloader.
First, i have used the flashtool and received tha Error: ERROR - ERR_SEVERITY="MAJOR"ERR_CLASS="SECURITY_CLASS"ERR_DYNAMIC="SIN header verification failed. When i search in the net i find that is probably because the bootloader was blocked,
Then i tried the method that you post: 1 - Verify if was possibly the unblock with the S1 tool, Result: It was.... 2 - i utilize the msm 7227, but the error was something like: acess root denied: unable to gain acess root, inapropiate mask. And my phone is root and all functional, xrecovery installed, etc...
After this i have use the method official of SE and when i use the flashtool to complete the process, my phone aparently was unblocked because it was retorned to the factory settings. But, when i tried to flash another kernel or change the rom (with pre installed kernel e baseband) i got the same message form before:
Error: ERROR - ERR_SEVERITY="MAJOR"ERR_CLASS="SECURITY_CLASS"ERR_DYNAMIC="SIN header verification failed.
What i do? I am desesperatly...............
Thanks anyway

felpsi said:
Hi i have read your explanation about the solution to that problem and i have some problems ( i wanna your help, if you can,plz) with flash other kernel and verify if i have unblocked may bootloader.
First, i have used the flashtool and received tha Error: ERROR - ERR_SEVERITY="MAJOR"ERR_CLASS="SECURITY_CLASS"ERR_DYNAMIC="SIN header verification failed. When i search in the net i find that is probably because the bootloader was blocked,
Then i tried the method that you post: 1 - Verify if was possibly the unblock with the S1 tool, Result: It was.... 2 - i utilize the msm 7227, but the error was something like: acess root denied: unable to gain acess root, inapropiate mask. And my phone is root and all functional, xrecovery installed, etc...
After this i have use the method official of SE and when i use the flashtool to complete the process, my phone aparently was unblocked because it was retorned to the factory settings. But, when i tried to flash another kernel or change the rom (with pre installed kernel e baseband) i got the same message form before:
Error: ERROR - ERR_SEVERITY="MAJOR"ERR_CLASS="SECURITY_CLASS"ERR_DYNAMIC="SIN header verification failed.
What i do? I am desesperatly...............
Thanks anyway
Click to expand...
Click to collapse
The original SE firmware will always go through ok because it doesn't need to change the kernel-loader. Try to do everything using flashtool... Root it ( flashtool will do all the needed steps for you with appropriate instructions if needed ), after that, unlock your bootloader using the method in the plugins-menu... You should be able to flash a custom kernel after these steps.

felpsi said:
Hi i have read your explanation about the solution to that problem and i have some problems ( i wanna your help, if you can,plz) with flash other kernel and verify if i have unblocked may bootloader.
First, i have used the flashtool and received tha Error: ERROR - ERR_SEVERITY="MAJOR"ERR_CLASS="SECURITY_CLASS"ERR_DYNAMIC="SIN header verification failed. When i search in the net i find that is probably because the bootloader was blocked,
Then i tried the method that you post: 1 - Verify if was possibly the unblock with the S1 tool, Result: It was.... 2 - i utilize the msm 7227, but the error was something like: acess root denied: unable to gain acess root, inapropiate mask. And my phone is root and all functional, xrecovery installed, etc...
After this i have use the method official of SE and when i use the flashtool to complete the process, my phone aparently was unblocked because it was retorned to the factory settings. But, when i tried to flash another kernel or change the rom (with pre installed kernel e baseband) i got the same message form before:
Error: ERROR - ERR_SEVERITY="MAJOR"ERR_CLASS="SECURITY_CLASS"ERR_DYNAMIC="SIN header verification failed.
What i do? I am desesperatly...............
Thanks anyway
Click to expand...
Click to collapse
For anyone who has the same problem:
Put the logging in flashtool to Debug mode. This might help to tackle the real problem instead of getting the "there is a @#$%^error!".
This extended error states that the phone isnt unlocked properly. I had the same problem, and found that you cannot unlock it unless you first install a rooted kernel afer the initial rooting. (just use the "wrench" kernelinstaller in flashtool, and pick the FS Doomlord kernel)
(Else the unlocking wont give a error in the normal logging mode, but wont work either. When in debug it says its done, but failed to unlock due to the unrooted kernel. Even when the phone is rooted.)
Good luck.

Pantera88 said:
For anyone who has the same problem:
Put the logging in flashtool to Debug mode. This might help to tackle the real problem instead of getting the "there is a @#$%^error!".
This extended error states that the phone isnt unlocked properly. I had the same problem, and found that you cannot unlock it unless you first install a rooted kernel afer the initial rooting. (just use the "wrench" kernelinstaller in flashtool, and pick the FS Doomlord kernel)
(Else the unlocking wont give a error in the normal logging mode, but wont work either. When in debug it says its done, but failed to unlock due to the unrooted kernel. Even when the phone is rooted.)
Good luck.
Click to expand...
Click to collapse
Nope... in any case, there is no doomlord kernel for our phones What he did was trying to unlock the bootloader manually, without allowing his pc root access... Doing it all in flashtool should have done the trick.

I successfully managed using flashtool in ubuntu 12.04
RodJahLa said:
Then I made the udev rule for usb flasher
Code:
$ cat /etc/udev/rules.d/Flashtool.rules
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
When I run the Flashtool/Flashtoolconsole as my own user there is no permission:
Code:
$ ./FlashToolConsole --action=flash --file=/home/danialbehzadi/Downloads/E10_nAa-14_2.6.29.6-nAa-14.ftf --kernel=yes --system=yes
JAVA_HOME not set. Using default value : ./x10flasher_lib/linjre64
02/016/2012 16:16:55 - INFO - <- This level is successfully initialized
02/016/2012 16:16:55 - INFO - Flashtool Version 0.9.1.0 built on 2012-08-31 00:17:29
02/016/2012 16:16:55 - INFO - Choosed /home/danialbehzadi/Downloads/E10_nAa-14_2.6.29.6-nAa-14.ftf
02/016/2012 16:16:55 - INFO - Preparing files for flashing
02/016/2012 16:16:55 - INFO - Please connect your phone in flash mode
02/017/2012 16:17:02 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:03 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:04 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:04 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:05 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:05 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:06 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:06 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:07 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:07 - ERROR - No permission on device. Add valid udev rules
02/017/2012 16:17:08 - ERROR - No permission on device. Add valid udev rules
Any idea? :confused
Hi, try to add your user group in your udev rules file in :/etc/udev/rules.d/"your usb here is=Flashtool.rules ".rules
should be like this : ", GROUP="your username"
Code:
$ sudo gedit /etc/udev/rules.d/Flashtool.rules
# USB device 0x0fce:0x* (usb) Sony Ericsson devices
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce",SYSFS{idProduct}=="*", MODE="0777", GROUP="your username"
Then restart udev:
Code:
$: sudo service udev restart
udev stop/waiting
udev start/running, process 30009
that should fix it, have a try, sory for my english
Regards.
Click to expand...
Click to collapse
Hi I used the syntax in flashtool site for udev device specification
I have added the folowing line
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="*", MODE="0777"
to the end of this file
/etc/udev/rules.d/70-persistent-net.rules
hey you do not need to change these parameters indicated in green to anything else, 0fce is general I guess and * is a widechar for any device then do not change these!!!
you should use
sudo gedit /etc/udev/rules.d/70-persistent-net.rules
to be able to edit the file
then issue the following command
sudo restart udev
and its done you will be able to connect usb in flash mode

Solution is Relock bootloader. My problem is solved.
1-) Download: http://www.mediafire.com/file/g1b5j7...bootloader.ftf
2-) Flash "Xperia_Relock_bootloader.ftf" with FlashTool.
That's it.
Related link; http://forum.xda-developers.com/showthread.php?t=1134335

Related

[Q] Problem rooting WT19i Live with Walkman

Hello,
I've been trying to flash the old .58 firmware on my device in order to be able to root it.
I'm using Flashtool and followed the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=1559685
So I downloaded the .58 and when I try to connect my phone in flashmode, Flashtool says the following:
Code:
17/032/2012 09:32:48 - INFO - <- This level is successfully initialized
17/032/2012 09:32:48 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
17/032/2012 09:32:48 - INFO - You can drag and drop ftf files here to start flashing them
17/032/2012 09:32:51 - INFO - Device connected with USB debugging off
17/032/2012 09:32:51 - INFO - For 2011 devices line, be sure you are not in MTP mode
17/032/2012 09:32:55 - INFO - Selected WT19i_4.0.2.A.0.58_(1254-1868).ftf
17/032/2012 09:32:55 - INFO - Preparing files for flashing
17/032/2012 09:32:56 - INFO - Please connect your device into flashmode.
17/033/2012 09:33:01 - INFO - Device disconnected
17/033/2012 09:33:05 - INFO - Device connected in flash mode
17/033/2012 09:33:05 - INFO - Reading device information
17/033/2012 09:33:25 - INFO - Start Flashing
17/033/2012 09:33:25 - INFO - Flashing loader
17/033/2012 09:33:25 - INFO - Ending flash session
17/033/2012 09:33:25 - ERROR -
17/033/2012 09:33:25 - ERROR - Error flashing. Aborted
17/033/2012 09:33:25 - INFO - Device disconnected
17/033/2012 09:33:40 - INFO - Device connected with USB debugging off
17/033/2012 09:33:40 - INFO - For 2011 devices line, be sure you are not in MTP mode
This is the complete output.
Additional information: I am using Linux(64-bit) and installed FlashTool according to the instructions on their site. Some people say you need to install some kind of drivers? I have the android-sdk installed but I don't see any drivers in the ./drivers directory in flashtool.
Here's the terminal output:
Code:
[email protected] ~/Downloads/FlashTool $ sudo ./FlashTool
[sudo] password for andreas:
JAVA_HOME not set. Using default value : ./x10flasher_lib/linjre64
WT19i_4.0.2.A.0.58_(1254-1868).ftf
WT19i_4.0.2.A.0.58_(1254-1868).ftf
java.io.IOException: readReply : First data read request failed
at linuxlib.JUsb.readS1Device(JUsb.java:108)
at flashsystem.io.USBFlashLinux.readS1Reply(USBFlashLinux.java:55)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:45)
at flashsystem.X10flash.openDevice(X10flash.java:404)
at flashsystem.X10flash.openDevice(X10flash.java:345)
at gui.FlasherGUI$43.run(FlasherGUI.java:1058)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
at flashsystem.X10flash.processHeader(X10flash.java:181)
at flashsystem.X10flash.uploadImage(X10flash.java:196)
at flashsystem.X10flash.sendLoader(X10flash.java:225)
at flashsystem.X10flash.flashDevice(X10flash.java:317)
at gui.FlasherGUI$43.run(FlasherGUI.java:1059)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
flashsystem.X10FlashException
at flashsystem.X10flash.uploadImage(X10flash.java:217)
at flashsystem.X10flash.sendLoader(X10flash.java:225)
at flashsystem.X10flash.flashDevice(X10flash.java:317)
at gui.FlasherGUI$43.run(FlasherGUI.java:1059)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
The exceptions appear at the same time the error in flashtool comes up.
I've been trying it many times now, but I can't get it to work.
Any help is greatly appreciated. Thanks in advance.
EDIT: Using an older version of FlashTool seems to have fixed the problem. Currently flashing.

Bump
Can noone give me any advice on this? The error always happens exactly 20 seconds after connecting the phone in flashmode.

Try using in windows may solve..gud luck
Sent from my WT19i using xda premium

Report this bug at the flashtool thread

[Q] Xperia Mini Pro (SK17) howto boot device in flash mode?

Hi everyone,
I use Ubuntu 12.04 moved Flashtool on my system added the
rules to /etc/udev (checked from this Guide) and also readed this one.
With lsusb the device looks connected when even if the smartphone is
startet normal and when the device is OFF and i connect the usb cable
and press the volume down button.
It is not sure for me how i can start my device in flashmode as
it let flashtool its work with SK17i_4.0.2.A.0.62_Baseband+Kernel.ftf.
Can somebody explain me how i can proof that the device is startet
in flashmode correctly? Do it boot in a other way and show something
in flashmode or is the display after SE normaly blank?
My next step is that i like to get it updated and rooted (with this
update_4.0.2.A.0.69_SK17_PreRoot-Ex.zip one i guess). Must i transfer
this update with flashtool too? Or how can i bring this update on my device?
Flashtool dont start to flash my device (maybe becuse i have no clue
to start it correctly in flashmode). Or do i need to install an app?

steavenX said:
Hi everyone,
I use Ubuntu 12.04 moved Flashtool on my system added the
rules to /etc/udev (checked from this Guide) and also readed this one.
With lsusb the device looks connected when even if the smartphone is
startet normal and when the device is OFF and i connect the usb cable
and press the volume down button.
Click to expand...
Click to collapse
Yes, but when the device is turned off, first hold down the Volume DOWN button, then connect the cable.
steavenX said:
It is not sure for me how i can start my device in flashmode as
it let flashtool its work with SK17i_4.0.2.A.0.62_Baseband+Kernel.ftf.
Can somebody explain me how i can proof that the device is startet
in flashmode correctly? Do it boot in a other way and show something
in flashmode or is the display after SE normaly blank?
Click to expand...
Click to collapse
If you did, like I said previously, green LED lights up, display stays off and your device in flashmode.
steavenX said:
My next step is that i like to get it updated and rooted (with this
update_4.0.2.A.0.69_SK17_PreRoot-Ex.zip one i guess). Must i transfer
this update with flashtool too? Or how can i bring this update on my device?
Flashtool dont start to flash my device (maybe becuse i have no clue
to start it correctly in flashmode). Or do i need to install an app?
Click to expand...
Click to collapse
No, this has to be installed via Recovery. Recovery requires custom kernel(and unlocked bootloader) or rooted ROM(which is pointless then).
Install older firmware, .58 or older, root it and then make direct update from your phone to .62(.69 if you're in Germany).
Place your phone in flashmode, when Flashtool asks it. Make sure drivers are properly installed, no additional apps needed.

Show me the rules
Sent from my SK17a using xda premium

Thanks for your answer. I googled a little bit and found that
there was an update for flashtool released.
Code:
* 0.8.0.0 :
[b]- Fixed an issue with flashing ftf under linux (specially ubuntu 12.04) [/b]
- Fixed system app backup when ls applet used to enumerate system apps is busybox one with colorization
- Added a kernel.sin extractor (ELF Extractor) to get image, ramdisk and rpm.bin on 2012 devices
- Added a Sin editor which is only capable of extracting data part from sin files for the moment.
- Added drivers for Xperia U, Sola, P
- Added Xperia U, Sola, P recognition (thanks to krabappel2548)
I had lost my mind and was a little bit before driveing crazy because there was no reason that i could found as reason because it dont work ...
Cross fingers that hopefully the newer version will work
@ChavitoArg
~# cat /etc/udev/rules.d/99-android.rules
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="6166", MODE="0777"
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="e166", MODE="0777"
Do you see any thing wrong? Or do you need the rules self?

30/005/2012 23:05:54 - INFO - <- This level is successfully initialized
30/005/2012 23:05:54 - INFO - Flashtool Version 0.8.0.0 built on 2012-05-27 18:20:39
30/005/2012 23:05:54 - INFO - You can drag and drop ftf files here to start flashing them
30/005/2012 23:05:57 - INFO - Device disconnected
30/006/2012 23:06:34 - INFO - Selected SK17i_4.0.2.A.0.62_Baseband+Kernel.ftf
30/006/2012 23:06:34 - INFO - Preparing files for flashing
30/006/2012 23:06:35 - INFO - Please connect your device into flashmode.
30/006/2012 23:06:55 - INFO - Device connected in flash mode
30/006/2012 23:06:55 - INFO - Opening device for R/W
30/006/2012 23:06:55 - INFO - Reading device information
30/006/2012 23:06:55 - INFO - Phone ready for flashmode operations.
30/006/2012 23:06:55 - INFO - Start Flashing
30/006/2012 23:06:55 - INFO - Flashing loader
30/006/2012 23:06:58 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTABLE
30/006/2012 23:06:58 - INFO - Flashing kernel.sin
30/007/2012 23:07:02 - INFO - Flashing fota1.sin
30/007/2012 23:07:03 - INFO - Flashing fota0.sin
30/007/2012 23:07:04 - INFO - Flashing adsp.sin
30/007/2012 23:07:08 - INFO - Flashing amss_fs.sin
30/007/2012 23:07:08 - INFO - Flashing amss.sin
30/007/2012 23:07:22 - INFO - Flashing apps_log.sin
30/007/2012 23:07:22 - INFO - Ending flash session
30/007/2012 23:07:22 - INFO - Flashing finished.
30/007/2012 23:07:22 - INFO - Please wait. Phone will reboot
30/007/2012 23:07:22 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
30/007/2012 23:07:22 - INFO - Device connected in flash mode
30/009/2012 23:09:02 - INFO - Device disconnected
Click to expand...
Click to collapse
My smartphone did not automaticly reboot. After a couple mins i did it manual, and it boot with my current / old android ...
When i select the Firmware to flash are there a couple *.sin files in the firmware content files? I selected all and hope that was correctly.

steavenX said:
My smartphone did not automaticly reboot. After a couple mins i did it manual, and it boot with my current / old android ...
When i select the Firmware to flash are there a couple *.sin files in the firmware content files? I selected all and hope that was correctly.
Click to expand...
Click to collapse
Phone is restarted to flashmode. Disconnect and power it up yourself.
The ftf file, that you used, was only kernel and baseband(no system, no data - no ROM itself), not the whole package. Download full ftf file and try again.
These .sin files are just shown, you don't have to choose anything there.
Sent from my Xperia Live using xda premium

I just want to let you know that it workd fine for me with flashtool v8 to root android gb. Now i try to get it working with ICS
Thanks for the help and sorry - i missed to drop a short note here.
Mostly i have some trouble because i have no native windows system - i love my linux system too much
With Flashtool Version 0.8.0.0 i am currently unable to flash a ST18i rootable kernel on my xperia mini pro. I hope v.9.5 will work *cross fingers*
flashsystem.X10FlashException: ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="IMAGE_ADDRESS_RANGE";ERR_DYNAMIC="SIN-block eraseblock mismatch";
at flashsystem.Command.send(Command.java:130)
at flashsystem.X10flash.uploadImage(X10flash.java:207)
at flashsystem.X10flash.sendImages(X10flash.java:275)
at flashsystem.X10flash.flashDevice(X10flash.java:334)
at gui.FlasherGUI$45.run(FlasherGUI.java:1094)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
flashsystem.X10FlashException: ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="IMAGE_ADDRESS_RANGE";ERR_DYNAMIC="SIN-block eraseblock mismatch";
at flashsystem.X10flash.uploadImage(X10flash.java:217)
at flashsystem.X10flash.sendImages(X10flash.java:275)
at flashsystem.X10flash.flashDevice(X10flash.java:334)
at gui.FlasherGUI$45.run(FlasherGUI.java:1094)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
Click to expand...
Click to collapse

steavenX said:
I just want to let you know that it workd fine for me with flashtool v8 to root android gb. Now i try to get it working with ICS
Thanks for the help and sorry - i missed to drop a short note here.
Mostly i have some trouble because i have no native windows system - i love my linux system too much
With Flashtool Version 0.8.0.0 i am currently unable to flash a ST18i rootable kernel on my xperia mini pro. I hope v.9.5 will work *cross fingers*
Click to expand...
Click to collapse
Maybe better root with that method, it should work. And some people reported, that their devices bricked while flashing neo kernel...

Just a final note ...
With the updated flashtool version it worked fine.

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

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

[Q] Flash Sola back to .10 (Drivers trouble)

Hello,
I was trying to root my sola so to solve the wifi bug.
I found i need to flash it back from .54 to .10 using flashtool
Although, i am not being able to do it as I get a error message regarding drivers
What I do is I install flashtool on c:
I go to the drivers folder and execute Flashtool-drivers.exe and I install the Sola Drivers as well as the Flashboot and Fastboot drivers.
I open flashboot, select the .10 kernel, press flash, it tells me to turn off my sola and run it at flash mode (Volume down + USB) and then it gives me Drivers error message...
Can anyone help me?
08/041/2013 16:41:58 - INFO - <- This level is successfully initialized
08/041/2013 16:41:59 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
08/042/2013 16:42:05 - INFO - Device connected with USB debugging on
08/042/2013 16:42:07 - INFO - Connected device : Sony Xperia Sola
08/042/2013 16:42:07 - INFO - Installed version of busybox : N/A
08/042/2013 16:42:07 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
08/042/2013 16:42:13 - INFO - List of connected devices (Device Id) :
08/042/2013 16:42:13 - INFO - - USB\VID_0FCE&PID_6173&MI_01\7&37E26950&0&0001 Driver installed : true
08/042/2013 16:42:13 - INFO - - USB\VID_0FCE&PID_6173&MI_00\7&37E26950&0&0000 Driver installed : true
08/042/2013 16:42:13 - INFO - - USB\VID_0FCE&PID_6173\BX9033RP3D Driver installed : true
08/042/2013 16:42:13 - INFO - List of ADB devices :
08/042/2013 16:42:13 - INFO - - BX9033RP3D
08/042/2013 16:42:13 - INFO - List of fastboot devices :
08/042/2013 16:42:13 - INFO - - none

This not flash mode, you device must be powered off to connect in flash mode.

ChikeD said:
This not flash mode, you device must be powered off to connect in flash mode.
Click to expand...
Click to collapse
Ahhh.
that was it. i must connect first of all in flash mode...
Ok. I did it.
Anyway now I got this message:
08/002/2013 18:02:25 - ERROR - Error in processHeader : 995 : A operação de E/S was cancelled due to a module exit or an application request.
08/002/2013 18:02:25 - ERROR - Error flashing. Aborted
08/002/2013 18:02:25 - INFO - Device disconnected

haloboyscp said:
Ahhh.
that was it. i must connect first of all in flash mode...
Ok. I did it.
Anyway now I got this message:
08/002/2013 18:02:25 - ERROR - Error in processHeader : 995 : A operação de E/S was cancelled due to a module exit or an application request.
08/002/2013 18:02:25 - ERROR - Error flashing. Aborted
08/002/2013 18:02:25 - INFO - Device disconnected
Click to expand...
Click to collapse
I saw the Error in processHeader before, not sure if the same number, and it was also driver issue I think.
Can you post the whole log?

ChikeD said:
I saw the Error in processHeader before, not sure if the same number, and it was also driver issue I think.
Can you post the whole log?
Click to expand...
Click to collapse
I already got that.
that was just because i was running on flashloader 64, i switched for normal flashloader and it ran.
I think now i have done the whole thing for rooting the phone, though... Using Es File Explorer, I go to root there and it's still nothing there.
When i flashed back from the .10 to .54 it was written 08/011/2013 19:11:27 - INFO - Loader : S1_Root_3065 - Version : R5E003 / Bootloader status : ROOTABLE
so everything should have been ok?
:S
Thanks guys

Now I flash the phone, everything works.
I flash back to .10.
I try to root and get an error message like.
Could not restore. reconnect external memory and try again
I read it would be because the phone wasnt flashed on .10 but i do that...
What can it be?
Thanks

Problems after update Xperia M2 to Kitkat 4.4.2

Well, flashing the phone was succesfull. But now I have no chance to unlock the bootloader after *#*#7378423#*#* it says "Bootloader Unlock: No" on the other hand he don´t accept the USB drivers on the Build 18.3.C.0.37, installed over Android SDK Manager and Sony PC Companion. I become two unknown devices and a connection via MTP so i can´t try it a second time ?? any ideas.
Update: After some trys ... after *#*#7378423#*#* I don´t become information, I only can "Reset Customizacion", so I give it a nother try and Xperia Flashing Tool says
02/038/2014 22:38:54 - INFO - Root Access Allowed
02/040/2014 22:40:29 - INFO - Cannot open bundle. Flash operation canceled
Update2:
After I have exclude:
Bootbundle
Partition
Kernel
Fota
Baseband
System
Elabel
02/057/2014 22:57:57 - INFO - Device disconnected
02/058/2014 22:58:33 - INFO - Opening device for R/W
02/058/2014 22:58:33 - INFO - Start Flashing
02/058/2014 22:58:33 - INFO - Processing loader.sin
02/058/2014 22:58:33 - INFO - Checking header
02/058/2014 22:58:33 - INFO - Ending flash session
02/058/2014 22:58:33 - ERROR -
02/058/2014 22:58:33 - ERROR - Error flashing. Aborted
02/058/2014 22:58:33 - ERROR - Drivers need to be installed for connected device.
02/058/2014 22:58:33 - ERROR - You can find them in the drivers folder of Flashtool.
defentily the USB Drivers ....
but I have tried it over SDK over Sony Companion and download and install them manually
by the way its a little bit strange
NEED HELP

OK ... I have solved the problem ... can be closed or deleted :laugh:

Better Mobile App

welcome