Related
This has been solved! Check at bottom for solution!
I have been looking around to find a way to unlock it simply, but nothing was possible.
I've enabled all development settings, it's SEMC SIMLOCK, it's still on R, I've even moved to other rom to try it to make it work, disabled AV, firewall, installed drivers, everything but NOTHING worked.
Here are logs (Flashtool 0.6.7.0 and generic msm7227 cmd file):
Code:
18/010/2012 01:10:57 - INFO - <- This level is successfully initialized
18/010/2012 01:10:58 - INFO - Flashtool Version 0.6.7.0 built on 2012-01-15 22:00:21
18/011/2012 01:11:06 - INFO - Device connected with USB debugging off
18/011/2012 01:11:06 - INFO - For 2011 devices line, be sure you are not in MTP mode
18/011/2012 01:11:08 - INFO - List of connected devices (Device Id) :
18/011/2012 01:11:08 - INFO - - USB\VID_0FCE&PID_2138\4342353131534C4E5235 Driver installed : true
18/011/2012 01:11:08 - INFO - - USB\VID_0FCE&PID_2138&MI_01\6&1A726446&0&0001 Driver installed : true
18/011/2012 01:11:08 - INFO - - USB\VID_0FCE&PID_2138&MI_00\6&1A726446&0&0000 Driver installed : true
18/011/2012 01:11:08 - INFO - List of ADB devices :
18/011/2012 01:11:09 - INFO - - 4342353131534C4E5235
[B]18/011/2012 01:11:09 - INFO - - emulator-5554[/B] [I]< What the hell is this!?[/I]
18/011/2012 01:11:09 - INFO - List of fastboot devices :
18/011/2012 01:11:09 - INFO - - none
Code:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Waiting ...
error: more than one device and emulator
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights
.
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Waiting ...
error: more than one device and emulator
Getting ROOT rights.
error: more than one device and emulator
Waiting ...
error: more than one device and emulator
Writing patched semcboot. Two step process
First, we need get access to semcboot area
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Second, we need to write semcboot ;)
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Press any key to continue . . .
I really want to know how to fix this damn thing because I've wasted 5 HOURS ON THIS and NOTHING WORKED.
Here's solution: Run CMD, and run adb -e reboot (forces all emulators to reboot), and make sure you don't have any other emulators by running command "adb devices". You'll have to check 3-4 times to be sure by terminating idle adb.exe in task manager.
Hi mates¡
First of all, sorry for my english.
I didnt want open a thread for my issue but i cant find anthing thath work for me. I began to comment the issue at Pandemic's thread (it's the guide that I below to flash). When I read the answers is like my problem is so weird...
Well, my setup:
* Neo Mt15i with 0.62 stock
* Pc with a clean installation of Ubuntu 12.04
* I installed Java JDK with this Guide:
http://forums.team-nocturnal.com/showthread.php/772
* I installed ADB with that:
http://forums.team-nocturnal.com/showthread.php/773
After that, I add tu /udev/rules/ with my IDVENDOR and IDPRODUCT (I get it using the terminal using "$ lsusb". I readed it from a guide at XDA but cant find now, later I will edit this and add the link ) the line from flashtool web:
Add these rules to /etc/udev :
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
Click to expand...
Click to collapse
Click to expand...
Click to collapse
* Download Flashtool 0.6.9.1;M check Md5 (OK) and extrac in home folder (my user folder)
* Download 2 differents files of firmware 0.42 GLOBAL for MT15i; I cant find the MD5 of those
PROCESS
Well, doing all of that Flashtool can recognise my Neo ON with Usb debbuging ON; third applications ON; MSC ON
FLASHTOOL LOG:
02/058/2012 11:58:14 - INFO - <- This level is successfully initialized
02/058/2012 11:58:14 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:43:11
02/058/2012 11:58:14 - INFO - You can drag and drop ftf files here to start flashing them
02/058/2012 11:58:19 - INFO - Device disconnected
02/058/2012 11:58:28 - INFO - Device connected with USB debugging off
02/058/2012 11:58:28 - INFO - For 2011 devices line, be sure you are not in MTP mode
02/058/2012 11:58:29 - INFO - Device connected with USB debugging on
02/058/2012 11:58:30 - INFO - Connected device : MT15
02/058/2012 11:58:30 - INFO - Installed version of busybox : N/A
02/058/2012 11:58:30 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
Click to expand...
Click to collapse
Afterthat click flash; select Firmware (on fw folder) and connect the phone on FLASHMODE when the prompt order and thats its my LOG:
02/058/2012 11:58:54 - INFO - Device disconnected
02/059/2012 11:59:10 - INFO - Selected MT15i_4.0.2.A.0.42_Global.ftf
02/059/2012 11:59:10 - INFO - Preparing files for flashing
02/059/2012 11:59:12 - INFO - Please connect your device into flashmode.
02/059/2012 11:59:17 - INFO - Device connected in flash mode
02/059/2012 11:59:17 - INFO - Phone ready for flashmode operations.
02/059/2012 11:59:17 - INFO - Start Flashing
02/059/2012 11:59:17 - INFO - Flashing loader
02/059/2012 11:59:19 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : NOT_ROOTABLE
02/059/2012 11:59:19 - INFO - Flashing adsp.sin
02/059/2012 11:59:23 - INFO - Ending flash session
02/059/2012 11:59:39 - ERROR - Transferred 41472 bytes of 65536
02/059/2012 11:59:39 - ERROR - Error flashing. Aborted
02/059/2012 11:59:40 - INFO - Device disconnected
Click to expand...
Click to collapse
I must to unplug the NEO because it dont work. When I do this LOG its the 10 time i tried, and never works, even I wait for half hour. Thats because I didnt wait this time, always its the same...
I will update that with SCREENSHOTS later... For a easier understanding.
* I must use a virtual machine to install SEUS or PCCOMPANION, because of that I create that with VIRTUAL BOX and install winXP. I try flashtool here too.
I installed JavaJDK; SDK; DRIVERS from drivers folder of Flashtool.
No works either...The same result
I think to create another VM with win7 to try on that but i will do it later.
Thats all my problem, i dont know what more I can do...Could you help me??
Many many thanks for all those wath read the long text and dont get tired of my english.
Your udev rules is flaky, flashtool is a more than just adb.
Use the one from here
http://forum.xda-developers.com/showthread.php?p=25511424
Also don't connect the phone till it tells you
Sent from my MT11i using Tapatalk
Thanks for the fast answer.
In the link that you wrote before there are another link of minus,and those are dead links...
My android rules in udev have more info, I copy that of the link I posted before about install ADB. At final of these links I write that one of FLAHTOOL web. I found another three lines to write here but im not at pc and I havent the links here... This three lines was writed for a Spanish xdader at a thread its the only thing I remember.
Later I will post the link and my android rules.
Any idea for now?
Sent from my MT15i using XDA
The link is not dead, click standard view, then back then refresh it will work
Sent from my MT11i using Tapatalk
Sorry men, its true, I check ir fast and didnt think too much...tomorrow I will try them on pc.
I will search info about these files because I dont know anything,
There are another thread talking about them, or an howto install them?? Im not at pc and search here its worth....
Im so noob at linux too
But I learn fast when something its interesting to me, and ubuntu surprise so much to me.
Many many thanks for your help
Sent from my MT15i using XDA
which language installed on your ubuntu is it non-english
exactly flashtool have some issues on non-english OS
you can put this line on flashtool executable file
export LANG=en_US.UTF-8
than flashtool will work fine
EDIT:flashtool was updated to 0.7.1.0 you can get it from here
mpiekp said:
The link is not dead, click standard view, then back then refresh it will work
Sent from my MT11i using Tapatalk
Click to expand...
Click to collapse
I change my android.rule file, I put yours one. Continue cant flashing, and when I connect with the phone ON Flashtool recognise it, and ADB too (with "$ adb devices").
The first one I have was three lines (one/conecction mode) which I get from this thread:
http://forum.xda-developers.com/showthread.php?t=1612273
Thats one is my actual 99-android.rules
http://tinypaste.com/91108a48
yacloo said:
which language installed on your ubuntu is it non-english
exactly flashtool have some issues on non-english OS
you can put this line on flashtool executable file
export LANG=en_US.UTF-8
than flashtool will work fine
EDIT:flashtool was updated to 0.7.1.0 you can get it from here
Click to expand...
Click to collapse
Thanks men, I have spanish language installed on Ubuntu, and i havent any idea of where I have to put that line of code when I open it with gEdit.
could I change my language now for that?
I see now that always that I unplugg the phone flashtool first say that is in Usb debuging OFF and then says thats its ON,,,I saw it on other thread (which i cant found for now)
With the new version of Flashtool i have always the same problem:
04/000/2012 05:00:01 - INFO - <- This level is successfully initialized
04/000/2012 05:00:01 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/000/2012 05:00:01 - INFO - You can drag and drop ftf files here to start flashing them
04/000/2012 05:00:01 - INFO - Device disconnected
04/000/2012 05:00:11 - INFO - Selected MT15i_4.0.2.A.0.42_Vodafone.ftf
04/000/2012 05:00:11 - INFO - Preparing files for flashing
04/000/2012 05:00:11 - INFO - Please connect your device into flashmode.
04/000/2012 05:00:16 - INFO - Device connected in flash mode
04/000/2012 05:00:17 - INFO - Reading device information
04/000/2012 05:00:37 - INFO - Start Flashing
04/000/2012 05:00:37 - INFO - Flashing loader
04/000/2012 05:00:37 - INFO - Ending flash session
04/000/2012 05:00:37 - ERROR -
04/000/2012 05:00:37 - ERROR - Error flashing. Aborted
04/000/2012 05:00:37 - INFO - Device disconnected
Click to expand...
Click to collapse
With olders flashtools have same issues that before, starts but stops randomly...nothing changes after all...for now I hope.
The ways off today:
* 3 FTF 0.42 global and vodafone for MT15i
* 3 versions of FLASHTOOL (all with md5 OK)
* Repeat after fail, dont use before SEUS
* Ubuntu and Winxp on VM
Thanks for all the support
pollolpc said:
Thanks men, I have spanish language installed on Ubuntu, and i havent any idea of where I have to put that line of code when I open it with gEdit.
could I change my language now for that?
Click to expand...
Click to collapse
open FlashTool file and your file must look like this
#!/bin/sh
export BASEDIR=$(dirname $0)
export system64=$(uname -m)
export LANG=en_US.UTF-8
if test -z "${JAVA_HOME}"
then
if test "${system64}" = "x86_64"
then
export JAVA_HOME=${BASEDIR}/x10flasher_lib/linjre64
else
export JAVA_HOME=${BASEDIR}/x10flasher_lib/linjre32
fi
echo "JAVA_HOME not set. Using default value : ${JAVA_HOME}"
fi
chmod 755 ${BASEDIR}/x10flasher_lib/adb.linux
chmod 755 ${BASEDIR}/x10flasher_lib/fastboot.linux
chmod 755 ${BASEDIR}/x10flasher_lib/adb.mac
chmod 755 ${BASEDIR}/x10flasher_lib/fastboot.mac
if test -e ${JAVA_HOME}/bin/java
then
$JAVA_HOME/bin/java -Xms128m -Xmx512m -jar x10flasher.jar
else
echo "No Java in specified path in JAVA_HOME=${JAVA_HOME}"
echo "Set the variable to a valid Java installation"
fi
Click to expand...
Click to collapse
Because I didnt knew how insert that line in FLASHTOOL i tried to do other thing; change language on a terminal wich will run flashtool....i dont have idea if this is stupid....but i tried, nothing to loose i thinked....
"change the language with that :
$ export LANG=en_US.UTF-8
Click to expand...
Click to collapse
I copied the info give me the terminal, i didnt know if this could be helpful...
Post at tiny paste for a cleaner post:
http://tinypaste.com/38e38b82
yacloo said:
open FlashTool file and your file must look like this
Click to expand...
Click to collapse
Ok many many thanks, i give a try richt now
Didnt work bro, try to start flashing but stops suddenly without flash any file. Before didnt try flash, stops at READ DEVICE...
Heres the log:
http://tinypaste.com/37c68abc
Thanks a lot for your attention
pollolpc said:
Didnt work bro, try to start flashing but stops suddenly without flash any file. Before didnt try flash, stops at READ DEVICE...
Heres the log:
http://tinypaste.com/37c68abc
Thanks a lot for your attention
Click to expand...
Click to collapse
I think you are using 64-bit ubuntu
Check that libusb-1.0 is installed. On 64bits system, both 64bit and 32bit should be installed
hope can work
yacloo said:
I think you are using 64-bit ubuntu
Check that libusb-1.0 is installed. On 64bits system, both 64bit and 32bit should be installed
hope can work
Click to expand...
Click to collapse
Im usin 64 bits, yes. I think I installed them...I check Synaptics:
Uploaded with ImageShack.us
Both ticked from bottom no?
I think only 64bit libusb installed
You can get it those files for 32 bit from packages.ubuntu.com
Both files are same low versioned one for old applications
Sent from my MT11i using XDA
yacloo said:
I think only 64bit libusb installed
You can get it those files for 32 bit from packages.ubuntu.com
Both files are same low versioned one for old applications
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Im reading about this, i found that if I install 32 bits package, uninstall 64 bits....that isnt a problem? ... I found this in another forum:
http://askubuntu.com/questions/127701/gcc-m32-cannot-find-libraries
You could install the 32-bit packages for these libraries:
$ sudo apt-get install libusb-dev:i386 libX11-dev:i386
Note, however, that this will remove the 64-bit versions. Probably it's better to use a chroot (e.g. with cowbuilder or pbuilder) or Qemu image for this kind of thing. E.g. create the file ~/.pbuilderrc-precise-i386:
# Set this to the distribution you want to build for
DISTRIBUTION=precise
# The architecture you want to build for
ARCHITECTURE=i386
# The directory in which to store the chroot base image
BASEPATH=/var/cache/pbuilder/base-precise-i386.cow
# The repositories to be enabled in the /etc/apt/sources.list
COMPONENTS="main universe"
# If you want to speed things up with ccache, enable these options
export CCACHE_DIR="/var/cache/pbuilder/ccache"
export PATH="/usr/lib/ccache:${PATH}"
# List here all packages you need to build your software
# (e.g. build-essential, libusb-dev, libX11-dev, etc.)
EXTRAPACKAGES=ccache
# List here all directories from you system that should be visible inside the chroot
BINDMOUNTS="${CCACHE_DIR} ${HOME}/projects"
Then install cowbuilder and create the base image as follows:
$ sudo apt-get install cowbuilder
$ sudo cowbuilder --create --configfile ~/.pbuilderrc-precise-i386
Lastly, enter the chroot and finish configuring it (copy over configuration files:
$ sudo cowbuilder --login --save-after-exec --configfile ~/.pbuilderrc-precise-i386
You can exit the chroot using Ctrl+D or using exit. Now you have set up your base-image. In the future, don't use the --save-after-exec flag any more when entering the chroot. This ensures that all the modifications will be discarded after you leave the chroot, ensuring a clean build environment for future builds.
Now you should be able to enter the chroot and build your software:
$ sudo cowbuilder --login --configfile ~/.pbuilderrc-precise-i386
% cd $HOME/projects/foo
% # build project foo
Note, however, that the files created in this way will be owned by root. Hence, out-of-source builds are a very good idea.
Click to expand...
Click to collapse
I dont know what to do
pollolpc said:
Im reading about this, i found that if I install 32 bits package, uninstall 64 bits....that isnt a problem? ... I found this in another forum:
http://askubuntu.com/questions/127701/gcc-m32-cannot-find-libraries
I dont know what to do
Click to expand...
Click to collapse
That was ia32 lib issue install both files and ia32 lib file other 64 ones will not be removed
Sent from my MT11i using XDA
I check that with this: $ dpkg -l libusb\* and I have this versions:
||/ Nombre Versión Descripción
+++-==============-==============-============================================
ii libusb-0.1-4 2:0.1.12-20 userspace USB programming library
ii libusb-1.0-0 2:1.0.9~rc3-2u userspace USB programming library
un libusb-1.0-0-d <ninguna> (no hay ninguna descripción disponible)
un libusb0 <ninguna> (no hay ninguna descripción disponible)
ii libusbmuxd1 1.0.7-2 USB multiplexor daemon for iPhone and iPod T
Click to expand...
Click to collapse
0,1.4 is 32 bits or im wrong again?
The last version of flashtool say that:
04/015/2012 07:15:07 - INFO - <- This level is successfully initialized
04/015/2012 07:15:07 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/015/2012 07:15:07 - INFO - You can drag and drop ftf files here to start flashing them
04/015/2012 07:15:08 - INFO - Device connected with USB debugging on
04/015/2012 07:15:09 - INFO - Connected device : MT15
04/015/2012 07:15:09 - INFO - Installed version of busybox : N/A
04/015/2012 07:15:09 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
04/015/2012 07:15:09 - INFO - Phone in recovery mode
04/015/2012 07:15:09 - INFO - Root Access Allowed
WTF? Im still at 0.62 on "about"
Sorry for be worried
...I have an update avaiable ny OTA....The 0.62...and my about section sqy 0.62 too..:banghead:
Sent from my MT15i using XDA
pollolpc said:
I check that with this: $ dpkg -l libusb\* and I have this versions:
0,1.4 is 32 bits or im wrong again?
The last version of flashtool say that:
04/015/2012 07:15:07 - INFO - <- This level is successfully initialized
04/015/2012 07:15:07 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/015/2012 07:15:07 - INFO - You can drag and drop ftf files here to start flashing them
04/015/2012 07:15:08 - INFO - Device connected with USB debugging on
04/015/2012 07:15:09 - INFO - Connected device : MT15
04/015/2012 07:15:09 - INFO - Installed version of busybox : N/A
04/015/2012 07:15:09 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
04/015/2012 07:15:09 - INFO - Phone in recovery mode
04/015/2012 07:15:09 - INFO - Root Access Allowed
WTF? Im still at 0.62 on "about"
Sorry for be worried
Click to expand...
Click to collapse
download those files and install via dpkg -i *.deb
libusb-0.1-4_0.1.12-20_i386.deb
libusb-1.0-0_1.0.9~rc3-2ubuntu1_i386.deb
and you have to search on synaptic for ia32-libs and ia32-libs-multiarch
than install those packages
if doesn't work switch to 32bit ubuntu or 32bit windows for better compatibility
It's working fine here on 64 12.4
If the above doesn't work, I'll post a list of installed packages, should sort you out
Sent from my MT11i using Tapatalk
Hi guys!
My device seems to be dead.
I tried upgrading from GB2.3.4 to 2.3.6, and that's when the problem occurs.
I used ODIN 4.3.8 to flash the firm ware. But ODIN was downloading MIBIB for the past few hours.
And then, the screen appear a "Phone connecting to a PC, with a exclamation mark in between."
Any idea what has happened? In need of help desperately.
Thanks in advance.
Ben
Tried to flash cm-10.1-20130509-UNOFFICIAL
BenjaminCheng said:
Hi guys!
My device seems to be dead.
I tried upgrading from GB2.3.4 to 2.3.6, and that's when the problem occurs.
I used ODIN 4.3.8 to flash the firm ware. But ODIN was downloading MIBIB for the past few hours.
And then, the screen appear a "Phone connecting to a PC, with a exclamation mark in between."
Any idea what has happened? In need of help desperately.
Thanks in advance.
Ben
Click to expand...
Click to collapse
I also am receiving the same screen upon boot after trying to flash (cm-10.1-20130509-UNOFFICIAL) which I downloaded from a link here.
The info below is from stock mobile before crash:
Model number
GT-S5570
Android version
2.2.1
Baseband version
S5570DXKB1
Kernel version
2.6.32.9-perf
[email protected] #1
Build number
FROYO.DXKG2_______________________________
When I start my phone in recovery this is what I see:
Android System Recovery
Samsung Recovery Utils - for BML -
(then the Options are):
1) reboot system now
2) apply sdcard : update.zip
3) wipe data / factory reset
4) wipe cache partion
(Below that it reads):
#Manual Mode#
--Appling Multi - CSC--
multicsc : src /system/c
c/KOR/System/ .______________________________
Before I did flash I did a search on Sam Firmware and when it diagnosed my mobile it returned the following information:
Model : GT_S5570
Country : Open Asia
Version : Android 2.2.1
Changelist : N/A
Build date : N/A
Product Code: OLB
PDA : S5570DXKB1
CSC : S5570OLBKB1
Modem : None_____________________________
Before I proceeded with flash I installed; SuperSU and Root Checker.
I did a root diagnostic and the return was:
Root Checker
SU: su found [/system/xbin]
Version: 1.45; SUPERSU
Root Access: access granted
UID/GID: uid = 0(root)
gid = 0(root)
Unix Utils: busybox
/system/xbin/busybox
(I don’t know where busybox came from)
PATH: /system/xbin
/system/sbin
/sbin
/system/bin ____________________
Build Info from Root Checker
Board: GT-S5570
Boot Loader: Unkwn
Brand: SAMSUNG
CPU_ABI: armeabi
CPU_ABI2: Unkwn
Device: GT-S5570
Display: FROYO.DXKG2
Fingerprint: Samsung/GT-S5570/GT-S5570/GT-S5570:2.2.1/FROYO/DXKG2; - user/release-keys
Hardware: gt-s5570
Host: DELL135
ID: FROYO
Manufacturer: Samsung
Model: GT-S5570
Product: GT-S5570
Radio: Unkwn
Tags: release-keys
Type: user
Unknown: unknown
User: root______________________________________
I then proceeded to flash (cm-10.1-20130509-UNOFFICIAL), that I downloaded from a link off xda – forum.
About 3 minutes into the flash process it abruptly stopped.
I waited another 5 minutes before disconnecting the usb, then when I rebooted all I get is a screen with Phone connecting to PC with an exclamation mark between them.
If anyone can help me at this point, I would greatly appreciate your input.
Thank You for your time,
Ron Roby
Searched the forum but found nothing to fit my problem (at least no thread with a solution...)
I have an Xperia U with ICS ST25i_6.0.B.3.184_Generic_World.
Rooted, unlocked.
Was dreadfully slow and cashed all the time, so i tried to restore the factory default with the Sony Bridge for Mac.
That started, the failed mid-process and told me that he cannot communicate with the installer on the phone.
Of cause boot-up was not happening anymore after this - just a short xperia logo and then some icon telling me that it won't start.
Tried to use flashtool several times.
Flashmode starts, logs this to the console and dowsn't seem to do anything substancial afterwards:
Code:
08/028/2013 22:28:51 - INFO - (MainSWT.java:131) - Device connected in flash mode
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1020
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 35632
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 2097152 ; Partition block size : 512 ; Partition size : 1.0Gb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 4308
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 4194304 ; Partition block size : 512 ; Partition size : 2.0Gb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1438
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 32768 ; Partition block size : 512 ; Partition size : 16.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1279
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 6144 ; Partition block size : 512 ; Partition size : 3.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1069
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 256 ; Partition block size : 512 ; Partition size : 0.128Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1689
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 16384 ; Partition block size : 512 ; Partition size : 8.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1602
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 512000 ; Partition block size : 512 ; Partition size : 250.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1020
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1438
08/028/2013 22:28:51 - DEBUG - (SinFileHeader.java:96) - Sin version 2 ; Partition block count : 32768 ; Partition block size : 512 ; Partition size : 16.0Mb
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 1028
08/028/2013 22:28:51 - DEBUG - (SinFile.java:272) - Header size : 542856009
The green LED goes off after some 20 or 30 seconds and nothing happens.
Phone is stuck with the red loading-LED on and won't do anything afterwards.
Holding VolUp + Power after battry-cycling just makes the blue LED blink once and gives single vibration.
Then the phone goes into the red-LED stasis as well.
The screen doesn't show anything anymore at any time / action.
Is there still hope or will I open a second thread to ask for new phone recommendations?
Post flashtool full log with default log level(info)
IAmNice said:
Have you tried charging the phone for a few hours? Can you boot into fastboot mode? If you can try fastbooting a kernel.
Click to expand...
Click to collapse
Fastboot wont work. Although I installed the driver, rebooted, etc.
Flashtool says:
Code:
08/001/2013 23:01:57 - ERROR - (MainSWT.java:117) - Drivers need to be installed for connected device.
08/001/2013 23:01:57 - ERROR - (MainSWT.java:118) - You can find them in the drivers folder of Flashtool.
It's an XP SP3 running in a Parallels VM.
Reactions to plugging in/out are "normal" in windows terms. The usual "plig plong" and for Fastboot the little popup on the icons tray and the driver-installer popping up. Maybe I need to unload some driver or install a separate pack?
IAmNice said:
If flashtool says so I would do it.
Click to expand...
Click to collapse
I would if I could. Or if he would. Or if he would recognize it when installed
The driver installer says he did it and it doesn't change anything.
But seriously: Is there a way to see if the driver is already there, or remove and reinstall it or just manually add some package?
Bro you got a mac user here also.
Go to flashtool website and download the MAC VERSION of flashtool. Parallels/vmware is very buggy with flashtool as the device connects to the mac, needs some time to the vm. By then, the device would already time out and auto disconnect.
Sent from my LT22i using xda premium
AndroidNoob69 said:
Go to flashtool website and download the MAC VERSION of flashtool. Parallels/vmware is very buggy with flashtool as the device connects to the mac, needs some time to the vm. By then, the device would already time out and auto disconnect.
Click to expand...
Click to collapse
Ah there is a new version for mac? Neat!
So far I only found the terminal version.
That said I used the win/VM version to unlock and flash my phone - went well before.
I also have news:
I kept the phone charging over night and now it won't launch into ANY mode any more.
No Fastboot, no Flashmode. Reset doesn't do nothing.
Time to whip out the JTAG module and solder some adapters?
@brainzilla :hey mate dont worry its not a bigger problem..as you can access fastboot and flashboot so dont worry about the brick ..it is just softbrick..if possible do it in a xp sp3 system..
1.download flashtool for windows 32bit
2.install it
3.inside the installation folder you will find driver installation folder & click it
4.choose fastboot option which is just below the all options
5.connect your device to system with fastboot mod(power (+) vol+)
6.it will show to install driver ..then click it and go to advance option and then choose from hard disk
7.click f1boots driver or something which will be shown
8.then again put the device into fastboot mod
9.it will show your device in flashtool as connected in fastboot
10.Easily flash a kernel and then a custom rom and voila
---------- Post added at 08:43 PM ---------- Previous post was at 08:40 PM ----------
brainzilla said:
Ah there is a new version for mac? Neat!
So far I only found the terminal version.
That said I used the win/VM version to unlock and flash my phone - went well before.
I also have news:
I kept the phone charging over night and now it won't launch into ANY mode any more.
No Fastboot, no Flashmode. Reset doesn't do nothing.
Time to whip out the JTAG module and solder some adapters?
Click to expand...
Click to collapse
means when you are connecting to pc what is happening??are you getting any vibration when try to switch on the device??
bibhu059 said:
means when you are connecting to pc what is happening??are you getting any vibration when try to switch on the device??
Click to expand...
Click to collapse
As of this morning nothing happens anymore.
Well the charge-indicator is red when plugged in. That's it.
No vibrations, further lights or reaction from PC or Mac.
brainzilla said:
As of this morning nothing happens anymore.
Well the charge-indicator is red when plugged in. That's it.
No vibrations, further lights or reaction from PC or Mac.
Click to expand...
Click to collapse
led is getting off after sometime???and when you are trying to click power botton red led is blinking for a while??
bibhu059 said:
led is getting off after sometime???and when you are trying to click power botton red led is blinking for a while??
Click to expand...
Click to collapse
Stays on as long as power is present.
Clicking any button does nothing.
Yesterday evening when I plugged it in for the night to charge the LED went red and the phone entered Flashmode immediately - flashmode stopped after the timeout and when unplugging the charge-LED stayed red forever. Re-plugging didn't change anything, Flashmode didn't start a second time. Taking out the battery made it go off and it stayed like that until plugging it in the next time.
brainzilla said:
Stays on as long as power is present.
Clicking any button does nothing.
Yesterday evening when I plugged it in for the night to charge the LED went red and the phone entered Flashmode immediately - flashmode stopped after the timeout and when unplugging the charge-LED stayed red forever. Re-plugging didn't change anything, Flashmode didn't start a second time. Taking out the battery made it go off and it stayed like that until plugging it in the next time.
Click to expand...
Click to collapse
as no botton is working..no flashmod..fastboot mod..nothing means hard brick..have you made anythng with ta backup or something??
Btw do you have warranty?
trancyh but
bibhu059 said:
have you made anythng with ta backup or something??
Btw do you have warranty?
Click to expand...
Click to collapse
Dunno - what is TA Backup? Only place I saw that is in Flashtool to exclude TA I think.
I still have warranty, but I used the sony site to get an unlock-code.
So it's gonna at least cost me some €. Will call em tomorrow.
Used ones are from 80€ upwards, so I wonder how much Sony will charge...
brainzilla said:
Dunno - what is TA Backup? Only place I saw that is in Flashtool to exclude TA I think.
I still have warranty, but I used the sony site to get an unlock-code.
So it's gonna at least cost me some €. Will call em tomorrow.
Used ones are from 80€ upwards, so I wonder how much Sony will charge...
Click to expand...
Click to collapse
listen dont worry..before taking to sony service center again check for all options(fastboot,flashmod)..if nothing is hapening then
take it to service center and act as a noob..if they ask what happen just say updating phone software through pc companion..after updataion it is not getting on..only this much with a louder voice and dont let them you have unlocked the device..i have recently changed my board by applying this..so good luck
bibhu059 said:
if nothing is hapening then take it to service center and act as a noob..if they ask what happen just say updating phone software through pc companion.. so good luck
Click to expand...
Click to collapse
Hehe thanks. But the german site doesn't even list any phone-repair-centers.
But I will try to find out more tomorrow. The only work till 6
The thing is u played with pcc with unlocked bl... did u relocked it before doing something with pcc? here is the trouble i guess!
I don t know how xU is done but if nobody could repair it for u ,u should buy a battery and change it... Or at least unconnect yours for cuple of minutes then replug it and plug charger on...
because kernel don t start so battery not charging thats why every one should do flashing and everything could mess the phone with at least 60% of battery in case something like that happens... theres a thread somewhere in xda for recovery from brick, find it i must go to bed lollll
sent with my Nypon using tapatalk 2
Alx31TLse said:
I don t know how xU is done but if nobody could repair it for u ,u should buy a battery and change it... Or at least unconnect yours for cuple of minutes then replug it and plug charger on...
Click to expand...
Click to collapse
Ahhh! I see!
The digital limbo it was in caused the charger to stop working and sucked the battery dead.
So the red LED now just tells me the battery is at 0%.
Will try to recharge with my bench-supply.
But those batteries are a pain in the ass to interface...
Like i said im not sure but look flashing a kernel takes average one sec!
And only led and no screen on u know what i mean...if u could have just a bit of juice then its enough to fastboot. U must unplug battery cuz u will never be able to start it if not...
And soon as u could flash kernel then u touch nothing plug in charger for cuple hours and u should be good to flash a ftf and run on it for a day
And please guys...u have u bl? FORGOT PCC lolll unless u relock it...i didn t start pcc since almost a year
sent with my Nypon using tapatalk 2
OK guys thanks for all the technical and moral support so far!
I figured a way to load my battery with a bench-supply.
The procedure involved springs from a pen, small screws from an old HDD, micro-clamps, multimeter-cables/probes, silver tape and a toolmaker's vice....
By the way: The BA600 Battery is protected by a small circuit - so you need more than the nominal 4.2V to charge it.
I set it to the 5.1V a regular USB-charger outputs and it did the trick in about 2hrs.
Anyhow I was then able to use the latest OSX version of Flashtool in Fastboot mode and flash a kernel.
Then I used the Flashmode and flashed the s*** out of it.
That said: It works again! :good: :good: :good:
So at least I have gingerbread back and will give Cyan 10.0 a try.
THANKS TO ALL OF YOU GUYS!
Seriously! Wicked good support here!
Happy for u.
Im sure next time u ll b careful
sent with my Nypon using tapatalk 2
Alx31TLse said:
Im sure next time u ll b careful
Click to expand...
Click to collapse
More like "Next time I know what I do because I learned it the hard way..."
The whole documentation and "support" for the procedures is quite complicated in my opinion.
I mean how complicated is it to code a HELP-button into Flashtool?
Anyways - thanks again!
I am sorry that I know there are so many articles talking about
Drivers need to be installed for connected device.
You can find them in the drivers folder of Flashtool.
I have read so many articles but still cannot find out the problem.
I go to "Devices" of Flashtool and "Check Drivers"
It gave me this
01/004/2014 00:04:31 - INFO - List of connected devices (Device Id) :
01/004/2014 00:04:31 - INFO - - USB\VID_0FCE&PID_51AF\CB5A1YAHWN Driver installed : true
01/004/2014 00:04:31 - INFO - - USB\VID_0FCE&PID_51AF&MI_01\6&E66E0BD&0&0001 Driver installed : true
01/004/2014 00:04:31 - INFO - - USB\VID_0FCE&PID_51AF&MI_00\6&E66E0BD&0&0000 Driver installed : true
01/004/2014 00:04:31 - INFO - List of ADB devices :
01/004/2014 00:04:31 - INFO - - CB5A1YAHWN
01/004/2014 00:04:31 - INFO - List of fastboot devices :
01/004/2014 00:04:31 - INFO - - none
And I could not unlock bootloader.
I have ticked the USB Debug yet my Z2 is not rooted yet.
Do I have to root it first?
May someone guide me how to unlock because I cannot finish it using the official way
It always keeps telling me "Waiting for device"
Thank you so much!
http://www.theandroidsoul.com/unlock-bootloader-on-sony-xperia-z2/
I followed this website.
Using method 1, I could not achieve step 4
Using method 2, when I type fastboot.exe -i 0x0fce getvar version
noting happened, it seemed to be saying "cannot find 0x0fce" or somthing else
I don't know why it keeps telling me no driver installed
I go to Device Manager of Windows and it shows it has the updated driver installed in the PC
I am using Win 8.1
http://forum.xda-developers.com/showthread.php?t=2635830
This thread will help alot
Press windowsKey + R
type/paste
Code:
shutdown -o -r -t 0
into the box, this will restart your machine in the advanced startup menu.
when it restarts choose "disable driver signing" Then install the driver manually using the "have disk" option. when you reboot again the driver should be working.
-------------------
I followed what it said but when is "when it restarts choose "disable driver signing" Then install the driver manually using the "have disk" option. "???
I could not find disable driver signing.
After entering the shutdown command, what button should I press? Thank you for replying! I wish I will be able to flash rom today
Not sure what to do then because i ran into the same issue but i just used a linux OS as a work around
Thanks for answering
I will try using Win Vista
I hope someone could teach me