Unlock Bootloader - Error android_winusb.inf - Xperia Z3 Compact Q&A, Help & Troubleshooting

Processing step by step the official Unlock your boot loader fpr sony xperia z3 compact D5803_ 23.5.A.0.570 developer.sonymobile.com/unlockbootloader
1. Installation of SDK, Studio, Eclipse. Downloaded the Google USB Driver Package und replaced the original android_winusb.inf by the sony fastboot driver android_winusb.inf like required in C:\Users\AppData\Local\Android\sdk\extras\google\usb_driver
2. Connected z3c offline to pc and press up button
3. Device manager starts and shows S1 Fastboot
4. Update driver by path C:\Users\AppData\Local\Android\sdk\extras\google\usb_driver
5. Installation of the official fastboot driver fails because missing hash value in the driver android_winusb.inf .
Do you have same experience or advice ?

This procedure looks a bit strange and unneeded..
To keep it bit more simple just use "Flashtool" http://www.flashtool.net/downloads.php
And use its integrated driver installation feature to install Fastboot and Flashmode Drivers AND your Device Drivers (Note that you need to pick Z3C for sure)..
http://www.android-hilfe.de/attachm...a-driver-pack-v1-8-20141101-setup-png.419663/
http://www.android-hilfe.de/attachm...a-driver-pack-v1-8-20141101-setup-png.419664/
But before you start... Save your TA Partition!!!!

fluffi444 said:
But before you start... Save your TA Partition!!!!
Click to expand...
Click to collapse
+1
The threads are full of people saying they don't have the DRM keys to make their camera and extra functions work again.
Follow the guide here

Related

ADB Driver installation issues Windows 7

Hello,
I wanted to root my new Sony Xperia T and I found this http://forum.xda-developers.com/showthread.php?t=1886460.
However I needed to install the ADB drivers and I am having extreme difficulties in doing so. From my limited knowledge on the subject I guessed that the ADB drivers are installed when I plug my phone into my computer. When I plugged my phone in windows installed two drivers. When I then went into device manager to see if my phone was registered as an android device but it wasn't. It was instead listed as a portable device. I also tried running
Code:
adb devices
but this ended up with an empty list. Despite this my phone appears in My Computer and I can transfer files to and from it easily.
After looking on the internet for a while I found I needed a few things installed. So I removed the drivers, installed the Android SDK with SDK-tools and the Sony PC companion as well as turn my phone to USB debugging. I then retried windows installed the same two drivers and it again was listed as a portable device.
I looked up this issue and found suggestions to restart the SDK-tools ADB server, restart my phone, update drivers, unlock my phone and install PDaNet. These all ended with the same result. I also found a suggestion to update the drivers by going into the Android SDK and using the driver in there. This didn't work though as Windows said the current version of the driver is the most up to date. I tried various techniques suggested to get around this but I was unable to.
Any help on how to install these drivers is greatly appreciated. My phone is about a month old, unrooted, Sony Xperia T (LT30p). My computer runs Windows 7 Professional 64bit.
Thanks,
JamesStewy
(I may have forgotten some of the things I tried to get it to work yesterday so please suggest anything )
Download flashtool and install the drivers from the driver folder in there. They are the only drivers I ever install.
Use the Tx, flashmode and fastboot drivers
Sent from my star trek communicator
Sony Flagship device circa 2145
It was kind of nightmarish to get the phone recognized for me as well. I managed to solve it (after may trials and errors) by manually "updating" the phone drivers once it was connected with the ones in the pccompanion folder; specifically the ones called sa0105...
Hello gregbradley and Arcano. Thanks a lot for your replies.
manually "updating" the phone drivers once it was connected with the ones in the pccompanion folder; specifically the ones called sa0105
Click to expand...
Click to collapse
I found the drivers in the PC Companion folder except I was unable to install them either by right clicking on the inf and clicking install or by going into device manager right clicking on my phone -> Update Driver Software... -> Browse my computer for driver software -> Enter in PC Companion drivers folder -> Next -> Windows Message (attached file). Is there another way of installing the driver? I also previously tried getting windows to not install the drivers when I plugged my phone in but nothing I could find on the internet worked.
Download flashtool and install the drivers from the driver folder in there.
Click to expand...
Click to collapse
Sorry for being a bit of a n00b but what is a flashtool and where do I get it? Also, same as previous, I can't find anyway of overriding drivers (I have gone through about three pages of google but can't find a solution that works for me).
Thanks again for your replies,
JamesStewy
JamesStewy said:
Sorry for being a bit of a n00b but what is a flashtool and where do I get it?
Thanks again for your replies,
JamesStewy
Click to expand...
Click to collapse
Flashtool is THE tool for use with xperia devices. Look in the first thread of the development section.
It should be the first thing you download when you get an xperia device.
EDIT
No need to post your thanks. If you feel the need to express gratitude to anyone on xda just their thanks button
JamesStewy said:
I found the drivers in the PC Companion folder except I was unable to install them either by right clicking on the inf and clicking install or by going into device manager right clicking on my phone -> Update Driver Software... -> Browse my computer for driver software -> Enter in PC Companion drivers folder -> Next -> Windows Message (attached file). Is there another way of installing the driver? I also previously tried getting windows to not install the drivers when I plugged my phone in but nothing I could find on the internet worked.
Click to expand...
Click to collapse
The way I did it was to plug the phone in, wait till the automatic driver installation failed, and then in the device manager I selected the phone and went thru the "update drivers" procedure. You must select the specific folder where that driver is, not the parent, or windows won't detect it. In my case that folder is named
C:\Program Files (x86)\Sony\Sony PC Companion\Drivers\{2CD1390C-A74E-434A-B652-73D3683B3BEF}
which is quite a weird name; just look for the folder with sa0105* drivers inside, and that's the one.
By the way, I never had a "WPD composite device". This is how it is shown now in device manager:
The way I did it was to plug the phone in, wait till the automatic driver installation failed
Click to expand...
Click to collapse
I saw this method on the internet but the weird thing is is that the drivers install correctly, first time, every time. See attached pictures.
Flashtool is THE tool for use with xperia devices. Look in the first thread of the development section. It should be the first thing you download when you get an xperia device.
Click to expand...
Click to collapse
I got the tool, found the drivers folder but was unable to install the drivers.
JamesStewy
JamesStewy said:
I saw this method on the internet but the weird thing is is that the drivers install correctly, first time, every time. See attached pictures.
I got the tool, found the drivers folder but was unable to install the drivers.
JamesStewy
Click to expand...
Click to collapse
¿Could it be that you have two phones detected?, as my pc only shows "Xperia T", no trace of "LT30p"; and the adb driver is in a category of its own.
I have no idea. I only have one thing connected to my computer which is my phone. I don't have an adb, Sony or android node in device manager at all.
JamesStewy
I don't know what else to tell you then. You might try uninstalling the LT30p, and forcing the upgrade to the pccompanion drivers I talked about before. But this is a wild guess, I can't really help you any further.
It's your adb installation correct. Have your added it to the path in environment.
Do you have usb debugging on in settings on your phone.
What was the error when you installed the flash tool drivers
What dies flash tool say when you attach the phone whilst it is open.
As the post above says, you could uninstall all phone/Sony/adb software and drivers and re install them.
I have never heard of this issue and just installing flash tool and/or pccompanion is enough to install all the drivers
Sent from my star trek communicator
Sony Flagship device circa 2145
It's your adb installation correct. Have your added it to the path in environment.
Click to expand...
Click to collapse
I am not sure. Is the adb installation part of the Android SDK platform-tools? If so I think it is. I can use all the commands such as adb devices but this returns and empty list. And yes it is in my PATH environment variable.
Do you have usb debugging on in settings on your phone.
Click to expand...
Click to collapse
Yes.
What was the error when you installed the flash tool drivers
Click to expand...
Click to collapse
When you say install, what do you mean? If you mean the process I described in a previous post then I get the message attached (untitled2.png).
going into device manager right clicking on my phone -> Update Driver Software... -> Browse my computer for driver software -> Enter in PC Companion drivers folder (or any other folder with appropriate drivers) -> Next -> Windows Message (attached file).
Click to expand...
Click to collapse
What dies flash tool say when you attach the phone whilst it is open.
Click to expand...
Click to collapse
Is the flash tool called EMMA or something? I downloaded it of Sony's site here: developer.sonymobile.com/services/flash-tool/. If so I can't get in because I am still waiting for a confirmation email.
As the post above says, you could uninstall all phone/Sony/adb software and drivers and re install them.
Click to expand...
Click to collapse
When I uninstall them and plug my phone back in the drivers on the phone install to my computer. Pictures attached. These drivers have nothing to do with ADB and only allow Windows to transfer files to my phone.
JamesStewy
No, flashtool I'd found in the first post in the development section.
Please download it, install it, and ruin the driver.exe found in the driver folder of flashtool in the installation path.
Install the Tx, flash mode and fast boot drivers
Sent from my star trek communicator
Sony Flagship device circa 2145
That's where I looked. Can you post a link.
JamesStewy
you sure you looked properly
http://forum.xda-developers.com/forumdisplay.php?f=1801
the very first thread. The link is in the very first post
EDIT
If you google "flashtool" and click I feel lucky it takes you straight to the flashtool homepage...
Xperia T - adb problems
I also tried all sort of things until this:
- you must put your phone in Mass Storage mode, as default is MTP mode.
As simple as that.
On your phone (unpluged) - Settings / Xperia / USB Connectivity / USB Connection Mode - and select MASS Storage, not MTP. I did uncheck Install PC Companion. Plug USB back, put your phone in debugging mode - It work right away. No need to Update drivers, no need to change the android_winusb.inf. You may need to kill adb.exe before trying again adb devices.
That was it for me
Hi laplada27,
Thanks for your reply. When I get home today I will give that a go.
Thanks,
James
Solution
laplada27 said:
I also tried all sort of things until this:
- you must put your phone in Mass Storage mode, as default is MTP mode.
As simple as that.
On your phone (unpluged) - Settings / Xperia / USB Connectivity / USB Connection Mode - and select MASS Storage, not MTP. I did uncheck Install PC Companion. Plug USB back, put your phone in debugging mode - It work right away. No need to Update drivers, no need to change the android_winusb.inf. You may need to kill adb.exe before trying again adb devices.
That was it for me
Click to expand...
Click to collapse
YES! It worked
Thank you so much.
James
Installing drivers 8.1
I am trying currently to update my T, it has an unlocked bl that I did when I first got it in Dec 12.
I am running w8.1 64 bit.
Tried both mass storage mode & mtp mode.
I have the latest 64 bit version of flashtool installed.
I am trying to flash the 295 generic ce ftf android 4.3 update, no problems with the ftf itself.
The error flashtool spits out is that the drivers are not installed, either the adb or flashmode drivers.
I have repeatedly tried to install the drivers that come with flashtool, and it appears that they install, but
there are a few that won't, I think namely the above.
I note that when I have device manager open, it detects the T, when plugged in in flashmode (i.e. turned off, with volume down)
as an s1boot device. I have intercepted device manager several times when it does this, in order to try and update the drivers
by hand, but no luck.
When I first plugged the T in in flashmode mode, it installed some drivers automatically, however, not ones that will allow flashtool
to work.
In truth I am now scratching my head as to what to do next.
I never had any problems with w7 64 ultimate flashing the T, solid as a rock, all the drivers would install as required, and I am
thinking the easiest way to update my T would be to use a w7 based machine, however, if anyone has any more ideas as to
what might help me flash it using 8.1 then I would be very grateful to hear them.
TheGSL
I think there is a patch for Windows 8.1... Search the forum and you will find it.
Good luck!

Device not recognizing on fastboot (to unlock BL)

I tried to unlock my BL today. but when i tried to connect my phone to fastboot windows 8.1 (64 bit) says USB device cannot recognize. Tried with driver signing off, tried alot of drivers (ADB drivers installed correctly btw). anybody else had this problem? anyway to fix this?
STALKER_88 said:
I tried to unlock my BL today. but when i tried to connect my phone to fastboot windows 8.1 (64 bit) says USB device cannot recognize. Tried with driver signing off, tried alot of drivers (ADB drivers installed correctly btw). anybody else had this problem? anyway to fix this?
Click to expand...
Click to collapse
Since you said u disabled signature verification now you follow my steps.
1.Open C:\Flashtool\drivers
2.Open Flashtool-drivers.exe
3.Click next and then select Flashmode drivers, Fastboot drivers, common drivers for viskan board:Xperia SP
4.Click install
5.Reboot your PC
Phoenix854 said:
Since you said u disabled signature verification now you follow my steps.
1.Open C:\Flashtool\drivers
2.Open Flashtool-drivers.exe
3.Click next and then select Flashmode drivers, Fastboot drivers, common drivers for viskan board:Xperia SP
4.Click install
5.Reboot your PC
Click to expand...
Click to collapse
Thanks man. i just upgraded my OS to Windows 10, not it works fine. :victory:
Phoenix854 said:
Since you said u disabled signature verification now you follow my steps.
1.Open C:\Flashtool\drivers
2.Open Flashtool-drivers.exe
3.Click next and then select Flashmode drivers, Fastboot drivers, common drivers for viskan board:Xperia SP
4.Click install
5.Reboot your PC
Click to expand...
Click to collapse
Hi,
I have managed to download and install the drivers successfully, Sony Sa0108 ADB Interface Driver, however, my phone is not being detected in Fastboot and windows. I am getting an error message saying Fastboot devices is not recognised as an internal or external command. Please can you help. Thank you.
Shoyaibpatel786 said:
Hi,
I have managed to download and install the drivers successfully, Sony Sa0108 ADB Interface Driver, however, my phone is not being detected in Fastboot and windows. I am getting an error message saying Fastboot devices is not recognised as an internal or external command. Please can you help. Thank you.
Click to expand...
Click to collapse
you need to install the system wide version, or point your command line to the folder the adb.exe is located in

Why is there no loader.sin in the ROMs I'm downloading with Xperifirm?

I am going to downgrade my X Perf from N to MM to do a TA backup and then upgrade again, but I have reached a rather annoying snag and I don't know if I'm doing something wrong. I am using Flashtool version 0.9.23.0, so it should work with the phone, but I still have to choose the phone every time, it doesn't read it from the bundle. And every attempt on the 4-5 ROMs I've tried so far gives me the error messages:
Code:
26/022/2016 09:22:46 - INFO - No loader in the bundle. Searching for one
26/022/2016 09:22:53 - INFO - No matching loader found
26/022/2016 09:22:53 - WARN - No loader found or set manually. Skipping loader
26/022/2016 09:22:53 - INFO - Ending flash session
26/022/2016 09:22:53 - ERROR - null
26/022/2016 09:22:53 - ERROR - Error flashing. Aborted
From what I can find out the problem is that there is no loader.sin in the firmwares I download. So far there hasn't been one in any of them! I have tried downloading on two different computers, and the same result all the time. Can anybody please tell me what I am doing wrong here? Or if the loader.sin is supposed to be taken from somewhere else. I haven't found anything about that in any of the "how to" threads I've seen.
same problem here..
First of all ensure Flashtool's drivers are properly installed on your system (windows 8/8.1/10 video guide)!
Also, you can try using an older version of Flashtool (0.9.18.6) to flash MM ftf. And ofc the new one for N.
The loader.sin is not part of ftf anymore, see MM and N ftf contents I've created and flashed successfully:
Serajr, thanks! I will make another attempt. And I have read your posts too, but didn't find a solution to this. Does this mean that Flashtool has to read the loader from the phone it's flashing, then?
Mastiff said:
Serajr, thanks! I will make another attempt. And I have read your posts too, but didn't find a solution to this. Does this mean that Flashtool has to read the loader from the phone it's flashing, then?
Click to expand...
Click to collapse
Exactly, that's why drivers must be properly installed!
And just in case...
If you want a recovery too, go for this one (multirom-20161218-recovery-fota-dora.zip). It is weird, but official twrp for dora does not work!!
To flash it, unpack the zip and flash its image with this fastboot command (just after you unlock your device's bootloader):
fastboot flash recovery twrp.img (after OK messages, unplug usb cable to turn device off).
Now you must enter on recovery (mandatory, otherwise you will need to flash twrp again), to do that: press Power and Volume Down buttons simultaneously, and release only the Power buttom when sony logo appears.
While on recovery ignore/disable any multirom function (unless you want it).
Well, I got one step further! I had misunderstood about the drivers, I thought it refered to the same driver as the ADB driver... But now I got to this:
26/033/2016 14:33:16 - WARN - No loader found or set manually. Skipping loader
26/033/2016 14:33:16 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : ROOTABLE
26/033/2016 14:33:16 - INFO - Max packet size set to 4M
26/033/2016 14:33:16 - INFO - USB buffer size set to 512K
26/033/2016 14:33:17 - INFO - Parsing boot delivery
26/033/2016 14:33:30 - INFO - No flash script found.
26/033/2016 14:33:30 - INFO - Flash script is mandatory. Closing session
26/033/2016 14:33:30 - INFO - Ending flash session
26/033/2016 14:33:30 - INFO - Flashing finished.
26/033/2016 14:33:30 - INFO - Please unplug and start your phone
26/033/2016 14:33:30 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
26/033/2016 14:33:30 - INFO - Device connected in flash mode
26/033/2016 14:33:48 - INFO - Device disconnected
Click to expand...
Click to collapse
I did choose not to use an FSC script as you said, but does that have anything to do with the reason for this failure, or is there something else going on here?
Edit: I'm still trying to downgrade to MM so I can backup the TA. I selected to wipe everything except the TA, and I excluded the TA, which I understood that I should do. Is there something I should have done while converting the file?
Mastiff said:
Well, I got one step further! I had misunderstood about the drivers, I thought it refered to the same driver as the ADB driver... But now I got to this:
I did choose not to use an FSC script as you said, but does that have anything to do with the reason for this failure, or is there something else going on here?
Edit: I'm still trying to downgrade to MM so I can backup the TA. I selected to wipe everything except the TA, and I excluded the TA, which I understood that I should do. Is there something I should have done while converting the file?
Click to expand...
Click to collapse
Did you do this?
Code:
26/033/2016 14:33:30 - INFO - For flashtool, [B][U]Unknown Sources[/U][/B] and [U][B]Debugging[/B][/U] must be checked in phone settings
Yep. I started the phone and checked that it was done after that fail, and both were set to on. Some of the first things I do on a phone, Titanium backup needs those settings to work. Of course it also needs root, which I do not yet have...
Edit: It is USB debugging that it means, right? Under Developer options?
I tried to start the phone again and authorize the pc for USB debugging (never had to do that before on any phone), but it didn't change anything.
Yep, it is!
Well buddy, things are starting to become tough. Try this:
- Turn your device off and keep it disconnected from usb
- Open Flashtool and start the MM flash process (choose firmware, etc...)
- Click on flash button. The message to connect your device in flash mode will pop up
- Now connect your phone to the usb while pressing Volume Down button (and do release it after flash process begins)
Ofc I can also being forgetting something, so please, anybody else reading to this thread, comment on!
Edit: On ftf creation I've also ignored FSC script! Did you?
Edit 2: Let windows recognizes your device into flashmode. With Flashtool closed (and others windows apps too), also with your device turned off, connect it to the usb with Volume Down (flashmode) button pressed. Is everything ok, did windows recognize it?
Do the same after you unlock the bootloader, with Volume Up (fastboot), and type in a windows command prompt: fastboot devices
Well, I installed the drivers again, just to test. But one thing: I only found the common drivers, and not a driver that worked specifically for the X Performance. Can that be the problem? I thought it would be in this version of Sony Mobile Flasher. Also I see a few errors in device manager. It's named "SOMC Flash Device", but under the Information part I see:
Device USB\VID_0FCE&PID_ADDE\5&2c705bfe&0&1 could not be migrated.
Click to expand...
Click to collapse
So is this still a driver issue? I looked through the list in the drivers installation program, but didn't see any driver for this phone. So I only get two drivers, the Google Inc. Win USB and Sony Mobile Communications ggsomc. I am probably missing something, right?
Edit: Not sure if I skipped the FSC script, but I'm making a new bundle now and will try with that to see if I may have forgotten to skip it on creation this last time.
Nope, new bundle didn't help. Also I found an old howto that said;
NOTE: If your list of files includes “fwinfo.xml” as highlighted below then manually delete it before continuing to the FlashTool steps. You MUST delete this file otherwise your FTF firmware file will corrupt.
Click to expand...
Click to collapse
But that was from 2014, so I do assume that this has been fixed.
And to continue the stream of info, this is not the firmware, it seems. I tried with a different firmware (Nougat for Nordic Countries) and it went just like with the Polish Marshmallow.
I have an idea for a last attempt: I will reset the phone to factory, do a very quick setup to where I get USB debugging and unknown sources and then try again.
Ok, download this one from sony and unpack it.
Now add hardware manually and point to the *.inf file (there should be at least 3 options to install).
Edit: "Device USB\VID_0FCE&PID_ADDE\5&2c705bfe&0&1 could not be migrated." << I have this too, and everything works!
Thanks! But I get a message that there are no drivers compatible with Windows 64 in that file. Weird, because it actually says that it does on that page. Maybe it just isn't compatible with Windows 10, I will try it on a Windows 7 computer I have here.
Nope, same error from both flash attempts and the driver file when using Windows 7. I do not have a Windows 7 32 bit device anywhere near, I'm afraid.
Mastiff said:
Thanks! But I get a message that there are no drivers compatible with Windows 64 in that file. Weird, because it actually says that it does on that page. Maybe it just isn't compatible with Windows 10, I will try it on a Windows 7 computer I have here.
Click to expand...
Click to collapse
This is the inf file and all x64 (and 32) contents from my android sdk folder. Try pointing to this one!
This is very strange, if those drivers worked on your system. Still the same thing, no compatible driver, check that any drivers in the directory are made for Windows 64 bit systems (roughly translated from Norwegian). But it is the SOMC Flash Device that I should use this driver on, right? In that case I have no idea why that's happening here.
Mastiff said:
This is very strange, if those drivers worked on your system. Still the same thing, no compatible driver, check that any drivers in the directory are made for Windows 64 bit systems (roughly translated from Norwegian). But it is the SOMC Flash Device that I should use this driver on, right? In that case I have no idea why that's happening here.
Click to expand...
Click to collapse
It is weird indeed! I think so, and I really don't remenber the right one, maybe Android Composite ADB interface.
Windows 7 things are much easier, but it must work on 10 as well! Hope you succeed!!
Edit: For further info to unlock device's bootloader > https://www.youtube.com/watch?v=iIdJg7KNH3A

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 5

Hello Everyone !!​
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD​
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008​
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you
reserved
@vasu97
We already have a dedicated thread on the same topic.
what can i edit so it won't relock the bootloader? or does it relock it?
vasu97 said:
Hello Everyone !!​
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD​
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008​
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you
Click to expand...
Click to collapse
Holy crap! I literally spent the last 12 hours trying to get my phone fixed. This was the only solution. Thank you so much!!!
If anyone had problems with the MSM tool "Sahara communication failed," unplug your phone. Turn it off by holding the power button for a while. Hold the power up for 10 seconds, then keep holding the volume up and plug your phone in to the PC. The MSM tool should automatically detect and restore your phone.
vasu97 said:
reserved
Click to expand...
Click to collapse
thank you so much
I've tried all the steps on multiple ports and different computers but I got always the errno 258 while loading the cache.img. Don't know what else to do...

Installing Flashtool drivers (MacOS)

Hello. I am trying to follow this rooting guide .
I am stuck on the following point:
3. ....... Install flashtool, navigate to its folder, and open folder called Drivers and install following drivers: Flashmode drivers,fastboot drivers and xperia z3 compact drivers.
Click to expand...
Click to collapse
As I am using MacOS, I look in the contents folder of the Flashtool application, but I cannot see a file called 'Drivers' or similar anywhere.
Flashtool seems to detect my phone without issue.
Any help would be greatly appreciated.
I think MacOS doesn't need drivers as I believe it is the same with Linux it should work out of the box as is.

Categories

Resources