OK so this is my first time making a thread at XDA i am having problem about installing a custom kernel here http://forum.xda-developers.com/showthread.php?t=2345567 using flashtool my phone bootloader is unlocked and rooted this is the result
29/033/2014 14:33:33 - INFO - Flashtool Version 0.9.18.4 built on 12-05-2014 22:00:00
29/033/2014 14:33:33 - INFO - Executing search strategies to find proxy selector
29/033/2014 14:33:34 - INFO - No proxy found for IE. Trying next one
29/033/2014 14:33:34 - INFO - Strategy firefox failed trying next one : No Firefox installation found
29/033/2014 14:33:34 - INFO - No proxy found for java. Trying next one
29/033/2014 14:33:34 - INFO - Syncing devices from github
29/033/2014 14:33:34 - INFO - Scanning devices folder for changes.
29/033/2014 14:33:42 - INFO - Pulling changes from github.
29/033/2014 14:33:43 - INFO - Devices sync finished.
29/033/2014 14:33:47 - INFO - Device disconnected
29/033/2014 14:33:57 - INFO - Device connected in fastboot mode
29/033/2014 14:33:58 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\Kernel\kernel.elf
29/033/2014 14:33:58 - INFO - Flashing selected kernel
29/033/2014 14:33:59 - INFO - sending 'boot' (9924 KB)...
29/033/2014 14:33:59 - INFO - FAILED (data transfer failure (Too many links))
29/033/2014 14:33:59 - INFO - finished. total time: 0.853s
29/033/2014 14:33:59 - INFO - FASTBOOT Output:
sending 'boot' (9924 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 0.853s
29/033/2014 14:33:59 - INFO - Please check the log before rebooting into system
29/033/2014 14:33:59 - INFO - Device disconnected
29/034/2014 14:34:00 - INFO - Device connected in flash mode
can anyone help me with this situation???
Please post in [Q&A] [KERNEL][SP] DooMKernel (v13)[20140604] so that one of the experts may be of help.
Related
This is the log,
I tried to flash kernel because I want to install CM10
My device is rooted(Tipo)
25/039/2013 17:39:09 - INFO - Device connected with USB debugging on
25/039/2013 17:39:09 - INFO - Connected device : Sony Xperia Tipo
25/039/2013 17:39:09 - INFO - Installed version of busybox : BusyBox v1.20.2-linusyang (2012-10-15 16:24:24 CST) multi-call binary.
25/039/2013 17:39:09 - INFO - Android version : 4.0.4 / kernel version : 3.0.8-perf / Build number : 11.0.A.4.27
25/039/2013 17:39:10 - INFO - Checking root access
25/039/2013 17:39:10 - INFO - Root Access Allowed
25/040/2013 17:40:36 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
25/040/2013 17:40:45 - INFO - Device will soon enter fastboot mode
25/040/2013 17:40:45 - INFO - Device disconnected
25/040/2013 17:40:47 - INFO - Device connected in fastboot mode
25/040/2013 17:40:59 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Barve\Desktop\Android\Fastboot\boot.img
25/040/2013 17:40:59 - INFO - Flashing selected kernel
25/040/2013 17:40:59 - INFO - sending 'boot' (7185 KB)...
25/040/2013 17:40:59 - INFO - FAILED (remote: The Device must be rooted first)
25/040/2013 17:40:59 - INFO - finished. total time: 0.006s
25/040/2013 17:40:59 - INFO - FASTBOOT Output:
sending 'boot' (7185 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.006s
I already posted this problem many times nobody is answering.
U need to unlock the bootloader
Sent from my ST26i using xda premium
Did you press 'select kernel to flash' or 'select system to flash'? You need to flash system.
Sent from my Sony Xperia Miro
Thanks bro. But I was fed up and I installed gimlo.
But still thanks. Cause in future it will definitely help.
Sent from my ST21i using xda app-developers app
Hi all
*
recently acquired the M2 and decided to change rom via flashtool, but it turned out that this is an absolute mistake
because during installation (specifically when you connect your phone in fastboot mode, and you'll see a window with a choice of phone model.) does not display drivers for m2 (although they were installed in the Sony PC Companion and others available on various forums do not change) and then on flashtool-a screen pops Flash canceled.
when I tried to return the it (saved log with flashtool):
16/057/2014 12:57:33 - INFO - <- This level is successfully initialized
16/057/2014 12:57:33 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
16/057/2014 12:57:37 - INFO - Device connected in fastboot mode
16/057/2014 12:57:39 - INFO - List of connected devices (Device Id) :
16/057/2014 12:57:39 - INFO - - USB\VID_0FCE&PID_0DDE\ZH8005DY04 Driver installed : true
16/057/2014 12:57:39 - INFO - List of ADB devices :
16/057/2014 12:57:40 - INFO - - none
16/057/2014 12:57:40 - INFO - List of fastboot devices :
16/057/2014 12:57:40 - INFO - - none
16/002/2014 13:02:56 - INFO - Selected system (system.img or system.sin): C:\Flashtool\boot.img.img
16/002/2014 13:02:56 - INFO - Flashing selected system
16/002/2014 13:02:59 - INFO - Please check the log before rebooting into system
16/003/2014 13:03:41 - INFO - Selected null
16/003/2014 13:03:41 - INFO - Flash canceled
16/010/2014 13:10:58 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\boot.img.img
16/010/2014 13:10:58 - INFO - Flashing selected kernel
16/011/2014 13:11:00 - INFO - sending 'boot' (13692 KB)...
16/011/2014 13:11:00 - INFO - OKAY [ 0.516s]
16/011/2014 13:11:00 - INFO - writing 'boot'...
16/011/2014 13:11:00 - INFO - OKAY [ 1.641s]
16/011/2014 13:11:00 - INFO - finished. total time: 2.156s
16/011/2014 13:11:00 - INFO - FASTBOOT Output:
sending 'boot' (13692 KB)...
OKAY [ 0.516s]
writing 'boot'...
OKAY [ 1.641s]
finished. total time: 2.156s
16/011/2014 13:11:00 - INFO - Please check the log before rebooting into system
:crying:
since then the phone stops at the loading screen sony and the only way to disable a button OFF
sony pc companion and it does not detect
when I go into recovery -> mount / system error message bereave me mounting / system!
* I have no idea what I did wrong, but if anyone knows the answer it begs help !!
P.S. sorry for the poor knowledge of English (google translate)
You attempt to install a rom or a kernel ?
Have you installed Fastboot and flashmode drivers which are on C/flashtool/drivers folders ?
your flashtool version is old
update your flashtool, because it have the latest drivers
młodzianin115 said:
Hi all
*
recently acquired the M2 and decided to change rom via flashtool, but it turned out that this is an absolute mistake
because during installation (specifically when you connect your phone in fastboot mode, and you'll see a window with a choice of phone model.) does not display drivers for m2 (although they were installed in the Sony PC Companion and others available on various forums do not change) and then on flashtool-a screen pops Flash canceled.
when I tried to return the it (saved log with flashtool):
16/057/2014 12:57:33 - INFO - <- This level is successfully initialized
16/057/2014 12:57:33 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
16/057/2014 12:57:37 - INFO - Device connected in fastboot mode
16/057/2014 12:57:39 - INFO - List of connected devices (Device Id) :
16/057/2014 12:57:39 - INFO - - USB\VID_0FCE&PID_0DDE\ZH8005DY04 Driver installed : true
16/057/2014 12:57:39 - INFO - List of ADB devices :
16/057/2014 12:57:40 - INFO - - none
16/057/2014 12:57:40 - INFO - List of fastboot devices :
16/057/2014 12:57:40 - INFO - - none
16/002/2014 13:02:56 - INFO - Selected system (system.img or system.sin): C:\Flashtool\boot.img.img
16/002/2014 13:02:56 - INFO - Flashing selected system
16/002/2014 13:02:59 - INFO - Please check the log before rebooting into system
16/003/2014 13:03:41 - INFO - Selected null
16/003/2014 13:03:41 - INFO - Flash canceled
16/010/2014 13:10:58 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\boot.img.img
16/010/2014 13:10:58 - INFO - Flashing selected kernel
16/011/2014 13:11:00 - INFO - sending 'boot' (13692 KB)...
16/011/2014 13:11:00 - INFO - OKAY [ 0.516s]
16/011/2014 13:11:00 - INFO - writing 'boot'...
16/011/2014 13:11:00 - INFO - OKAY [ 1.641s]
16/011/2014 13:11:00 - INFO - finished. total time: 2.156s
16/011/2014 13:11:00 - INFO - FASTBOOT Output:
sending 'boot' (13692 KB)...
OKAY [ 0.516s]
writing 'boot'...
OKAY [ 1.641s]
finished. total time: 2.156s
16/011/2014 13:11:00 - INFO - Please check the log before rebooting into system
:crying:
since then the phone stops at the loading screen sony and the only way to disable a button OFF
sony pc companion and it does not detect
when I go into recovery -> mount / system error message bereave me mounting / system!
* I have no idea what I did wrong, but if anyone knows the answer it begs help !!
P.S. sorry for the poor knowledge of English (google translate)
Click to expand...
Click to collapse
download the software of your mobile from xperiadownload
uninstall flashtool from your pc
download the last version of flashtool
install it
install the drivers from this destination C:\Flashtool\drivers
only check : flashmode drivers , fastboot drivers , xperia z2 device drivers ( u'll find 2 of this check the both )
move the software ftf file to the destination C:\Flashtool\firmwares
tern off the phone and charge it to the half
open flashtool and click flash > flashmode > check your sofware
click flash
when a window pops up tilliny u to connect your phone
pres on volume down on the phone and connect the USB cable and let it flash
when it ends unplug the phone and power it on wait 10m at the first boot
and it'll run again
Good first sorry for the English evil, I to have a problem I already released the bootloader and caught again, today I want to unlock again so that is giving this:
14/055/2013 22:55:31 - INFO - Device connected in fastboot mode
14/055/2013 22:55:36 - INFO - Unlocking phone using key XXXXXXXXXXXXXXXXXX
14/055/2013 22:55:36 - INFO - ...
14/055/2013 22:55:36 - INFO - FAILED (remote: Command did not succeed)
14/055/2013 22:55:36 - INFO - finished. Total time: 0.035s
XXXXXXXXXXXXXXXXXX = the unlock code i got from Sony
Someone help me with this problem?
Hello, i check my service menu and it tells be Yes for boot loader. (See attachment)
When i try fastboot -i 0x0fce oem unlock 0xDBB27AC5A71632B5
FAILED (remote: Command not allowed)
finished. total time: 0.023s
When i try flashtool.
03/028/2017 19:28:44 - INFO - Unlocking phone using key DBB27AC5A71632B5
03/028/2017 19:28:44 - INFO - ...
03/028/2017 19:28:44 - INFO - FAILED (remote: Command not allowed)
03/028/2017 19:28:44 - INFO - finished. total time: 0.013s
I am out of ideas.
I'am either unlocked, since it says UnLocked
When i try Z5_AndroPluck kernel i get
target reported max download size of 536870912 bytes
sending 'boot' (16828 KB)...
OKAY [ 0.379s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.401s
I got it by using flashtool, C:\Users\[USER]\.flashTool\registeredDevices\[serial of your phone]\ulcode.txt with the unlock code from sony.
Then i ran flashtool, pressed BLU.
PHP:
03/037/2017 21:37:18 - INFO - Phone ready for flashmode operations.
03/037/2017 21:37:18 - INFO - Opening TA partition 2
03/037/2017 21:37:19 - INFO - Current device : E6653 - BH90GM494D - 1298-8309_R7C - 1295-7444_32.2.A.0.305 - GENERIC_32.2.A.0.305
03/037/2017 21:37:19 - INFO - Closing TA partition
03/037/2017 21:37:19 - INFO - No loader in the bundle. Searching for one
03/037/2017 21:37:19 - INFO - Processing loader.sin
03/037/2017 21:37:19 - INFO - Checking header
03/037/2017 21:37:19 - INFO - Flashing data
03/037/2017 21:37:20 - INFO - Loader : S1_Root_f936 - Version : MSM8994_41 / Boot version : S1_Boot_MSM8994_LA1.2.2_42 / Bootloader status : ROOTABLE
03/037/2017 21:37:20 - INFO - Max packet size set to 4M
03/037/2017 21:37:20 - INFO - Opening TA partition 2
03/037/2017 21:37:20 - INFO - Start Reading unit 00 00 08 B2
03/037/2017 21:37:20 - INFO - Reading TA finished.
03/037/2017 21:37:20 - INFO - Closing TA partition
03/037/2017 21:37:27 - INFO - Unlocking device
03/037/2017 21:37:27 - INFO - Opening TA partition 2
03/037/2017 21:37:27 - INFO - Writing TA unit 000008B2. Value : 44 42 42 32 37 41 43 35 41 37 31 36 33 32 42 35
03/037/2017 21:37:27 - INFO - Closing TA partition
03/037/2017 21:37:27 - INFO - Unlock finished
Need you help
Now I got the same problem - can't unlock bootloader xperia z5
my phone is can't power on (alway reboot and reboot)
I want to flashing or root my phone, could to help me please
thank you
[email protected]
I want to flash the oem file.
But I get a script error.
Flashtool 0.9.28.0
24/037/2020 22:37:59 - INFO - Searching for a web proxy
24/037/2020 22:37:59 - INFO - No proxy found, using direct connection
24/038/2020 22:38:01 - INFO - Loading devices database
24/038/2020 22:38:02 - INFO - Loaded 127 devices
24/038/2020 22:38:02 - INFO - Starting phone detection
24/038/2020 22:38:10 - INFO - Device connected with USB debugging on
24/038/2020 22:38:10 - ERROR - Cannot identify your device.
24/038/2020 22:38:10 - INFO - Selecting from user input
24/047/2020 22:47:33 - INFO - Connected device : J92XX
24/047/2020 22:47:33 - INFO - Installed version of busybox : N/A
24/047/2020 22:47:33 - INFO - Android version : 10 / kernel version : / Platform : 64bits / Build number : 55.1.A.0.748
24/047/2020 22:47:33 - INFO - Phone in recovery mode
24/047/2020 22:47:33 - INFO - Root Access Allowed
24/047/2020 22:47:54 - INFO - Selected Bundle for Sony Xperia 5 Dual(J9210). FW release : Android 10. Customization : United Kingdom
24/047/2020 22:47:54 - INFO - Preparing files for flashing
24/048/2020 22:48:27 - INFO - Device connected with USB debugging off
24/048/2020 22:48:27 - INFO - For 2011 devices line, be sure you are not in MTP mode
24/048/2020 22:48:29 - INFO - Device disconnected
24/048/2020 22:48:33 - INFO - Please connect your device into flashmode.
24/048/2020 22:48:36 - INFO - Using Gordon gate drivers version 3.2.0.0
24/048/2020 22:48:37 - INFO - USB buffer size set to 512K
24/048/2020 22:48:37 - INFO - Opening device for R/W
24/048/2020 22:48:37 - INFO - Device ready for R/W.
24/048/2020 22:48:37 - INFO - Reading device information
24/048/2020 22:48:37 - INFO - Reading phone properties
24/048/2020 22:48:37 - INFO - Sending getvar:max-download-size
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:version
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:version-bootloader
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:version-baseband
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvarroduct
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:serialno
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:secure
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Sector-size
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Version-sony
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:USB-version
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:max-download-size
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Loader-version
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvarhone-id
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvarevice-id
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Rooting-status
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Sector-size
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Ufs-info
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Emmc-info
24/048/2020 22:48:37 - INFO - getvar status : FAIL
24/048/2020 22:48:37 - WARN - Emmc-info not supported
24/048/2020 22:48:37 - INFO - Sending getvarefault-security
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvarlatform-id
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Keystore-counter
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Security-state
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:S1-root
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Sake-root
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Battery
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Frp-partition
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Stored-security-state
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending getvar:Keystore-xcs
24/048/2020 22:48:37 - INFO - getvar status : OKAY
24/048/2020 22:48:37 - INFO - Sending Get-root-key-hash
24/048/2020 22:48:37 - INFO - Get-root-key-hash status : OKAY
24/048/2020 22:48:37 - INFO - Sending Read-TA:2:2202
24/048/2020 22:48:37 - INFO - Read-TA status : OKAY
24/048/2020 22:48:37 - INFO - Sending Read-TA:2:2205
24/048/2020 22:48:37 - INFO - Read-TA status : OKAY
24/048/2020 22:48:37 - INFO - Sending Read-TA:2:2210
24/048/2020 22:48:37 - INFO - Read-TA status : OKAY
24/048/2020 22:48:37 - INFO - Sending Read-TA:2:4900
24/048/2020 22:48:37 - INFO - Read-TA status : OKAY
24/048/2020 22:48:37 - INFO - Sending Read-TA:2:10021
24/048/2020 22:48:37 - INFO - Read-TA status : FAIL
24/048/2020 22:48:37 - WARN - Unit 10021 does not exist ( Hex unit value 00002725 )
24/048/2020 22:48:37 - INFO - Connected device : J9210 / SW release 1318-9849_55.1.A.0.748 / Customization Unknown: Nov 13 2019/21:19:49
24/048/2020 22:48:37 - INFO - Last flash date : null
24/048/2020 22:48:37 - INFO - Phone ready for flashmode operations.
24/048/2020 22:48:37 - INFO - Start Flashing
24/048/2020 22:48:37 - INFO - Parsing boot delivery
24/048/2020 22:48:37 - INFO - Found a boot delivery
24/048/2020 22:48:37 - ERROR - No flash script found. Flash script is mandatory
24/048/2020 22:48:37 - INFO - Sending Sync
24/048/2020 22:48:39 - INFO - Sync status : OKAY
24/048/2020 22:48:39 - INFO - Sending powerdown
24/048/2020 22:48:39 - INFO - powerdown status : OKAY
24/048/2020 22:48:42 - INFO - Device disconnected
24/048/2020 22:48:43 - INFO - Device connected in flash mode
help me plz
Look up fsc script for Flashtool if you want to continue to use this method. You will need to find device specific file and put it in the Flashtool folder. The easier method would be to use Newflasher. There are tutorials on XDA.
augie7107 said:
Look up fsc script for Flashtool if you want to continue to use this method. You will need to find device specific file and put it in the Flashtool folder. The easier method would be to use Newflasher. There are tutorials on XDA.
Click to expand...
Click to collapse
I don't know if script files are supported for the dual version.
I have already used the 55.sfc file, but failed to install the tft file.
augie7107 said:
Look up fsc script for Flashtool if you want to continue to use this method. You will need to find device specific file and put it in the Flashtool folder. The easier method would be to use Newflasher. There are tutorials on XDA.
Click to expand...
Click to collapse
I think someone suffered a similar phenomenon like me.
Can you give Newflasher a try?
augie7107 said:
Can you give Newflasher a try?
Click to expand...
Click to collapse
Tried, in several different versions.
You cannot install ftf on various older versions.
I tried 10 to 20 versions.
In 20 versions I get an sfc error.
In 10 versions , you get an -error- error.
The picture below shows an error in 10 versions.(ex.:16
ver, 18 ver..)
changikman said:
Tried, in several different versions.
You cannot install ftf on various older versions.
I tried 10 to 20 versions.
In 20 versions I get an sfc error.
In 10 versions , you get an -error- error.
The picture below shows an error in 10 versions.(ex.:16
ver, 18 ver..)
Click to expand...
Click to collapse
Hello i experienced the very same issue with flashtool when it doesn't seem to recognize the flash script the solution is to use newsflasher now I'm running Android 9 in Xperia 5 J9210 from Android 10 with the Drm keys still intact.
I had that problem with Windows 10. It was the default antivirus that Flashtool detects as a Trojan. Give access permission and you can flash without problems
You could try to create script by logging USB under whilst Companion installs, But i think Flashtool USB parse function is broken. Atleast it doesnt work for me, it just remains in idle the whole time
I must report great news: Update 55.1.A.12.28 for Xperia 5 is a greatest update ever! Recording (4K 60 fps) is fixed, and like bonus perfect stabilisation added! It is impressive work, Sony
Now, I can to say: Xperia 5 is best phone
Hi
It seems that it is something broken in Flashtool (even the latest ...33). For me it flashes ftf files and recognizes the fsc script (including the 55) but it skips some of the most important partitions due to "partition delivery script not found" witch it is included in the Xperifirm downloaded firmware.
i guess not the flashing part is broken, but bundle creation part it is something wrong with it!
Solved also with newflasher
The only problem with newflasher i had issues with magisk boot image patched after performing a first boot with non patched stock img (i had to clear userdata partition )