[TOOL/ST18] [UPDATE 07/01/2013] Flashtool version 0.9.10.0 - Windows / Linux / Mac

[Tunixer]

thanks U it'very useful tool

 

[chindoel]

Thank's a bunch.. i need this so muchhh....

 

[viiter]

what do i need to do, so i can connect my phone in fastboot mode and use flashtool fastboot mode to flash kernel

i am using linux mint?

 

[Androxyde]

Just wait 0.6.8 to come tomorrow with working linux fastboot

Envoyé depuis mon LT18i avec Tapatalk

 

[wut288]

Thank you very much

 

[*boy*racer*]

I have installed flash tool on Ubuntu but I don't know how to work it lol. I run the program and get the box up and stuff, but it has no fast boot drivers for my phone? It doesn't recognise my phone. What do I need to do??

Thanks

Sent from my ST18i using xda premium

 

[Androxyde]

I have installed flash tool on Ubuntu but I don't know how to work it lol. I run the program and get the box up and stuff, but it has no fast boot drivers for my phone? It doesn't recognise my phone. What do I need to do??

Thanks

Sent from my ST18i using xda premium

You must have libusb-1.0 installed and :

- udev rules to access device in R/W
Or
- Run flashtool as root

The udev rules I posted on flashtool homepages are from my ubuntu installation (11.10)

Search on ubuntu forum about udev rules if you don't know how to set it

 

[noobonxdadevelopers]

...
When I try to install drivers from FlashTool package I get error message from DPInst64.exe after unpacking all files, something like "Can't execute DPInst.exe on this version of operating system".
...
My Windows version is Seven SP1 Prof x64.
...

set compatibility mode to Windows Vista

 

[duxxyuk]

getting flashtool working in ubuntu

At first I couldn't get flashtool working under ubuntu (in my case 11.10).

Having looked around the net I came across http://www.xoomforums.com/forum/motorola-xoom-development/6513-ubuntu-fastboot.html.

Here's what I did :

First, remove any rules you already set up for your Android Device (If any), they'll be very obvious if you look in /etc/udev/rules.d/

now create a new file using the command
sudo gedit /etc/udev/rules.d/99-android.rules
Now, paste all of the rules in below below:


#Acer
SUBSYSTEM=="usb", SYSFS{idVendor}=="0502", MODE="0666"
#Dell
SUBSYSTEM=="usb", SYSFS{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", SYSFS{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", SYSFS{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", SYSFS{idVendor}=="12d1", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", SYSFS{idVendor}=="0482", MODE="0666"
#LG
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
#Pantech
SUBSYSTEM=="usb", SYSFS{idVendor}=="10A9", MODE="0666"
#Samsung
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", SYSFS{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0666"
#ZTE
SUBSYSTEM=="usb", SYSFS{idVendor}=="19D2", MODE="0666"

Save and close this file.
Change the file permissions:

sudo chmod a+r /etc/udev/rules.d/99-android.rules

Now, unplug all Android Devices...

Restart the uDev service:
sudo /etc/init.d/udev restart

now for me it worked ... I hope I helped someone out.

 

[*boy*racer*]

Umm I have android rules that I tried to set up but I continued with this method and my ubuntu doesn't recognise it still. I don't know how to delete previous android.rules as it's read only.

Any ideas?

Nothing to do with me running ics?

Sent from my ST18i using xda premium

 

[duxxyuk]

I would suggest that you start again....deleting the ubuntu udev rules is simply a question of removing the file /etc/udev/rules.d/99-android.rules and restarting the udev service... You definitely need to have the right rights (sudo must work)...

The first time you setup the rules did you add to another file in /etc/udev/rules.d/ caus if you did you'll need to remove what you added.

 

[amodeos]

hard to download

ive tried to download this new update several time but always got a problem with it. uploading.com ask me upgrade to the premium account,please use mirror for it. thanks anyway for great helping job

 

[syin16]

kernel.sin

hi guyz, hope you guyz can help me to clarify this matter

rite now im using se stock .62 rom, since it this rom, root is lost, so in order to get the root WITHOUT unlocking the bootloader, i figure i have to donwgrade rite? Here's my question

1. downgrade all of my rom, basically i have to flash the 4.0.2.A.0.42.ftf, root then flash the 4.0.2.A.0.62.ftf containing the kernel.sin from .42 rom is it?

or

2. just use the kernel.sin from .42 rom, just create an ftf bundle with that kernel.sin only

adsp.sin
amss_fs.sin
amss.sin
apps.sin
cache.sin
fota0.sin
fota1.sin
loader.sin
kernel.sin ---this is what im talking about---
system.sin
userdata.sin

 

[duxxyuk]

hi guyz, hope you guyz can help me to clarify this matter

2. just use the kernel.sin from .42 rom, just create an ftf bundle with that kernel.sin only

Normally using an unlocked bootloader one would simply use 7zip to open the ST18i_4.0.2.A.0.42_(Central-Europe).ftf file, pull out the kernel.sin then flash that using fastboot mode (hold down voldup then whilst keeping voldup pressed plug in usb - it goes blue yay!).

In your case (locked bootloader) you can flash only in "flashmode" (hold down voldown then whilst keeping voldown pressed plug in usb - it goes green yay!) I suggest that you first flash a complete .42 ftf then go about flashing the .62 ftf. BEFORE FLASHING tick the "Exclude Kernel" checkbox. IMHO that should do it.

 

[syin16]

Normally using an unlocked bootloader one would simply use 7zip to open the ST18i_4.0.2.A.0.42_(Central-Europe).ftf file, pull out the kernel.sin then flash that using fastboot mode (hold down voldup then whilst keeping voldup pressed plug in usb - it goes blue yay!).

In your case (locked bootloader) you can flash only in "flashmode" (hold down voldown then whilst keeping voldown pressed plug in usb - it goes green yay!) I suggest that you first flash a complete .42 ftf then go about flashing the .62 ftf. BEFORE FLASHING tick the "Exclude Kernel" checkbox. IMHO that should do it.

my mistake guyz, i didnt notice the box for exclude system, baseband and kernel box, what if i just flash the .42 ftf with "Exclude system and baseband"? would that work?

 

[amodeos]

I think thats will work

 

[syin16]

I think thats will work

unfortunately, it didnt work, when i downgrade the kernel only, then try to root with doomlord easy rooting from v1 till v4, still no root, gonna try to downgrade the whole rom this time
http://forum.xda-developers.com/showthread.php?t=1321582

 

[syin16]

unfortunately, it didnt work, when i downgrade the kernel only, then try to root with doomlord easy rooting from v1 till v4, still no root, gonna try to downgrade the whole rom this time
http://forum.xda-developers.com/showthread.php?t=1321582

the root is successful when i downgrade the whole rom, then i flash the .62 ftf exclude the .62 kernel, the result was root lost, the superuser app is still there but somehow the root is lost

i even bundled the .42 ftf containing only the kernel.sin but with no avail, gonna try to bundle the .62 ftf without the kernel.sin this time

for the meanwhile, anyone has any other suggestions?

 

[Taverius]

Would be really awesome if it was available somewhere else than uploaded.to ...

 

[amodeos]

yeah....please OP make mirror to another link, i cannt reach uploaded.com