Hello. My xperia m2 says that there are no updates and the phone is up to date but it's with android 4.4.2. Theres 1 secound delay in the sound when I play games or use downloaded apps like youtube also the audio doesn't sound very good. To fix that I need to update the android version but I cant. I connected the phone to my computer and updated it with sony PC companion but the version is still 4.4.2. What should I do? I don't want to use flashtools or anything. I think it's the phone's fault for that and I should give it back to the place where I bought it so they can fix that. The phone is brand new and they already changed my camera because it wasn't working. So what should I do?
I suppose it has to do with the Country of your phone and/or if it is branded. IF after using PC Companion it's still with 4.4.2 I'm afraid your best (and only) option is to use Flashtool. Not sure how it works if it is branded though, you may need to to something to be able to de-brand it.
Well, actually try first to check if 4.4.4 is available in this way:
- Dial *#*#7378423#*#* (*#*#service#*#*)
- Check the number in Service Info/SW Info/Customization version. You just need the xxxx-yyyy part
- Downdload and install Flashtool (it's small. You just need it for checking)
- Run Flashtool
- Go to Devices/Check Updates
- Select your phone double clicking on the id xxxx-yyyy you have got before.
- If the version is 18.3.C (like the one for 3 UK) there is no 4.4.4. the latest ROM is 4.4.2. It must be 18.3.1.C for 4.4.4
My is branded from T-mobile, and i flashed CE ftf to debrande, everything is good except i don't have extra apps that T-mobile puts in. As i know your safe flashing ftf cos it's official Sony's software, just using Flashtool instead of PC Companion and you won't lose warranty, as long as you don't unlock bootloader.
Good Luck.
Xperia M2 D2303 on K.K. 4.4.4
Do I install the flashtool on my computer or on my phone?
foxymount said:
Do I install the flashtool on my computer or on my phone?
Click to expand...
Click to collapse
Obviously on the computer. It's needed to flash the phones from it. Just google it, you find it immediately. Then if you decide to flash a generic 4.4.4 FTF just search around. There are dozens of guides in the Internet.
Alright thanks for your support guys
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.
So it looks like XperiFix is pretty far behind in terms of device support, XZ2 is in experimental status since August with no sources for recovery, and it's likely that XZ3 will take a long time. We can unlock the boot loader but at huge risk to our camera functionality (green photos or nothing at all depending on how badly Sony has shafted us this time).
Prior to any further action or research a reliable way to backup the TA partition to enable a full BL relock in case of trouble seems prudent.
The XZ3 ships with the August patch level in .220. As of writing there is a system update available and I'm guessing it will update the ROM to the September patch level. Google Project Zero has published an exploit that is fixed with the September patch level: OATmeal on the Universal Cereal Bus: Exploiting Android phones over USB. The article is vague about the attack surface of Android Pie but it seems that on Oreo and earlier the patch can be executed on a locked phone, and that while there is some mitigation present in Pie, it should still be possible to execute the patch on an unlocked phone running Pie.
Of course this wouldn't give us root on a locked BL because of the boot signature verification (just a bricked phone if we attempt to modify boot.img), but it should be possible to at least dump the TA partition, allowing the bootloader to be safely unlocked and relocked with DRM keys intact.
Hopefully some developers and security researchers will show some interest in Sony's new flagship so ROM development can flourish here on XDA.
Hey @mufunyo
I created TWRP for the XZ2, XZ2C and XZ2P.
It took a long time, because the bootloader was locked until the September Firmware Update, which prevents modified bootimages to boot.
Because the Sony AOSP Project did need the time to integrate the TAMA Plattform with its new 4.9 Kernel.
The XZ2 Tamaline is the first Sony Device who as the 4.9 Kernel, instead of the 4.4 Kernel.
Of course this took time.
They are working hardly to migrate the older device to Kernel 4.9, too.
I am in contact with @sToRm// to get the DRMFix fully working. I use my own device for his testing purposes.
Everything is fine, except a little bug in the bootimage patcher routine, which is preventing the system to load the already finished DRMFix.
Btw. WIth the "manual" loaded DRMFIX (yes, hacky, to test it) we achieve to activate every feature which would need a locked bootloader (DRM).
SInce the XA2 and XZ2 we also still can shot pictures with the stock app, only the preview is black.
And the video playback will still work.
https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597
PS:
Since the XZ3 is part of the TAMALine, too, I could create a TWRP too.
Of course I would need a person which wants to test it with me and will unlock his bootloader.
And the bootloader need to be capable booting modified bootimages.
MartinX3 said:
Since the XZ3 is part of the TAMALine, too, I could create a TWRP too.
Of course I would need a person which wants to test it with me and will unlock his bootloader.
And the bootloader need to be capable booting modified bootimages.
Click to expand...
Click to collapse
Of course I would be willing to test with my own XZ3. However I would want to wait for the XZ2 DRM fix to be fully working before committing to it, if you can understand. I've had dust between the sensor and lens of my Z2 and Z5 (loose back cover and cracked screen respectively), so this is the first time in years I actually have a fully working phone camera, haha.
mufunyo said:
Of course I would be willing to test with my own XZ3. However I would want to wait for the XZ2 DRM fix to be fully working before committing to it, if you can understand. I've had dust between the sensor and lens of my Z2 and Z5 (loose back cover and cracked screen respectively), so this is the first time in years I actually have a fully working phone camera, haha.
Click to expand...
Click to collapse
Of course, follow the twrp xz2 thread
I will make a status update after storms DRMfix installation routine works
The fix itself is working, I tested it in the XZ2 XZ2C and XZ2P
You can write me a PM, after you wants to test
But we first make sure that there is no Sony bootloader upgrade needed to boot modified bootimages
The XZ2 and XZ2c is sharing now the same firmware as the XZ3 (all are Tama platform)
After I adapt twrp on pie and someone helps me, I could start tryjng to create twrp for the XZ3.
if u haven't already created twrp for xz3, im willing to help!!! want to root my xz3 badly...
MartinX3 said:
The XZ2 and XZ2c is sharing now the same firmware as the XZ3 (all are Tama platform)
After I adapt twrp on pie and someone helps me, I could start tryjng to create twrp for the XZ3.
Click to expand...
Click to collapse
clyde112 said:
if u haven't already created twrp for xz3, im willing to help!!! want to root my xz3 badly...
Click to expand...
Click to collapse
The single problem was the missing tester.
No one asked me :silly:
But let's wait for the next monthly patch or I would need to patch the twrp again. :silly:
Send me a message after you receives it
But be aware that I only have limited free time to work on it
ok sounds great, I understand/appreciate your limited free time.
looking forward to this, will pm u after monthly patch!
MartinX3 said:
The single problem was the missing tester.
No one asked me :silly:
But let's wait for the next monthly patch or I would need to patch the twrp again. :silly:
Send me a message after you receives it
But be aware that I only have limited free time to work on it
Click to expand...
Click to collapse
MartinX3 said:
The single problem was the missing tester.
No one asked me :silly:
Click to expand...
Click to collapse
I got in contact with @sToRm// already but he says he doesn't have a DRM fix for Pie yet, so I'm holding off for that.
How to enable oem unlocking in XZ3 H9493
MartinX3 said:
Hey @mufunyo
I created TWRP for the XZ2, XZ2C and XZ2P.
It took a long time, because the bootloader was locked until the September Firmware Update, which prevents modified bootimages to boot.
Because the Sony AOSP Project did need the time to integrate the TAMA Plattform with its new 4.9 Kernel.
The XZ2 Tamaline is the first Sony Device who as the 4.9 Kernel, instead of the 4.4 Kernel.
Of course this took time.
They are working hardly to migrate the older device to Kernel 4.9, too.
I am in contact with @sToRm// to get the DRMFix fully working. I use my own device for his testing purposes.
Everything is fine, except a little bug in the bootimage patcher routine, which is preventing the system to load the already finished DRMFix.
Btw. WIth the "manual" loaded DRMFIX (yes, hacky, to test it) we achieve to activate every feature which would need a locked bootloader (DRM).
SInce the XA2 and XZ2 we also still can shot pictures with the stock app, only the preview is black.
And the video playback will still work.
https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597
PS:
Since the XZ3 is part of the TAMALine, too, I could create a TWRP too.
Of course I would need a person which wants to test it with me and will unlock his bootloader.
And the bootloader need to be capable booting modified bootimages.
Click to expand...
Click to collapse
My H9493 (HONGKONG) couldn't enable oem unlocking in developer options. I have tried Pattern+VPN+Google account, no luck.
I think no official unlock is available currently for XZ3.
Since you cannot find the device name on the Sony dev page.
jamesys said:
My H9493 (HONGKONG) couldn't enable oem unlocking in developer options. I have tried Pattern+VPN+Google account, no luck.
Click to expand...
Click to collapse
It's a bug.
They will fix it.
Maybe with next monthly update.
Bootloader unlock bug got fixed und may be released with the December update.
https://github.com/sonyxperiadev/bug_tracker/issues/211#issuecomment-440851984
MartinX3 said:
Bootloader unlock bug got fixed und may be released with the December update.
https://github.com/sonyxperiadev/bug_tracker/issues/211#issuecomment-440851984
Click to expand...
Click to collapse
That mean, we become custom ROMs for this phone?
GreyFox777 said:
That mean, we become custom ROMs for this phone?
Click to expand...
Click to collapse
The XZ2c, XZ2 and XZ3 are very similar.
I wouldn't wonder, if someone would maintain these devices at once.
Maybe the XZ2P, too.
But at first we need to be patient.
We XZ2 owners for our first Custom Stock Room yesterday.
You may loose your camera after unlocking.
On the XZ2/compact/premium the december patch broke the camera for unlocked devices. It shoot green pictures.
Downgrading to the november patch fixed it.
But we only have a working camera on the XZ2 devices, because we used a drmfix on oreo before.
I don't know if the same problem will happen on the XZ3, but if you really need the camera, i would wait for one to test the unlocking first.
At the moment, there is no PIE DRMfix.
PS:
Of course, AOSP will have a working camera, but the camera is not fully implemented at the moment.
But it will.
Is it possible to enable RAW Support on rooted AOSP-Roms on Xperia Phones? Maybe GCam works then? This phone really needs it!
Last hope before selling this beautiful phone.
madphone said:
Is it possible to enable RAW Support on rooted AOSP-Roms on Xperia Phones? Maybe GCam works then? This phone really needs it!
Last hope before selling this beautiful phone.
Click to expand...
Click to collapse
No, because RAW is not disabled there. :silly:
The entire camera2api is available. But please look into the bugtracker of my aosp rom in the xz2 ROM thread to know at which time the camera got fully implemented.
MartinX3 said:
You may loose your camera after unlocking.
On the XZ2/compact/premium the december patch broke the camera for unlocked devices. It shoot green pictures.
Downgrading to the november patch fixed it.
But we only have a working camera on the XZ2 devices, because we used a drmfix on oreo before.
I don't know if the same problem will happen on the XZ3, but if you really need the camera, i would wait for one to test the unlocking first.
At the moment, there is no PIE DRMfix.
PS:
Of course, AOSP will have a working camera, but the camera is not fully implemented at the moment.
But it will.
Click to expand...
Click to collapse
Wait, so unlocking the bootloader only affects the camera on the stock ROM, while a custom one is a totally different story? Did I get that right?
TunerCP said:
Wait, so unlocking the bootloader only affects the camera on the stock ROM, while a custom one is a totally different story? Did I get that right?
Click to expand...
Click to collapse
Unlock the bootloader on latest PIE.
The preview and photos will be fine.
Except the low light anti noise feature.
The aosp has its own hardware drivers, independent from stock.
But there are many partitions in the phone from the stock used by aosp except the big ones you flash.
I am Japanese XperiaXZs user.
I want to use Android9 on my XperiaXZs.
But Japanese Xperia's can't unlock bootloader.
So I can't use Android9 rom of AOSP.
Please tell me if anyone knows the method.
if you can't unlock bootloader then it is impossible to install custom rom
so far no one is working on pie for the xzs
Thank you!
yogikura said:
I am Japanese XperiaXZs user.
I want to use Android9 on my XperiaXZs.
But Japanese Xperia's can't unlock bootloader.
So I can't use Android9 rom of AOSP.
Please tell me if anyone knows the method.
Click to expand...
Click to collapse
now there can be YES and NO
by flashtool if you try flashing xz1 rom on xzs, even if it doesn't warn you that firmware doesn't match with device! and some how u bypass that! and from flashtool devices folder! if you copy xz1 FCSSCRIPT file and DROP it under XZs folder by changing 41.7.fcs for xzs so that Flashtool reads this xz1 file as XZs so that it can PROPERLY FLASH TA Partitions like XPERIA COMPANION would have.....
but the problem is
xzs on older method of DRM KEYS! , and flashtool may not able to properly flash it....
more over! you can TRY the NEW FLASHER.zip on xda! its design to flash XZP xz1 xz2 etc etc , may be it will be able to flash! the EXTRACTED SIN FILES by command line! however again! it will do the FLASHING thinking its XZ1 device .... so ..
in a nut shell! even if you able to flash Android9 of XZ1 on XZs, the device may never wake up! Kernels versions are different!
and since boot is locked! you can't even do many things!!!
btw nothing is tooo good about Android9!
XZs is more productive on Oreo!
thank you!
I continue to use XperiaXZs of Android8.
If you want the gesture control (actually disabled in Sony's android 9 implementation), you can install Fluid N.G application.
Thank you!
I think I want to use it!