Database Info

[Q]

Hi everyone i have a z3v (used) the version of the firmware is 23.0.E.1.11 and i want to update the device to 23.0.E.1.44 plz help me with intructions; the phone keep saying that its updated but with sonybridge (mac) i get the message : there was an issue with the update engine description: UE error 1100.
thnks

mohkam84 said:
Hi everyone i have a z3v (used) the version of the firmware is 23.0.E.1.11 and i want to update the device to 23.0.E.1.44 plz help me with intructions; the phone keep saying that its updated but with sonybridge (mac) i get the message : there was an issue with the update engine description: UE error 1100.
thnks
Click to expand...
Click to collapse
You should just try the Update Phone option that's already in Settings?

GigaSPX said:
You should just try the Update Phone option that's already in Settings?
Click to expand...
Click to collapse
thnks a lot for u're time i will upload screen captures :good:

mohkam84 said:
thnks a lot for u're time i will upload screen captures :good:
Click to expand...
Click to collapse
Then your next solution is grabbing a program called Xperifirm. It's like Flashtool, but this one supports our phones. It will have the update you need from here:
http://forum.xda-developers.com/cro...perifirm-xperia-firmware-downloader-t2834142/

thnks a lot xperifirm is good app and it contains the firmware for the z3v; the problem is that flashtool doesn't have the z3v in devices list for updating or reinstall the firmware
i think i should wait for update (flashtool) and them i flash it with the 23.0.E.1.44
i just want to remove or fix the flashing Red Frame/Border in my device (the Strict Mode method does not solve it)
i found a way but rooted devices only and u knew; no root available for z3v

mohkam84 said:
thnks a lot xperifirm is good app and it contains the firmware for the z3v; the problem is that flashtool doesn't have the z3v in devices list for updating or reinstall the firmware
i think i should wait for update (flashtool) and them i flash it with the 23.0.E.1.44
i just want to remove or fix the flashing Red Frame/Border in my device (the Strict Mode method does not solve it)
i found a way but rooted devices only and u knew; no root available for z3v
Click to expand...
Click to collapse
Just install the Z3, flashtool and fastboot drivers. They will work for the Z3v
Then flash it

ok thnks; do u have tutorial describes how flashing it

Struggling with Flashing ROM after root, Please help!

Hey guys,
Hoping you guys can help me out with my Z3 (D6603)
I have Flashed D6603_23.0.1.A.5.77.img
Also, I have completed installation of TWRP recovery and I do have ROOT access through Super SU.
I Have tried flashing two completely different ROMS (Glide & Blisspop)
But, I keep getting the same error:
---------------------------------------------------------
Installing: /sdcard/BlissPop-v3.2-z3-OFFICIAL-20150427-0047.zip
Finding update package...
Opening Update package ...
Installing Update.
This package is for D6602, D6603, D6633, DD6643, D6653, D6616, Z3, Leo
This device is Sirius
E: Error in sdcard/Blisspop-v3.2-z3-OFFICIAL-20150427-0047.zip
(status 7 )
E Installation aborted
--------------------------------------------------
Windows recognises my device as a Xperia Z2. I understand that the flash won't apply as it thinks its going on the wrong device but I don't know how to flash it right!
Help!
Thanks all

how come windows & recovery detect ur device as sirius?
if u sure urs r Z3, edit build.prop.
i recommend u to use use build prop editor from google play by JRummy.
change device to leo & model to D6603
AOSP based rom needs unlocked bootloader. make sure u knows what u doing.

monx® said:
how come windows & recovery detect ur device as sirius?
if u sure urs r Z3, edit build.prop.
i recommend u to use use build prop editor from google play by JRummy.
change device to leo & model to D6603
AOSP based rom needs unlocked bootloader. make sure u knows what u doing.
Click to expand...
Click to collapse
Thank you, I have got windows to see It's a Z3 now, I opened Prop.editor and its confirmed the following
Ro.build.product = D6603
Rob.build.description=D6603-user 4.4.4 23.0.A.2.93 ovf_Rw:user/release-keys
( My rooting status is "Bootloader Unlocked = YES")

Can't flash new firmware with flashtool

Hi,
I bought my Z5 online and I am living in Germany, my Z5 has a spanish firmware. I would like to flash it to the customized_DE firmware, but flashtool always stops at the same location (Max packet size set to 4096K). I read somewhere else that it works when you're using an older version of flashtool, but there it stops at flasing loader.
Does anyone have the same error and found a solution?
Many thanks to all!

Use the latest flashtool available
download ftf file through xperifirm
if you are using windows 8.1, disable usb verification enforcement
change compatibility on flashtool from windows 8 to windows 7
for more, use google, and you are doing this on your own risk

Had the same problem because I was using an old version of flashtool. Ended up finding the righ place to download it on flashtool.net.
Which version are you using?

Phone stuck in bootloop after update to nougat

Hey everyone,
Yesterday I installed the new 32.3.A.0.376 update on my 100% Stock Z5 (E6653) via the xperia companion.
After the update it was stuck in a bootloop (crashes and restarts shortly after the android animation finishes)
Here is the full timeline:
Update via xperia companion -> bootlop
Remove SD Card and SIM -> bootlop
Repair via xperia companion -> bootloop
Second repair via xperia companion -> bootloop
Flash Nougat with the flashtool -> bootloop
Flash latest non-nougat firmware -> it boots!
This time I did the update to nougat via OTA -> bootloop
Flash different nougat firmare via flashtool -> bootloop
Back to marshmallow...
Factory reset & Install update via xperia companion on a different computer -> bootloop
Install marshmallow, factory reset & Install ota update -> bootloop
So basically i tried every possible combination of installing the update without unlocking the bootloader or other things that might void warranty. It just won't boot!
What do you guys think might be the cause for this? And what can i try to get nougat working on my device before sending it in for a repair? Thanks!

how about cables? have you tried using different usb cables? how about non sony cables? or any other authentic original cable! like samsung usb2 ?

Cables? Sounds more like voodoo too me I mean I did the whole thing without any cables attached, too (OTA).

nbzklr said:
Cables? Sounds more like voodoo too me I mean I did the whole thing without any cables attached, too (OTA).
Click to expand...
Click to collapse
sir
when you tried all these possible combinations of flashtool, MM, N, repairs via sony pc suite etc even on different computer,
my question is did you add trying different usb cable in all this process?
and when you say you have tried different version N, can you be specific what build you tried?

YasuHamed said:
sir
when you tried all these possible combinations of flashtool, MM, N, repairs via sony pc suite etc even on different computer,
my question is did you add trying different usb cable in all this process?
and when you say you have tried different version N, can you be specific what build you tried?
Click to expand...
Click to collapse
I flashed 32.3.A.0.376-R4D and 32.3.A.0.376-R5D (one is with provider customization, one without).
And I just tried it with a different cable on a different usb port. But I'm afraid it's still the same result.

nbzklr said:
I flashed 32.3.A.0.376-R4D and 32.3.A.0.376-R5D (one is with provider customization, one without).
And I just tried it with a different cable on a different usb port. But I'm afraid it's still the same result.
Click to expand...
Click to collapse
sir if possible
1. kindly paste Flashtool log here ( of both machines )
2. what is the operating system of those two different pc's ? win 7 and/or win10
3. have you ever successfully flashed your xperia using those ssytems before? (considering driver issues)
4. flashtool 0.9.23.2 supports N (ONLY) any other version can't install it , so can u check what version of flashtool you used ( in both machines?)
thank you

YasuHamed said:
sir if possible
1. kindly paste Flashtool log here ( of both machines )
2. what is the operating system of those two different pc's ? win 7 and/or win10
3. have you ever successfully flashed your xperia using those ssytems before? (considering driver issues)
4. flashtool 0.9.23.2 supports N (ONLY) any other version can't install it , so can u check what version of flashtool you used ( in both machines?)
thank you
Click to expand...
Click to collapse
To answer your questions:
1. I currently don't have one but I do not recall any errors appearing in the logs.
2. I'm using windows 10 and yes, drivers were installed correctly (by booting the system with signature checks disabled)
3. I did successfully flash marshmallow (32.2.A.5.11) multiple times after the failed nougat update.
4. My version of flashtools matches 0.9.23.2
I tried to update the the phone multiple time using official tools (OTA, xperia companion) before resorting to flashtool.
This, and the fact that flashtool works well otherwise, means the issue is with my device and/or the update itself and not with flashtool.
Is it possible to get some log files out of the device to see what's causing the crash?

nbzklr said:
To answer your questions:
1. I currently don't have one but I do not recall any errors appearing in the logs.
2. I'm using windows 10 and yes, drivers were installed correctly (by booting the system with signature checks disabled)
3. I did successfully flash marshmallow (32.2.A.5.11) multiple times after the failed nougat update.
4. My version of flashtools matches 0.9.23.2
I tried to update the the phone multiple time using official tools (OTA, xperia companion) before resorting to flashtool.
This, and the fact that flashtool works well otherwise, means the issue is with my device and/or the update itself and not with flashtool.
Is it possible to get some log files out of the device to see what's causing the crash?
Click to expand...
Click to collapse
after asking so many questions and reading all your answers ! i feel like saying i wish i could get hold of your device to see what actually got wrong in OTA flashing!
the reason why ask all these question is that it happend with my friends Z1 years ago when by simply updating to news OTA , device got stuck in bootloop! and the only thing he could do is unlock the bootloader and installed cynogenmod. at that time i could not find any possible reason why this has happend!
the ultimate solution for you could be unlocking boot loader OR wait until we get some sense on the internet about this issue! ( i will research more)
btw, I always flash my device on win7 64bit. if possilbe try flashing via win7 , just in case.
also i couldn't help thinking , it might have something to do with FSC script! even on the flashtool download page! they have mention how few devices get bricked if flashtool is used! but then you tried updating via xperia companion also!
http://www.flashtool.net/downloads.php

YasuHamed said:
The ultimate solution for you could be unlocking boot loader OR wait until we get some sense on the internet about this issue! ( i will research more)
Click to expand...
Click to collapse
Yeah, I already feared that this would be the only solution :crying:
Next week I'm gonna try to get a refund/replacement, so let's see how that goes first before I unlock the bootloader.
Thanks for your help though!

nbzklr said:
Yeah, I already feared that this would be the only solution :crying:
Next week I'm gonna try to get a refund/replacement, so let's see how that goes first before I unlock the bootloader.
Thanks for your help though!
Click to expand...
Click to collapse
to be honest there is nothing wrong with your device! you had rooted 5.11 easily! this means the stock android .372 or .376 having N kernel is not working properly with your hardware!
if you are replacing your device then no need to unlock your bootloader! unless u want rooted phone!
REMEMBER to research all about DRM KEYS and TA backups before you even think about unlocking in your dream.

nbzklr said:
Yeah, I already feared that this would be the only solution :crying:
Next week I'm gonna try to get a refund/replacement, so let's see how that goes first before I unlock the bootloader.
Thanks for your help though!
Click to expand...
Click to collapse
When you were making .ftf ,did you delete fwinfo and exclude .ta files ?
If not, that can lead to bootloop.

Hey guys, I just want to give you a quick update on the issue:
Last week I brought my phone to a local retailer, they sent it in and today I received a completely new device with Android 7.0 pre-installed!
So it seems like the issue was covered by warranty.
All in all I'm surprised how smooth everything went.
And thanks to everyone who tried to help me here!

Help me please! Sony Xperia XZ SO-01j

Hello XDA Dev community!
I'm new and I have heard good reviews about this site. I hope you could help me with my problem. I managed to buy an Xperia XZ So-01J model locked to NTT Docomo then got it unlocked thru a code. I need to flash it to a generic stock rom but I keep getting the partition.sin error and soft bricking my device in the process. If I tick partition.sin in the "exclude" category, a new error comes up again from the .sin files. Am I missing something here? I'm new to the whole Xperia game but I got a little knowledge about it epecially with Flashtool. I used to be a Samsung user and have never encountered something like this flashing roms using odin and a custom recovery.
model: Sony Xperia XZ SO-01J
39.0.B.0.361
NTT DoCoMo
Answers are highly appreciated! Thank you

almeister41 said:
Hello XDA Dev community!
I'm new and I have heard good reviews about this site. I hope you could help me with my problem. I managed to buy an Xperia XZ So-01J model locked to NTT Docomo then got it unlocked thru a code. I need to flash it to a generic stock rom but I keep getting the partition.sin error and soft bricking my device in the process. If I tick partition.sin in the "exclude" category, a new error comes up again from the .sin files. Am I missing something here? I'm new to the whole Xperia game but I got a little knowledge about it epecially with Flashtool. I used to be a Samsung user and have never encountered something like this flashing roms using odin and a custom recovery.
model: Sony Xperia XZ SO-01J
39.0.B.0.361
NTT DoCoMo
Answers are highly appreciated! Thank you
Click to expand...
Click to collapse
Dear are you using latest xperia flashtool which use fsc script. I think you are using old flashtool. Also check drivers are cirrectly installed. Signature verification should be off in window.

faizanfaizan said:
Dear are you using latest xperia flashtool which use fsc script. I think you are using old flashtool. Also check drivers are cirrectly installed. Signature verification should be off in window.
Click to expand...
Click to collapse
Thank you for the quick reply! I'm using Flashtool 0.9.23.1 .. I will try to re-install the drivers see if that works. Thank you again

almeister41 said:
Thank you for the quick reply! I'm using Flashtool 0.9.23.1 .. I will try to re-install the drivers see if that works. Thank you again
Click to expand...
Click to collapse
Welcome dear.
Use 0.9.23.2 if possible. Put off the signature verification in window. Turn off antivirus. Dont plug any other device in usb port.
Installed drivers from driver folder of flashtool.

faizanfaizan said:
Welcome dear.
Use 0.9.23.2 if possible. Put off the signature verification in window. Turn off antivirus. Dont plug any other device in usb port.
Installed drivers from driver folder of flashtool.
Click to expand...
Click to collapse
Tried everything you stated and sadly it doesnt work as well. Maybe there isn't a way to flash SO-01J to a generic rom. :crying:

almeister41 said:
Tried everything you stated and sadly it doesnt work as well. Maybe there isn't a way to flash SO-01J to a generic rom. :crying:
Click to expand...
Click to collapse
Yes it's looking that. I also search for your probpem nut nothing is found. Can your model fall in f8331 aur f8332 category. Otherwise contact with androplus, a great developer in xperia software.

faizanfaizan said:
Yes it's looking that. I also search for your probpem nut nothing is found. Can your model fall in f8331 aur f8332 category. Otherwise contact with androplus, a great developer in xperia software.
Click to expand...
Click to collapse
It's a single sim phone. so It falls under F8331. Thank you @faizanfaizan for all your help!

almeister41 said:
It's a single sim phone. so It falls under F8331. Thank you @faizanfaizan for all your help!
Click to expand...
Click to collapse
If it's f8331 then just install boot image from androplus through fastboot and then install recovery through fastboot and install custom rom.

Responses are still very much appreciated. I still have hope the SO-01J can be flashed with a generic ROM.

almeister41 said:
Hello XDA Dev community!
I'm new and I have heard good reviews about this site. I hope you could help me with my problem. I managed to buy an Xperia XZ So-01J model locked to NTT Docomo then got it unlocked thru a code. I need to flash it to a generic stock rom but I keep getting the partition.sin error and soft bricking my device in the process. If I tick partition.sin in the "exclude" category, a new error comes up again from the .sin files. Am I missing something here? I'm new to the whole Xperia game but I got a little knowledge about it epecially with Flashtool. I used to be a Samsung user and have never encountered something like this flashing roms using odin and a custom recovery.
model: Sony Xperia XZ SO-01J
39.0.B.0.361
NTT DoCoMo
Answers are highly appreciated! Thank you
Click to expand...
Click to collapse
Hello i were having the same problem xperia xz dual(F8332)
use original cable to connect pc and direct attach to motherboard (from back panel) and try to re install the drivers.

good day
did you manage to fix this?? same prob.. so-01j user here

was anyone able to flash generic firmware ?
so-01j did anyone figure out how to flash f8331 firmware it always fails im tired of the docomo software and I want to stay stock I know theres a way to get generic firmware on this some insight would be great
francisac3 said:
good day
did you manage to fix this?? same prob.. so-01j user here
Click to expand...
Click to collapse

almeister41 said:
Hello XDA Dev community!
I'm new and I have heard good reviews about this site. I hope you could help me with my problem. I managed to buy an Xperia XZ So-01J model locked to NTT Docomo then got it unlocked thru a code. I need to flash it to a generic stock rom but I keep getting the partition.sin error and soft bricking my device in the process. If I tick partition.sin in the "exclude" category, a new error comes up again from the .sin files. Am I missing something here? I'm new to the whole Xperia game but I got a little knowledge about it epecially with Flashtool. I used to be a Samsung user and have never encountered something like this flashing roms using odin and a custom recovery.
model: Sony Xperia XZ SO-01J
39.0.B.0.361
NTT DoCoMo
Answers are highly appreciated! Thank you
Click to expand...
Click to collapse
Hi!
I am also experiencing the same situation. Who can help me?

Who can help me?

:crying: I m haven the same condition with you. Who can help me? Asking for help.i used all the flashtool,but it still dont ok.

I have the same condition with you.I do it yesterday.you should use 0.9.23.2.Flashtool flash so 01j .ftf. Yesterday i went to japanese NTT'S Home net to download it.

Did you flash the international ROM? Or still use Docomo 6.0.1?

same problem here , i try to flash 41.3.A.2.24 AU on my Sony Xperia XZ SO-01J but it always appear error at all sin files start from partition.sin
anyone have solve this problem?

AFAIK you cannot flash that file to that device.

you can't flash other rom into this phone, it only accept docomo rom. the bootloader is locked and it's not unlockable (as far as I know unless docomo allows it or someone managed to find a way). so I did the next best thing, by removing some of the docomo apps through adb. I also removed some Sony apps like Xperia Tips and Whats New and a few others (facebook etc). battery life has been better since less things running in the background now, free RAM is around 1gb though I don't play games at all.