Hi there, I am currently a user of an iPhone 6 and ordered a second hand Sony Xperia Z3 which arrived a week ago. I haven't had time to set it up as I have been away with work, so last night when I tried to root the handset (a requirement for me) I had great trouble. I have a lot of experience in rooting Android handsets having been with Android for a number of years before my short stint with iOS. I received the handset on 4.4.4 firmware and couldn't use the giefroot tool as my firmware wasn't compatible. I had a software update so updated to Lollipop and tried again, it still gave me the same message. I then tried to downgrade the firmware using Flashtool however after around 3 hours, the application could STILL not recognise my device through fastboot as I couldn't get the drivers to install.
I have three more days left in my return warranty and I was wondering if this is a common problem? I have read on the forum about compatibility settings I can change to get the drivers working, is this a viable solution?
Also - on a side note, the phone I received is in great condition(cosmetically). However; there seems to be a little bump where the frame separates from the screen just where the volume buttons are. Would this effect the waterproofness of the handset.
Thanks
Disable driver signature verification, than try to install the drivers again. Those are really needed to flash with flashtool.
Thank you for your reply. I've already done this and it still fails.
I get the error "DPInst.exe does not execute on your current operating system" when I try to disable driver check
EDIT: Setting compatibility mode of the exe in Flashtool/Drivers to Windows Vista solved the problem (I had this previously set to W7)
Try to install concept marshmallow software through concept installer. It installs all the drivers and programs needed. I use windows 10 and that solved my problem.
Related
I have an un-branded Samsung Omnia 7 (Deutsche Telekom I believe). I did the force update for mango and was able to update to 7403 just fine. However, at the last step 2 of 2 of updating to 7720 it gave me the error code 80180048. I do not have a walshed phone because I tried using the walshed fix and the program said my phone wasn't walshed. Any one having this issue or have fix for this? Thanks.
All Languages
I was having a problem with failled Mango update and I discovered I used the Walsh tool wrong. I only selected the language that was "checked" in my keyboard settings and not ALL languages that were available on my phone. Once I selected all languages, the update went flawlessly.
---------- Post added at 08:43 PM ---------- Previous post was at 08:25 PM ----------
Did you also install the Windows Phone Support Tool? It may be needed for the Walsh Tool.
I have samsung focus (from Rogers Canada) and am facing exactly the same problem, I have reset my phone a couple of times but still receiving the same error, am not sure what to do now, can someone suggest following steps? I don't have walshed phone and walsh tool gave me missing clsid exception.
frazrasheed said:
I have samsung focus (from Rogers Canada) and am facing exactly the same problem, I have reset my phone a couple of times but still receiving the same error, am not sure what to do now, can someone suggest following steps? I don't have walshed phone and walsh tool gave me missing clsid exception.
Click to expand...
Click to collapse
Samsung Focus has two hardware revisions.
You will not be able to get passed the last steps to update to Mango if you have rev. 1.4
rev 1.3(Micron): Windows 7.5 update will be available through Zune on 9/27.
rev 1.4(LSI) : Update has not entered the AT&T SPE lab yet; however, Samsung is targeting for 10/17 lab entry and 10/31 TA"
you can check which revision you have by pulling out the battery. there should be a revision number on on a white sticker on the device.
I have checked the focus revision number on my phone and it is 1.3, I found that one may use windows phone support tool to solve the issue, but it always gave me the 'the device not in connect to pc mode' error while I am pretty sure the device is infact that mode, so somehow it doesn't see that. I am still confused what to do now?
frazrasheed said:
I have checked the focus revision number on my phone and it is 1.3, I found that one may use windows phone support tool to solve the issue, but it always gave me the 'the device not in connect to pc mode' error while I am pretty sure the device is infact that mode, so somehow it doesn't see that. I am still confused what to do now?
Click to expand...
Click to collapse
sounds like a USB driver issue.
open Device Manager
open Zune
plug in the phone into the USB
In the device manager you should see Windows Phone USB Device at the very bottom come in.
Double click and double click Windows Phone USB. Got to Driver tab and make sure it reads Deiver Version 4.8.2345.0
if you have something older, uninstall the driver, unplug the phone, then plug it back in and hopefully it will pick up the new one.
I have exactly the same problem as Starsyde.
Forced update managed to get me through to 7403 and then on step 2 of 2 I get error 80180048. Tried at least 6 or 7 times and always get the same result.
My phone is also an Omnia 7 (bought it unlocked but has the Orange UK logo and apps preloaded).
It's not Walshed (I didn't even have an idea what that even meant until a couple hours ago but still tried that tool, just in case - it says "Good news, your phone isn't Walshed!") and the Windows Phone Support Tool says the phone's not in a "Connect to PC state", even though it is.
To sum up: nothing works.
Oh, almost forgot: I then saw the post about the USB drivers, it's version is 4.8.2148.0 but it says it's the last version so it won't update, and when I unsinstalled it, it automatically installed the same version.
mrrtt said:
I have exactly the same problem as Starsyde.
Forced update managed to get me through to 7403 and then on step 2 of 2 I get error 80180048. Tried at least 6 or 7 times and always get the same result.
My phone is also an Omnia 7 (bought it unlocked but has the Orange UK logo and apps preloaded).
It's not Walshed (I didn't even have an idea what that even meant until a couple hours ago but still tried that tool, just in case - it says "Good news, your phone isn't Walshed!") and the Windows Phone Support Tool says the phone's not in a "Connect to PC state", even though it is.
To sum up: nothing works.
Oh, almost forgot: I then saw the post about the USB drivers, it's version is 4.8.2148.0 but it says it's the last version so it won't update, and when I unsinstalled it, it automatically installed the same version.
Click to expand...
Click to collapse
odd, the latest drivers are 4.8.2345.0 and these were installed a week before Mango was released to prepare the phones for Mango. Not sure why it would give you an older USB driver....
I updated the USB driver but the problem stays the same, not sure what else could be done
derausgewanderte said:
sounds like a USB driver issue.
open Device Manager
open Zune
plug in the phone into the USB
In the device manager you should see Windows Phone USB Device at the very bottom come in.
Double click and double click Windows Phone USB. Got to Driver tab and make sure it reads Deiver Version 4.8.2345.0
if you have something older, uninstall the driver, unplug the phone, then plug it back in and hopefully it will pick up the new one.
Click to expand...
Click to collapse
I'm been have the same problem with a samsung focus v1.3, i've tried everthing i could find, but nothing worked. I hope someone has an answer to what causing this.
I've reflashed the phone with both the rogers and at&t roms(many times) but can only get to 7403.
Also i have tried 4 different computers, one was ever XP.
i am getting the same update error with my Branded HTC HD7
Same error Omnia 7.
Posted it at MS forums: http://answers.microsoft.com/en-us/...-omnia-7/779a50b6-2080-40da-b106-c8b365c25372
Edit: Fixed mine by reverting back to 7392 and fixing a couple of registry values for language packs. I wanted to remove the ones I didn't need. That created the conflict. Now I'm on Mango!
DesiChoza said:
Same error Omnia 7.
Posted it at MS forums:
Edit: Fixed mine by reverting back to 7392 and fixing a couple of registry values for language packs. I wanted to remove the ones I didn't need. That created the conflict. Now I'm on Mango!
Click to expand...
Click to collapse
how did u revert back to 7392 update and which registry settings did you tweaked? would u mind sharing it with us? i have done hard reset on my phone but the os version is still 7.0.7043 and since i reset, there is no backup in zune to revert
well i uninstalled and reinstalled ZUNE then flashed the 7004 Schubert rom
plugged in the HD7 went through the update procedure from 7004 to nodo it automatically updated to 7403 but it errored out on the final mango update
Try This?
fouros said:
well i uninstalled and reinstalled ZUNE then flashed the 7004 Schubert rom
plugged in the HD7 went through the update procedure from 7004 to nodo it automatically updated to 7403 but it errored out on the final mango update
Click to expand...
Click to collapse
Not to be insulting, but did you try the Walsh Tool and select ALL languages that are on your phone. Most people who have gotten to the end of the MANGO update and failed with this error code fixed this with the Walsh Tool. Please don't dismiss it out of hand, it has solved this error code issue with a lot of people.
JamesAllen said:
Not to be insulting, but did you try the Walsh Tool and select ALL languages that are on your phone. Most people who have gotten to the end of the MANGO update and failed with this error code fixed this with the Walsh Tool. Please don't dismiss it out of hand, it has solved this error code issue with a lot of people.
Click to expand...
Click to collapse
i am not insuted and yes i did use the Walsh tool with the program saying my HD7 was not in a walshed state
pretty confused at the moment on what next to try
DesiChoza said:
Same error Omnia 7.
Posted it at MS forums:
Edit: Fixed mine by reverting back to 7392 and fixing a couple of registry values for language packs. I wanted to remove the ones I didn't need. That created the conflict. Now I'm on Mango!
Click to expand...
Click to collapse
Could you please elaborate?
Just to add to this, my brother inlaws focus, which i flashed with the rogers rom(It was a gift), installed the mango update yesterday morning. His phone is identical to mine.
fouros said:
well i uninstalled and reinstalled ZUNE then flashed the 7004 Schubert rom
plugged in the HD7 went through the update procedure from 7004 to nodo it automatically updated to 7403 but it errored out on the final mango update
Click to expand...
Click to collapse
I am now on Mango
i had to use another telstra ROM for the HD7
http://forum.xda-developers.com/showthread.php?t=993186
installed this , forced update and now Mango tastes sweet
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 purchased a used m8 win phone att, the phone seems to have an insider preview of windows phone 10 which isn't a complete OS ( i think it's old preview version maybe an alpha release ) this version has no basic application, no setting no camera app no dialer !
it can receive calls yet you can't dial a number yourself
even if you click on all setting in the notification bar it's tells you that this app in not available search for it in the store and guess what! there is no windows store installed !
i have done a factory reset , it didn't help
i have tried to use Windows Device Recovery Tool to flash a new version or downgrade to stable win 8.1
but i can't get the driver of the device it's stated in the device manager as USB BLDR with no available drivers
tried to flash the RUU from Xda, but it needs the driver as well !
i have spent a lot of time trying to fix this issue with no luck
I have an HTC 8X (AT&T) still running Windows Phone 8.0 (8.0.10501.127) as it seems AT&T never pushed out 8.1/8.1.1 for it. How do I manually install 8.1 (or is it 8.1.1 ?) on this 8X?
I faced the same issue today
Bought 8X for collection and was unable to check OTA updates (looks that all servers all down). I recommend to try Windows Device Recovery Tool, it may suggest to install latest firmware.
Also, you can try to install firmware manually but it requires to have y-cable, device unbranding and creating goldcard. This is complicated process overall and may brick your device (since this device is not supported and ROM urls on old threads may be broken, I do not recommend you to do that)
Hi,
OTC will work when you look at this:
OTC Updater can't reach Microsoft Update Servers
I tried to flash a possible Update, but got this error - anybody knows what's going on here? OTC Updater download OtcUpdater 8.2.1.0 Waiting for next device. Please connect a device via USB. Press q to quit. Lumia 650(RM-1152_15637)...
forum.xda-developers.com
Best regards,
Joachim
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!