Hi
I have Z3 D6603 was working fine
I downloaded 5.1.1 MEA and create FTF and flash with flash tool
now wifi and Bluetooth not open at all
i tried downgrade to 4.4.4 and 5.0.1 but still same
any solution for that
best regards
Same here. Locked bootloader, stock FTF that was updated to 5.1.1 via OTA. WiFi is wonky since then. I tried flashing different FTF's, including 5.1.1, 5.0.1 and 4.4.4, but WiFi is still quite wonky.
I also tried recovering using the PC Companion, thought it might have some extra magic compared to Flashtool - but no, WiFi is still extremely wonky: it is restarting itself every few seconds.
tracid said:
I also tried recovering using the PC Companion, thought it might have some extra magic compared to Flashtool - but no, WiFi is still extremely wonky: it is restarting itself every few seconds.
Click to expand...
Click to collapse
i have the same issue, have you sorted that or still not yet?
still have same problem
mak_us1977 said:
still have same problem
Click to expand...
Click to collapse
I downgraded to kitkat 4.4.4 and wifi still not working, same as bluetooth,
meanwhile I got reply from sony support, and it is a hardware not a software issue, so the only solution is to send to the sony service and they need to replace motherboard I belive
Related
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
Hi,
I'have tried to manual update my D6603 Xperia Z3 to the latest firmware 23.1.A.1.232 (from 23.1.A.1.200) which is StageFright free.
I downloaded the FTF from XperiaFirm and than I flashed it using flashtool, no errors displayed. The phone now is in bootloop, stuck in boot animation.
My phone was unlocked and not rooted
Please, help
Olivum09 said:
Hi,
I'have tried to manual update my D6603 Xperia Z3 to the latest firmware 23.1.A.1.232 (from 23.1.A.1.200) which is StageFright free.
I downloaded the FTF from XperiaFirm and than I flashed it using flashtool, no errors displayed. The phone now is in bootloop, stuck in boot animation.
My phone was unlocked and not rooted
Please, help
Click to expand...
Click to collapse
You didn't have to use flashtool. Use PC Companion. Sony's tool does the update for you.
Sent from my D6603 using Tapatalk
viewtifuljoe71 said:
You didn't have to use flashtool. Use PC Companion. Sony's tool does the update for you.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
Ok, I know, but my purpose was to change form Customized-ES to Custominzed-IT.
Once done that I would have downgraded my phone to Kitkat in order to root it.
Some minutes ago I managed to run 23.4.A.1.232 on my D6603 but I have some compatibility issues, preinstalled GAPPS don't run and the screen back illumination never turn off. I really don't know whats going on on that phone...
Now I'm using sony companion tool to repair the phone, if all goes right and I'm not going back to Customised-ES later I'll try to root it.
Basically all of this was a trial to understand if a was able to root it.
Olivum09 said:
Ok, I know, but my purpose was to change form Customized-ES to Custominzed-IT.
Once done that I would have downgraded my phone to Kitkat in order to root it.
Some minutes ago I managed to run 23.4.A.1.232 on my D6603 but I have some compatibility issues, preinstalled GAPPS don't run and the screen back illumination never turn off. I really don't know whats going on on that phone...
Now I'm using sony companion tool to repair the phone, if all goes right and I'm not going back to Customised-ES later I'll try to root it.
Basically all of this was a trial to understand if a was able to root it.
Click to expand...
Click to collapse
OK. I understand.
Sent from my D6603 using Tapatalk
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!
I unlocked my bootloader and relocked it with flashtool. Now I can only take photos on the camera app (same results with 3rd party apps). Any kind of video recording lags extremely or just gives me a blank screen and the fingerprint scanner doesn't respond. Like it's turned off. Any ideas how to fix this? I'm using the z5 premium e6853.
Thanks.
Mike3009 said:
I unlocked my bootloader and relocked it with flashtool. Now I can only take photos on the camera app (same results with 3rd party apps). Any kind of video recording lags extremely or just gives me a blank screen and the fingerprint scanner doesn't respond. Like it's turned off. Any ideas how to fix this? I'm using the z5 premium e6853.
Thanks.
Click to expand...
Click to collapse
How did you relock bootloader? with TA backup?
Try to use patched kernel.
Thanks for the reply. I actually just was about to report back that I fixed the issue. I flashed over the drm workaround with twrp.
I found it here:
https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
Happy to say everything is working perfectly now.
Will this work for 7 nougat on a z5?
I'm not sure. I flashed back to marshmallow to get it working. Then upgraded to the latest official firmware after.
i have even flashed back to marshmallow and still fingerprint is not working - has all the apk but doesnt look like its activating @Mike3009 are you able to give me the steps you used - i have tried numerous different processes
smiley.raver said:
i have even flashed back to marshmallow and still fingerprint is not working - has all the apk but doesnt look like its activating @Mike3009 are you able to give me the steps you used - i have tried numerous different processes
Click to expand...
Click to collapse
I'm pretty new to all of this so I'm not sure if this is the most efficient way to do it but here's what I did.
first I downloaded the official marshmallow firmware from xperiafirm and flashed it over with the latest version of flashtool. If you're bootloader isn't already unlocked, you should unlock it in flashtool. (needs to stay unlocked after too for this to work. I tried relocking it after and lost functionality) after you've flashed it over you need to get a modified kernel for your phone and firmware version. Flash that over and install the latest twrp. After that install the drm fix. Test if everything is working and if it is, download the latest official firmware from xperiafirm and flash over with flashtool.
Mike3009 said:
I'm pretty new to all of this so I'm not sure if this is the most efficient way to do it but here's what I did.
first I downloaded the official marshmallow firmware from xperiafirm and flashed it over with the latest version of flashtool. If you're bootloader isn't already unlocked, you should unlock it in flashtool. (needs to stay unlocked after too for this to work. I tried relocking it after and lost functionality) after you've flashed it over you need to get a modified kernel for your phone and firmware version. Flash that over and install the latest twrp. After that install the drm fix. Test if everything is working and if it is, download the latest official firmware from xperiafirm and flash over with flashtool.
Click to expand...
Click to collapse
Tried all that lol aw well I'm due for a new phone in a few months. I know mine isnt hardware related, but just something missing. Do you remember with MM firmware you got?
smiley.raver said:
Tried all that lol aw well I'm due for a new phone in a few months. I know mine isnt hardware related, but just something missing. Do you remember with MM firmware you got?
Click to expand...
Click to collapse
Try this drm fix. http://www.theandroidsoul.com/restore-drm-xperia-z5/
As for my marshmallow firmware, I'm in Taiwan so I used the only one listed on xperiafirm for Taiwan. Sorry I'm not able to use a Pc now to confirm.
are you on android 7.1.1?
Oops double post...sorry. Look below.
Yes. I didn't know to back up my drm keys before unlocking my bootloader and thought I was screwed. Now I'm on the latest 7.1.1, all drm functions working and I have root access. This drm fix works perfectly on the z5 premium e6853.(other models too but I can't personally verify)
Hey amazing people,
I have an urgent issue regarding my moto z xt1650-02, everything working fine until I upgrade to android 8.0 and after one week of upgrade problem started my wifi frequently disconnecting starting I have tried each and every help on the internet such as:
Cach clean
Factory reset
Wifi preference reset
All app preferences reset
Try to unlock the bootloader via Motorola official site but there I got the message that "Your device does not qualify for bootloader unlocking".
So time wifi start working and next day the same condition toggling between saved or connecting but no interne, I can see all wifi networks but can't connect?
I hope anyone here resolves this issue to root or at least wifi in working condition?
mirza5313 said:
Hey amazing people,
I have an urgent issue regarding my moto z xt1650-02, everything working fine until I upgrade to android 8.0 and after one week of upgrade problem started my wifi frequently disconnecting starting I have tried each and every help on the internet such as:
Cach clean
Factory reset
Wifi preference reset
All app preferences reset
Try to unlock the bootloader via Motorola official site but there I got the message that "Your device does not qualify for bootloader unlocking".
So time wifi start working and next day the same condition toggling between saved or connecting but no interne, I can see all wifi networks but can't connect?
I hope anyone here resolves this issue to root or at least wifi in working condition?
Click to expand...
Click to collapse
Tried looking here
https://forum.xda-developers.com/moto-z/help
I would reflash the firmware
Just don't downgrade, use same version or newer.
sd_shadow said:
Tried looking here
https://forum.xda-developers.com/moto-z/help
I would reflash the firmware
Just don't downgrade, use same version or newer.
Click to expand...
Click to collapse
I am not sure what are you suggesting me? could you please explain further as I am brand new for these kinds task
sd_shadow said:
Tried looking here
https://forum.xda-developers.com/moto-z/help
I would reflash the firmware
Just don't downgrade, use same version or newer.
Click to expand...
Click to collapse
I had tried to flash rom but no luck, bootloader is locked and I don't have one to unlock the bootloader?
mirza5313 said:
I had tried to flash rom but no luck, bootloader is locked and I don't have one to unlock the bootloader?
Click to expand...
Click to collapse
As long as you don't downgrade you should be able to flash firmware
sd_shadow said:
As long as you don't downgrade you should be able to flash firmware
Click to expand...
Click to collapse
Can you please guide me step by step how to "flash firmware"?