Hi
- I forced a full TWRP backup of my C6603 phone to another phone xperia z (C6616) -
To do that I renamed the repertory identity of the C6616 with the C6603 code name (renamed twrp\backups\CB5A1TRTGJ to twrp\backups\CB5A1SWVAJ) I do that to see the TWPR backup in the menu.
Result is catastrophic:
- No boot, no vibration, no vibration when hard reset too
- Cannot go into fastboot, adb not working, usb debugging was on in recovery but don't work
- When I connect to wall charger a continuous blinking red light, battery level is ok but I don't know if charging
- Never seen again yellow, blue or green light
- Tried flashtool, the phone is detected but not identified! Process jammed when tried to reading the phone, cannot read model and identity.
- In flashtool phone showed in flash mode, no need pressing low volume, no blue light!?
- Always flashmode detected but phone deconnect and reconnect after 2-3 min
Processing of loader.sin finished with errors
I tried PC companion. Detect the phone but cannot identify it, so process cannot continue.
Bootloader seem corrupt.. And it is locked
I have the original TA backup of the phone but how I can write it?
Here is a way to write bootloader with original TA ?
A way to force a "RAW" write of the bootloader with TA ? Skipping model detection ? Trim Area ? Jtag?
I read a lot of topics but I did not find any solution. Help please!
Carl
Y did u do dis
When I had problems with flashing through the flashtool on Linux, Windows was there to help. But my Z was in a good shape compared to yours.
Sorry, but I don't know how to help you.
Your 6603 twrp backup that you forced to restore on your 6616, may have contained a TA backup. If this is restored to a different device, then a permanent, unrecoverable hard-brick is enivitable.
Mobo replacement is the only option.
I sincerely hope this was not the case in your situation. Check your twrp backup files and see...
Exactly my case... But I have a TA backup!
shoey63 said:
Your 6603 twrp backup that you forced to restore on your 6616, may have contained a TA backup. If this is restored to a different device, then a permanent, unrecoverable hard-brick is enivitable.
Mobo replacement is the only option.
I sincerely hope this was not the case in your situation. Check your twrp backup files and see...
Click to expand...
Click to collapse
The TA partion was in the backup But I have a backup of the TA !
The only way I can communicate to the phone is with S1Tool and probes test. Error #0017 msg at the ends, MINOR ERROR [ 0x80080021_, err: 0017 ]
error while uploading final HDR block. Here is a way to convert the TA file and upload it with S1tool ?
Thanks¸
Carl
Solved hard brick c6xx ))))
SOLVED!!!
I used a tool to convert my TA partion backup to a S1tool compatible file !!!
Incredible !! Resurrection ))))
I used probe test point, run S1tool, emergency mode, flash generated file and WOW
Thanks all
Carl
shoey63 said:
Your 6603 twrp backup that you forced to restore on your 6616, may have contained a TA backup. If this is restored to a different device, then a permanent, unrecoverable hard-brick is enivitable.
Mobo replacement is the only option.
I sincerely hope this was not the case in your situation. Check your twrp backup files and see...
Click to expand...
Click to collapse
Congratulations:thumbup:
This is the first instance I have heard of whereby a user has restored their Ta partition to a bricked device
Maybe you should make a detailed tutorial about how you did it. I'm sure there are other users in a similar situation
can you help me out im in the same boat what probe test point s1tool etc
thanks
RE help
Do you have the original TA partition backup of the phone?
if yes, send me a picture of the back with the back cover removed
If not I cannot help you
Carl
Related
SOLVED I just had to restart the script.
Today I decided to unlock my boot loader after still experiencing lag and force closes in .201.
I wanted to backup my TA though, so after reading threads I chose DevShaft's Backup TA batch scripts, which got stuck on "INTEGRITY CHECK".
I quickly searched it up after half an hour of it stuck on this screen and found a post where it got stuck on "BACKING UP TA..." only to find that this could kill an Xperia device. I panicked, re read it and found that I was not experiencing the same problem. I checked the batch scripts for where it could get stuck at and if it could kill my phone.
I'm not sure whether it's fine, and my phone will not be bricked and I can try again or unlock the boot loader. I am on the .257 firmware.
Any ideas? The only thing I am worried about is that the command it is stuck at is running under su.
EDIT: My phone is an SIM-free, locked boot loader C5303, and am running the tool on Windows 8.1 64-bit. Reading the batch source, I have identified the place where it has got stuck on - the command to check the MD5 of the .img file on the phone. This doesn't seem to be harmful to my phone but it is plugged in the back of the PC and charging in case.
Did you try to backup after the unlock? Because a unlock of bootloader will wipe the TA partition, you need to back it up before bootloader unlock
Sent from my C5303 using xda app-developers app
Thanks for replying quickly
noahvt said:
Did you try to backup after the unlock? Because a unlock of bootloader will wipe the TA partition, you need to back it up before bootloader unlock
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
Thank you for replying quickly. No, I have not unlocked the boot loader yet. My phone is a C5303, and I am using my brother's gaming rig to do it, as I have a Mac and two computers running Linux.
Solved!
Just restarted it and it worked fine after exiting Sony PC companion.
hello, my xperia sp has been soft-bricked! im trying to get it back to normal, but i can't!
i downloaded the stock firmware for my phone c5306( .205 ) and im trying to flash it via flashtool.
a hundred times i have got the system.sin error! drivers updated, tried with different pcs, different cables! no result, same error!
i also tried excluding system.sin from the right column, all other files are flashed normally! but when i try system.sin, error!
also, my phone shows green light after sometime after i plug it into the charger! when i remove it and hold power button for 2sec, the red led flashes and goes off, if i hold it it keeps flashing!
also it will only show sony logo after flash mode has been exited!
please help me! i have spent 3 days on it(day and night) but still no solution!:crying:
i just got this phone 1 week ago!
i have also attached the image of the error!
please help devs! i will be very greatful!
the reason i think is that when the system.sin is almost done, the phone is exiting flashmode? this might be the reason?
if yes please give solution!
( i checked by disconnecting phone while the flashing was halfway through, same error!)
Firstly, try flashing some different FTF files, as this is most likely the problem.
If that doesn't work and you are already on unlocked bootloader, you can try the following:
1. Flash everything in the .ftf file using the latest Flastool, except system (system.sin).
2. Open the .ftf file using 7zip and extract the system.sin.
3. Flash the system.sin using fastboot: fastboot flash system system.sin.
The above method has worked for others with similar problems. Again, only for unlocked bootloader.
If that fails you might also have corrupted or broken NAND memory. Hardware issue is surely a probability.
Other might have other suggestions...
Gamm86 said:
If you are already on unlocked bootloader, you can try the following:
1. Flash everything in the .ftf file using the latest Flastool, except system (system.sin).
2. Open the .ftf file using 7zip and extract the system.sin.
3. Flash the system.sin using fastboot: fastboot flash system system.sin.
The above method has worked for others with similar problems. Again, only for unlocked bootloader.
If that fails you might also have corrupted or broken NAND memory. Hardware issue is surely a probability.
Other might have other suggestions...
Click to expand...
Click to collapse
somehow i flashed ftf! but now the phone reboots only after flash/fastboot mode, first it used to show only sony logo, but now it shows sony,xperia, xperia bootanimation, off!
if i flash system.sin through fastboot, where should i place the file?
moosa27 said:
if i flash system.sin through fastboot, where should i place the file?
Click to expand...
Click to collapse
In the folder where you extracted fastboot.
Fastboot is a program on it's own. I'm not talking about the fastboot mode in flashtool. (http://forum.xda-developers.com/showthread.php?t=2588979)
Again, ONLY FOR UNLOCKED BOOTLOADER.
If you haven't unlocked it, this methode won't work.
Try flashing a different FTF, as I mentioned after editing my post.
Gamm86 said:
In the folder where you extracted fastboot.
Fastboot is a program on it's own. I'm not talking about the fastboot mode in flashtool. (http://forum.xda-developers.com/showthread.php?t=2588979)
Again, ONLY FOR UNLOCKED BOOTLOADER.
If you haven't unlocked it, this methode won't work.
Try flashing a different FTF, as I mentioned after editing my post.
Click to expand...
Click to collapse
now whats happening is, when i press power button for 2 or more secs, the red led flashes! when i connect the phone to wall charger, red led stays on.
i took device into fastboot mode and rebooted into device via flashtool......
then the device booted normally and showed android id upgrading......... app 49 of 179 then off!
does this mean i should charge it? as far as i know, i have 70-80% battery.......
Leave phone in charging overnight and stay calm
Sent from my C5302 using XDA Free mobile app
moosa27 said:
then the device booted normally and showed android id upgrading......... app 49 of 179 then off!
does this mean i should charge it? as far as i know, i have 70-80% battery.......
Click to expand...
Click to collapse
Your battery is dead, but since android said it was upgrading apps, this means your problem is most likely fixed.
Let it charge for a few hours.
Gamm86 said:
You battery is dead, but since android said it was upgrading apps, this means your problem is most likely fixed.
Let it charge for a few hours.
Click to expand...
Click to collapse
Thanks.for all your efforts my phone was back normal yesterday
moosa27 said:
Thanks.for all your efforts my phone was back normal yesterday
Click to expand...
Click to collapse
Glad you got everything sorted.
Unless an Xperia SP has hardware problems, i'm quite sure it cannot get fully bricked.
I have exactly the same problem
Could you give me the steps to fix this problem? I have exactly the same problem when i try to install android with flashtool. No matter the version:
"24/017/2014 23:17:58 - ERROR - Processing of system.sin finished with errors.
24/017/2014 23:17:58 - INFO - Ending flash session
24/017/2014 23:17:58 - ERROR - 31 : A device attached to the system is not functioning.
24/017/2014 23:17:58 - ERROR - Error flashing. Aborted"
And when i try to power up a red led is blinking. If i connect the charger the red led stays on. Also, its hard to enter flashmode (green led) and fast boot (blue led) doesn't seem to work in Flashtool (in order to select system.sin to Flash). Despite the blue led is on, Flashtool doesn't let me to reboot into fastboot mode.
You got yourself a driver problem. Reinstall the drivers
i have the same problem. any solution for locked bootlader?sir please help i always get system.sin error when i flashed the stock rom.
ohmygel said:
i have the same problem. any solution for locked bootlader?sir please help i always get system.sin error when i flashed the stock rom.
Click to expand...
Click to collapse
you cant be hard bricked on locked bootloader . it hapenned to me. solutions:
1. get another ftf files, sometimes ftf can get damaged.
2. install custom drivers.
3. try different pcs (My Solution )
4. charge the phone 1 day (24hrs)
5. unlock bootloader and flash custom kernel and flash a rom, then u can flash stock and relock bl
6. change ur cable.
if no one of this solutions fix ur problem u are so bad
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
MAAAN!!! this worked!! I was spending many days and nights wondering WHY??? Thank you!!! :laugh::laugh:
I could flash 4.4.4 normally with the latest flashtool but no 5.x.x version would work!
If this is important enough maybe Androxyde will take a look into that...
Anyways , I am happy now^^
knauji said:
MAAAN!!! this worked!! I was spending many days and nights wondering WHY??? Thank you!!! :laugh::laugh:
I could flash 4.4.4 normally with the latest flashtool but no 5.x.x version would work!
If this is important enough maybe Androxyde will take a look into that...
Anyways , I am happy now^^
Click to expand...
Click to collapse
Lol its not a known problem and please do not notify Androxyde about it. Version post 0.19.8.6 but prior to 0.19.9.1 uses a template file called fsc to accommodate new xperia devices. This breaks support for older xperia devices that doesn't have the fsc template. The template can be created of course, but it seemed no one from the xperia sp community want to contribute lol.
So the versions that will make ftf flashable again is 0.19.8.6 and 0.19.9.1+. You could have solve this by yourself if you read the note given on the website properly.
TechnoSparks said:
Lol its not a known problem and please do not notify Androxyde about it. Version post 0.19.8.6 but prior to 0.19.9.1 uses a template file called fsc to accommodate new xperia devices. This breaks support for older xperia devices that doesn't have the fsc template. The template can be created of course, but it seemed no one from the xperia sp community want to contribute lol.
So the versions that will make ftf flashable again is 0.19.8.6 and 0.19.9.1+. You could have solve this by yourself if you read the note given on the website properly.
Click to expand...
Click to collapse
Well, I don't know what FSC is and the changelog on the website says the new version is compatible with all xperia devices....so that is what I used. How could I know..?
but it works now, that's all I need^^
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
Thanks button is broken but THANKS ! It was driving me crasy !!! :highfive:
BTW, the version is 0.9.18.6
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
I seach like crazy and ask Questions w/out an answer! THX a lot!!! It worked!!!
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
can you provide me the download link of flashtool 0.18.6
Hi guys,
I got a Z1 this morning (2nd hand). There was a problem with the camera not adjusting focus so I thought I'd update to a custom ROM and see how that went before I replaced the camera module.
Firstly I rooted my phone with no probs.
I then backed up the TA and unlocked the bootloader, again with no probs.
Now I ran into some problems I can't remember the tutorial I read but it said you needed a custom kernel for custom recovery.
So I booted into fastboot and flashed Z1_DooMLoRD_AdvStkKernel_FW-108_v05.
That flashed ok but now the phone wont boot (static red LED). I can still get into fastboot mode and flash kernels no problems.
I'm pretty sure I can get into flash mode, no LED shows up but it shows as device connected in Flashtool.
I try to flash firmwares (tried 4.4 latest and 4.3) however it fails with the error
21/040/2014 19:40:31 - ERROR - Processing of loader.sin finished with errors.
21/040/2014 19:40:31 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x800A0017 ";
Click to expand...
Click to collapse
I searched the problems and saw people saying to install every driver in flashtool which I've done which makes no difference.
Installed SEUS, the Sony companion tool. Nothing seems to help with the error.
I'm about to uninstall everything and reinstall to see if that helps but otherwise I'm stumped. Any insight would be appreciated
Edit: Just in case, it's a C6903. It was on 4.4.2 Official FW
I also checked if my bootloader was unlockable before unlocking (it was)
BTW I've tried all 6 of my USB ports and 8 different cables
Oh and I know when the brick happened, not sure what I should have done differently? (flashed recovery, ROM then kernel?)
FML!
Delete this if you want. Guy told me it was a Z1, after now 12hrs of thinking it was and trying to fix a Z1, it turns out it's a Z.
Flashed a Z kernel and have life again
I've try update my software with OTA and PC Companion before and it said error. Then I tried to flash 292 FTF using flashtool 0.9.18.4 and this error keep showing.
07/001/2015 03:01:51 - INFO - Phone boot version : S1_Boot_Lagan_1.0_2. Boot delivery version : S1_Boot_Lagan_1.1.1_1
07/001/2015 03:01:51 - INFO - Going to flash boot delivery
07/001/2015 03:01:51 - INFO - Processing emmc_appsboot_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin
07/001/2015 03:01:51 - INFO - Checking header
07/001/2015 03:01:51 - ERROR - Processing of emmc_appsboot_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin finished with errors.
07/001/2015 03:01:51 - INFO - Ending flash session
07/001/2015 03:01:51 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80080021 ";
Click to expand...
Click to collapse
I've checked *#*#7378423#*#* and bootloader unlocked is yes
Please solve this error for me
Thank you!
And I've spend 2 days searching, it's not much but I think I can't do anything to solve this problem.
hacphongthan said:
I've try update my software with OTA and PC Companion before and it said error. Then I tried to flash 292 FTF using flashtool 0.9.18.4 and this error keep showing.
I've checked *#*#7378423#*#* and bootloader unlocked is yes
Please solve this error for me
Thank you!
And I've spend 2 days searching, it's not much but I think I can't do anything to solve this problem.
Click to expand...
Click to collapse
Why you're using flashtool instead of fastboot if your bootloader is unlocked either way?
You can try to flash Lollipop 5.0.x ROM : PABX's ROM YUGA 5.0
The instructions are written in the page, but before that you need to download android SDK.
After you will be done that either, you will need to go /sdk/platform-tools/ (where fastboot.exe and adb.exe are installed), then with holding SHIFT button press Right Mous Button and push "Open command prompt here". And then just write the commands which are written in the page, again.
And don't forget to install adb and fastboot drivers.
LaurynasVP said:
Why you're using flashtool instead of fastboot if your bootloader is unlocked either way?
The instructions are written in the page, but before that you need to download android SDK.
After you will be done that either, you will need to go /sdk/platform-tools/ (where fastboot.exe and adb.exe are installed), then with holding SHIFT button press Right Mous Button and push "Open command prompt here". And then just write the commands which are written in the page, again.
And don't forget to install adb and fastboot drivers.
Click to expand...
Click to collapse
So my phone bootlocker has been unlocked right ?
Can I do anything to relock it?
I don't have old TA partition because I've bought an used phone and I just want to use stock ROM
hacphongthan said:
So my phone bootlocker has been unlocked right ?
Can I do anything to relock it?
I don't have old TA partition because I've bought an used phone and I just want to use stock ROM
Click to expand...
Click to collapse
If via *#*#7378423#*#* shows, that status is : "Bootloader unlockED: YES", then yes, your bootloader is unlocked and your DRM keys have been erased permanently, without any way of getting them back (if you don't have TA-Partition backup, of course). If status is : "Bootloader unlock ALLOWED: Yes", then your bootloader isn't unlocked and yours DRM keys is in their "place".
If your bootloader unlocked, then you could ask the person you have bought your phone from for TA-Partition backup, if he/she has it.
If not - don't ever think to flash anyone else's Ta-Partition, otherwise you'll brick your phone permanently.
You can relock it via Flashtool, If I'm right. But it doesn't change the situation you're in, 'cause your DRM keys are lost and you'll not be able to use BE2, Clear Audio+ and other fuctions, which requires the DRM keys to be working.
I'm sorry about that.
You can still flash stock .FTF, I suggest you to flash Generic.
If error persists, you could try other .ftf to fry for flashing.
LaurynasVP said:
If via *#*#7378423#*#* shows, that status is : "Bootloader unlockED: YES", then yes, your bootloader is unlocked and your DRM keys have been erased permanently, without any way of getting them back (if you don't have TA-Partition backup, of course). If status is : "Bootloader unlock ALLOWED: Yes", then your bootloader isn't unlocked and yours DRM keys is in their "place".
If your bootloader unlocked, then you could ask the person you have bought your phone from for TA-Partition backup, if he/she has it.
If not - don't ever think to flash anyone else's Ta-Partition, otherwise you'll brick your phone permanently.
You can relock it via Flashtool, If I'm right. But it doesn't change the situation you're in, 'cause your DRM keys are lost and you'll not be able to use BE2, Clear Audio+ and other fuctions, which requires the DRM keys to be working.
I'm sorry about that.
You can still flash stock .FTF, I suggest you to flash Generic.
If error persists, you could try other .ftf to fry for flashing.
Click to expand...
Click to collapse
It's show me Bootloader unlock allowed: Yes. I've flash C6603_10.5.1.A.0.292_Generic_NCB.ftf for my device but it show the above error.
Then I flash C6603_10.1.1.A.1.307_Generic BE.ftf it's all right nothing error.
Both of them are GENERIC but the 292 ftf error.
Could you please help suggest me which 292 ftf not error on my device.
And one more thing strange, I can't update my device with OTA even on 307 TFT. Someone say it only happen if my bootloader unlocked
I just tried C6603_10.5.1.A.0.292_Generic_UK.ftf too but it still error
The fact is I can't only flash which FTF include S1_Boot_Lagan_1.0_2 that mean I can't update my S1_Boot ?
hacphongthan said:
It's show me Bootloader unlock allowed: Yes. I've flash C6603_10.5.1.A.0.292_Generic_NCB.ftf for my device but it show the above error.
Then I flash C6603_10.1.1.A.1.307_Generic BE.ftf it's all right nothing error.
Both of them are GENERIC but the 292 ftf error.
Could you please help suggest me which 292 ftf not error on my device.
And one more thing strange, I can't update my device with OTA even on 307 TFT. Someone say it only happen if my bootloader unlocked
I just tried C6603_10.5.1.A.0.292_Generic_UK.ftf too but it still error
The fact is I can't only flash which FTF include S1_Boot_Lagan_1.0_2 that mean I can't update my S1_Boot ?
Click to expand...
Click to collapse
Well, you've not unlocked your bootloader. Your bootloader status is locked. However, do you have flashtool drivers? You could give a try on another pc, maybe your pc is causing issues, like mine (my os is Windows 10 and doesn't support fastboot and adb, as I can see).
LaurynasVP said:
Well, you've not unlocked your bootloader. Your bootloader status is locked. However, do you have flashtool drivers? You could give a try on another pc, maybe your pc is causing issues, like mine (my os is Windows 10 and doesn't support fastboot and adb, as I can see).
Click to expand...
Click to collapse
Yes I have flash tool driver on windows 7 Vmware but it error same my Windows 8 main PC :crying:.
Talk about OTA, why I can't update via OTA or PC companion
hacphongthan said:
Yes I have flash tool driver on windows 7 Vmware but it error same my Windows 8 main PC :crying:.
Talk about OTA, why I can't update via OTA or PC companion
Click to expand...
Click to collapse
I don't know anything else whast I could suggest you. U should better contact SONY:
Sony Support. Or if you have warranty - take it to there
LaurynasVP said:
I don't know anything else whast I could suggest you. U should better contact SONY:
Sony Support. Or if you have warranty - take it to there
Click to expand...
Click to collapse
oh ok thanks for your help
Hello!
I had my phone MB replaced during service and before that I got a full TWRP backup, including system and TA.
After I got it back (new MB) i rooted it and restored the full TWRP backup, without thinking too much..
Unfortunately the phone now is hard bricked, only the red light will blink when connected to PC but that's about it. No flashmode or fastboot.
The question is if I can do anything to salvage this phone.. I only have a full TWRP backup (system and TA taken before the MB swap), but I don't know if this can help. Can I try to use S1tool for this, or there is no chance?
any suggestion is welcome, thanks!
correction..
Actually, i did get a full twrp backup before restoring that old backup that crashed the phone. but it is on the phones internal memory, and i have no access anymore.
Assuming that i could get basic adb access to pull that backup out and get a ta.img out of it, or to somehow directly restore the full twrp backup - then it could work by using the s1tool method.
but i dont know if this basic access is possible.. any thoughts? i don't want to disassemble the back if it is hopeless in the first place..
If the phone can't be detected by ADB Access and all other attempts have failed most likely its a hard brick.
There's a great guide on how to recover from problems like such though I cannot guarantee it would work, but its better to try. Click Here
A last resort option would be to send it to Sony
thanks but it is a hard brick in any case, cause i restored a wrong ta (imei, etc). I was hoping to be able to wipe the ta by unlocking the bootloader, via s1tool, but i am not sure this can wipe the ta to the extent that i can reboot the phone or use adb with it. anyone knows?
if i could manage to use adb with it i could pull out the correct ta from the twrp backup in my internal memory and use that to revive the phone, as others have done.. but it seems like a long shot.
also if anyone has any info on where the test point is for this device..
thanks