Hey XDA.
For long i have been trying to get a custom ROM for my android, but to be able to do that, i need to unlock bootloarders for my device.
I have been trying for a couple of months now, and everytime i try, i hope that it will work this time... but i always end up quitting, because i always encounter some problem, i cant seem to resovle.
I was wondering if anyone would like to help me through, step by step, until it actually works.
This is what i have tried
- I have entered the system configurator, and it says yes to that my device can be unlocked.
- I have enabled all the developer options descirbed everywhere
- I have downloaded the Android SDK, with the google USB drivers.
- I have gotten my unlock-code from Sony
But everytime i try to follow the steps from Sony, I get an error when coming to install the drivers.
The tutorial says, that when i plug the usb-cable to my computer, i would be prompted to install some drivers... I dont, it automaticly installs something called "S1Boot Fastboot".
Then i enter my device-manager, finds the device, and updates drivers manually from my computer.
But when i point to the downloaded drivers, i get this error:
Windows found a driver-software for your device, but encountered an error while trying to install it.
Windows ADB Interface
The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tampered with.
The files i have downloaded are all those Sony told me to download, from the official distributors... I got no idea how to solve this issue!!
Can anybody please help to fix this issue, or guide me through another way that works?
I have given up trying...
Download flashtool, and instal drivers from his directory (flashtool and fastboot) drivers.
Also instal PC Companion, but restart pc after instal (PC Companion also installs drivers)
Also, you might turn of driver signature checking if you are on windows 8.1, google it.
electrash said:
Download flashtool, and instal drivers from his directory (flashtool and fastboot) drivers.
Also instal PC Companion, but restart pc after instal (PC Companion also installs drivers)
Also, you might turn of driver signature checking if you are on windows 8.1, google it.
Click to expand...
Click to collapse
I agree with this. I just did it the other day.
I'm using a Win 8.1 laptop and it was driving me mad. I followed the information regarding changing some of my start up settings on the laptop and flashtool installation of drivers worked. Follow this. http://forum.xda-developers.com/showthread.php?t=1913245&page=6
In my case i had Flashtool installed, but when i went to install the drivers for my z1 , the windows installer would always fail. After using the information on that page I Linked, it worked straight away!
Good luck .
Thanks alot!
Thank you very much guys, that was just what i missed!
Glad you finally got it!
Sent from my C6903 using XDA Free mobile app
Related
Okay,
This is my friends phone and since i've done it i feel responsible,whatever.
The story goes,the xperia was on stock 4.2.2 i believe and we decided to flash 4.4 on it. So we downloaded the zip etc.
Now i've done the research and i think we shouldve first installed 4.3 then 4.4,i also think we shouldve flashed the kernel via flashtool first.
Anyway,now when i boot it vibrates and only shows the sony logo. I cant get into recovery.
We did manage to get into download mode with flashtool. But it disconnects (Do i need fastboot drivers,adb?)
Your input would be very appreciated!
Thanks in advance
You can hopefully use Flashtool to flash an appropriate stock FTF file to get the phone back to normal working order. There is a thread in here somewhere that links the latest version of Flashtool.
After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. Go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia V? or T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** Win8.1 will not allow these drivers to install. At all. Win8 will allow but you must disable Driver Signature Enforcement first. I dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again.
Wow thank you so much! I've tried all of the above but on windows 8.1 laptop. But I got ahold of a windows 7 one and it did the job perfectly. Thanks!
Sent from my GT-I9505 using xda app-developers app
Thanks
LaZiODROID said:
You can hopefully use Flashtool to flash an appropriate stock FTF file to get the phone back to normal working order. There is a thread in here somewhere that links the latest version of Flashtool.
After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. Go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia V? or T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** Win8.1 will not allow these drivers to install. At all. Win8 will allow but you must disable Driver Signature Enforcement first. I dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again.
Click to expand...
Click to collapse
Thanks, I also have same problem, Thanks again
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
melficeapollo said:
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
Click to expand...
Click to collapse
Here is a channel i subscribe and the guy goes in detail about wugfresh root tool kid, some of the videos are from december. hope it helps.
https://www.youtube.com/channel/UCWhQwvCaC2ZMkCnrC15NfAw
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
melficeapollo said:
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
Click to expand...
Click to collapse
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Evolution_Freak said:
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Click to expand...
Click to collapse
Tried that like it was going out of style lol. No luck.
i finally got it figured out!!
i used the toolkit and install;ed Universal Google Drivers (option #3) and my pc was finally able to detect my device in recovery mode.
so if anyone comes across the same problem of not having the "right" drivers or not having your device detected,
1.) Install Universal Google Drivers and reboot your computer
2.) proceed to sideload your update.
I can't get Flashtool to flash an ftf to my Z3 Compact. Every time I connect the phone in flashmode Flashtool reports "Processing of loader.sin finished with errors" and aborts the flash.
I've installed every driver that came with Flashtool, and my Sony ADB driver is up to date as far as I can tell. I have USB debugging turned on, and MTP mode turned off.
Does anyone have any ideas for what I might try to get this working?
(I'm doing this on Windows XP by the way - is this a blindingly obvious reason for Flashtool not to work? If so then maybe it really is time to upgrade…)
ejstubbs said:
I can't get Flashtool to flash an ftf to my Z3 Compact. Every time I connect the phone in flashmode Flashtool reports "Processing of loader.sin finished with errors" and aborts the flash.
I've installed every driver that came with Flashtool, and my Sony ADB driver is up to date as far as I can tell. I have USB debugging turned on, and MTP mode turned off.
Does anyone have any ideas for what I might try to get this working?
(I'm doing this on Windows XP by the way - is this a blindingly obvious reason for Flashtool not to work? If so then maybe it really is time to upgrade…)
Click to expand...
Click to collapse
Having the same issue here. I'm on a W 8.1 machine. All drivers installed successfully. then I'm getting exactly the same issue as you have
i've tried to re-install all the drivers and downloaded several times both the .ftf and the whole firmware thru XperiFirm..but nothing. I'm getting always the same error at the same stage....please some help! :crying:
I got my phone flashed in the end. I'm not 100% sure what finally got it working but one thing I know that I did do that I hadn't done before was to download the "Support Zone" addons in PC Companion (as per the advice here). I also re-installed (again) some of the Flashtool drivers: the generic ones, and the specific one for the Z3 Compact.
After I did that, Windows went through another of its "installing new hardware" things when I connected the phone in flashmode. The flash failed first time, but I left the phone connected and re-ran the flash from the point where you click on the lightning bolt button. That time, Flashtool found the phone already connected in flashmode, and successfully completed the flashing of the ftf.
I don't know whether it was the immediate re-try of the flash that got it to work, or the extra set of drivers from Sony PC Companion, or a combination of both - or just the wind coming from a different direction this morning! But at least I've now been able to get all the way through the instructions here, and I now have a rooted phone with dual recovery installed
So obviously XP wasn't the problem. Saying that, I see that you are using Windows 8. Are you aware of the complications involved in installing the Flashtool drivers in Windows 8? See here for detailed advice & guidance, specifically starting at PART 2: Driver installation in Windows 8.
ejstubbs said:
I got my phone flashed in the end. I'm not 100% sure what finally got it working but one thing I know that I did do that I hadn't done before was to download the "Support Zone" addons in PC Companion (as per the advice here). I also re-installed (again) some of the Flashtool drivers: the generic ones, and the specific one for the Z3 Compact.
After I did that, Windows went through another of its "installing new hardware" things when I connected the phone in flashmode. The flash failed first time, but I left the phone connected and re-ran the flash from the point where you click on the lightning bolt button. That time, Flashtool found the phone already connected in flashmode, and successfully completed the flashing of the ftf.
I don't know whether it was the immediate re-try of the flash that got it to work, or the extra set of drivers from Sony PC Companion, or a combination of both - or just the wind coming from a different direction this morning! But at least I've now been able to get all the way through the instructions here, and I now have a rooted phone with dual recovery installed
So obviously XP wasn't the problem. Saying that, I see that you are using Windows 8. Are you aware of the complications involved in installing the Flashtool drivers in Windows 8? See here for detailed advice & guidance, specifically starting at PART 2: Driver installation in Windows 8.
Click to expand...
Click to collapse
i just managed to flash the OS. the issue for me wasn't about the drivers or the wrong system FTF. it was about Java
I solved the issue installing the below
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
i went ahead by tentatives..i had no error about Java errors but seems it was related to Java..since without Flashtool was unable to flash..
Hope this will help someone else with the same issue
Just to be precise and complete. for those who are starting doing this i will suggest to
- Install PC Companion from Sony
- Install Flashtool drivers (if you have Windows 8.1 like me then you need to follow the below procedure
"1) Press the Windows key + R and in the run box type: shutdown.exe /r /o /f /t 00
– Now make the following selections to boot into the Start Up Setting Screen: Troubleshoot > Advanced options > Start Up Settings > Restart
– Then, when the machine restarts, select number 7 i.e. “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.
2) Now you can install the Flashtool drivers.
– Windows will warn that the driver is not signed and will require you to confirm the installation.
– Once the installation is complete, reboot the machine"
- Install Java as per above link. then you should be good to go
Not java I think
giuvilas said:
i just managed to flash the OS. the issue for me wasn't about the drivers or the wrong system FTF. it was about Java
I solved the issue installing the below
....
i went ahead by tentatives..i had no error about Java errors but seems it was related to Java..since without Flashtool was unable to flash..
Hope this will help someone else with the same issue
Just to be precise and complete. for those who are starting doing this i will suggest to
- Install PC Companion from Sony
- Install Flashtool drivers (if you have Windows 8.1 like me then you need to follow the below procedure
"1) Press the Windows key + R and in the run box type: shutdown.exe /r /o /f /t 00
– Now make the following selections to boot into the Start Up Setting Screen: Troubleshoot > Advanced options > Start Up Settings > Restart
– Then, when the machine restarts, select number 7 i.e. “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.
2) Now you can install the Flashtool drivers.
– Windows will warn that the driver is not signed and will require you to confirm the installation.
– Once the installation is complete, reboot the machine"
- Install Java as per above link. then you should be good to go
Click to expand...
Click to collapse
-----------------
So I had exactly the same issue and error, on Windows 7, and think I copied what you did here in allowing Windows to install a driver (pop up notification in bottom right of screen type) by taking my finger off 'volume down' and letting Windows do it's thing. Then when something called a 'SMEC driver' (I didn't catch the exact name). I didn't install Java and I didn't install any extra Sony stuff. This cleared the error and when I plugged the phone back in (without holding vol down) Flashtool found it and went ahead. It looked like it was stuck for a while, but did eventually get there. Only problem is my z3 compact then took ages to start up, and when it did all the rubbish Sony customisation was still there, all the bad apps etc, so not sure if it worked. Hope this helps someone in any case or to better diagnose the issue...
Flashtool is known to have a few errors with Windows 8.1 and 8 machines specifically with driver installation found in the drivers folder.
KB2917929 is needed for the driver installation to work and hopefully ensure a successful flash of a .ftf file.
Hey chaps,
I'm having a spot of trouble with Emma, I'm afraid.
I've followed the bootloader unlocking steps, the fastboot driver is where it ought to be.
My machine is displaying the phone when in flash mode as "SOMC Flash Device". Can't uninstall the drivers, can't update them with the fastboot driver as it's shown.
As a result, (assuming I haven't missed things or mixed it all up like a twat) Emma isn't identifying my phone. I'm connecting it in flash mode of course, I'm getting nothing.
Any ideas what could be the trouble?
what are you trying to do?
meaniez said:
what are you trying to do?
Click to expand...
Click to collapse
Flash a sony build
why are you using emma and not the Flashtool ?
Tried that too, connected in flash mode and keep getting errors.
At this point I'm thinking it's a driver issue, but for the life of me I can't fix it.
Really unsure where to go from here.
just some thoughts
1. try to download and install ADB driver if you haven't already.
2. try connecting the phone to a different usb port [sounds incredibly stupid, but it does work sometimes].
3. [assuming you're using windows] while the phone is connected, go to the device manager, look for phone [presumably under android device or sony] and uninstall the driver.
what kind of errors are you getting using the flashtool?
meaniez said:
just some thoughts
1. try to download and install ADB driver if you haven't already.
2. try connecting the phone to a different usb port [sounds incredibly stupid, but it does work sometimes].
3. [assuming you're using windows] while the phone is connected, go to the device manager, look for phone [presumably under android device or sony] and uninstall the driver.
what kind of errors are you getting using the flashtool?
Click to expand...
Click to collapse
3. Yeah I've done that. When it's connected in flash mode, it's detected as S1 Service (SOMC Flash Device). I'm fairly sure that's where the trouble lays, but everytime I try to uninstall the drivers to prepare installing the "correct" ones, the system hangs and I'm forced to hard reset.
Literally just says:
INFO - Checking header
INFO - Ending flash session
ERROR -
ERROR - Error flashing. Aborted
INFO - Device connected in flash mode
The drivers are there in the flashtool folder. Install the flashmode and fastboot mode drivers from there and then try connecting your phone into flashmode as a trial. If you see it connects, then proceed to flash the firmware
Sent from my D5833 using XDA Free mobile app
Could you please tell which sony build you are trying to flash?
I think you are flashing a wrong rom..
Alright I'm fairly convinced I'm just a dumbass. I haven't switched roms on a phone since my S3.
So far all I've done is unlock the bootloader, following the instructions from the sony dev video.
I've got a D5833, running 23.0.1.A.1.49 build. Doesn't seem to be any further updates OTA or through PC companion.
Flashtool and drivers are installed. ADB as well.
I haven't got CWM or anything running on it thus far, and I'm suspecting that that might be the problem.
Help a newbie, save the rainforest. <3
Hey guys,
long story short: I flashed my device and now my pc wont recognise the usb-connection between my phone and computer. The hardware-manager describes as if the phone cant tell the computer that it is a z3 compact.
Errormessage: Unknown USB-device (Cannot get the device description)
*something like that*
what I did to troubleshoot:
- reflash the device with firmeware: A.1.264 (without this strange script)
- reflash the device with the concept preview (without this strange script)
- installed PC Companion from Sony
- Linux cant see the phone, but can flash it
- USB-Debugging wont work as well
Nothing worked for me so far. Anyone an idea what to do?
thanks in advance
Nummer35 said:
Hey guys,
long story short: I flashed my device and now my pc wont recognise the usb-connection between my phone and computer. The hardware-manager describes as if the phone cant tell the computer that it is a z3 compact.
Errormessage: Unknown USB-device (Cannot get the device description)
*something like that*
what I did to troubleshoot:
- reflash the device with firmeware: A.1.264 (without this strange script)
- reflash the device with the concept preview (without this strange script)
- installed PC Companion from Sony
- Linux cant see the phone, but can flash it
- USB-Debugging wont work as well
Nothing worked for me so far. Anyone an idea what to do?
thanks in advance
Click to expand...
Click to collapse
I tried a fresh install of windows 10 and flashed the official 6.0.1 update fia .zip
NOTHING HELPED any ideas?
Nummer35 said:
NOTHING HELPED any ideas?
Click to expand...
Click to collapse
Some roms come with the usb functions disabled, removed as bloatware. So it's possible the first rom you tried didn't have the usb functions installed.
Do you have the correct drivers
Presumably flashtool can see your phone and it's still charging, so I'm sure the hardware is ok.
Did you try a repair with PC companion?
Do you have a different usb lead you can try?
Didgesteve said:
Some roms come with the usb functions disabled, removed as bloatware. So it's possible the first rom you tried didn't have the usb functions installed.
Do you have the correct drivers
Presumably flashtool can see your phone and it's still charging, so I'm sure the hardware is ok.
Did you try a repair with PC companion?
Do you have a different usb lead you can try?
Click to expand...
Click to collapse
Hey,
thanks for your answere. I found a "solution" to connect the phone via fastboot to the pc and with this I could do a complete reset with the PCC. When the phone is booted however I get the same error message over and over again: Cant get a device description!
Maybe you can look up the specific driver which is used in the device-manager so I can force windows to use this one?
Nummer35 said:
Hey,
thanks for your answere. I found a "solution" to connect the phone via fastboot to the pc and with this I could do a complete reset with the PCC. When the phone is booted however I get the same error message over and over again: Cant get a device description!
Maybe you can look up the specific driver which is used in the device-manager so I can force windows to use this one?
Click to expand...
Click to collapse
Did you install the ADB drivers that come with flashtool? Look in the install folder for a folder called 'drivers' run the exe in there and tik the fist two and then Z3c.
Yep, all three unsigned drivers.