Related
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.
Hi, i have xperia V (protoype). It was working fine, until i decide to put new Android (i was 4.0.4 on it). I don't have much of experience in flashing, but i did success already with my two other phones (ARC and P ), so i thought this time will be easy as usually. but...
phone was dead as stone..i spend more than week to trying all methods what i was able to find. now it's a big mess in my head and my PC, but now i made phone to start in recovery menu. thats all. tried install different roms, cyanomodgens-nothing... it just shows me SONY-->cyanomodgen and freez. at the moment flashtool can't see my phone.
if anyone can help me what to do( step by step), how to make this phone working again -i will be very happy person.
sorry for english.
vibogd said:
Hi, i have xperia V (protoype). It was working fine, until i decide to put new Android (i was 4.0.4 on it). I don't have much of experience in flashing, but i did success already with my two other phones (ARC and P ), so i thought this time will be easy as usually. but...
phone was dead as stone..i spend more than week to trying all methods what i was able to find. now it's a big mess in my head and my PC, but now i made phone to start in recovery menu. thats all. tried install different roms, cyanomodgens-nothing... it just shows me SONY-->cyanomodgen and freez. at the moment flashtool can't see my phone.
if anyone can help me what to do( step by step), how to make this phone working again -i will be very happy person.
sorry for english.
Click to expand...
Click to collapse
Try a clean install :
Wipe Data + Cache + System + Dalvik
vibogd said:
Hi, i have xperia V (protoype). It was working fine, until i decide to put new Android (i was 4.0.4 on it). I don't have much of experience in flashing, but i did success already with my two other phones (ARC and P ), so i thought this time will be easy as usually. but...
phone was dead as stone..i spend more than week to trying all methods what i was able to find. now it's a big mess in my head and my PC, but now i made phone to start in recovery menu. thats all. tried install different roms, cyanomodgens-nothing... it just shows me SONY-->cyanomodgen and freez. at the moment flashtool can't see my phone.
if anyone can help me what to do( step by step), how to make this phone working again -i will be very happy person.
sorry for english.
Click to expand...
Click to collapse
how did you install recovery?
Aria.A97 said:
Try a clean install :
Wipe Data + Cache + System + Dalvik
Click to expand...
Click to collapse
did it 1000000000 times-and nothing... completely lost.
vibogd said:
did it 1000000000 times-and nothing... completely lost.
Click to expand...
Click to collapse
can you tell me how you installed recovery?
isko95 said:
can you tell me how you installed recovery?
Click to expand...
Click to collapse
just make it clear.. is it menu when need to press volume button when "sony" appears on the screen?
i can't tell you exactly how i did it- i did it with flashboot (boot.img or something), don't remember. didn't touch the phone for week, because i don't know what and how to do. as i said, i need step-by-step advice from beginning. if anyone will help me-i will be sooo happy
1. Is your bootloader unlocked - and did you test if your BL is/was unlockable?
If BL is unlocked correctly:
2. Try to flash another kernel in recovery,such as http://forum.xda-developers.com/showthread.php?t=2223534
Then try to install a CM-ROM for example.
dyfk3l said:
1. Is your bootloader unlocked - and did you test if your BL is/was unlockable?
If BL is unlocked correctly:
2. Try to flash another kernel in recovery,such as http://forum.xda-developers.com/showthread.php?t=2223534
Then try to install a CM-ROM for example.
Click to expand...
Click to collapse
1. i did kernel install
2. CM install shows me some errors. can you drop me link for rom, please?
p.s. tried another CM-and again: "sony"->"cyanogenmod"->blank screen (phone is on)
We cannot help you unless you answer our questions correctly.
BL unlocked correctly?
Already tried another kernel?
dyfk3l said:
We cannot help you unless you answer our questions correctly.
BL unlocked correctly?
Already tried another kernel?
Click to expand...
Click to collapse
well, i did unlock ( i was thinking i did it-got code, entered it). and now i got message on flashtool
- Reading device information
29/018/2014 19:18:27 - INFO - Unable to read from phone after having opened it.
29/018/2014 19:18:27 - INFO - trying to continue anyway
29/018/2014 19:18:32 - INFO - Processing loader.sin
29/018/2014 19:18:32 - INFO - Checking header
29/018/2014 19:18:32 - ERROR - Error in processHeader : 6 : The handle is invalid.
29/018/2014 19:18:32 - INFO - Your phone bootloader cannot be officially unlocked
when i do that "fastboot.exe -i 0x0fce oem unlock 0xxxxxx" it says "phone is already unlocked! "
yes, i tried different kernels.
there are so many files with *.img, sin, elf, ftf -i don't have clue what has to be done.
when phone was OK i checke in service (?) menu and it was "bootloader unlock allowed-yes"
i'm trying to answer as much as i can.
vibogd said:
29/018/2014 19:18:32 - INFO - Your phone bootloader cannot be officially unlocked
Click to expand...
Click to collapse
That sounds strange - because you said that service menu allowed unlocking bootloader. To be honest, I don't know what happens if try to unlock a bootloader which is not unlockable.
Regarding flashing: Take the NKernel from my link, open the ZIP file and extract the kernel.elf.
Then flash elf file via fastboot: fastboot flash boot kernel.elf
And then try to get into recovery and then try to flash a CM ROM like this from your external SD: https://download.cyanogenmod.org/get/jenkins/39793/cm-10.1.3-RC1-tsubasa.zip (10.1.3-RC1).
dyfk3l said:
That sounds strange - because you said that service menu allowed unlocking bootloader. To be honest, I don't know what happens if try to unlock a bootloader which is not unlockable.
Regarding flashing: Take the NKernel from my link, open the ZIP file and extract the kernel.elf.
Then flash elf file via fastboot: fastboot flash boot kernel.elf
And then try to get into recovery and then try to flash a CM ROM like this from your external SD: https://download.cyanogenmod.org/get/jenkins/39793/cm-10.1.3-RC1-tsubasa.zip (10.1.3-RC1).
Click to expand...
Click to collapse
can't see kernel.elf in zip.
vibogd said:
can't see kernel.elf in zip.
Click to expand...
Click to collapse
It's in #7 where I asked you the first time to try another kernel!
http://forum.xda-developers.com/showpost.php?p=52279445&postcount=7
Try installing the ROM with NKernel recovery, otherwise you can flash the boot.img from the CM ROM (inside zip, also via fastboot). Can you install the ROM with one of the kernels?
dyfk3l said:
It's in #7 where I asked you the first time to try another kernel!
http://forum.xda-developers.com/showpost.php?p=52279445&postcount=7
Try installing the ROM with NKernel recovery, otherwise you can flash the boot.img from the CM ROM (inside zip, also via fastboot). Can you install the ROM with one of the kernels?
Click to expand...
Click to collapse
ok... i installed kernel.elf, when i reboot into recover mode i was unable to choose anything-touchscreen doesn't respond, buttons does nothing aswell.
i'm sure i do everything ok, but every time phone stuck on second screen after "sony"
after flahsing boot.img phone stuck on first screen"sony"
p.s i don't know if that is important, but almost every time pc trying to instal drivers, but...MTP drivers was not instaled
vibogd said:
i'm sure i do everything ok, but every time phone stuck on second screen after "sony"
Click to expand...
Click to collapse
That's normal, you can't boot a CM Rom with NKernel (which is for stock 4.1). You always need the right kernel for every Rom (and Rom generation - a CM 11 kernel won't boot with CM 10.2).
It was just to test if recovery is working. But you say it doesn't respond? Of course tochscreen is not working in CWM! You have to navigate with Vol up/down and enter via power button. I hope you know that?!
Go ahead and try different kernels/Roms. Like this: http://aokp.co/devices/tsubasa
Install boot.img from zip via fastboot, go into recovery and try to install the AOKP Rom from your externel SD card. Does recovery work? Can you install Rom?
dyfk3l said:
That's normal, you can't boot a CM Rom with NKernel (which is for stock 4.1). You always need the right kernel for every Rom (and Rom generation - a CM 11 kernel won't boot with CM 10.2).
It was just to test if recovery is working. But you say it doesn't respond? Of course tochscreen is not working in CWM! You have to navigate with Vol up/down and enter via power button. I hope you know that?!
Go ahead and try different kernels/Roms. Like this: http://aokp.co/devices/tsubasa
Install boot.img from zip via fastboot, go into recovery and try to install the AOKP Rom from your externel SD card. Does recovery work? Can you install Rom?
Click to expand...
Click to collapse
yes, i know have to use vol + -, but noone button works.
one more q.. it doesn't matter prototype phone or not? uufff.. i'm almost give up. looks like i'm doing same and same every time and no effect.
thanks for helping and not leaving me alone with that head pain
p.s. just installed boot.img, but when tried to run recovery-just dead androbot appears on the screen
Sorry, but I've got no idea.
I never had the problem that a flashed kernel's recovery is not working - and I don't know why. Sorry.
Must have to do with the Flashtool message that your bootloader cannot be unlocked. There is sth. really strange...
dyfk3l said:
Sorry, but I've got no idea.
I never had the problem that a flashed kernel's recovery is not working - and I don't know why. Sorry.
Must have to do with the Flashtool message that your bootloader cannot be unlocked. There is sth. really strange...
Click to expand...
Click to collapse
01/022/2014 13:22:35 - INFO - Please check the log before rebooting into system
01/022/2014 13:22:44 - INFO - Device disconnected
01/022/2014 13:22:49 - INFO - Please connect your device into flashmode.
01/022/2014 13:22:55 - INFO - Device connected in flash mode
01/022/2014 13:22:55 - INFO - Opening device for R/W
01/022/2014 13:22:55 - INFO - Reading device information
01/022/2014 13:22:55 - INFO - Phone ready for flashmode operations.
01/022/2014 13:22:55 - INFO - Current device : Unknown: Mar 29 2013/12:30:02 - CB5A1KBDPF - Unknown: Mar 29 2013/12:30:02 - Unknown: Mar 29 2013/12:30:02 - Unknown: Mar 29 2013/12:30:02
01/023/2014 13:23:04 - INFO - Processing loader.sin
01/023/2014 13:23:04 - INFO - Checking header
01/023/2014 13:23:04 - INFO - Flashing data
01/023/2014 13:23:10 - INFO - Loader : S1_Root_7054 - Version : R5A058 / Boot version : R10A112 / Bootloader status : ROOTABLE
01/023/2014 13:23:10 - INFO - Start Reading unit 000008B2
01/023/2014 13:23:10 - INFO - Reading TA finished.
01/023/2014 13:23:14 - INFO - Unlocking device
01/023/2014 13:23:14 - INFO - Writing TA unit : [00, 00, 08, B2, 00, 00, 00, 10, 35, 34, 34, 43, 32, 44, 34, 45, 35, 41, 41, 32, 41, 32, 37, 44]
01/023/2014 13:23:14 - INFO - Unlock finished
01/023/2014 13:23:23 - INFO - Ending flash session
01/023/2014 13:23:23 - INFO - You can now unplug and restart your device
01/023/2014 13:23:23 - INFO - Device connected in flash mode
01/023/2014 13:23:24 - INFO - Device disconnected
01/023/2014 13:23:26 - INFO - Device connected in flash mode
as i can understand-i did unlock.
I suggest to flash stock ROM and then relock your bootloader
Aria.A97 said:
I suggest to flash stock ROM and then relock your bootloader
Click to expand...
Click to collapse
when i flashed ftf (flashmode), phone is not responding at all ( just one vibro when press on button) and screen stays black.
Hello, I Have Tmobile C6606
So here is what i did:
-I first rooted
-Then I installed TWRP
-I then tried to install a ROM and followed "Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool"
-So i picked up Xperia Z (C6603) 10.3.1.A.2.74 T-Mobile NL ( Dont know what I was thinking... I should of known.)
-Flashed it with Flashtool and now it boots up in a different language AND after I unlock the lock screen
it goes black and reboots ><. I cant get into settings or anything, Cant even see the homescreen.
I then found C6606_T-Mobile US_1272-8668_10.4.C.0.814_R12C and tried to flash it knowing that I had messed up
with a different firmware from NL. BUT this is all I get:
- Device connected in flash mode
- Selected Bundle for Sony Xperia Z (C6606). FW release : 10.1.C.0.814. Customization : Sony
- Preparing files for flashing
- Please connect your device into flashmode.
- Opening device for R/W
- Reading device information
- Phone ready for flashmode operations.
- Current device : C6603 - CB5A1T7GGU - 1270-3839_R7B - 1269-5309_10.3.1.A.2.74 - TELEKOM-LTE_10.3.1.A.2.74
- Start Flashing
- Processing loader.sin
- Checking header
- Flashing data
- Processing of loader.sin finished.
- Loader : S1_Root_5ca3 - Version : APQ8064_30 / Boot version : S1_Boot_Lagan_1.1.1_1 / Bootloader status : NOT_ROOTABLE
- No bootdelivery to send
- Ending flash session
- Flashing finished.
- Please unplug and start your phone
- For flashtool, Unknown Sources and Debugging must be checked in phone settings
- Device connected in flash mode
I know I messed up and I am hoping there is a fix for this, Any advice or Ideas are appreciated.
Thanks in advance.
psycho-punk said:
Do you have the logs from when you flashed C6603 FTF?
Sent from my Paranoid ZL
Click to expand...
Click to collapse
No, Dont have the logs
1281
psycho-punk said:
I'm no expert, but maybe I can help. Can you take a screenshot of what the C6606 FTF contains and post it here?
Sent from my Paranoid ZL
---------- Post added at 07:27 AM ---------- Previous post was at 07:08 AM ----------
Maybe you should try the C6606 .230 FTF on 'Firmware' page of Flashtool's website.
Do post the logs.
Sent from my Paranoid ZL
Click to expand...
Click to collapse
I just flashed "10.5.A.0.230 Customized US"
And it booted and seems to be functional on this firmware.
Noobie974 said:
Hello, I Have Tmobile C6606
So here is what i did:
-I first rooted
-Then I installed TWRP
-I then tried to install a ROM and followed "Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool"
-So i picked up Xperia Z (C6603) 10.3.1.A.2.74 T-Mobile NL ( Dont know what I was thinking... I should of known.)
-Flashed it with Flashtool and now it boots up in a different language AND after I unlock the lock screen
it goes black and reboots ><. I cant get into settings or anything, Cant even see the homescreen.
I then found C6606_T-Mobile US_1272-8668_10.4.C.0.814_R12C and tried to flash it knowing that I had messed up
with a different firmware from NL. BUT this is all I get:
- Device connected in flash mode
- Selected Bundle for Sony Xperia Z (C6606). FW release : 10.1.C.0.814. Customization : Sony
- Preparing files for flashing
- Please connect your device into flashmode.
- Opening device for R/W
- Reading device information
- Phone ready for flashmode operations.
- Current device : C6603 - CB5A1T7GGU - 1270-3839_R7B - 1269-5309_10.3.1.A.2.74 - TELEKOM-LTE_10.3.1.A.2.74
- Start Flashing
- Processing loader.sin
- Checking header
- Flashing data
- Processing of loader.sin finished.
- Loader : S1_Root_5ca3 - Version : APQ8064_30 / Boot version : S1_Boot_Lagan_1.1.1_1 / Bootloader status : NOT_ROOTABLE
- No bootdelivery to send
- Ending flash session
- Flashing finished.
- Please unplug and start your phone
- For flashtool, Unknown Sources and Debugging must be checked in phone settings
- Device connected in flash mode
I know I messed up and I am hoping there is a fix for this, Any advice or Ideas are appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Ok,
Download the stock firmware for ur mobile. Then keep the firmware in firmware folder in flashtool folder, then flash the firmware in flash mode, dont change any settings. While flashtool preparing the file dont attachbusb till the flashtool ask you
Try this, then tell me again
psycho-punk said:
Did you download the firmware from the link I mentioned?
Sent from my Paranoid ZL
Click to expand...
Click to collapse
Yea I did, Iam on
Model Number: C6616
Android: 4.4.2
This is Awesome, Thought i had ruined it.
Thank you very much for your time and quick response
I can now sleep in peace (its 12:43AM)
I have Sony Xperia Z c6603 (Vodafone IT). I am attempting to flash ftf to have it access the US bands. I have tried:
10.5.A.0.230 C6606 Customize US and C6506 Customize US;
10.4.C.0.814 C6606 T-mobile US (i do have a tmo sim);
14.4.A.0.108 c6806 Customize US; 10.4.B.0.569 c6506 Customize US. All downloaded through the "Check updates" tool in Flasher by Androxyde. None of these attempts have been successful. They have all be attempted several time. Right now I have my phone charging and it is stuck in a reboot loop. My latest attempt was the 10.4.C.0.814 C6606 T-mobile US. I get the t-mobile screen and even gets me as far as the lock screen, but then just black and moments later a reboot. The first time I try to boot my phone after flashing 10.4.C.0.814 C6606 T-mobile US (before the boot loops begins) I did get a dialog box staying "Process system isn't responding. Do you you want to close it?" wait button or OK button. Frankly I would like to have the c6506 or the c6806 firmware, but t-mobile is getting me a tad further than the other versions.
However the only common denominator between every attempt is the follow text in the log
20/004/2014 11:04:23 - INFO - Ending flash session
20/004/2014 11:04:23 - INFO - Flashing finished.
20/004/2014 11:04:23 - INFO - Please unplug and start your phone
20/004/2014 11:04:23 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
20/004/2014 11:04:23 - INFO - Device connected in flash mode
20/008/2014 11:08:30 - INFO - Device disconnected
I have been re-flashing this thing over and over and I have repaired it with Sony Mac Bridge a couple time. After the repair and before I semi bricked this thing, I did check debugging and unknown sources. That was several attempts ago, though. I have not been able to boot the phone.
Any suggestions?
p.s. i have also tried to flash ftf from the link you provided and have had no luck with those either. I am going to try that again while I wait for the cyber forum gods to send me any suggestions.
hi everyone
i have a xperia sp c5303 and this information you need to know:
1) unlocked bootloader
2) i had Mahdi Rom ver 2.7
3) williams kernel v42
now my problem
my phone suddenly restart and stop on boot loop
then i try to flash with flash tools and i notice it's not work for the first time because i flash sevral time my phone and others
then try fast boot and not work again
then start search and realize my phone had hard break or soft break ( i cant realize diff between two )
now that's interesting because my battery level is so low and i need to wall charge for hours to get the green ( when connect to charger sony arm show and red led on and 3 sec later black screen and red led off . 2 hours later red les startin on and 30min laters turn to green and on my phone show battery level of full )
but when i want to flash for 10 sec battery die and flash give me nothing
24/051/2014 12:51:15 - INFO - Selected Bundle for Xperia SP(C5303). FW release : 12.0.A.2.266. Customization : Middle East
24/051/2014 12:51:15 - INFO - Preparing files for flashing
24/051/2014 12:51:28 - INFO - Please connect your device into flashmode.
24/051/2014 12:51:30 - INFO - Device connected in flash mode
24/051/2014 12:51:30 - INFO - Opening device for R/W
24/051/2014 12:51:30 - INFO - Reading device information
24/051/2014 12:51:31 - INFO - Phone ready for flashmode operations.
24/051/2014 12:51:31 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
24/051/2014 12:51:31 - INFO - Start Flashing
24/051/2014 12:51:31 - INFO - Processing loader.sin
24/051/2014 12:51:31 - INFO - Checking header
24/051/2014 12:51:31 - INFO - Flashing data
24/051/2014 12:51:31 - INFO - Processing of loader.sin finished.
24/051/2014 12:51:32 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
24/053/2014 12:53:48 - INFO - Ending flash session
and then nothing happen and my phone led on the flash mode goes off and battery die and i try to start again of begining
any suggestion for you guys can help me please ?
if i try oppen the phone by myself ( because i repair laptop ) and change the battery . do you think i can flash again and the error in flash mode because of battery level .
thx
more information about fastboot
when I want to flash kernel (boot.img) with fastboot phone very easily goes to fastboot mode and blue led start and when i want to start flash here goes nothing ( waiting for my phone ) that's weird because program said the phone connected.
although i try to flash kernel with QuikIMG too and the same happens.
need your suggest ...
rayanafshan said:
hi everyone
i have a xperia sp c5303 and this information you need to know:
1) unlocked bootloader
2) i had Mahdi Rom ver 2.7
3) williams kernel v42
now my problem
my phone suddenly restart and stop on boot loop
then i try to flash with flash tools and i notice it's not work for the first time because i flash sevral time my phone and others
then try fast boot and not work again
then start search and realize my phone had hard break or soft break ( i cant realize diff between two )
now that's interesting because my battery level is so low and i need to wall charge for hours to get the green ( when connect to charger sony arm show and red led on and 3 sec later black screen and red led off . 2 hours later red les startin on and 30min laters turn to green and on my phone show battery level of full )
but when i want to flash for 10 sec battery die and flash give me nothing
24/051/2014 12:51:15 - INFO - Selected Bundle for Xperia SP(C5303). FW release : 12.0.A.2.266. Customization : Middle East
24/051/2014 12:51:15 - INFO - Preparing files for flashing
24/051/2014 12:51:28 - INFO - Please connect your device into flashmode.
24/051/2014 12:51:30 - INFO - Device connected in flash mode
24/051/2014 12:51:30 - INFO - Opening device for R/W
24/051/2014 12:51:30 - INFO - Reading device information
24/051/2014 12:51:31 - INFO - Phone ready for flashmode operations.
24/051/2014 12:51:31 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
24/051/2014 12:51:31 - INFO - Start Flashing
24/051/2014 12:51:31 - INFO - Processing loader.sin
24/051/2014 12:51:31 - INFO - Checking header
24/051/2014 12:51:31 - INFO - Flashing data
24/051/2014 12:51:31 - INFO - Processing of loader.sin finished.
24/051/2014 12:51:32 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
24/053/2014 12:53:48 - INFO - Ending flash session
and then nothing happen and my phone led on the flash mode goes off and battery die and i try to start again of begining
any suggestion for you guys can help me please ?
if i try oppen the phone by myself ( because i repair laptop ) and change the battery . do you think i can flash again and the error in flash mode because of battery level .
more information about fastboot
when I want to flash kernel (boot.img) with fastboot phone very easily goes to fastboot mode and blue led start and when i want to start flash here goes nothing ( waiting for my phone ) that's weird because program said the phone connected.
although i try to flash kernel with QuikIMG too and the same happens.
need your suggest ...
thx
Click to expand...
Click to collapse
anyone please...
hey guys . im still waiting ...
Try using a different usb port on your laptop or a different usb cable. Sometimes flashing may fail due to damaged usb port or cable. Also try using the usb cable that sony bundled with your phone (I used LG cable and didnt work for me). If that doesnt work, it seems that your battery is dead.
tj_droid said:
Try using a different usb port on your laptop or a different usb cable. Sometimes flashing may fail due to damaged usb port or cable. Also try using the usb cable that sony bundled with your phone (I used LG cable and didnt work for me). If that doesnt work, it seems that your battery is dead.
Click to expand...
Click to collapse
1) i use my pc and my sony laptop and 3 diffrent cable sony nokia sony
2) i try diffrent usb port such az usb2 and usb3
3) when i try to flash in flashmod with flashtool after
24/051/2014 12:51:15 - INFO - Selected Bundle for Xperia SP(C5303). FW release : 12.0.A.2.266. Customization : Middle East
24/051/2014 12:51:15 - INFO - Preparing files for flashing
24/051/2014 12:51:28 - INFO - Please connect your device into flashmode.
24/051/2014 12:51:30 - INFO - Device connected in flash mode
24/051/2014 12:51:30 - INFO - Opening device for R/W
24/051/2014 12:51:30 - INFO - Reading device information
24/051/2014 12:51:31 - INFO - Phone ready for flashmode operations.
24/051/2014 12:51:31 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
24/051/2014 12:51:31 - INFO - Start Flashing
24/051/2014 12:51:31 - INFO - Processing loader.sin
24/051/2014 12:51:31 - INFO - Checking header
24/051/2014 12:51:31 - INFO - Flashing data
24/051/2014 12:51:31 - INFO - Processing of loader.sin finished.
24/051/2014 12:51:32 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
24/053/2014 12:53:48 - INFO - Ending flash session
this log green led for flash mod turn off ( when i try to flash and connect usb until green led off take 5 sec not more)
4) if my battery dead if replace with new one ... can flash it again?
thx for respond
if my battery dead if replace with new one ... can flash it again?
Hello.
It could help others more if you could describe what happened when you tried to turn on the phone, after the flashmode LED turned off? Thanks.
rayanafshan said:
if my battery dead if replace with new one ... can flash it again?
Click to expand...
Click to collapse
Try locking your bootloader first (If it possible through fastboot). Looking at the errors the flashtool is giving, it seems like the flashing stops because bootloader is unlocked. Even if you read flashtool thread, it says bootloader should be locked (as far as I remember, havent visited the thread since a long time)
TechnoSparks said:
Hello.
It could help others more if you could describe what happened when you tried to turn on the phone, after the flashmode LED turned off? Thanks.
Click to expand...
Click to collapse
battery dead and need recycle again for more hours.
tj_droid said:
Try locking your bootloader first (If it possible through fastboot). Looking at the errors the flashtool is giving, it seems like the flashing stops because bootloader is unlocked. Even if you read flashtool thread, it says bootloader should be locked (as far as I remember, havent visited the thread since a long time)
Click to expand...
Click to collapse
that is actually good idea thx . i'll gonna working on that and let you know for 5-6 hours.
thank you both for respond.
rayanafshan said:
battery dead and need recycle again for more hours.
that is actually good idea thx . i'll gonna working on that and let you know for 5-6 hours.
thank you both for respond.
Click to expand...
Click to collapse
i try and that's result
when i want to relock my phone with flashtool ( because my phone sp 2013 for sony and they said we must do it this way for relock) here it is my log
27/004/2014 21:04:34 - INFO - Device connected in flash mode
27/004/2014 21:04:35 - INFO - Opening device for R/W
27/004/2014 21:04:35 - INFO - Reading device information
27/004/2014 21:04:35 - INFO - Phone ready for flashmode operations.
27/004/2014 21:04:35 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
27/004/2014 21:04:38 - INFO - Processing loader.sin
27/004/2014 21:04:38 - INFO - Checking header
27/004/2014 21:04:38 - INFO - Flashing data
27/004/2014 21:04:38 - INFO - Processing of loader.sin finished.
27/004/2014 21:04:39 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
27/004/2014 21:04:39 - INFO - Start Reading unit 000008B2
27/004/2014 21:04:39 - INFO - Reading TA finished.
and stop and 5 min later when i disconnect the phone this log
27/031/2014 23:31:55 - ERROR - Read error :31 : A device attached to the system is not functioning.
27/031/2014 23:31:55 - INFO - Your phone bootloader cannot be officially unlocked
27/031/2014 23:31:55 - INFO - You can now unplug and restart your phone
and when ii see this i try to use rubber band trick and see this in the morning
28/035/2014 06:35:09 - INFO - Device connected with USB debugging off
28/035/2014 06:35:09 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/035/2014 06:35:10 - INFO - Device disconnected
28/045/2014 06:45:01 - INFO - Device connected in flash mode
28/045/2014 06:45:43 - INFO - Device disconnected
28/049/2014 06:49:14 - INFO - Device connected with USB debugging off
28/049/2014 06:49:14 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/049/2014 06:49:18 - INFO - Device disconnected
28/058/2014 06:58:45 - INFO - Device connected in flash mode
28/059/2014 06:59:28 - INFO - Device disconnected
28/002/2014 07:02:55 - INFO - Device connected with USB debugging off
28/002/2014 07:02:55 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/002/2014 07:02:59 - INFO - Device disconnected
28/012/2014 07:12:26 - INFO - Device connected in flash mode
28/013/2014 07:13:09 - INFO - Device disconnected
28/016/2014 07:16:32 - INFO - Device connected with USB debugging off
28/016/2014 07:16:32 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/016/2014 07:16:36 - INFO - Device disconnected
28/026/2014 07:26:02 - INFO - Device connected in flash mode
28/026/2014 07:26:45 - INFO - Device disconnected
28/030/2014 07:30:08 - INFO - Device connected with USB debugging off
28/030/2014 07:30:08 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/030/2014 07:30:12 - INFO - Device disconnected
28/039/2014 07:39:39 - INFO - Device connected in flash mode
28/040/2014 07:40:21 - INFO - Device disconnected
28/043/2014 07:43:41 - INFO - Device connected with USB debugging off
and this repeat again and again . interesting was i am always active usb debugging mode and now log said is off. i confused here
now my usb debugging off how flash what can i do now .
for unlocked bootloader for flash
i want my phone back
help
Okay the problem is getting worse. Have you tried to unlock your bootloader again? If not, please try so. I have a final option for you to decide.
TechnoSparks said:
Okay the problem is getting worse. Have you tried to unlock your bootloader again? If not, please try so. I have a final option for you to decide.
Click to expand...
Click to collapse
i try several time .
this morning
there is another way to relock bootloader other than flashtool for sp?
if there are other way please.. or if any way to back my phone .
rayanafshan said:
i try several time .
this morning
there is another way to relock bootloader other than flashtool for sp?
if there are other way please.. or if any way to back my phone .
Click to expand...
Click to collapse
Please understand my posts correctly. Are you currently on an unlocked bootloader? Or if you can confirm it is locked, do you manage to be able to unlock the bootloader through the Flashtool?
TechnoSparks said:
Please understand my posts correctly. Are you currently on an unlocked bootloader? Or if you can confirm it is locked, do you manage to be able to unlock the bootloader through the Flashtool?
Click to expand...
Click to collapse
ohhh ok i get wrong . now i found you mean i unlocked bootloader however it is unlocked. ok i try and ley your know
rayanafshan said:
ohhh ok i get wrong . now i found you mean i unlocked bootloader however it is unlocked. ok i try and ley your know
Click to expand...
Click to collapse
hi again
now result
in 2days i try evrything
1- i try to unlocked again with fastboot but fastboot said you unlocked bootloader before and then finished
2- try to unlocked bootloader with flashtool with the final version and when said connect your phone with flashmode and i did it then said pick your model phone and i select xperia sp and green led turn off ang didnt enything
i unlocked bootloader before many time and now i'm stuck
if there is another way please let me know?
rayanafshan said:
hi again
now result
in 2days i try evrything
1- i try to unlocked again with fastboot but fastboot said you unlocked bootloader before and then finished
2- try to unlocked bootloader with flashtool with the final version and when said connect your phone with flashmode and i did it then said pick your model phone and i select xperia sp and green led turn off ang didnt enything
i unlocked bootloader before many time and now i'm stuck
if there is another way please let me know?
Click to expand...
Click to collapse
I can't really help if I don't know the current state of your bootloader
Your last option here is to retry flashing a stock ROM FTF onto your phone. I hope it will work. [Choose your desired stock ROM based on your XSP model here]
TechnoSparks said:
I can't really help if I don't know the current state of your bootloader
Your last option here is to retry flashing a stock ROM FTF onto your phone. I hope it will work. [Choose your desired stock ROM based on your XSP model here]
Click to expand...
Click to collapse
I really do not understand what you asking from me
if you want to know about my bootloader : is 100% unlocked and when i try to unlocked again it's said you bootloader unloacked if you need i posted log from fastboot here
also i try more than 100 times to flash with stock ftf of my phone and also flash kernel stock and flash recovery for unlocked and locked bootloader . i try everything in this froum and others
i dont know why when i want to flash kernel ( stock and cm) is stuck on
flashing...
and blue led is on untill battery dead and myphone not respond to program
i posted logs before
here situation of my phone
xperia sp xx03
bootloader unlocked
android 4.4.4 mahdi version 2.8
recovery cm11_williams_kernel_v4
evrything start of here 3 weeks ago
((my phone restart and when i far from my phone , it stucked on boot logo animation for 3 or 4 hours and when i found my phone situation shutdown my phone via the OFF botton of the back of my phone.))
and then i try to flash FTF stock or CM from MahdiRom or any rom , did not let me. and you know others untill now ?
I research and i Think the only way is from Fastboot mode and fstboot program with terminal function .
can you undrestand my problem know please?
rayanafshan said:
I really do not understand what you asking from me
if you want to know about my bootloader : is 100% unlocked and when i try to unlocked again it's said you bootloader unloacked if you need i posted log from fastboot here
also i try more than 100 times to flash with stock ftf of my phone and also flash kernel stock and flash recovery for unlocked and locked bootloader . i try everything in this froum and others
i dont know why when i want to flash kernel ( stock and cm) is stuck on
flashing...
and blue led is on untill battery dead and myphone not respond to program
i posted logs before
here situation of my phone
xperia sp xx03
bootloader unlocked
android 4.4.4 mahdi version 2.8
recovery cm11_williams_kernel_v4
evrything start of here 3 weeks ago
((my phone restart and when i far from my phone , it stucked on boot logo animation for 3 or 4 hours and when i found my phone situation shutdown my phone via the OFF botton of the back of my phone.))
and then i try to flash FTF stock or CM from MahdiRom or any rom , did not let me. and you know others untill now ?
I research and i Think the only way is from Fastboot mode and fstboot program with terminal function .
can you undrestand my problem know please?
Click to expand...
Click to collapse
My intention or objective right now is to have you successfully boot up your phone and restore it without relying on flashtool so much.
Since you said your bootloader is unlocked, you'll now left to flash DoomLord's advanced kernel that will give you recovery access.
Because my understanding is limited, based on your posts earlier, it seemed you indeed tried to flash a kernel via fastboot but your phone died. Based on multiple logs, there are also multiple errors that seemed to be involving hardware. And due to that kind of advanced log error I must apologise and tell you that I am now unable to help you.
Your log listed so many errors, it even unable to detect the model number of your phone, nor the current state of your bootloader (on newer posts).
If you wish to try my last suggestion, do said so. Otherwise, I have to back myself out of this since it is not my expertise.
I am very sorry
TechnoSparks said:
My intention or objective right now is to have you successfully boot up your phone and restore it without relying on flashtool so much.
Since you said your bootloader is unlocked, you'll now left to flash DoomLord's advanced kernel that will give you recovery access.
Because my understanding is limited, based on your posts earlier, it seemed you indeed tried to flash a kernel via fastboot but your phone died. Based on multiple logs, there are also multiple errors that seemed to be involving hardware. And due to that kind of advanced log error I must apologise and tell you that I am now unable to help you.
Your log listed so many errors, it even unable to detect the model number of your phone, nor the current state of your bootloader (on newer posts).
If you wish to try my last suggestion, do said so. Otherwise, I have to back myself out of this since it is not my expertise.
I am very sorry
Click to expand...
Click to collapse
i know that situation is sucks i know and thank you for helping me to this step and i'm so much own you.
but last question i found a post for fastboot unbricked my type of phone but i dont undrestand small part of it and maybe it's help others
boot.img -The main kernel and initrd
recovery.img -A 'backup' kernel, initrd, and OS 4 sysm recovery/maintanance
sytem.img -The main OS
userdata.img -User data and settings
splash.img -Has Boot image. can be splash1 as well.
cache.img -Temp storage
...there can be similar partition names depends on your device type.... but basically these 6 partitions constitute a ROM. Copy all of (6) files to .android folder. (Henceforth, we can use this recovery.img as stock recovery for your device.)
"As your device is bricked/corrupted, we need to erase all old Partitions and flash (rewrite) new partitions that we have extracted from Update zip and placed in .android."
(1) Lets erase all partitions first (one by one)using: fastboot erase <partition>
Quote
C:\.android>fastboot erase system
Successful
C:\.android>fastboot erase recovery
Successful
C:\.android>fastboot erase boot
Successful
C:\.android>fastboot erase userdata
Successful
C:\.android>fastboot erase splash
Successful
C:\.android>fastboot erase cache
Successful
(2) Continuing with Flashing new partions using the Images copied in .android:
Command: fastboot flash <partition> <partition_name.img>
Quote
C:\.android>fastboot flash boot boot.img
Successful
C:\.android>fastboot flash recovery recovery.img
Successful
C:\.android>fastboot flash system system.img here people gen. get stuck
Successful
C:\.android>fastboot flash userdata userdata.img
Successful
C:\.android>fastboot flash splash splash.img
Successful
C:\.android>fastboot reboot
If all successful, Your phone will update and automatically reboot into the Factory State. Cheers !!!
...If you are Unable to flash 'system.img' successfully...
Reason: Your device is not allowing to format and rewrite 'system' partition manually. If your device is Rooted then probably such failure will never occur.
Let's overcome this Issue as well...Try Following...
First, Understand current State of Device...
We Wiped out old partitions and Flashed new partitions except :-\ system :-\ So No System on your Device at present.
What we will do now..
We will now wipe all partitions again
We will then flash only recovery.img saved in .android folder
We will use update.zip saved in .android folder to Flash it using SD Card.
We will copy update.zip on SD Card (using adb). If you can do it manually using a card reader skip step-II in below process.
Step-I: Wiping 'partitions' and Flashing 'recovery.img':Let's wipe all partitions again:
Quote
C:\.android>fastboot -w
C:\.android>fastboot reboot-bootloader
C:\.android>fastboot flash recovery recovery.img
C:\.android>reboot
Step-II: Copy update.zip on SDCARD
Quote
C:\.android>adb push update.zip /data/sdcard
(Let the process complete. It will take damm much more time !!!)
Once you get 'Successful' message..your update.zip is on your SDCARD. If this is tidious then get a Card reader and copy Update.zip to SD Card directly and replace in Device.
Step-III: As you can't manage to see what is happening on screen(No Display) hence Don't do mistakes here, read carefully and follow exactly:
1.Reboot Device into Recovery Mode:
On cmd type:
Quote
C:\.android>adb reboot recovery
2.Now Press 'Volume(-)' button ONCE. (Once means 'once only'-if you did mistake here repeat the Step-III)
3.Press 'Power' Button TWICEand Leave you Device for some 10 Minutes time.
If phone don't get alive in 10 Minutes Repeat Step-III again.
You may not able to see but Your phone will update and automatically reboot into the Factory State. Cheers !!!
Explaining Last Step:
We used simple logic in last procedure/ Its nothing but updating using Recovery Mode. Always remember Custom Recovery of Micromax A56/57 has following options: (May be diferent for other devics)
1. Reboot device
2. Apply Update.Zip from SDCARD
3. Wipe userdata on device/Factory Update
4. Wipe Cache on Device
As the default curser in recovery UI remains on Option-1 and we needed to choose Option-2.
Hence to select "Apply update for sdcard" we pressed 'Vol(-)' ONCE and then to Confirm and execute that option Tapped 'POWER' button TWICE.
Hope this Guide helped you or ...will Help you to help others !!!
Click to expand...
Click to collapse
i want to know where i found update.zip or recovery.img sytem.img userdata.img splash.img cache.img because in stock rom sp they are .sin
if i wipe my all partition maybe i have chance to restore my phone
thank you
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?