This bug is really annoying me and I can't find any posts on it in any threads.
The haptic feedback in menu and back buttons on mini doesn't work with any setting, but there is vibration in the back button for example if you're using the setting "stop app via long-press".
Why is this, and since the vibration is clearly working could someone maybe play around with the hw_config and fix it for me?
Regards
Sent from my ST15i using xda premium
Anyone?
Sent from my ST15i using xda premium
I have the same problem. My vibration works fine from incoming calls and messages but aint getting any haptic feedback from typing message or from the BACK or MENU keys.
I posted about the bug on the free xperia bugtracker site, I'll post here if I get any response over there
Sent from my ST15i using xda premium
Ok great !
Got a reply today and they adviced to reflash kernel and new baseband(64). I did this and no improvement unfortunately..
Sent from my ST15i using xda premium
yup !
also happen to me
menu and back doesn't vibrate ..tired of looking for solution
flash back to hybrom
I had same problem, but I had it for all the CyanogenMod and MiniCyanogenMod ROMs. I think it is a bug which still has to be fixed. I spent lots of time, looking for a solution but I couldn't find any.
i am having same issue..but it is not that much annoying..i get used to it..
digvijayam said:
i am having same issue..but it is not that much annoying..i get used to it..
Click to expand...
Click to collapse
Hey All,
I have been searching XDA for last couple of days,unfortunately haven't been able to root my phone till now,I've used fastboot, runme.exe,flash tool ver 0.6.7 and nothing worked:
Below are the logs for both.
Fastboot :C:\Users\Maurm\Desktop\Fastboot\fastboot>fastboot flash boot boot.img
sending 'boot' (6598 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
Flash Tool
18/037/2012 16:37:09 - INFO - <- This level is successfully initialized
18/037/2012 16:37:09 - INFO - Flashtool Version 0.6.7.0 built on 2012-01-21 17:31:40
18/037/2012 16:37:09 - INFO - You can drag and drop ftf files here to start flashing them
18/037/2012 16:37:15 - INFO - Device disconnected
18/038/2012 16:38:45 - INFO - Device connected with USB debugging off
18/038/2012 16:38:45 - INFO - For 2011 devices line, be sure you are not in MTP mode
18/038/2012 16:38:46 - INFO - Device connected with USB debugging on
18/038/2012 16:38:48 - INFO - Connected device : SK17
18/038/2012 16:38:48 - INFO - Installed version of busybox : N/A
18/038/2012 16:38:48 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
18/042/2012 16:42:17 - INFO - Pushing C:\Flashtool\.\devices\SK17\busybox\1.19.0\busybox to /data/local/tmp/busybox
18/042/2012 16:42:18 - INFO - Pushing C:\Flashtool\.\custom\root\zergrush.tar.uue to /data/local/tmp
18/042/2012 16:42:19 - INFO - Running part1 of Root Exploit, please wait
18/042/2012 16:42:39 - INFO - Waiting for device
18/043/2012 16:43:40 - INFO - Forced stop waiting.
18/043/2012 16:43:40 - INFO - Running part2 of Root Exploit
18/043/2012 16:43:40 - INFO - Running rootit2
18/043/2012 16:43:40 - ERROR - Cleaning rootit files
Mounting /system R/W
FTError
18/055/2012 16:55:45 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
18/055/2012 16:55:45 - INFO - Device Status: ADB mode
18/055/2012 16:55:49 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
18/055/2012 16:55:52 - INFO - Device will soon enter fastboot mode
18/055/2012 16:55:53 - INFO - Device disconnected
18/055/2012 16:55:55 - INFO - Device connected in fastboot mode
18/056/2012 16:56:16 - INFO - Selected kernel (boot.img or kernel.sin)
18/056/2012 16:56:16 - INFO - HotBooting selected kernel
18/056/2012 16:56:16 - INFO - FASTBOOT Output:
downloading 'boot.img'...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
18/056/2012 16:56:16 - INFO - Device should now start booting with this kernel
18/056/2012 16:56:54 - INFO - Selected kernel (boot.img or kernel.sin):
18/056/2012 16:56:54 - INFO - Flashing selected kernel
18/056/2012 16:56:54 - INFO - FASTBOOT Output:
sending 'boot' (6598 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
18/056/2012 16:56:54 - INFO - Please check the log before rebooting into system
18/057/2012 16:57:01 - INFO - Finished Fastboot Toolbox
Appreciate immediate response as I'm struggling with unresponsive behavior of this phone
Below are my phone details please help.
Xperia SK17i
Android :2.3.4
Build Number 4.0.2.A.0.62
Kernal : 2.6.32.9-perf [email protected]#1
Baseband Version:8x55A-AAABQOAZM-203028D-64
maurm said:
Hey All,
I have been searching XDA for last couple of days,unfortunately haven't been able to root my phone till now,I've used fastboot, runme.exe,flash tool ver 0.6.7 and nothing worked:
Below are the logs for both.
Fastboot :C:\Users\Maurm\Desktop\Fastboot\fastboot>fastboot flash boot boot.img
sending 'boot' (6598 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
Flash Tool
18/037/2012 16:37:09 - INFO - <- This level is successfully initialized
18/037/2012 16:37:09 - INFO - Flashtool Version 0.6.7.0 built on 2012-01-21 17:31:40
18/037/2012 16:37:09 - INFO - You can drag and drop ftf files here to start flashing them
18/037/2012 16:37:15 - INFO - Device disconnected
18/038/2012 16:38:45 - INFO - Device connected with USB debugging off
18/038/2012 16:38:45 - INFO - For 2011 devices line, be sure you are not in MTP mode
18/038/2012 16:38:46 - INFO - Device connected with USB debugging on
18/038/2012 16:38:48 - INFO - Connected device : SK17
18/038/2012 16:38:48 - INFO - Installed version of busybox : N/A
18/038/2012 16:38:48 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
18/042/2012 16:42:17 - INFO - Pushing C:\Flashtool\.\devices\SK17\busybox\1.19.0\busybox to /data/local/tmp/busybox
18/042/2012 16:42:18 - INFO - Pushing C:\Flashtool\.\custom\root\zergrush.tar.uue to /data/local/tmp
18/042/2012 16:42:19 - INFO - Running part1 of Root Exploit, please wait
18/042/2012 16:42:39 - INFO - Waiting for device
18/043/2012 16:43:40 - INFO - Forced stop waiting.
18/043/2012 16:43:40 - INFO - Running part2 of Root Exploit
18/043/2012 16:43:40 - INFO - Running rootit2
18/043/2012 16:43:40 - ERROR - Cleaning rootit files
Mounting /system R/W
FTError
18/055/2012 16:55:45 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
18/055/2012 16:55:45 - INFO - Device Status: ADB mode
18/055/2012 16:55:49 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
18/055/2012 16:55:52 - INFO - Device will soon enter fastboot mode
18/055/2012 16:55:53 - INFO - Device disconnected
18/055/2012 16:55:55 - INFO - Device connected in fastboot mode
18/056/2012 16:56:16 - INFO - Selected kernel (boot.img or kernel.sin)
18/056/2012 16:56:16 - INFO - HotBooting selected kernel
18/056/2012 16:56:16 - INFO - FASTBOOT Output:
downloading 'boot.img'...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
18/056/2012 16:56:16 - INFO - Device should now start booting with this kernel
18/056/2012 16:56:54 - INFO - Selected kernel (boot.img or kernel.sin):
18/056/2012 16:56:54 - INFO - Flashing selected kernel
18/056/2012 16:56:54 - INFO - FASTBOOT Output:
sending 'boot' (6598 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
18/056/2012 16:56:54 - INFO - Please check the log before rebooting into system
18/057/2012 16:57:01 - INFO - Finished Fastboot Toolbox
Appreciate immediate response as I'm struggling with unresponsive behavior of this phone
Below are my phone details please help.
Xperia SK17i
Android :2.3.4
Build Number 4.0.2.A.0.62
Kernal : 2.6.32.9-perf [email protected]#1
Baseband Version:8x55A-AAABQOAZM-203028D-64
Click to expand...
Click to collapse
go here:http://forum.xda-developers.com/showthread.php?t=1500226
Related
Hi experts
I'm unable to install the MiniCMSandwich kernel on my st15i. tried this method (the 2nd one via flashtool) twice or thrice but still my i'm not able to install it
http://forum.xda-developers.com/showthread.php?t=1500226
the log is this
05/000/2012 16:00:25 - INFO - <- This level is successfully initialized
05/000/2012 16:00:25 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
05/000/2012 16:00:25 - INFO - You can drag and drop ftf files here to start flashing them
05/000/2012 16:00:30 - INFO - Device disconnected
05/001/2012 16:01:25 - INFO - Device connected with USB debugging off
05/001/2012 16:01:25 - INFO - For 2011 devices line, be sure you are not in MTP mode
05/001/2012 16:01:29 - INFO - Device connected with USB debugging on
05/001/2012 16:01:29 - INFO - Connected device : ST15
05/001/2012 16:01:29 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
05/001/2012 16:01:29 - INFO - Android version : 2.3.3 / kernel version : 2.6.32.9-perf
05/001/2012 16:01:29 - INFO - Root Access Allowed
05/002/2012 16:02:15 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
05/002/2012 16:02:15 - INFO - Device Status: ADB mode
05/002/2012 16:02:16 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
05/002/2012 16:02:21 - INFO - Device will soon enter fastboot mode
05/002/2012 16:02:21 - INFO - Device disconnected
05/002/2012 16:02:23 - INFO - Device connected in fastboot mode
05/002/2012 16:02:57 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot_smultron_rc3_final.img
05/002/2012 16:02:57 - INFO - Flashing selected kernel
05/002/2012 16:02:57 - INFO - FASTBOOT Output:
sending 'boot' (6006 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
05/002/2012 16:02:57 - INFO - Please check the log before rebooting into system
05/002/2012 16:02:59 - INFO - Please wait device is rebooting into fastboot mode (via Fastboot)
05/003/2012 16:03:00 - INFO - Device will soon reboot back into fastboot mode
05/003/2012 16:03:00 - INFO - Device disconnected
05/003/2012 16:03:02 - INFO - Please wait device is rebooting into fastboot mode (via Fastboot)
05/003/2012 16:03:02 - INFO - Device connected in fastboot mode
05/003/2012 16:03:02 - INFO - Device will soon reboot back into fastboot mode
05/003/2012 16:03:02 - INFO - Device disconnected
05/003/2012 16:03:04 - INFO - Device connected in fastboot mode
05/003/2012 16:03:10 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot_smultron_rc3_final.img
05/003/2012 16:03:10 - INFO - Flashing selected kernel
05/003/2012 16:03:10 - INFO - FASTBOOT Output:
sending 'boot' (6006 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
05/003/2012 16:03:10 - INFO - Please check the log before rebooting into system
Another question how can i check the kernel is installed properly so that i can proceed to install miui ?????
Thanks
same problem in cmd also
Whne i'm trying to use the cmd method it's saying the same error. my bootloader is unlocked & the device is rooted. I can use the R/O & R/W both on root explorer. then why it's saying that "The device must be rooted first"
Please help
thanks again
Comon
Someone plz reply
Thanks
Is the phone in fastboot? Do you have drivers installed?
Sent from my WT19i using xda premium
I want to install this custom rom on xperia ray: http://forum.xda-developers.com/showthread.php?t=1825892
My phone: xperia ray ST18i
Android: 2.3.4
Kernel: 2.6.32.9
Firmware: 4.0.2.A.0.69
What steps i must do with my phone, to install that rom?
goran9888 said:
I want to install this custom rom on xperia ray: http://forum.xda-developers.com/showthread.php?t=1825892
My phone: xperia ray ST18i
Android: 2.3.4
Kernel: 2.6.32.9
Firmware: 4.0.2.A.0.69
What steps i must do with my phone, to install that rom?
Click to expand...
Click to collapse
First rule of xda is SEARCH! So search.
Second: there is a Q&A thread, ask questions there
Third: what you linked is an ICS rom, and you are on GB and i think (but you didn't wrote) you are on locked bootloader. You must upgrade to latest ics, and root it at install cwm.
Fourth: In linked thread there are a guide how to install for locked
Locked-bootloader instructions
After Root & Install CWM
1) Backup current system with CWM
1) Wipe data/factory reset
2) Wipe cache partition
3) Mounts and Storage -> format /system
4) Advanced -> Wipe Dalvik cache
5) Install zip from SD Card -> Then select MIUI ROM zip file
7) Then restore DATA only from your ROM backup
8) Restart
NOTE: the above procedure is necessary every time you install a ROM on a locked boot-loader
Click to expand...
Click to collapse
How can i upgrade to latest ICS? Do on xda have tutorial - i cant find it?
I tried like this but failed with error: http://www.youtube.com/watch?v=n9ox6CYNmac
Can i upgrade it to ICS with flashtool?
goran9888 said:
How can i upgrade to latest ICS? Do on xda have tutorial - i cant find it?
I tried like this but failed with error: http://www.youtube.com/watch?v=n9ox6CYNmac
Can i upgrade it to ICS with flashtool?
Click to expand...
Click to collapse
There is a button called search. Use it and learn by yourself.
Skickat från min ST18i via Tapatalk 2
you can update using PCC or SEUS..then you install cwm using x-parts..choose rom you want and flash according to the rom instructions..
---------- Post added at 12:24 AM ---------- Previous post was at 12:16 AM ----------
you can use flashtool and flash these .ftf file...
http://forum.xda-developers.com/showthread.php?t=1627627
Hi ...
I search forum and i find some parts.
I now have android 4.0.3, kernel 2.6.32.9-perf [email protected] #1 and build number: 4.1.A.0.562. My phone have unlocked bootloader and is rooted with this metod: http://forum.xda-developers.com/showthread.php?t=1601038
I now have SuperUser app and i am manualy install busybox, and root chacker basic who is tell that my phone is really rooted.
Problem is, when try to install this custom rom: http://forum.xda-developers.com/showthread.php?t=1989885
First, i must to flash kernel to FlyKernel JB. But problem is that flashtool display this error:
09/035/2012 17:35:35 - INFO - <- This level is successfully initialized
09/035/2012 17:35:35 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
09/035/2012 17:35:35 - INFO - You can drag and drop ftf files here to start flashing them
09/035/2012 17:35:39 - INFO - Device disconnected
09/035/2012 17:35:45 - INFO - Device connected in fastboot mode
09/035/2012 17:35:56 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
09/035/2012 17:35:56 - INFO - Device Status: ADB mode
09/036/2012 17:36:02 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\flykernel_jb_7a.img
09/036/2012 17:36:02 - INFO - Flashing selected kernel
09/036/2012 17:36:02 - INFO - sending 'boot' (5292 KB)...
09/036/2012 17:36:02 - INFO - FAILED (remote: The Device must be rooted first)
09/036/2012 17:36:02 - INFO - finished. total time: 0.001s
09/036/2012 17:36:02 - INFO - FASTBOOT Output:
sending 'boot' (5292 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
09/036/2012 17:36:02 - INFO - Please check the log before rebooting into system
09/036/2012 17:36:47 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\flykernel_jb_7a.img
09/036/2012 17:36:47 - INFO - Flashing selected kernel
09/036/2012 17:36:47 - INFO - sending 'boot' (5292 KB)...
09/036/2012 17:36:47 - INFO - FAILED (remote: The Device must be rooted first)
09/036/2012 17:36:47 - INFO - finished. total time: 0.002s
09/036/2012 17:36:47 - INFO - FASTBOOT Output:
sending 'boot' (5292 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
09/036/2012 17:36:47 - INFO - Please check the log before rebooting into system
09/036/2012 17:36:49 - INFO - Finished Fastboot Toolbox
Click to expand...
Click to collapse
And i tried with different kernel for different rom, and problem again displayed.
09/008/2012 23:08:38 - INFO - <- This level is successfully initialized
09/008/2012 23:08:38 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
09/008/2012 23:08:38 - INFO - You can drag and drop ftf files here to start flashing them
09/008/2012 23:08:47 - INFO - Device connected with USB debugging off
09/008/2012 23:08:47 - INFO - For 2011 devices line, be sure you are not in MTP mode
09/009/2012 23:09:57 - INFO - Device connected with USB debugging on
09/009/2012 23:09:58 - INFO - Connected device : ST18
09/009/2012 23:09:58 - INFO - Installed version of busybox : BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary.
09/009/2012 23:09:58 - INFO - Android version : 4.0.3 / kernel version : 2.6.32.9-perf / Build number : 4.1.A.0.562
09/011/2012 23:11:06 - INFO - Device disconnected
09/011/2012 23:11:47 - INFO - Device connected in fastboot mode
09/011/2012 23:11:53 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
09/011/2012 23:11:53 - INFO - Device Status: FASTBOOT mode
09/011/2012 23:11:57 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot_9.587c.img
09/011/2012 23:11:57 - INFO - Flashing selected kernel
09/011/2012 23:11:57 - INFO - sending 'boot' (5810 KB)...
09/011/2012 23:11:57 - INFO - FAILED (remote: The Device must be rooted first)
09/011/2012 23:11:57 - INFO - finished. total time: 0.002s
09/011/2012 23:11:57 - INFO - FASTBOOT Output:
sending 'boot' (5810 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
09/011/2012 23:11:57 - INFO - Please check the log before rebooting into system
09/012/2012 23:12:05 - INFO - Finished Fastboot Toolbox
Click to expand...
Click to collapse
i think you can try this method..
you must update to latest ICS .587
http://www.xperiatimes.com/2012/08/root-xperia-ray-404-41b0587-41b0431.html
My phone was already rooted using flashtool using 0.2.9.1 GB-ready and had unlocked bootloader. However on updating flashtool, the app tells me that my phone isn't rooted and doesn't have an unlocked bl as well. So I tried flashing it but every time I boot the device into flash mode the process stops and I get this error :
15/022/2012 19:22:13 - INFO - Please connect your device into flashmode.
15/022/2012 19:22:19 - INFO - Device connected in flash mode
15/022/2012 19:22:19 - INFO - Opening device for R/W
15/022/2012 19:22:19 - INFO - Reading device information
15/022/2012 19:22:19 - INFO - Phone ready for flashmode operations.
15/022/2012 19:22:19 - INFO - Start Flashing
15/022/2012 19:22:19 - INFO - Processing loader
15/022/2012 19:22:19 - INFO - Checking header
15/022/2012 19:22:19 - INFO - Ending flash session
15/022/2012 19:22:19 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Click to expand...
Click to collapse
Can anybody tell me the solution for this? I had xrecovery installed previously, I tried using SuperOneClick 2.3.3. Funny thing is that I can root my phone(shell root as well) and then start Flashtool 0.9.9 which will detect my phone as rooted(!).. but I can't install CWM recovery.. everytime I do so I get a process done message but if I go into Tools->Reboot->Recover->Specific Recovery all I get is a blank screen.
Now if I restart my phone after getting it rooted from superoneclick, it gets unrooted automatically! This is getting very confusing.. Can somebody help me please?
OP sorry, I have no answers, but I have the same/similar problem.
I figure if I add my information to the information you have provided we may collectively invite some comment to stair us in the direction to an answer.
OP, hope that's OK with you.
Just one thing OP, have you installed the Flashtool 0.9.9 Windows update/bug fix (assuming you're using windows)??
FlashTool-windows-0.9.9update1.zip
I am having all sorts of problems attempting to install a CM9/CM10 kernel with CWM recovery mode on my XPERIA X10i.
My end goal is to install [CM10] v4 (Torch) by: scritch007
I have an unlock??? bootloader and can root my phone. But I'm beginning to question that!!!
I have the following information provided from S1 Tool
Code:
Welcome to S1 tool.
RUNNING S1_EROM VER "R8A031"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1241-1846_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: CB537QU1MN
SEMC SIMLOCK CERTIFICATE
Elapsed:55 secs.
Using the service information menu *#*#7378423#*#* I was able to see my SIM lock was unlocked [] SIM = 0
I have installed a fresh copy of GB 2.3.3 using Flashtool 0.9.9 with additional Windows update1.
I used a 'World' GB 2.3.3 ftf see above.
I have also installed GB using Sony Ericsson Update Service (SEUS) which provides the same base OS.
[Root XPERIA X10i using FlashTool 0.9.9]
I have rooted the device using ZergRush exploit from Flashtools 0.9.9 with update patch FlashTool-windows-0.9.9update1.zip
To do this, I started the phone and enabled debug and unknown source.
With the phone still up and running and Flashtool 0.9.9 also running, I plugged in the USB cable.
I select the "My X10" option -> root -> Force ZergRush and the process then rooted the phone and the phone rebooted with root access, no problems there.
Code:
19/042/2012 11:42:06 - INFO - <- This level is successfully initialized
19/042/2012 11:42:06 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-21 23:15:59
19/042/2012 11:42:06 - INFO - You can drag and drop ftf files here to start flashing them
19/042/2012 11:42:12 - INFO - Device connected with USB debugging on
19/042/2012 11:42:12 - INFO - Connected device : X10
19/042/2012 11:42:12 - INFO - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
19/042/2012 11:42:12 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-modFXP-DooMKernel-v06 / Build number : 3.0.1.G.0.75
19/042/2012 11:42:12 - INFO - Root Access Allowed
I can also install CWM recovery this way too.
After I have gained root access I have the phone up and running and again plug the USB cable in.
I select recovery mode option in Flashtool 0.9.9 and I'm requested to power down my phone and reconnect.
This then installs a recovery mode, either CWM or xRecovery depending on which one I select.
Again, this is all good and I can boot into either xRecovery or CWM recovery depending on which is installed.
I have installed and used other versions of Flashtool, however the outcomes always seems to be the same.
If I attempt to install a CM9/CM10 ftf I get the following error message:
Code:
19/016/2012 03:16:36 - INFO - <- This level is successfully initialized
19/016/2012 03:16:36 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-21 23:15:59
19/016/2012 03:16:36 - INFO - You can drag and drop ftf files here to start flashing them
19/016/2012 03:16:42 - INFO - Device disconnected
19/016/2012 03:16:55 - INFO - Selected X10_4.1.X_CMX10_bootmanager_v14.ftf
19/016/2012 03:16:55 - INFO - Preparing files for flashing
19/016/2012 03:16:56 - INFO - Please connect your device into flashmode.
19/017/2012 03:17:45 - INFO - Device connected in flash mode
19/017/2012 03:17:46 - INFO - Opening device for R/W
19/017/2012 03:17:46 - INFO - Reading device information
19/017/2012 03:17:46 - INFO - Phone ready for flashmode operations.
19/017/2012 03:17:46 - INFO - Start Flashing
19/017/2012 03:17:46 - INFO - Processing loader
19/017/2012 03:17:46 - INFO - Checking header
19/017/2012 03:17:46 - INFO - Ending flash session
19/017/2012 03:17:46 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
19/017/2012 03:17:46 - ERROR - Error flashing. Aborted
19/017/2012 03:17:46 - INFO - Device connected in flash mode
19/017/2012 03:17:47 - INFO - Device disconnected
19/017/2012 03:17:49 - INFO - Device connected in flash mode
19/018/2012 03:18:10 - INFO - Device disconnected
19/018/2012 03:18:13 - INFO - Device connected with USB debugging off
19/018/2012 03:18:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/018/2012 03:18:23 - INFO - Device disconnected
At the moment I have just given up until I have some good leads to renew my CM9/CM10 install efforts.
At the moment I have GB 2.3.3 rooted with ZergRush exploit.
xRecovery installed
DooMLoRD DooMkernel V6 install with overclocked CPU of 1152MHz
The phone is up and running, rooted and has a modified Kernel which I recovered via xRecovery backup restore.
So, I have a working GB 2.3.3 phone with root access....but I want more...
My phone seems to be a one trick pony and I don't seem to be able to install CM9/CM10 with the information I have to hand.
Any thoughts I why I'd be getting the "SIN header verification failed" message????
********* Update **************
[ANSWER]
I solved my problem by unlocking the bootloader on my XPERIA X10i using the following information.
Tutorial: Rooting, Bootloader unlocking&updating
Remember to have debugging and Unknown source ticked on your XPERIA X10i phone.
Code:
20/015/2012 16:15:44 - INFO - Device connected with USB debugging off
20/015/2012 16:15:44 - INFO - For 2011 devices line, be sure you are not in MTP mode
20/015/2012 16:15:44 - INFO - Device connected with USB debugging on
20/015/2012 16:15:45 - INFO - Connected device : X10
20/015/2012 16:15:45 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
20/015/2012 16:15:45 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
20/015/2012 16:15:46 - INFO - Remounting system read-write
20/015/2012 16:15:46 - INFO - Installing toolbox to device...
20/015/2012 16:15:46 - INFO - Pushing C:\Program Files\Flashtools 0.8.6\Flashtool\custom\root\ftkit.tar to /data/local/tmp
20/015/2012 16:15:46 - INFO - Running installftkit as root thru sysrun
20/015/2012 16:15:47 - INFO - Root Access Allowed
20/016/2012 16:16:22 - INFO - Please connect your device into flashmode.
20/016/2012 16:16:27 - INFO - Device disconnected
20/017/2012 16:17:22 - INFO - Device connected in flash mode
20/017/2012 16:17:22 - INFO - Opening device for R/W
20/017/2012 16:17:22 - INFO - Reading device information
20/017/2012 16:17:22 - INFO - Phone ready for flashmode operations.
20/017/2012 16:17:22 - INFO - Flashing loader
[COLOR="Red"]20/017/2012 16:17:24 - INFO - Loader : S1_Loader_Root_f851 - Version : R4A024 / Bootloader status : UNROOTABLE[/COLOR]
20/017/2012 16:17:24 - INFO - Start Reading property
20/017/2012 16:17:24 - INFO - Reading TA finished.
20/017/2012 16:17:24 - INFO - Ending flash session
20/017/2012 16:17:24 - INFO - Found semcSL
20/017/2012 16:17:24 - INFO - You can now unplug and turn on device, then plug it again
20/017/2012 16:17:24 - INFO - Waiting for device
20/019/2012 16:19:39 - INFO - Device connected with USB debugging on
20/019/2012 16:19:40 - INFO - Pushing C:\Program Files\Flashtools 0.8.6\Flashtool\custom\features\UnlockBL\files\qsd8250\qsd8250bootwrite_semcSL to /data/local/tmp
20/019/2012 16:19:40 - INFO - Pushing C:\Program Files\Flashtools 0.8.6\Flashtool\custom\features\UnlockBL\files\qsd8250\mapper_2.6.29-00054-g5f01537.ko to /data/local/tmp
20/019/2012 16:19:40 - INFO - Pushing C:\Program Files\Flashtools 0.8.6\Flashtool\custom\features\UnlockBL\files\qsd8250\fixPart to /data/local/tmp
20/019/2012 16:19:40 - INFO - Running runfixPart as root thru sysrun
20/019/2012 16:19:41 - INFO - Successfully applied fixPart. Rebooting
20/019/2012 16:19:41 - INFO - Waiting for device
20/019/2012 16:19:42 - INFO - Device disconnected
20/019/2012 16:19:53 - INFO - Device connected with USB debugging off
20/019/2012 16:19:53 - INFO - For 2011 devices line, be sure you are not in MTP mode
20/019/2012 16:19:57 - INFO - Device connected with USB debugging on
20/020/2012 16:20:10 - INFO - Running runbootwrite as root thru sysrun
20/020/2012 16:20:11 - INFO - Successfully applied unlock. Rebooting
20/020/2012 16:20:11 - INFO - Running runClean as root thru sysrun
20/020/2012 16:20:13 - INFO - Device disconnected
20/020/2012 16:20:24 - INFO - Device connected with USB debugging off
20/020/2012 16:20:24 - INFO - For 2011 devices line, be sure you are not in MTP mode
20/020/2012 16:20:33 - INFO - Device disconnected
20/020/2012 16:20:36 - INFO - Device connected with USB debugging on
20/020/2012 16:20:36 - INFO - Connected device : X10
20/020/2012 16:20:36 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
20/020/2012 16:20:36 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
20/020/2012 16:20:48 - INFO - Root Access Allowed
20/023/2012 16:23:12 - INFO - Device disconnected
20/024/2012 16:24:10 - INFO - Log written to C:\Program Files\Flashtools 0.8.6\Flashtool\flashtool_2012-12-19_04-10-47.log
Don't 'freak out' when you see "Bootloader status : UNROOTABLE" scroll across the screen. My heart sunk when I saw that, but I let the first phase of the process complete and then connect the phone to the USB cable after the phone had re-booted with Flashtool 0.8.6 (in my case) still running and the process completed. In my case I got my phone back unlocked and still rooted. All good.
I'm pretty sure my bootloader was not locked when I started out a year or so ago, but I can't be absolutely sure; so somehow it's seems to have become locked during that time. Maybe because I was just recovering the same build each time I never installed anything else to check.
Like the OP, I originally rooted my phone by using 0.2.9.1 GB-ready using a convoluted process compared to todays one click root process.
Now when I flash a ftf file in Flashtool it runs through without any errors.
I was then able to go on and install [CM10] v4 (Torch) by: scritch007 without any problems.
Hope some of this information can help others.
My downloaded Flashtool has a virus. So I use the 0.9.0.0 version and it works ok.
I had the same issue too with v 0.9.9.0. for rooting I use v 0.6.8.0
i have Bricked my Xperia ion(soft brick).
And now if i plug to charger or to pc it starts rebooting ( only sony logo lights up and then become yellowish and restarts the phone,it appears i think 10-20 times and then turn off).
I can't charge because if i put to wall charger after 10 minutes it starts bootlooping and then turn off and again the led becomes red and then again it starts bootloops........:crying::crying::crying::crying::crying::crying::crying::crying:
Gaurav Vashist said:
i have Bricked my Xperia ion(soft brick).
And now if i plug to charger or to pc it starts rebooting ( only sony logo lights up and then become yellowish and restarts the phone,it appears i think 10-20 times and then turn off).
I can't charge because if i put to wall charger after 10 minutes it starts bootlooping and then turn off and again the led becomes red and then again it starts bootloops........:crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Ok, can you enter to CWM?
Plus, this is not the subforum to post this things.
Try this.
This is the forum where you can post your problem.
manudo said:
Ok, can you enter to CWM?
Plus, this is not the subforum to post this things.
Try this.
This is the forum where you can post your problem.
Click to expand...
Click to collapse
no i can't enter the cwc:crying::crying:
and for ur rom i think u should try a different name ( my opinion_)
Gaurav Vashist said:
no i can't enter the cwc:crying::crying:
and for ur rom i think u should try a different name ( my opinion_)
Click to expand...
Click to collapse
I don't have that device but there's something called "fastboot" mode that is for flashing custom kernels. I suggest that try to enter that mode, if you can... Flash a kernel for your phone and enter to CWM, if you can do that, you have done a HUGE step.
Have to update my signature, I'll build in JB not ICS, nevermind.
manudo said:
I don't have that device but there's something called "fastboot" mode that is for flashing custom kernels. I suggest that try to enter that mode, if you can... Flash a kernel for your phone and enter to CWM, if you can do that, you have done a HUGE step.
Have to update my signature, I'll build in JB not ICS, nevermind.
Click to expand...
Click to collapse
i can access fastmode but flashtool gives an error"device must be rooted first"
05/023/2014 10:23:13 - INFO - <- This level is successfully initialized
05/023/2014 10:23:14 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
05/023/2014 10:23:21 - INFO - Device disconnected
05/023/2014 10:23:43 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/023/2014 10:23:43 - INFO - Preparing files for flashing
05/023/2014 10:23:43 - ERROR - .\firmwares\prepared\userdata.sin (Access is denied)
05/023/2014 10:23:43 - INFO - Cannot open bundle. Flash operation canceled
05/024/2014 10:24:02 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/024/2014 10:24:02 - INFO - Preparing files for flashing
05/024/2014 10:24:42 - INFO - List of connected devices (Device Id) :
05/024/2014 10:24:42 - INFO - List of ADB devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:42 - INFO - List of fastboot devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:48 - INFO - Please connect your device into flashmode.
05/031/2014 10:31:42 - INFO - Device connected in fastboot mode
05/032/2014 10:32:03 - INFO - Flash canceled
05/032/2014 10:32:12 - ERROR - This action needs a connected device in ADB mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ ]
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/032/2014 10:32:25 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/033/2014 10:33:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\kernel.sin
05/033/2014 10:33:04 - INFO - Flashing selected kernel
05/033/2014 10:33:04 - INFO - sending 'boot' (3209 KB)...
05/033/2014 10:33:04 - INFO - FAILED (remote: The Device must be rooted first)
05/033/2014 10:33:04 - INFO - finished. total time: 0.008s
05/033/2014 10:33:04 - INFO - FASTBOOT Output:
sending 'boot' (3209 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.008s
and also i can't access recovery mode)
No i think there should be no issuse
Gaurav Vashist said:
i can access fastmode but flashtool gives an error"device must be rooted first"
05/023/2014 10:23:13 - INFO - <- This level is successfully initialized
05/023/2014 10:23:14 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
05/023/2014 10:23:21 - INFO - Device disconnected
05/023/2014 10:23:43 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/023/2014 10:23:43 - INFO - Preparing files for flashing
05/023/2014 10:23:43 - ERROR - .\firmwares\prepared\userdata.sin (Access is denied)
05/023/2014 10:23:43 - INFO - Cannot open bundle. Flash operation canceled
05/024/2014 10:24:02 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/024/2014 10:24:02 - INFO - Preparing files for flashing
05/024/2014 10:24:42 - INFO - List of connected devices (Device Id) :
05/024/2014 10:24:42 - INFO - List of ADB devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:42 - INFO - List of fastboot devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:48 - INFO - Please connect your device into flashmode.
05/031/2014 10:31:42 - INFO - Device connected in fastboot mode
05/032/2014 10:32:03 - INFO - Flash canceled
05/032/2014 10:32:12 - ERROR - This action needs a connected device in ADB mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ ]
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/032/2014 10:32:25 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/033/2014 10:33:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\kernel.sin
05/033/2014 10:33:04 - INFO - Flashing selected kernel
05/033/2014 10:33:04 - INFO - sending 'boot' (3209 KB)...
05/033/2014 10:33:04 - INFO - FAILED (remote: The Device must be rooted first)
05/033/2014 10:33:04 - INFO - finished. total time: 0.008s
05/033/2014 10:33:04 - INFO - FASTBOOT Output:
sending 'boot' (3209 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.008s
and also i can't access recovery mode)
No i think there should be no issuse
Click to expand...
Click to collapse
Try to post the same thing in the Xperia ION forum, since I don't own the device, there's a LOT of people that can help you.
i decided to mess around with my old wt19 so after unlocking the bootloader i wanted to install a custom rom. I have some experience with that so im not a complete newbie
I have flashed roms and unlocked bootloaders on multiple devices. I always read carefully instructions etc.
But this one gave me a headache.
After deciding to install a custom rom i had to unlock the bootloader. I had problems with fastboot recognizing the device but after an hour and a half of so of reading ad searching i managed to get it working and unlocked the bootlader.
After that i spent about 50 mnutes looking for a good kernel and after failing to flash one via fastboot i used flashtool to do it.
I used this guide
After seeing no errors i unplugged the phone and tried booting. I pressed power button, the phone vibrated but the screen was always black and nothing happened.
Long pressing power button did not reset, completely unresponsive, i had to pull the battery out to make it vibrate again uppon booting but same thing happened, no response. Flashtool no longer recognises the device the ledt doesnt light up when charging but the phone got hot during this time indicating itwas trying to do something.
After a short while,maybe the battery died, but even pulling out the battery and trying to boot again did not make any vibration indicating it was completely dead.
Kernel i flashed was kappa kernel
I tried booting to kernels cwm recovery but nothing happened.
SO im out of ideas
Any suggestions ?
This is the flashtool log
15/003/2018 16:03:43 - INFO - Flashtool Version 0.9.25.0 built on 17-06-2018 16:00:00
15/003/2018 16:03:43 - INFO - Searching for a web proxy
15/003/2018 16:03:44 - INFO - No proxy found, using direct connection
15/003/2018 16:03:44 - INFO - Syncing devices from github
15/003/2018 16:03:44 - INFO - Opening devices repository.
15/003/2018 16:03:44 - INFO - Scanning devices folder for changes.
15/003/2018 16:03:52 - INFO - Pulling changes from github.
15/003/2018 16:03:53 - INFO - Devices sync finished.
15/003/2018 16:03:53 - INFO - Loading devices database
15/003/2018 16:03:53 - INFO - Loaded 112 devices
15/003/2018 16:03:53 - INFO - Starting phone detection
15/003/2018 16:03:56 - INFO - Device disconnected
15/027/2018 16:27:11 - INFO - Device connected with USB debugging on
15/027/2018 16:27:11 - INFO - Connected device : SonyEricson Xperia Live Walkman
15/027/2018 16:27:11 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary.
15/027/2018 16:27:11 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Platform : 32bits / Build number : 4.1.B.0.587
15/027/2018 16:27:11 - INFO - Checking root access
15/027/2018 16:27:12 - INFO - Installing toolbox to device...
15/027/2018 16:27:12 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
15/027/2018 16:27:12 - INFO - Running installftkit as root thru sysrun
15/027/2018 16:27:13 - INFO - Root Access Allowed
15/027/2018 16:27:28 - INFO - Device disconnected
15/027/2018 16:27:56 - INFO - Device connected with USB debugging off
15/027/2018 16:27:56 - INFO - For 2011 devices line, be sure you are not in MTP mode
15/027/2018 16:27:58 - INFO - Device connected with USB debugging on
15/027/2018 16:27:59 - INFO - Connected device : SonyEricson Xperia Live Walkman
15/027/2018 16:27:59 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary.
15/027/2018 16:27:59 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Platform : 32bits / Build number : 4.1.B.0.587
15/027/2018 16:27:59 - INFO - Checking root access
15/028/2018 16:28:01 - INFO - Root Access Allowed
15/030/2018 16:30:40 - INFO - Now plug your device in Fastboot Mode
15/030/2018 16:30:48 - INFO - Device disconnected
15/031/2018 16:31:05 - INFO - Device connected in fastboot mode
15/031/2018 16:31:34 - INFO - Selected kernel (boot.img or kernel.sin): C:\adb\platform-tools\KaCoconut2.img
15/031/2018 16:31:34 - INFO - Flashing selected kernel
15/031/2018 16:31:36 - INFO - target didn't report max-download-size
15/031/2018 16:31:36 - INFO - sending 'boot' (5580 KB)...
15/031/2018 16:31:36 - INFO - (bootloader) USB download speed was 9186kB/s
15/031/2018 16:31:36 - INFO - OKAY [ 0.629s]
15/031/2018 16:31:36 - INFO - writing 'boot'...
15/031/2018 16:31:36 - INFO - (bootloader) Download buffer format: boot IMG
15/031/2018 16:31:36 - INFO - (bootloader) Flash of partition 'boot' requested
15/031/2018 16:31:36 - INFO - (bootloader) S1 partID 0x00000003, block 0x00000148-0x00000179
15/031/2018 16:31:36 - INFO - (bootloader) Erase operation complete, 0 bad blocks encountered
15/031/2018 16:31:36 - INFO - (bootloader) Flashing...
15/031/2018 16:31:36 - INFO - (bootloader) Flash operation complete
15/031/2018 16:31:36 - INFO - OKAY [ 1.028s]
15/031/2018 16:31:36 - INFO - finished. total time: 1.657s
15/031/2018 16:31:36 - INFO - FASTBOOT Output:
target didn't report max-download-size
sending 'boot' (5580 KB)...
(bootloader) USB download speed was 9186kB/s
OKAY [ 0.629s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000148-0x00000179
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.028s]
finished. total time: 1.657s
15/031/2018 16:31:36 - INFO - Please check the log before rebooting into system
15/032/2018 16:32:53 - INFO - Device disconnected
15/040/2018 16:40:18 - INFO - Now plug your device in Fastboot Mode
15/042/2018 16:42:29 - INFO - Failed
Click to expand...
Click to collapse