[Q] So downgrading my phone has resulted in a bootloop.... - Sony Xperia ZR

Hi, following the lollipop update my WiFi stopped working(it was prerooted) so I tried flashing down to 10.5.A.0.230 so I could re install recovery, but now my phone is stuck on bootloop?
My Phone is:
Model: Xperia ZR(C5502)
Software before flashing Lollipop: 10.5.1.a.0.292, rooted with SuperSU
I tried reflashing it and I get this error: "Processing of loader.sin finished with errors. Ending flash session"
Can anyone help me?
The Firmware I flashed before when I first rooted the phone - 10.5.A.0.230 TW and it worked fine when I first flashed it almost a year ago. Can anyone help me?

YourFriendlyNig said:
Hi, following the lollipop update my WiFi stopped working(it was prerooted) so I tried flashing down to 10.5.A.0.230 so I could re install recovery, but now my phone is stuck on bootloop?
My Phone is:
Model: Xperia ZR(C5502)
Software before flashing Lollipop: 10.5.1.a.0.292, rooted with SuperSU
I tried reflashing it and I get this error: "Processing of loader.sin finished with errors. Ending flash session"
Can anyone help me?
The Firmware I flashed before when I first rooted the phone - 10.5.A.0.230 TW and it worked fine when I first flashed it almost a year ago. Can anyone help me?
Click to expand...
Click to collapse
have you tried repairing the phone using PC companion software provided you have not unlocked the bootloader by any method??

sourabhp said:
have you tried repairing the phone using PC companion software provided you have not unlocked the bootloader by any method??
Click to expand...
Click to collapse
By bootloop I mean it doesn't even get past the sony logo. Sony Bridge for Mac doesn't even know it's connected EDIT: Won't get past detecting because it disconnects 10 seconds after the sony logo
error I'm getting:
26/001/2015 14:01:26 - INFO - Device connected in flash mode
26/001/2015 14:01:42 - INFO - Selected Bundle for Sony Xperia ZR (C5502). FW release : 10.5.A.0.230. Customization : TW
26/001/2015 14:01:42 - INFO - Preparing files for flashing
26/001/2015 14:01:45 - INFO - Please connect your device into flashmode.
26/001/2015 14:01:47 - INFO - Opening device for R/W
26/001/2015 14:01:47 - INFO - Device ready for R/W.
26/001/2015 14:01:47 - INFO - Reading device information
26/002/2015 14:02:11 - INFO - Unable to read from phone after having opened it.
26/002/2015 14:02:11 - INFO - trying to continue anyway
26/002/2015 14:02:11 - INFO - Start Flashing
26/002/2015 14:02:11 - INFO - Processing loader.sin
26/002/2015 14:02:11 - INFO - Checking header
26/002/2015 14:02:11 - ERROR - Processing of loader.sin finished with errors.
26/002/2015 14:02:11 - INFO - Ending flash session
26/002/2015 14:02:11 - ERROR - S1 Header checksum Error
26/002/2015 14:02:11 - ERROR - Error flashing. Aborted
26/002/2015 14:02:11 - INFO - Device disconnected

Thanxx

Related

[Q] problem with flash xperia 10i

hi ,
i tray to flash a dead x10i with flasher but i have a problem
25/035/2012 13:35:58 - INFO - <- This level is successfully initialized
25/035/2012 13:35:58 - INFO - Flashtool Version 0.6.7.0 built on 2012-01-21 17:31:40
25/035/2012 13:35:58 - INFO - You can drag and drop ftf files here to start flashing them
25/036/2012 13:36:05 - INFO - Device disconnected
25/036/2012 13:36:24 - INFO - Selected Sony Ericsson X10i_2.1.A.435_GLOBAL-GGL GENERIC 1232-9897.ftf
25/036/2012 13:36:24 - INFO - Preparing files for flashing
25/036/2012 13:36:36 - INFO - Please connect your device into flashmode.
25/036/2012 13:36:43 - INFO - Device connected in flash mode
25/036/2012 13:36:43 - INFO - Opening device for R/W
25/036/2012 13:36:44 - INFO - Reading device information
25/036/2012 13:36:44 - INFO - Phone reading for flashing.
25/036/2012 13:36:44 - INFO - Start Flashing
25/036/2012 13:36:44 - INFO - Flashing loader
25/036/2012 13:36:48 - INFO - Loader version : R4A024 / Bootloader status : UNROOTABLE
25/036/2012 13:36:48 - INFO - Flashing kernel.sin
25/036/2012 13:36:52 - INFO - Flashing amss_fs.sin
25/036/2012 13:36:52 - INFO - Flashing dsp1.sin
25/036/2012 13:36:59 - INFO - Flashing fota1.sin
25/037/2012 13:37:01 - INFO - Flashing fota0.sin
25/037/2012 13:37:02 - INFO - Flashing amss.sin
25/037/2012 13:37:09 - ERROR -
25/037/2012 13:37:09 - ERROR - Error flashing. Aborted
25/037/2012 13:37:09 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
and with the SEUS a have the same problem update fail
ps : the x10i bloqued in flash mode , i can't run it when i press power i have just vibre but nathing happen
pls help
Um... but this is a x8 forum...
Hit the THANKS button if I helped!!
Sent from my W8 using Tapatalk
haykalo said:
i tray to flash a dead x10i with flasher but i have a problem
Code:
25/036/2012 13:36:44 - INFO - Flashing loader
25/036/2012 13:36:48 - INFO - Loader version : R4A024 / Bootloader status : UNROOTABLE
Click to expand...
Click to collapse
Feel free to correct me if I'm wrong, but I'm pretty sure you can not flash the boot loader with the boot loader being locked (the uppercase "R").
Since it seems the genuine loader is present you better look for a FTF bundle without the loader and kernel to flash back the stock ROM.
And it seems like he didnt root his phone.You should root your phone and unlock bootloader first if its not too late..
igibi011 said:
And it seems like he didnt root his phone.You should root your phone and unlock bootloader first if its not too late..
Click to expand...
Click to collapse
Nope, since all of this happens in flash mode the state of the ROM (rooted, non-rooted, crashed, ...) isn't even of any greater importance. The only thing that's important is that the boot loader environment still works (for running flash mode).
I think the "UNROOTABLE" error Flashtool gives comes from the circumstance that the partition where the loader and kernel is stored can't be rooted due to the boot loader being locked.
Unpacking the FTF and correctly re-bundling without the boot loader / kernel parts should actually work to have a plain ROM-only FTF restoration file.
Same goes for the X8 - there are some FTF's WITH the boot loader (aka "baseband") parts and there's at least one where it's just the ROM.
Happened to me once on an X10. Wouldn't even show the Sony Ericsson logo. Constantly vibrated. I thought I had bricked it.
I tried flashing the baseband again & it came back to life.

Stuck in a Bootloop/Boot stall Z1(Sony Logo) Pz Help!

Hello!
I upgraded my z1 to 4.3 but while attempting to make a call my phone froze and after restarting i was stuck in a boot loop.
I've very carefully went through many threads and finally decided to post because after trying all the methods i'm still stuck at boot stall. (Sony logo)
I've used the flashtool ( Version 0.9.13.0 ) to flash the latest FTF (C6903 14.2.A.0.290 Central Europe 1276-4314_R1B) But to no avail. I've also tried resetting it through SUS (complete system format/factory reset) and its the same.
Also tried downgrading to .257 and i'm still stuck with the same bootloop.
Here are the logs from Flashtool, If this helps.
21/019/2013 19:19:07 - INFO - Selected C6903 / 14.2.A.0.290 / Generic Central Europe 1276-4314
21/019/2013 19:19:07 - INFO - Preparing files for flashing
21/019/2013 19:19:29 - INFO - Please connect your device into flashmode.
21/020/2013 19:20:29 - INFO - Device disconnected
21/020/2013 19:20:50 - INFO - Device connected in flash mode
21/020/2013 19:20:50 - INFO - Opening device for R/W
21/020/2013 19:20:51 - INFO - Reading device information
21/020/2013 19:20:51 - INFO - Phone ready for flashmode operations.
21/020/2013 19:20:51 - INFO - Current device : C6903 - BH9085PV06 - 1277-2882_R2B - 1272-6084_14.2.A.0.290 - GLOBAL-LTE_14.2.A.0.290
21/020/2013 19:20:51 - INFO - Start Flashing
21/020/2013 19:20:51 - INFO - Processing loader.sin
21/020/2013 19:20:51 - INFO - Checking header
21/020/2013 19:20:51 - INFO - Flashing data
21/020/2013 19:20:51 - INFO - Loader : S1_Root_6732 - Version : MSM8974_23 / Boot version : S1_Boot_MSM8974_LA1.04_15 / Bootloader status : NOT_ROOTABLE
21/020/2013 19:20:51 - INFO - Disabling final data verification check
21/020/2013 19:20:51 - INFO - Processing partition-image.sin
21/020/2013 19:20:51 - INFO - Checking header
21/020/2013 19:20:51 - INFO - Flashing data
21/020/2013 19:20:51 - INFO - Parsing boot delivery
21/020/2013 19:20:51 - INFO - Phone boot version : S1_Boot_MSM8974_LA1.04_15. Boot delivery version : S1_Boot_MSM8974_LA1.04_15
21/020/2013 19:20:51 - INFO - Boot delivery is up to date. Nothing done for boot bundle
21/020/2013 19:20:51 - INFO - Processing kernel.sin
21/020/2013 19:20:51 - INFO - Checking header
21/020/2013 19:20:51 - INFO - Flashing data
21/020/2013 19:20:52 - INFO - Processing rpm.sin
21/020/2013 19:20:52 - INFO - Checking header
21/020/2013 19:20:52 - INFO - Flashing data
21/020/2013 19:20:52 - INFO - Processing fotakernel.sin
21/020/2013 19:20:52 - INFO - Checking header
21/020/2013 19:20:52 - INFO - Flashing data
21/020/2013 19:20:53 - INFO - Processing amss_fs_2.sin
21/020/2013 19:20:53 - INFO - Checking header
21/020/2013 19:20:53 - INFO - Flashing data
21/020/2013 19:20:53 - INFO - Processing amss_fs_1.sin
21/020/2013 19:20:53 - INFO - Checking header
21/020/2013 19:20:53 - INFO - Flashing data
21/020/2013 19:20:53 - INFO - Processing amss_fsg.sin
21/020/2013 19:20:53 - INFO - Checking header
21/020/2013 19:20:53 - INFO - Flashing data
21/020/2013 19:20:53 - INFO - Processing apps_log.sin
21/020/2013 19:20:53 - INFO - Checking header
21/020/2013 19:20:53 - INFO - Flashing data
21/020/2013 19:20:53 - INFO - Processing cache.sin
21/020/2013 19:20:53 - INFO - Checking header
21/020/2013 19:20:53 - INFO - Flashing data
21/020/2013 19:20:54 - INFO - Processing system.sin
21/020/2013 19:20:54 - INFO - Checking header
21/020/2013 19:20:54 - INFO - Flashing data
21/022/2013 19:22:48 - INFO - Processing userdata.sin
21/022/2013 19:22:48 - INFO - Checking header
21/022/2013 19:22:48 - INFO - Flashing data
21/023/2013 19:23:03 - INFO - Processing elabel-C6903-row_201310221100.1_14.2.A.0.290.sin
21/023/2013 19:23:03 - INFO - Checking header
21/023/2013 19:23:03 - INFO - Flashing data
21/023/2013 19:23:05 - INFO - Flashing cust-reset.ta
21/023/2013 19:23:05 - INFO - Custumization reset is now based on UI choice
21/023/2013 19:23:05 - INFO - Ending flash session
21/023/2013 19:23:05 - INFO - Flashing finished.
21/023/2013 19:23:05 - INFO - Please unplug and start your phone
21/023/2013 19:23:05 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
21/023/2013 19:23:05 - INFO - Device connected in flash mode
21/024/2013 19:24:43 - INFO - Device disconnected
Rebooting is fine it gives three vibrations and shuts down.
I havent rooted the device. This is the first update i've tried.
Trying to download C6903_14.1.G.2.257_GLOBAL-LTE (1277-1398).ftf to see if that would help but unfortunately, can't download, gets stuck , Temporary error, retrying.
Any help will be appreciated, i'm at my wits end trying to revive this phone but i just can't seem to understand where i'm going wrong.
Thanks in advance!
Did you do a wipe data, cache, appslog when you updated? and did you uncheck "no final validation" and everything else?
eclyptos said:
Did you do a wipe data, cache, appslog when you updated? and did you uncheck "no final validation" and everything else?
Click to expand...
Click to collapse
Yes I checked the options for wipe appslog/cache/data and left the exclude option unchecked and checked "no final validation"
It flashes the FTF but still stuck in the sony logo loop. :crying:
siavo said:
Yes I checked the options for wipe appslog/cache/data and left the exclude option unchecked and checked "no final validation"
It flashes the FTF but still stuck in the sony logo loop. :crying:
Click to expand...
Click to collapse
I assume that you can turn it on, but you get stuck in a bootloop.
Power it off (VOL up + power button) then keep holding VOL down + power button, when it starts booting, release the power button and keep holding the VOL down. This should boot you into safe mode (people call it debugging mode as it only loads preinstalled apps and the things it needs to boot with 0 customizations made)
siavo said:
and checked "no final validation"
Click to expand...
Click to collapse
I mean did you unchecked this "no final validation" Right? You phone still power up so switch it off, keep pressing volume down and connect to pc, let windows install drivers, do not install the manually into flashtool, keep pressing volume down and flash again the FTF, if the problem still there you can also try different FTF to be sure, maybe the FTF is the problem.
eclyptos said:
I mean did you unchecked this "no final validation" Right? You phone still power up so switch it off, keep pressing volume down and connect to pc, let windows install drivers, do not install the manually into flashtool, keep pressing volume down and flash again the FTF, if the problem still there you can also try different FTF to be sure, maybe the FTF is the problem.
Click to expand...
Click to collapse
Yes i did uncheck it.
I think the FTF is the problem, but i've tried many FTS's now, the only one that at least booted the phone was C6903 14.1.G.1.534 Global 1277-2880_R4A this also started after a few bootloops but in the end it started. I saw the settings and it Baseband version was unknown. 3 minutes later the phone rebooted and went into a bootloop again.
I updated via SUS hoping it would fix the baseband problem but still the same.
No luck
siavo said:
Yes i did uncheck it.
I think the FTF is the problem, but i've tried many FTS's now, the only one that at least booted the phone was C6903 14.1.G.1.534 Global 1277-2880_R4A this also started after a few bootloops but in the end it started. I saw the settings and it Baseband version was unknown. 3 minutes later the phone rebooted and went into a bootloop again.
I updated via SUS hoping it would fix the baseband problem but still the same.
No luck
Click to expand...
Click to collapse
Currently uploading the android 4.3 global ftf.
I'll post link here when it's done uploading, try that ftf anddont check/uncheck anything, keep it as it is! just select the ftf and click flash.
Just2Cause said:
Currently uploading the android 4.3 global ftf.
I'll post link here when it's done uploading, try that ftf anddont check/uncheck anything, keep it as it is! just select the ftf and click flash.
Click to expand...
Click to collapse
Great! thanks! I hope it works! I'll leave the options as they are and flash it. :good:
siavo said:
Great! thanks! I hope it works! I'll leave the options as they are and flash it. :good:
Click to expand...
Click to collapse
Global 4.3 is up!
Download
Just2Cause said:
Global 4.3 is up!
Download
Click to expand...
Click to collapse
Thanks, downloading now, will see how it goes!
Just2Cause said:
Global 4.3 is up!
Download
Click to expand...
Click to collapse
What is the size of the pictures taken in Superior Auto mode in this ftf? 8 MP or 20 MP?
bogdan wst said:
What is the size of the pictures taken in Superior Auto mode in this ftf? 8 MP or 20 MP?
Click to expand...
Click to collapse
Sorry, I don't know because I only updated to 4.3 to make a ftf for people to flash.
I am currently on the global 257 waiting for OTA to see if it keeps root or no.
Regards,
~J2C
Maybe someone who uses this ftf will tell us.
bogdan wst said:
Maybe someone who uses this ftf will tell us.
Click to expand...
Click to collapse
Hopefully it is 20 MP (or at least, I wish).
Waiting for a confirmation.
Just2Cause said:
I assume that you can turn it on, but you get stuck in a bootloop.
Power it off (VOL up + power button) then keep holding VOL down + power button, when it starts booting, release the power button and keep holding the VOL down. This should boot you into safe mode (people call it debugging mode as it only loads preinstalled apps and the things it needs to boot with 0 customizations made)
Click to expand...
Click to collapse
I've tried this and i still cannot get it out of bootloop, I can't get into safemode or anything.. Any thoughts?
Skygen said:
I've tried this and i still cannot get it out of bootloop, I can't get into safemode or anything.. Any thoughts?
Click to expand...
Click to collapse
Hold VOL up and power it should turn off, then hold VOL down and connect it to PC and use Sony Update Service to reinstall the firmware.
im the same problem i cant get secure mode
Another point, use the latest flashtool, doomkernel is based on 757 firmware so you need a 757 ftf. That's needs latest flashtool in order to flash it and you said you are using version 13
Sent from my C6903 using XDA Premium 4 mobile app
Hello,
I have the same problem - stop on SONY logo.
How it heppen.
1. I use [AROMAv2.3]CriskeloROM+v7.4[Xperia_Z1_690X][Android+4.4.4] for LB
2. I want to check something and made wipe, then WIPE cache, dalvik, and system and install rom once again, but after this I cant boot.
I try
1. Flash tool and flash by C6903_14.4.A.0.108_Generic FR 1276-5833_R5C --> phone connecting in flash mode but nothing heppend
---Edit
I forgot mention, that I have drivers for z1 in windows, hen I connect by Sonny PC Connection I get info on phone that he is not connected with computer
I resolved problem. There was a two separate problem. First tft was broke, but the second I tray flash by flash tool when Sony PC Connect was ruining (I forgot about this).

[Q] Device bricked, can't flash System, bootloop into Flashmode

Hello everone,
I really need any advice i can get. I tried so much to make my Xperia SP C5303 work again...
This is the situation
- I doesn't boot at all into the System or Kernel.
- when i connect the charger or connect it to the PC it will show a red LED for about 5 minutes and then go into Flashmode (Green LED).
- after a few minutes it shows a red LED again, then Flashmode again etc.. It keeps doing this for days.. Even after didn't charge it for months...
- at this moment my bootloader is locked
So I often tried to flash a new firmware because i obviously can access the flashmode.
And it starts the flashing but every time it aborts about 34 into flashing system.
It works to flash everything except system... I excluded System (and TA) and it flashes everything. Then i excluded everything except System and it always aborts about 34 into the process of flashing System.
I tried with different ftf files and different versions of Flashtool... Still the same...
I tried Emma and it didn't work.
I relocked the bootloader (the device bricked while using MIUI just from one day to the other without me doing anything special) and tried Sony Update Service (SUS)... But it just says the device is up to date
I am soooo stuck with this problem
Any help would be greatly appreciated. If anyone has any idea how to recover my device then i am more than happy to try it
Just a step by step instruction how you would try to recover the device can help i will try it
Thank you all very much!
Raffi
Here is a flashtool log:
01/046/2014 13:46:03 - INFO - <- This level is successfully initialized
01/046/2014 13:46:03 - INFO - Flashtool Version 0.9.15.0 built on 15-03-2014 23:00:00
01/046/2014 13:46:07 - INFO - Device disconnected
01/056/2014 13:56:00 - INFO - Selected Bundle for Xperia SP (C5303). FW release : 12.0.A.2.254. Customization : Generic_DE
01/056/2014 13:56:00 - INFO - Preparing files for flashing
01/056/2014 13:56:09 - INFO - Please connect your device into flashmode.
01/001/2014 14:01:12 - INFO - Device connected in flash mode
01/001/2014 14:01:13 - INFO - Opening device for R/W
01/001/2014 14:01:13 - INFO - Reading device information
01/001/2014 14:01:13 - INFO - Phone ready for flashmode operations.
01/001/2014 14:01:13 - INFO - Current device : Unknown: Aug 22 2013/17:11:23 - CB5123WHU6 - Unknown: Aug 22 2013/17:11:23 - Unknown: Aug 22 2013/17:11:23 - Unknown: Aug 22 2013/17:11:23
01/001/2014 14:01:13 - INFO - Start Flashing
01/001/2014 14:01:13 - INFO - Processing loader.sin
01/001/2014 14:01:13 - INFO - Checking header
01/001/2014 14:01:13 - INFO - Flashing data
01/001/2014 14:01:13 - INFO - Processing of loader.sin finished.
01/001/2014 14:01:14 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B017 / Bootloader status : ROOTABLE
01/001/2014 14:01:14 - INFO - Disabling final data verification check
01/001/2014 14:01:14 - INFO - No bootdelivery to send
01/001/2014 14:01:14 - INFO - Processing system.sin
01/001/2014 14:01:14 - INFO - Checking header
01/001/2014 14:01:15 - INFO - Flashing data
01/003/2014 14:03:18 - ERROR - Processing of system.sin finished with errors.
01/003/2014 14:03:18 - INFO - Ending flash session
01/003/2014 14:03:18 - ERROR - 31 : Ein an das System angeschlossenes Gerät funktioniert nicht.
01/003/2014 14:03:18 - ERROR - Error flashing. Aborted
01/003/2014 14:03:18 - INFO - Device disconnected
01/052/2014 13:52:51 - INFO - Current device : Unknown: Aug 22 2013/17:11:23 - CB5123WHU6 - Unknown: Aug 22 2013/17:11:23 - Unknown: Aug 22 2013/17:11:23 - Unknown: Aug 22 2013/17:11:23
01/052/2014 13:52:51 - INFO - Start Flashing
01/052/2014 13:52:51 - INFO - Processing loader.sin
01/052/2014 13:52:51 - INFO - Checking header
01/052/2014 13:52:51 - INFO - Flashing data
01/052/2014 13:52:51 - INFO - Processing of loader.sin finished.
01/052/2014 13:52:52 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B017 / Bootloader status : ROOTABLE
01/052/2014 13:52:52 - INFO - Processing partition-image.sin
01/052/2014 13:52:52 - INFO - Checking header
01/052/2014 13:52:52 - INFO - Flashing data
01/052/2014 13:52:52 - INFO - Processing of partition-image.sin finished.
01/052/2014 13:52:52 - INFO - No bootdelivery to send
01/052/2014 13:52:52 - INFO - Processing kernel.sin
01/052/2014 13:52:52 - INFO - Checking header
01/052/2014 13:52:53 - INFO - Flashing data
01/052/2014 13:52:55 - INFO - Processing of kernel.sin finished.
01/052/2014 13:52:55 - INFO - Processing fotakernel.sin
01/052/2014 13:52:55 - INFO - Checking header
01/052/2014 13:52:55 - INFO - Flashing data
01/052/2014 13:52:57 - INFO - Processing of fotakernel.sin finished.
01/052/2014 13:52:57 - INFO - Processing amss_fs_2.sin
01/052/2014 13:52:57 - INFO - Checking header
01/052/2014 13:52:57 - INFO - Flashing data
01/052/2014 13:52:57 - INFO - Processing of amss_fs_2.sin finished.
01/052/2014 13:52:57 - INFO - Processing amss_fs_1.sin
01/052/2014 13:52:57 - INFO - Checking header
01/052/2014 13:52:57 - INFO - Flashing data
01/052/2014 13:52:57 - INFO - Processing of amss_fs_1.sin finished.
01/052/2014 13:52:57 - INFO - Processing amss_fsg.sin
01/052/2014 13:52:57 - INFO - Checking header
01/052/2014 13:52:57 - INFO - Flashing data
01/052/2014 13:52:57 - INFO - Processing of amss_fsg.sin finished.
01/052/2014 13:52:57 - INFO - Processing apps_log.sin
01/052/2014 13:52:57 - INFO - Checking header
01/052/2014 13:52:57 - INFO - Flashing data
01/052/2014 13:52:58 - INFO - Processing of apps_log.sin finished.
01/052/2014 13:52:58 - INFO - Processing cache.sin
01/052/2014 13:52:58 - INFO - Checking header
01/052/2014 13:52:58 - INFO - Flashing data
01/053/2014 13:53:01 - INFO - Processing of cache.sin finished.
01/053/2014 13:53:01 - INFO - Processing system.sin
01/053/2014 13:53:01 - INFO - Checking header
01/053/2014 13:53:01 - INFO - Flashing data
01/054/2014 13:54:56 - ERROR - Processing of system.sin finished with errors.
01/054/2014 13:54:56 - INFO - Ending flash session
01/054/2014 13:54:56 - ERROR - Read error :31 : Ein an das System angeschlossenes Gerät funktioniert nicht.
01/054/2014 13:54:56 - ERROR - Error flashing. Aborted
01/054/2014 13:54:56 - INFO - Device disconnected
01/054/2014 13:54:57 - INFO - Device connected with USB debugging off
01/054/2014 13:54:57 - INFO - For 2011 devices line, be sure you are not in MTP mode
01/055/2014 13:55:02 - INFO - Device disconnected
did you try reverting to 4.1.2? tried check / uncheck options like reset customization, partition image, TA partition etc while flashing.
guess you might have lost DRM keys. did u backup those?
---------- Post added at 07:56 PM ---------- Previous post was at 07:53 PM ----------
check this out http://forum.xda-developers.com/showthread.php?t=1849170
might help u
Custom ROMs break offline charging on the SP. Seems like your phone battery is at 0% gets enough charge to start booting then runs out of battery before you can flash anything. I had this but was able to flash a new kernel, charge a bit more, flash the offline fix and then power down the phone using the button under the cover until it vibrates three times. Left it to charge for half an hour and then I could repair my phone by flashing a full ROM.
Sent from my C5303 using XDA Premium 4 mobile app
Thank you for the replies.
What is strange is that flashing everything except system works and takes longer than just flashing System. But while flashing system it always aborts...
So i am able to flash the kernel without problems but it still does show the same behaviour... And why does it then always automatically go into Flashmode?
But I will look for the offline charging fix and try it.
As for the post before: I tried every combination of options.. It is always the same.
And tried nearly everything mentioned in the Thread you posted as I found that thread too.
And I have a TA Backup but I think first I need to revive the phone before that is usefull. Or should i do anything with the TA Backup now?
Thanks again for all replies and i appreciate any further suggestions as I am still trying to get it working but slowly giving up
Raffi
Flash a kernel with a recovery, boot into CWM, see if the phone charges in CWM? If it does, wait for it to charge for an hour then flash a new rom.
I don't know why it goes into flash mode, but it did the same for me when I had low battery. To explain I was on a custom ROM that I let go to 0%, but also vol button boot recovery didn't work on this rom (latest CM10.2). So as soon as I put it on to charge the led went red for a while and then it would boot. At first it would boot up to my lock screen, but the battery was at 0% so a shutting down message would instantly appear, even though a charger was connected.
It would then instantly reboot, but generally it wouldn't make it past the booting splash screen, because the charge was so low. It might do this one or two more times before going dead (charging red led). I left it overnight in the hope it would boot connected to the charger but it didn't happen.
I too knew I had no more than 45 seconds to do anything in flash/fastboot before the phone would power down - so I charged for a bit, as soon as it booted, I hard powered down and went into fastboot, flashed a kernel with CWM (Doomlord's I think), booted into CWM, navigated to the offline fix, flashed it, shut down and hoped it wouldn't boot again...the battery splash screen was very welcome.
Hello,
the advice with the broken offline charging was helping a bit
So because I can only access flashmode (not fastboot) (and am on locked bootloader now) I needed a kernel in the form of *.ftf.
I found this http://forum.xda-developers.com/showthread.php?t=2682412 and flashed the C5303_12.1.A.0.266_C1-FW Kernel in Flashtool.
That indeed helped to charge more. That means that it stayed with a red Led for a long time but did not show anything on the screen. After charging it more I was able to flash the complete Xperia SP (C5303)_12.0.A.2.254_Generic_DE.with_loader.sin without errors.
I was already soo sure it was fixed but the same problems are there again...
-->No offline charging. (or at least this flashmode bootloop)
And right after flashing with some battery left I tried to turn it on again. And it showed the problem that I experienced the last time it was still working months ago. But I just now remembered that I had this problem because it was moths ago...
--> It shows nothing on the screen
That means that there is a very slight backlight illumination but nothing ever on the screen (also no bootlogo etc)
And when i was still on MIUI, shortly before I bricked it by trying to repair that problem, it had the problem too. The Rom was still working normally but it never showed anything on the screen. I could for example feel the vibration when I unlocked the screen so the rom, touch etc was working but nothing on the screen.
And now it shows some similar behavior. But nothing like a working system. (for example the pc doesn't recognise any device, what it should if it would have started the system) Just one vibration when trying to turn it on (that is more than it did before) and a slight illumination of the screen.
And now that the battery if empty again it is back to the flashmode bootloop...
So thank you for the tips but I am still stuck.
Because the system should now be intact I tried Sony Update Service and the repair option of sony pc companion but it still does say that the device is up to date / no software available.
I could try to flash the other kernel and charge it again, unlock the bootloader and flash Doomlordskernel. But does anybody have any idea, why there I still doesn't work and what could cause the screen problem?
Thank you all so much
Raffi
Update: I am again charging it with the 266 kernel and sometimes there is a white line on the most left side of the display from top to bottom...
Has anyone any idea what to do to get the display working again ?
Okay I flashed the .266 Rom and the screen problem is still there. But I got the idea to try out the MHL Adapter I have. And connected to my Screen it actually shows the display :0 So the Rom is at least booting now although the phone is still unusuable...
But there is a test that pops up every 2 seconds saying : "FACTORY STARTUP SERVICE - Please wait for on-screen POWER OFF button".
What can I do to get rid of this?
So maybe the screen is really broken? Bit it keeps displaying a white line... But nothing else... Or might it be a problems with the software that controls the display?
Thank you
Raffi
Raffii said:
Update: I am again charging it with the 266 kernel and sometimes there is a white line on the most left side of the display from top to bottom...
Has anyone any idea what to do to get the display working again ?
Click to expand...
Click to collapse
I think best solution is taking it too service center
Nanostray said:
I think best solution is taking it too service center
Click to expand...
Click to collapse
But after all what i did the warranty is gone for sure
It looks like this and touch is still working.
If I were you, I would simply wipe all and flash stock 4.3 (after locking BL). Everything back to factory.
If it works fine, there is nothing wrong with the phone.
if not - GO TO SONY SERVICE CENTER! You could be having a hardware problem and trying to solve via software.
My 2 cents.
headache59 said:
If I were you, I would simply wipe all and flash stock 4.3 (after locking BL). Everything back to factory.
If it works fine, there is nothing wrong with the phone.
if not - GO TO SONY SERVICE CENTER! You could be having a hardware problem and trying to solve via software.
My 2 cents.
Click to expand...
Click to collapse
Thank you
The bootloader is already locked all the time and this is a complete Stock 4.3 (although Canadian and I am from Germany).
I never thought it would do anything again so this is already great progress
Nobody had this kind of screen problem before?
Assuming it is not hardware issues...also I assume that your phone worked when you bought it (before you start mucking around with it)
Try this:
take any ftf stock from here http://forum.xda-developers.com/showthread.php?t=2311964
.257 or .254 or .266 is fine. Don't reuse your existing stocks.
Flash it using this guide http://forum.xda-developers.com/showthread.php?t=2658952
Reboot.
Don't try to root it.
Let us know what happens...
headache59 said:
Assuming it is not hardware issues...also I assume that your phone worked when you bought it (before you start mucking around with it)
Try this:
take any ftf stock from here http://forum.xda-developers.com/showthread.php?t=2311964
.257 or .254 or .266 is fine. Don't reuse your existing stocks.
Flash it using this guide http://forum.xda-developers.com/showthread.php?t=2658952
Reboot.
Don't try to root it.
Let us know what happens...
Click to expand...
Click to collapse
Thank you for your reply but both stocks I flashed were already from this thread and I flashed them completly (exluding TA) and unmodified
Raffii said:
Thank you for your reply but both stocks I flashed were already from this thread and I flashed them completly (exluding TA) and unmodified
Click to expand...
Click to collapse
I think you lucked out since you can't even flash...unless you have recovery and can install roms using it.
Sony centre is your best bet, sad to say...
Raffii said:
Okay I flashed the .266 Rom and the screen problem is still there. But I got the idea to try out the MHL Adapter I have. And connected to my Screen it actually shows the display :0 So the Rom is at least booting now although the phone is still unusuable...
But there is a test that pops up every 2 seconds saying : "FACTORY STARTUP SERVICE - Please wait for on-screen POWER OFF button".
What can I do to get rid of this?
So maybe the screen is really broken? Bit it keeps displaying a white line... But nothing else... Or might it be a problems with the software that controls the display?
Thank you
Raffi
Click to expand...
Click to collapse
Do what it says - Please wait for on-screen POWER OFF button. I had same. Morning turn On the phone and out of blue saw on screen triangle with tools mark then FACTORY STARTUP SERVICE - Please wait for on-screen POWER OFF button.
---------- Post added at 04:55 PM ---------- Previous post was at 04:48 PM ----------
Raffii said:
Hello,
the advice with the broken offline charging was helping a bit
So because I can only access flashmode (not fastboot) (and am on locked bootloader now) I needed a kernel in the form of *.ftf.
I found this http://forum.xda-developers.com/showthread.php?t=2682412 and flashed the C5303_12.1.A.0.266_C1-FW Kernel in Flashtool.
That indeed helped to charge more. That means that it stayed with a red Led for a long time but did not show anything on the screen. After charging it more I was able to flash the complete Xperia SP (C5303)_12.0.A.2.254_Generic_DE.with_loader.sin without errors.
I was already soo sure it was fixed but the same problems are there again...
-->No offline charging. (or at least this flashmode bootloop)
And right after flashing with some battery left I tried to turn it on again. And it showed the problem that I experienced the last time it was still working months ago. But I just now remembered that I had this problem because it was moths ago...
--> It shows nothing on the screen
That means that there is a very slight backlight illumination but nothing ever on the screen (also no bootlogo etc)
And when i was still on MIUI, shortly before I bricked it by trying to repair that problem, it had the problem too. The Rom was still working normally but it never showed anything on the screen. I could for example feel the vibration when I unlocked the screen so the rom, touch etc was working but nothing on the screen.
And now it shows some similar behavior. But nothing like a working system. (for example the pc doesn't recognise any device, what it should if it would have started the system) Just one vibration when trying to turn it on (that is more than it did before) and a slight illumination of the screen.
And now that the battery if empty again it is back to the flashmode bootloop...
So thank you for the tips but I am still stuck.
Because the system should now be intact I tried Sony Update Service and the repair option of sony pc companion but it still does say that the device is up to date / no software available.
I could try to flash the other kernel and charge it again, unlock the bootloader and flash Doomlordskernel. But does anybody have any idea, why there I still doesn't work and what could cause the screen problem?
Thank you all so much
Raffi
Click to expand...
Click to collapse
When you tried this - Because the system should now be intact I tried Sony Update Service and the repair option of sony pc companion but it still does say that the device is up to date / no software available. you don't need update. Instead use Repair or Reinstall option. If it fix the issue leave it stock so at least you can use it...
Thank you all. But I already tried the repair option in PC Companion but I will try it again when after I charged the phone to 100% to have some more time to play around.
And I still hope that it is software related but I am having less and less hope.
Because a new display is expensive Especially when the device is only 210€ now in Germany and I paid 350€ 10 months ago and only used it for a few months
Raffii said:
Thank you all. But I already tried the repair option in PC Companion but I will try it again when after I charged the phone to 100% to have some more time to play around.
And I still hope that it is software related but I am having less and less hope.
Because a new display is expensive Especially when the device is only 210€ now in Germany and I paid 350€ 10 months ago and only used it for a few months
Click to expand...
Click to collapse
I don't think anyone at sony SC checks for UL/root. I think you'll get it fixed under warranty
Nanostray said:
I don't think anyone at sony SC checks for UL/root. I think you'll get it fixed under warranty
Click to expand...
Click to collapse
+1
Just in case one of the devs works for sony in your hometown :laugh:- delete any root and recoveries in your phone before going in.
10 months - still under warranty.

Error While Upgrading my kitkat to lolipop.

hey guys, i rooted my phone few months ago and now lolipop came out, i cant upgrade from my phone directly idk why?> i gave me error like u cant update ur device. but then i try to update it with flasshtoll i have fully installed driver for my zr c5502.
but when i flash my phone and files are about to prepare i got error like this---
INFO - start flashing
INFO - flashing loader.sin
INFO - checking header
ERROR - processing of loader.sin finished with error
INFO - Ending flash session
ERROR -
ERROR - error flashinbg aborted
gaggi786 said:
hey guys, i rooted my phone few months ago and now lolipop came out, i cant upgrade from my phone directly idk why?> i gave me error like u cant update ur device. but then i try to update it with flasshtoll i have fully installed driver for my zr c5502.
but when i flash my phone and files are about to prepare i got error like this---
INFO - start flashing
INFO - flashing loader.sin
INFO - checking header
ERROR - processing of loader.sin finished with error
INFO - Ending flash session
ERROR -
ERROR - error flashinbg aborted
Click to expand...
Click to collapse
Dude I Think You Had Unlocked Your Bootloader , Lock Bootloader And Try To Flash Your Device Again ,And Connect Your Device In Flashing Mode By Pressing Volume Down Button While Connecting To PC It Will Flash Successfully. Still Any Problem Occurs Reply

(SOLVED)Xperia T (Lt30p) doesnt turn after flash

It seems that the newer version of flashtool had something weird that made the rom didnt flahs correctly, i just downgraded it and my phone is on again
Ok, I found way deeper a way to instal recovery from usb, and it didnt worked, so decided to give the next step, flashing a ROM
I went first for the 4.3 in order to root and later install recovery, the problem is, it doesnt go beyond the sony logo
Then I decided to making it back to 4.1 , and it only shows a triangle of warning and a small phone picture
Then i used another rom of original stock of 4.1, and it happens the same
The thing is the "newer" flashtool only recognize the ttf of 4.3 , with the other rooms always shows me a warning about the folder of firmwares, but when i try to flash it(4.3 with a lower label as custom) it marks me an error when is flashing the system:
09/007/2018 17:07:16 - INFO - Closing TA partition
09/007/2018 17:07:16 - INFO - Opening TA partition 2
09/007/2018 17:07:16 - INFO - Processing system.sin
09/007/2018 17:07:16 - INFO - Checking header
09/007/2018 17:07:17 - ERROR - Processing of system.sin finished with errors.
09/007/2018 17:07:17 - INFO - Ending flash session
09/007/2018 17:07:17 - ERROR -
09/007/2018 17:07:17 - ERROR - Error flashing. Aborted
I used a not so old flash tool I have, and it flashes the phone, doesnt tell me any errors, but the phone doesnt turn on anymore
And Xperia companion only says that there was an error trying to repair the software
Any help?

Categories

Resources