Hello
Flashtool can be downloaded on the Flashtool Homepage (on Installation tab)
As Flashtool was originally developped for X10, you can find a lot of information on the Original X10 Flashtool thread
Major update for 0.6.8.0 : Ability to now install CWM from Flashtool on locked bootloader for LT15/LT18.
Fastboot now works fine under linux
Major new feature :
- Fastboot toolbox for 2011 line devices.
- BL Unlock for X10 Mini/PRo and X8
Please post device related issues here in this thread
But there need to be special edit for x8
jit,xrecovery and other stuff for x10 will now work on x8
Changelog:
0.2.8:
[New] The device is autodetected by the flashtool at plug / unplug
[New] If you install xRecovery from flashtool, you can reboot into recovery from flashtool too (Advanced menu)
[New] You can now backup all /system/app content (Advanced menu)
[New] You can translate all parts of the Graphical Interface (look in x10flasher_lib/langs for samples)
[Upd] Firmware screen selection offers the ability to change the folder source containing ftf files.
[Upd] Clean task now has a notion of profile that can be imported/exported for sharing
[Upd] Customize is now APK Installer. This screen has the ability to choose the folder where apk files are
[Upd] Optimize should work for any device (X10, X10mini/pro, X8)
[Upd] xRecovery should work for any device (X10, X10mini/pro, X8)
[Bug] Flashing should not anymore hang if flash goes wrong. An error should be thrown and flash aborted
Watch this
hmmm...i hope it works, cuz i ever try use the optimize/xrecovery and it isn't work also stuck on boot...but if only for flashing it's work smoothly. i'm sure bin4ry will fixed it
regards,,,
cruizz said:
hmmm...i hope it works, cuz i ever try use the optimize and it isn't work
regards,,,
Click to expand...
Click to collapse
I hope too, I don't have any X8 so I can't test it ;-)
so... if we want to use flashtool, how and where to get the firmware?
I've tried it on latest SEMC rom. My phone was already rooted though and I had xrecovery installed. After you check for root you can optimize (will put on jit) and I also installed the new xrecovery.
works for x8
Edit: Install script don't work for xRecovery. It picks the right files, but the script fails.
Code:
09/054/2011 23:54:55 - INFO - <- This level is successfully initialized
09/055/2011 23:55:02 - INFO - Connected device : E15
09/055/2011 23:55:02 - INFO - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
09/055/2011 23:55:14 - DEBUG - <- This level is successfully initialized
09/055/2011 23:55:18 - DEBUG - Pushing .\custom\root\sysrun to /data/local/tmp/sysrun
09/055/2011 23:55:18 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\sysrun /data/local/tmp/sysrun
09/055/2011 23:55:18 - DEBUG - stderr :7 KB/s (101 bytes in 0.014s)
09/055/2011 23:55:18 - DEBUG - Pushing .\custom\root\checkperms to /data/local/tmp/runscript
09/055/2011 23:55:18 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\checkperms /data/local/tmp/runscript
09/055/2011 23:55:18 - DEBUG - stderr :0 KB/s (11 bytes in 0.011s)
09/055/2011 23:55:18 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
09/055/2011 23:55:18 - DEBUG - Running .\x10flasher_lib\adb shell su -c 'sh /data/local/tmp/sysrun'
09/055/2011 23:55:19 - DEBUG - stdout :uid=0(root) gid=0(root)
09/055/2011 23:55:19 - INFO - Root Access Allowed
09/055/2011 23:55:25 - INFO - Installing xRecovery to device...
09/055/2011 23:55:25 - INFO - Remounting system read-write
09/055/2011 23:55:25 - DEBUG - Pushing .\custom\root\sysrun to /data/local/tmp/sysrun
09/055/2011 23:55:25 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\sysrun /data/local/tmp/sysrun
09/055/2011 23:55:25 - DEBUG - stderr :10 KB/s (101 bytes in 0.009s)
09/055/2011 23:55:25 - DEBUG - Pushing .\custom\root\remount to /data/local/tmp/runscript
09/055/2011 23:55:25 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\remount /data/local/tmp/runscript
09/055/2011 23:55:25 - DEBUG - stderr :15 KB/s (156 bytes in 0.010s)
09/055/2011 23:55:25 - DEBUG - Running remount as root thru sysrun
09/055/2011 23:55:25 - DEBUG - Running .\x10flasher_lib\adb shell su -c 'sh /data/local/tmp/sysrun'
09/055/2011 23:55:26 - INFO - Pushing .\custom\xRecovery\xrecoveryE15.tar.gz to /data/local/tmp/xrecovery.tar.gz
09/055/2011 23:55:26 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\xrecoveryE15.tar.gz /data/local/tmp/xrecovery.tar.gz
09/055/2011 23:55:26 - DEBUG - stderr :1611 KB/s (1270848 bytes in 0.770s)
09/055/2011 23:55:27 - INFO - Pushing .\custom\xRecovery\chargemonnew to /data/local/tmp/chargemon
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\chargemonnew /data/local/tmp/chargemon
09/055/2011 23:55:27 - DEBUG - stderr :120 KB/s (741 bytes in 0.006s)
09/055/2011 23:55:27 - INFO - Pushing .\custom\xRecovery\chargerE15 to /data/local/tmp/charger
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\chargerE15 /data/local/tmp/charger
09/055/2011 23:55:27 - DEBUG - stderr :350 KB/s (14364 bytes in 0.040s)
09/055/2011 23:55:27 - INFO - Pushing .\custom\xRecovery\sh to /data/local/tmp/sh
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\sh /data/local/tmp/sh
09/055/2011 23:55:27 - DEBUG - stderr :1012 KB/s (735308 bytes in 0.709s)
09/055/2011 23:55:27 - DEBUG - Pushing .\custom\root\sysrun to /data/local/tmp/sysrun
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\sysrun /data/local/tmp/sysrun
09/055/2011 23:55:28 - DEBUG - stderr :14 KB/s (101 bytes in 0.007s)
09/055/2011 23:55:28 - DEBUG - Pushing .\custom\root\installrecovery to /data/local/tmp/runscript
09/055/2011 23:55:28 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\installrecovery /data/local/tmp/runscript
09/055/2011 23:55:28 - DEBUG - stderr :56 KB/s (583 bytes in 0.010s)
09/055/2011 23:55:28 - INFO - Running installrecovery as root thru sysrun
09/055/2011 23:55:28 - DEBUG - Running .\x10flasher_lib\adb shell su -c 'sh /data/local/tmp/sysrun'
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - INFO - xRecovery successfully installed
hmm - 2nd time i ran the script it installed. it's the removal of the temp files that fails.
I'm happy anyways
work on any devices?
wow, that good news
thanks..
oisteink said:
I've tried it on latest SEMC rom. My phone was already rooted though and I had xrecovery installed. After you check for root you can optimize (will put on jit) and I also installed the new xrecovery.
works for x8
Click to expand...
Click to collapse
glad to hear that...ready to download
@airyz :semarange endi gan?
menuju TKP gan... ama ijin sedotnya..
what does iptimize do? Does it autoinstall jit v2 for x8? does it work? Thanks
A new version (0.5.0.0) of flashtool is here
What's new for X8 comunity : BL unlock for X8 added
Androxyde said:
A new version (0.5.0.0) of flashtool is here
What's new for X8 comunity : BL unlock for X8 added
Click to expand...
Click to collapse
Thanks!!!
Here is a small update that resolves the following issue :
Device not recognized correctly when plugged.
https://github.com/downloads/Androxyde/Flashtool/Flashtool-0.5.1.0-update.exe
After the 0.5.1 update there are still issues.
not detecting properly
v291
Code:
19/002/2011 01:02:08 - INFO - <- This level is successfully initialized
19/002/2011 01:02:12 - INFO - Connected device : E15
19/002/2011 01:02:12 - INFO - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
v051:
Code:
19/001/2011 01:01:03 - INFO - <- This level is successfully initialized
19/001/2011 01:01:06 - INFO - Device connected with USB debugging on
19/001/2011 01:01:08 - ERROR - Cannot identify your device.
19/001/2011 01:01:08 - INFO - Selecting from user input
19/001/2011 01:01:13 - INFO - Connected device : E15
19/001/2011 01:01:13 - INFO - Installed version of busybox : BusyBox v1.19.2-cm71 bionic (2011-10-06 22:08 +0200) multi-call binary.
19/001/2011 01:01:13 - INFO - Android version : 2.3.7 / kernel version : 2.6.29-Alfs
19/001/2011 01:01:13 - INFO - Root Access Allowed
It is not see my phone automagically, need choose it.
edit:
v5 is looking for
buildprop=ro.product.device
recognition=E15
v291 was looking for
ro.product.model as far I remember
We need update build.prop or change e15.properites
Edited file attached.
@rav3n_pl
Wow, replaced the e15 properties without installing the 0.5.1 update and my e15 is
detectable by flashtool ....Thank you.
rav3n_pl said:
v291
Code:
19/002/2011 01:02:08 - INFO - <- This level is successfully initialized
19/002/2011 01:02:12 - INFO - Connected device : E15
19/002/2011 01:02:12 - INFO - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
v051:
Code:
19/001/2011 01:01:03 - INFO - <- This level is successfully initialized
19/001/2011 01:01:06 - INFO - Device connected with USB debugging on
19/001/2011 01:01:08 - ERROR - Cannot identify your device.
19/001/2011 01:01:08 - INFO - Selecting from user input
19/001/2011 01:01:13 - INFO - Connected device : E15
19/001/2011 01:01:13 - INFO - Installed version of busybox : BusyBox v1.19.2-cm71 bionic (2011-10-06 22:08 +0200) multi-call binary.
19/001/2011 01:01:13 - INFO - Android version : 2.3.7 / kernel version : 2.6.29-Alfs
19/001/2011 01:01:13 - INFO - Root Access Allowed
It is not see my phone automagically, need choose it.
edit:
v5 is looking for
buildprop=ro.product.device
recognition=E15
v291 was looking for
ro.product.model as far I remember
We need update build.prop or change e15.properites
Edited file attached.
Click to expand...
Click to collapse
what is the value you have for ro.product.device ?
the recognition property can be a coma separated list of values.
for example on X10 I have :
recognition=X10,SO-01B,es209ra
the latest one (es209ra) is the value set by FXP team for CM7 on X10
Androxyde said:
what is the value you have for ro.product.device ?
the recognition property can be a coma separated list of values.
for example on X10 I have :
recognition=X10,SO-01B,es209ra
the latest one (es209ra) is the value set by FXP team for CM7 on X10
Click to expand...
Click to collapse
In build.prop we have "shakira"
anyone has checked out if on E15 BL unlock works at all with the latest update??
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
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>cd android-sdk
C:\android-sdk>cd tools
C:\android-sdk\tools>fastboot.exe -i 0x0fce oem unlock 0xFF6C0B6CABAA77A3
... INFOUnlock phone requested
FAILED (remote: Phone is already unlocked!)
C:\android-sdk\tools>
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
@x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
1869 KB/s (119636 bytes in 0.062s)
remote object '/system/bin/ric' does not exist
.
Found Sony Backup-Restore.apk
LT26,LT22 etc. mode enabled!
.
Pushing busybox....
2338 KB/s (1085140 bytes in 0.453s)
Pushing su binary ....
2874 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
2491 KB/s (996704 bytes in 0.390s)
Making busybox runable ...
.
Pushing fake Backup
2304 KB/s (73728 bytes in 0.031s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.VIEW dat=com.sonyericsson.vendor.ba
ckuprestore/.ui.BackupActivity }
Error: Activity not started, unable to resolve Intent { act=android.intent.actio
n.VIEW dat=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity flg=0x100000
00 }
If all is successful i will tell you, if not this shell will run forever.
Running ......
05/040/2012 07:40:56 - INFO - <- This level is successfully initialized
05/040/2012 07:40:56 - INFO - Flashtool Version 0.9.8.0 built on 2012-10-01 19:35:32
05/040/2012 07:40:56 - INFO - You can drag and drop ftf files here to start flashing them
05/040/2012 07:40:58 - INFO - Device connected with USB debugging on
05/040/2012 07:40:59 - INFO - Connected device : ST25
05/040/2012 07:40:59 - INFO - Installed version of busybox : N/A
05/040/2012 07:40:59 - INFO - Android version : 2.3.7 / kernel version : 2.6.35.7+ / Build number : 6.0.B.3.184
05/041/2012 07:41:02 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\.\devices\ST25\busybox\1.19.0\busybox to /data/local/tmp/busybox
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
05/041/2012 07:41:07 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
05/041/2012 07:41:07 - INFO - Running part1 of Root Exploit, please wait
05/041/2012 07:41:26 - INFO - Waiting for device. After 60secs, stop waiting will be forced
05/042/2012 07:42:30 - INFO - Forced stop waiting.
05/042/2012 07:42:30 - ERROR - The part1 exploit did not work
05/042/2012 07:42:30 - INFO - Cleaning files
I want to root my phone mainly to clean **** like facebook and other which eat ram in stock rom. After that all i dont have any icons from supersu/superuser in list. In bin4ry script nothing happen but its supposed to show backup and restore window i think.
The method works only on ICS
Tapatalked !
Ok problem solved i uploaded rooted kernel for gb. And now all works fine. Topic can be closed or go to trash, thanks for reply.