Problem setting up fastboot - Sony Xperia T, TL, TX, V

I'm following the instructions from the Sony site about unlocking the bootloader and when I hold the fastboot button and plug the phone in, I get no option to tell it where the driver is. This means the driver fails, any idea how to get around this?
I'm on win 7.

rsmarsha said:
I'm following the instructions from the Sony site about unlocking the bootloader and when I hold the fastboot button and plug the phone in, I get no option to tell it where the driver is. This means the driver fails, any idea how to get around this?
I'm on win 7.
Click to expand...
Click to collapse
Does the computer make any noise? the usual "D Ding" that a computer makers when you insert a usb device? Also, does the LED turn blue when you plug it in?
And you are using the volume up button?

gregbradley said:
Does the computer make any noise? the usual "D Ding" that a computer makers when you insert a usb device? Also, does the LED turn blue when you plug it in?
And you are using the volume up button?
Click to expand...
Click to collapse
Yeah it made the ding and the first time showed that drivers failed to install, after that just the noises.
It does turn blue, then just shows the battery charge screen.

rsmarsha said:
Yeah it made the ding and the first time showed that drivers failed to install, after that just the noises.
It does turn blue, then just shows the battery charge screen.
Click to expand...
Click to collapse
Then unistall everything and start again. Make sure you get the correct driver from the site and put it in the correct folder for the sdk.

gregbradley said:
Then unistall everything and start again. Make sure you get the correct driver from the site and put it in the correct folder for the sdk.
Click to expand...
Click to collapse
I'll try, just downloaded the sdk extracted it and run eclipse. Installed the usb driver in there and then copied the file. No fastboot in my tools folder though.

rsmarsha said:
I'll try, just downloaded the sdk extracted it and run eclipse. Installed the usb driver in there and then copied the file. No fastboot in my tools folder though.
Click to expand...
Click to collapse
eclipse?
Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager.
Click to expand...
Click to collapse

gregbradley said:
eclipse?
Click to expand...
Click to collapse
Yeah it comes with a version of eclipse. I couldn't open the sdk manager from the extracted zip, had to do it via the include eclipse version. I installed the usb driver from there, v7.

rsmarsha said:
Yeah it comes with a version of eclipse. I couldn't open the sdk manager from the extracted zip, had to do it via the include eclipse version. I installed the usb driver from there, v7.
Click to expand...
Click to collapse
ok, not sure about that. I followed the link from the official sony site and it installed fine....those instructions are perfectly fine...

gregbradley said:
ok, not sure about that. I followed the link from the official sony site and it installed fine....those instructions are perfectly fine...
Click to expand...
Click to collapse
Thanks, I followed the same instructions, not sure what's going on.

rsmarsha said:
Thanks, I followed the same instructions, not sure what's going on.
Click to expand...
Click to collapse
I would ensure you unistall all adb, sdk and android related stuff.
Follow the instructions to install the sdk letter by letter. Make sure its in your root directory and that you run the sdk manager to install the latest google drivers..
Or see if you can borrow another machine to do it on.
Finally, try connecting in fastboot again and going to device manager and seeing if anything has a yellow exclamation mark or any devices are unrecognised...

When i download and extract the sdk i have an eclipse folder which I run to get the SDK and the install the driver and plug in the phone. I get a ding and then another as if it's unplugged. A bit stuck.

gregbradley said:
I would ensure you unistall all adb, sdk and android related stuff.
Follow the instructions to install the sdk letter by letter. Make sure its in your root directory and that you run the sdk manager to install the latest google drivers..
Or see if you can borrow another machine to do it on.
Finally, try connecting in fastboot again and going to device manager and seeing if anything has a yellow exclamation mark or any devices are unrecognised...
Click to expand...
Click to collapse
I have S1 fastboot with the yellow triangle but when I try to point it to the folder with the driver in, it doesn't find anything.

rsmarsha said:
I have S1 fastboot with the yellow triangle but when I try to point it to the folder with the driver in, it doesn't find anything.
Click to expand...
Click to collapse
Once you have copied over the file from the download on the sony site, just point it at the correct folder and click ok

gregbradley said:
Once you have copied over the file from the download on the sony site, just point it at the correct folder and click ok
Click to expand...
Click to collapse
Yeah that's what I did but windows doesn't find the driver there.

rsmarsha said:
Yeah that's what I did but windows doesn't find the driver there.
Click to expand...
Click to collapse
Something is not right with your setup.
If you could viseo exactly what you are doing and upload it that would help....or at the minimum state the steps you have gone through and exactly how you did them.

gregbradley said:
Something is not right with your setup.
If you could viseo exactly what you are doing and upload it that would help....or at the minimum state the steps you have gone through and exactly how you did them.
Click to expand...
Click to collapse
I have sorted it I think with info from this post.
http://forum.cyanogenmod.org/topic/57427-having-problems-connecting-to-fastboot-under-windows-7-64/
That worked and then I plugged the phone in again using fastboot and it picked it up and unlocked the bootloader.
Thanks for looking at this for me, it looks like it's a 64 bit windows problem.

Turned phone on ready to copy rom files over and the phone has reset to factory after unlocking bootloader, is that normal?

Yes, in the instructions for unlocking the bootloader it says that will happen
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?

gregbradley said:
Yes, in the instructions for unlocking the bootloader it says that will happen
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
Click to expand...
Click to collapse
Thanks, installed cm10 and it's buggy as hell on my phone so an unusable phone at the moment as i can't get it to be seen by flashtool anymore. Ah well that's for another thread, thanks for your help.

I'm not sure you've done stuff right if you're finding CM10 buggy.
Sent from my Xperia T using Tapatalk 2

Related

[Q] Help Unlocking Bootloader?!

Tried the sony method... Device not found...
Tried the flashtool method... Device not found...
I don´t know if I´m getting the fastboot drivers right or not, the does turn blue when I connect it to the PC in fastboot mode...
USB debugging is checked...
Does the phone need to be in sotck FW 350?
Help?
emoratori said:
Tried the sony method... Device not found...
Tried the flashtool method... Device not found...
I don´t know if I´m getting the fastboot drivers right or not, the does turn blue when I connect it to the PC in fastboot mode...
USB debugging is checked...
Does the phone need to be in sotck FW 350?
Help?
Click to expand...
Click to collapse
First of all, Bootloader Unlock Allowed: Yes?
diego9016 said:
First of all, Bootloader Unlock Allowed: Yes?
Click to expand...
Click to collapse
Yep...
emoratori said:
Yep...
Click to expand...
Click to collapse
Did you install the fastboot drivers?
diego9016 said:
Did you install the fastboot drivers?
Click to expand...
Click to collapse
I did, but I don´t know if they´re working.
Didn´t notice anything different in the device manager.
The first time I connected my device windows couldn´t install them, but it did not ask for them again.
How are them suposed to be installed?
emoratori said:
I did, but I don´t know if they´re working.
Didn´t notice anything different in the device manager.
The first time I connected my device windows couldn´t install them, but it did not ask for them again.
Click to expand...
Click to collapse
That's the problem. Windows can't install them just when you connect the phone, you need to install them manually.
When you downloaded the Unlock Bootloader tool, there was a folder or a zip with the drivers. If it is a zip, extract it.
Connect the phone leaving up arrow pressed, the led will turn blue.
Go to device manager on the pc, look for Fastboot or something like that.
Select browse my computer for driver software and select the divers folder. It should install them right away.
Now you have the fastboot drivers installed and you can continue with the procedure.
Edit: You already have the KEY from Sony?
diego9016 said:
That's the problem. Windows can't install them just when you connect the phone, you need to install them manually.
When you downloaded the Unlock Bootloader tool, there was a folder or a zip with the drivers. If it is a zip, extract it.
Connect the phone leaving up arrow pressed, the led will turn blue.
Go to device manager on the pc, look for Fastboot or something like that.
Select browse my computer for driver software and select the divers folder. It should install them right away.
Now you have the fastboot drivers installed and you can continue with the procedure.
Edit: You already have the KEY from Sony?
Click to expand...
Click to collapse
When I go to DEVICE MANAGER I can´t find fastboot or anything like it... There are a couple of unknown devices...
I should power down the phone and connect it with vol up right?
emoratori said:
When I go to DEVICE MANAGER I can´t find fastboot or anything like it... There are a couple of unknown devices...
Click to expand...
Click to collapse
Win7?
Can you attach some screenshots of the device manager page?
Yes. You need to power off and connect the device holding up until led turns blue.
diego9016 said:
Win7?
Can you attach some screenshots of the device manager page?
Yes. You need to power off and connect the device holding up until led turns blue.
Click to expand...
Click to collapse
Yeah, win7... 64x...
I´m at work right now... When I get home I´ll post...
PLEASE don´t leave me!!! hehehe...
emoratori said:
Yeah, win7... 64x...
I´m at work right now... When I get home I´ll post...
PLEASE don´t leave me!!! hehehe...
Click to expand...
Click to collapse
Don't worry, if I can help, I'll do it.
EDIT: When you get home, check this out. It was for 2011/12 devices, but most of the procedure works for the Z.
Fastboot drivers are unsurported on x64 you have disable driver verification
diego9016 said:
Don't worry, if I can help, I'll do it.
EDIT: When you get home, check this out. It was for 2011/12 devices, but most of the procedure works for the Z.
Click to expand...
Click to collapse
One question...
If I install the fastboot drivers through the flash tool should it work?
Maddhouse said:
Fastboot drivers are unsurported on x64 you have disable driver verification
Click to expand...
Click to collapse
How?
Thanks!
think this is it
1. download flashtool and install
2. type "bcdedit /set testsigning on" in cmd and restart PC
3. install driver in the flashtool "drivers" folder, check fastboot, agree when prompts
4. type "bcdedit /set testsigning off" in cmd and restart PC
http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484(v=vs.85).aspx
EDIT:
Also this might be handy if you are planning alot of adb usage
Got it!
Usb debugging was MST and not MCS... duh...
Unocked...
Recovery...
Rooted...
THANKS!

[Q] Fastboot not recognizing device?

I do have my drivers updated and installed (no HTC Sync).
I have sdk-tools and everything as well.
here's what i noticed:
So when I have my phone at the bootloader plugged into my USB, it won't say fastboot unless I press the volume up or down keys and as soon as i do then it says "FASTBOOT USB".
On the computer however, it just says "<Waiting for device>" forever. weird
Any ideas guys?
TechnoHacker said:
I do have my drivers updated and installed (no HTC Sync).
I have sdk-tools and everything as well.
here's what i noticed:
So when I have my phone at the bootloader plugged into my USB, it won't say fastboot unless I press the volume up or down keys and as soon as i do then it says "FASTBOOT USB".
On the computer however, it just says "<Waiting for device>" forever. weird
Any ideas guys?
Click to expand...
Click to collapse
do you have sdk tools installed properly??
Aldo101t said:
do you have sdk tools installed properly??
Click to expand...
Click to collapse
I believe so. I am able to use adb and etc not fastboot.
Also, windows pops up with an error saying "USB device malfunctioned" when its in fastboot.
TechnoHacker said:
I believe so. I am able to use adb and etc not fastboot.
Also, windows pops up with an error saying "USB device malfunctioned" when its in fastboot.
Click to expand...
Click to collapse
is your command prompt running as administrator, are you in the right directory ei/;cd c:\Program Files\Android\android-sdk\platform-tools) etc.
also the enviormental variables need to be set also
Aldo101t said:
is your command prompt running as administrator, are you in the right directory ei/;cd c:\Program Files\Android\android-sdk\platform-tools) etc.
also the enviormental variables need to be set also
Click to expand...
Click to collapse
Yes and yes.
I set the environment variables too
TechnoHacker said:
Yes and yes.
I set the environment variables too
Click to expand...
Click to collapse
well, shoot it should be ok then????
are the latest executibles of adb install check for updates on your sdk manager, open as administrator also. are you on windows 8.1 or using a 3.0 usb port, these will cause problems also
Aldo101t said:
well, shoot it should be ok then????
Click to expand...
Click to collapse
Yeah but it's not :/
Aldo101t said:
well, shoot it should be ok then????
Click to expand...
Click to collapse
Also HBOOT won't detect a PN07IMG.zip I have.
TechnoHacker said:
Also HBOOT won't detect a PN07IMG.zip I have.
Click to expand...
Click to collapse
no , it won't because of the internal sdcard, not like the external has different partitions.
Aldo101t said:
no , it won't because of the internal sdcard, not like the external has different partitions.
Click to expand...
Click to collapse
Oh got it thanks.
Now the fastboot thing is my only issue
TechnoHacker said:
Oh got it thanks.
Now the fastboot thing is my only issue
Click to expand...
Click to collapse
did you read my edit on post #6
Aldo101t said:
well, shoot it should be ok then????
are the latest executibles of adb install check for updates on your sdk manager, open as administrator also. are you on windows 8.1 or using a 3.0 usb port, these will cause problems also
Click to expand...
Click to collapse
No updates I checked the SDK Manager.
I'm on Windows 8 using a USB 2.0 Port.
TechnoHacker said:
No updates I checked the SDK Manager.
I'm on Windows 8 using a USB 2.0 Port.
Click to expand...
Click to collapse
ok, well that's all i can think of maybe someone more knowledgeable will chime in here.
Aldo101t said:
ok, well that's all i can think of maybe someone more knowledgeable will chime in here.
Click to expand...
Click to collapse
Okay, well thanks for your help though!
I have a couple ideas, not sure if any work.
1) test with the phone in android to see if HTC Sync recognizes the phone
2) Re-download fastboot and re extract it to make sure it's not that
3) Boot into twrp and see if it recognizes adb commands. This one won't fix it, but I'm just wondering if could possibly be a problem with the phone not recognizing while not in system
4) Use adb to reboot to bootloader instead of using the apm or holding down volume. "adb reboot bootloader"
If I helped you don't forget the thanks button!
Phone: Sprint HTC One
Rom: Dark EclipticONE 3.6
Kernel: ElementalX 0.4
Recovery: TWRP 2.5.0.0
Bootloader: Revone S-Off
TechnoHacker said:
Oh got it thanks.
Now the fastboot thing is my only issue
Click to expand...
Click to collapse
Try uninstalling everything HTC
Reboot you pc and phone
Once both are booted plug your phone in and it should load a bunch if drivers
Also when you go to bootloader it should install more drivers
If that does not work
Get the latest drivers from HERE choose the 6/6/13
Sent from my HTC One Everything you're phone isn't
bigdaddy619 said:
Try uninstalling everything HTC
Reboot you pc and phone
Once both are booted plug your phone in and it should load a bunch if drivers
Also when you go to bootloader it should install more drivers
If that does not work
Get the latest drivers from HERE choose the 6/6/13
Sent from my HTC One Everything you're phone isn't
Click to expand...
Click to collapse
Tried that, still no luck. I'm going to try installing HTC Sync from HTC, and then uninstall it and try.
plegrand said:
I have a couple ideas, not sure if any work.
1) test with the phone in android to see if HTC Sync recognizes the phone
2) Re-download fastboot and re extract it to make sure it's not that
3) Boot into twrp and see if it recognizes adb commands. This one won't fix it, but I'm just wondering if could possibly be a problem with the phone not recognizing while not in system
4) Use adb to reboot to bootloader instead of using the apm or holding down volume. "adb reboot bootloader"
If I helped you don't forget the thanks button!
Phone: Sprint HTC One
Rom: Dark EclipticONE 3.6
Kernel: ElementalX 0.4
Recovery: TWRP 2.5.0.0
Bootloader: Revone S-Off
Click to expand...
Click to collapse
1. It does.
2. I re-downloaded all the drivers. and it still isn't working .
[I have attached the issues that pop-up]
3. Yeah, it works perfectly in TWRP and it shows up in recovery mode.
4. I've tried both ways neither seem to work with it detecting fastboot
What version of Windows do you have?
Sent from my HTCONE using xda premium
mrlakadaddy said:
What version of Windows do you have?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Windows 8 Pro (64 bit)
Sent from my HTCONE using xda app-developers app

help unlocking bootloader

hey guys,
hopefully someone can help me, i'm trying to unlock my bootloader to install custom kernels.
here is when i think it goes wrong:
i'm using sony's official method but when i connect the phone in fastboot mode the computer doesn't ask for drivers like it should (says in instructions).
so i can't choose the modified driver that i've downloaded from the instructions.
thanks in advance!
you may already have it installed if you have installed flashtool.
I suggest deleting all sony/adb/phone applications on your computer, rebooting, and starting again
gregbradley said:
you may already have it installed if you have installed flashtool.
I suggest deleting all sony/adb/phone applications on your computer, rebooting, and starting again
Click to expand...
Click to collapse
that's correct indeed,
damnit.. i'm going to try it..
gregbradley said:
you may already have it installed if you have installed flashtool.
I suggest deleting all sony/adb/phone applications on your computer, rebooting, and starting again
Click to expand...
Click to collapse
even after a fresh install of my computer i can't get it to work.
i searched on google and found out that there are some issues with windows 8.
but after following specific instructions on windows 8 it still isn't working.
then i took an old windows vista computer from the attic and tried it with that.
it atleast asks for drivers but when i get the option to select the drivers myself it instantly disappears because the phone only stays in fastboot for about 10 seconds.
only thing i can think of is installing XP on my old system but is it normal it stays in fastboot for only 10 seconds? then it switches to charging mode.
unlock bootloader allowed is yes!
Download and install flash tool.
Run drivers.exe from the install folder.
Choose fastboot, flashmode and TX drivers.
Then try again for unlocking
Sent from my LT30p using xda premium
EDIT
W8 is a known problem with drivers. That's why is was failing before. Vista or W7 should work fine.
gregbradley said:
Download and install flash tool.
Run drivers.exe from the install folder.
Choose fastboot, flashmode and TX drivers.
Then try again for unlocking
Sent from my LT30p using xda premium
EDIT
W8 is a known problem with drivers. That's why is was failing before. Vista or W7 should work fine.
Click to expand...
Click to collapse
in the mean time i've read somewhere to use flashtool indeed.
got the drivers installed on my w8 system with flashtool, now the phone stays in fastboot (blue light)
then my next problem :laugh:
Open a command window and go to the tools folder within the Android SDK folder.
Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly.
there is no fastboot.exe in the tools folder of sdk..
there is one in some folder of flashtool, can i use that one to complete the last point of the instruction?
Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK
Click to expand...
Click to collapse
That is from step 8.
Did you download the google bit of the sdk?
EDIT
You could try this as well
minimal_adb_fastboot_v1.1.3_setup.exe - 2.12 MB
gregbradley said:
That is from step 8.
Did you download the google bit of the sdk?
EDIT
You could try this as well
minimal_adb_fastboot_v1.1.3_setup.exe - 2.12 MB
Click to expand...
Click to collapse
i finally found it.. it's not in tools folder anymore but platform tools.
i'm going to try again now..
Pollie81 said:
i finally found it.. it's not in tools folder anymore but platform tools.
i'm going to try again now..
Click to expand...
Click to collapse
yes..it has been moved. I forgot that myself
gregbradley said:
yes..it has been moved. I forgot that myself
Click to expand...
Click to collapse
it took a while and some extra grey hair but it's done..
i guess... it restarts and the phone went back to stock.
first i'm going to watch LA Ink on tv and then going to try to restore my backup and flash a custom kernel.
many thanks for your help! we got it working!
:good:

Swap firmware region

Hi Guys,
I currently have an Hong kongese version of our beloved xz1 compact but unfortunately the updates are painfully slow and i would like to change firmware with the tools posted on this forum.
I would like to change into a German one which seems to be one of the very first to receive updates.
I have a concern and a pair of questions for ya'll :
1. If i change the firmware to a region that far and different from the one i have already, will i have different data signal and possibly lower or much lower?
I ask this because i previously had the X compact and i tried to do the same and my signal was no where as consistent and full as with the original Firmware.
2. Is there a way to change to another firmware but maintain the modem settings or files or whatever to have the same signal strenght of the original Firmware ?
thanks fellas and i apologise for mistakes since Eng isn't my native language. I come from Pizza Land
[OT] I'm sorry I can't answer your question, but I have to say that your written English is better than that of most of my fellow Americans!
You should be able to flash almost any firmware version, I don't think there are different modem drivers for each region any more. I have tried several regions of firmware here in the UK and none have effected signal reception or strength.
You will need ADB drivers for the phone and beware if you've used your laptop/workstation for another model of phone as sometime this can interfere.
Start with Xperiafirm and download the most recent firmware build, which as I type is UK customised.
Download newflasher and unpack it into the same folder as the firmware.
Delete userdataXXX.sin
Turn off phone, plug it in, start newflasher, type 'n' to the first two questions.
This should get you the latest build phone with your data intact
Didgesteve said:
You should be able to flash almost any firmware version, I don't think there are different modem drivers for each region any more. I have tried several regions of firmware here in the UK and none have effected signal reception or strength.
You will need ADB drivers for the phone and beware if you've used your laptop/workstation for another model of phone as sometime this can interfere.
Start with Xperiafirm and download the most recent firmware build, which as I type is UK customised.
Download newflasher and unpack it into the same folder as the firmware.
Delete userdataXXX.sin
Turn off phone, plug it in, start newflasher, type 'n' to the first two questions.
This should get you the latest build phone with your data intact
Click to expand...
Click to collapse
thank you very much!
I'll follow your instructions.
Sent from my G8441 using Tapatalk
From my past experience, the Customized NOBA region is usually among the first wave (if not the first) to receive new firmware. If you're betting on consistent bleeding edge updates, I'd go all in with NOBA.
unotretresette said:
thank you very much!
I'll follow your instructions.
Sent from my G8441 using Tapatalk
Click to expand...
Click to collapse
ADB drivers
Xperiafirm
Newflasher
Didgesteve said:
ADB drivers
Xperiafirm
Newflasher
Click to expand...
Click to collapse
This is the most complete answer I could ever receive.
Unfortunately , I have had another problem.
I downloaded the ADB Drivers but I can't install them.
When the phone is on (I activated USB debugging as well) I can get ADB to work on my Computer.
I run the CMD Shell and input "adb devices" and the smartphone is recognised automatically, however when I switch off the xz1c and press volume down and plug it to the PC to activate the "FLASH MODE", the phone isn't recognised at all.
I went to "Device Manager" and saw "Android" with a yellow exclamation point next to it so I clicked and selected Update Drivers.
I chose the folder where I unzipped the one you asked me to download and selected the subfolders.
Once proceeded, I got a negative response from Windows saying that" Windows could not find the drivers for your device".
So I am stuck here and I can't use newflasher at all.
Sent from my G8441 using Tapatalk
unotretresette said:
This is the most complete answer I could ever receive.
Unfortunately , I have had another problem.
I downloaded the ADB Drivers but I can't install them.
When the phone is on (I activated USB debugging as well) I can get ADB to work on my Computer.
I run the CMD Shell and input "adb devices" and the smartphone is recognised automatically, however when I switch off the xz1c and press volume down and plug it to the PC to activate the "FLASH MODE", the phone isn't recognised at all.
I went to "Device Manager" and saw "Android" with a yellow exclamation point next to it so I clicked and selected Update Drivers.
I chose the folder where I unzipped the one you asked me to download and selected the subfolders.
Once proceeded, I got a negative response from Windows saying that" no drivers have been found".
So I am stuck here and I can't use newflasher at all.
Sent from my G8441 using Tapatalk
Click to expand...
Click to collapse
You could download and install flashtool. Although you cannot use flashtool to flash your XZ1c, once it's installed there is a 'Drivers' folder in it, inside that is a very handy .exe that installs all the drivers you need for flashing and ADB.
Otherwise a quick search found this
Edit: I don't think you have to hold the volume down to use newflasher. All I did was turn the phone off, plug it in, start newflasher.
Didgesteve said:
You could download and install flashtool. Although you cannot use flashtool to flash your XZ1c, once it's installed there is a 'Drivers' folder in it, inside that is a very handy .exe that installs all the drivers you need for flashing and ADB.
Otherwise a quick search found this
Edit: I don't think you have to hold the volume down to use newflasher. All I did was turn the phone off, plug it in, start newflasher.
Click to expand...
Click to collapse
I am using Windows 10 64bit and I get this error from newflasher :
No usb device with vid:0x0fce pid:0xb00b
unotretresette said:
I am using Windows 10 64bit and I get this error from newflasher :
No usb device with vid:0x0fce pid:0xb00b
Click to expand...
Click to collapse
If you are using Windows 10 then the drivers won't have installed properly.
You need to hold 'shift' while restarting the machine. Then when it starts in safe mode, look for 'disable driver signatures' or something like that, in the advanced menu.
Then try installing the drivers again.
Didgesteve said:
If you are using Windows 10 then the drivers won't have installed properly.
You need to hold 'shift' while restarting the machine. Then when it starts in safe mode, look for 'disable driver signatures' or something like that, in the advanced menu.
Then try installing the drivers again.
Click to expand...
Click to collapse
I did it already and I have installed the drivers.
I see the same error ....
unotretresette said:
I did it already and I have installed the drivers.
I see the same error ....
Click to expand...
Click to collapse
If you open device manager on the PC and then open up USB devices, you should see the phone listed, with a warning.
Update the drivers in the USB section with the ones you downloaded from Sony, just point to the unpacked folder, you don't need to open any of the folders, it should work with the sa0117adb.inf file.
This is while your phone is turned off and connected, not turned on.
Didgesteve said:
If you open device manager on the PC and then open up USB devices, you should see the phone listed, with a warning.
Update the drivers in the USB section with the ones you downloaded from Sony, just point to the unpacked folder, you don't need to open any of the folders, it should work with the sa0117adb.inf file.
This is while your phone is turned off and connected, not turned on.
Click to expand...
Click to collapse
When I connect my phone in FLASH MODE and I check Devices Manager, I see "android" with the warning....
I try to select the drivers I downloaded but windows says that the drivers aren't found for this devices.....
I did everything possible !
unotretresette said:
When I connect my phone in FLASH MODE and I check Devices Manager, I see "android" with the warning....
I try to select the drivers I downloaded but windows says that the drivers aren't found for this devices.....
I did everything possible !
Click to expand...
Click to collapse
Did you install the drivers from flashtool drivers folder?
Edit: in safe mode..
Didgesteve said:
Did you install the drivers from flashtool drivers folder?
Edit: in safe mode..
Click to expand...
Click to collapse
I did but i get always the same errors:crying:
unotretresette said:
I did but i get always the same errors:crying:
Click to expand...
Click to collapse
when you started the flashtool drivers update, which drivers did you pick?
Didgesteve said:
when you started the flashtool drivers update, which drivers did you pick?
Click to expand...
Click to collapse
I installed flash mode and fastboot drivers.
Sent from my G8441 using Tapatalk
unotretresette said:
I installed flash mode and fastboot drivers.
Sent from my G8441 using Tapatalk
Click to expand...
Click to collapse
Perhaps this Reddit guide can help you
Didgesteve said:
Perhaps this Reddit guide can help you
Click to expand...
Click to collapse
I read the guide but these steps are exactly the ones I followed already.
I'm very unlucky.
Probably something I did in the past or my OS doesn't allow me to do what I wanna do.
I try the last option with my wife's laptop with Windows 7.
If it doesn't work, I'll wait for the update to come naturally which will probably take some months [emoji854]
Sent from my G8441 using Tapatalk
unotretresette said:
I read the guide but these steps are exactly the ones I followed already.
I'm very unlucky.
Probably something I did in the past or my OS doesn't allow me to do what I wanna do.
I try the last option with my wife's laptop with Windows 7.
If it doesn't work, I'll wait for the update to come naturally which will probably take some months [emoji854]
Sent from my G8441 using Tapatalk
Click to expand...
Click to collapse
Did you enable USB debug in the developer options?

Windows 10 fastboot drivers not working

Hi guys,
I need to unroot my RP2 to send it in for repair, but I can't for the life of me get my fastboot drivers working in Windows 10 2004. I've tried various versions of the stock Google USB drivers (bootloader, of course), but the phone still shows up as "Android" in "Other devices".
Thanks in advance for any suggestions, fellas.
-edison
Try Samsung USB Drivers. Sometimes theirs work when Google's doesn't.
FQuimson23 said:
Try Samsung USB Drivers. Sometimes theirs work when Google's doesn't.
Click to expand...
Click to collapse
I downloaded their driver pack, but couldn't find any Android-specific ones. Any idea which one would work?
edison said:
I downloaded their driver pack, but couldn't find any Android-specific ones. Any idea which one would work?
Click to expand...
Click to collapse
https://developer.samsung.com/mobile/android-usb-driver.html
The issue is with the newest version of windows. I haven't tried the Samsung drivers. What worked for me was making a live usb install of FWUL. Then I could boot from the USB and everything worked.
I have Windows 10 Ver 20H2 installed and can confirm I have gotten ADB and Fastboot drivers WORKING, following the original installation instructions from Razer. It's not very clear, but be SURE to EXTRACT the files AFTER downloading from Razer. Follow the instructions CAREFULLY. I can't tell you how many times I've had to go back and re-read the directions to get it right. I went so far as to reinstall Windows 10 v.1909 on an external drive and issued commands that way, as a work around. Today, I decided to take a chance, and got everything working again.
MoPhoMike said:
I have Windows 10 Ver 20H2 installed and can confirm I have gotten ADB and Fastboot drivers WORKING, following the original installation instructions from Razer. It's not very clear, but be SURE to EXTRACT the files AFTER downloading from Razer. Follow the instructions CAREFULLY. I can't tell you how many times I've had to go back and re-read the directions to get it right. I went so far as to reinstall Windows 10 v.1909 on an external drive and issued commands that way, as a work around. Today, I decided to take a chance, and got everything working again.
Click to expand...
Click to collapse
i treid this with no luck
dokibull said:
i treid this with no luck
Click to expand...
Click to collapse
What errors are you seeing? No communication in fastboot mode? If so, your driver is not properly installed. Your phone MUST be in fastboot mode when installing the driver. If your phone is booted up, you;ll only be able to install the ADB driver.
Additionally, I should have gone back and edited this post. The issue I was facing "back then" was that I didn't follow the driver installation directions EXACTLY. It's a bit confusing, but if you follow it step-by-step, it'll get you there. Also DO NOT use a USB C to C cable or a USB-C port. USB-A 3.0 or slower is a must with this phone. Fastboot mode is VERY picky about which USB protocol and cable you use. Recently found this out with my Surface Pro7 and had to use a regular usb a-c cable going through a 4-port hub to communicate properly and get the correct fastboot driver to install.
so i turn off the phone. plug in to the pc, power on then volume down. i downloaded the drivers from the link, but if i trie to install the drivers(browse in the folder where thr driver is) windows says there are no drivers found for this device.
MoPhoMike said:
What errors are you seeing? No communication in fastboot mode? If so, your driver is not properly installed. Your phone MUST be in fastboot mode when installing the driver. If your phone is booted up, you;ll only be able to install the ADB driver.
Additionally, I should have gone back and edited this post. The issue I was facing "back then" was that I didn't follow the driver installation directions EXACTLY. It's a bit confusing, but if you follow it step-by-step, it'll get you there. Also DO NOT use a USB C to C cable or a USB-C port. USB-A 3.0 or slower is a must with this phone. Fastboot mode is VERY picky about which USB protocol and cable you use. Recently found this out with my Surface Pro7 and had to use a regular usb a-c cable going through a 4-port hub to communicate properly and get the correct fastboot driver to install.
Click to expand...
Click to collapse
so i turn off the phone. plug in to the pc, power on then volume down. i downloaded the drivers from the link, but if i trie to install the drivers(browse in the folder where thr driver is) windows says there are no drivers found for this device.
dokibull said:
so i turn off the phone. plug in to the pc, power on then volume down. i downloaded the drivers from the link, but if i trie to install the drivers(browse in the folder where thr driver is) windows says there are no drivers found for this device.
Click to expand...
Click to collapse
Open "device manager" with the phone in fastboot mode. Scroll down to "other devices" and you should see "Android" or something of that nature. Right click it and select "update driver" follow the steps on PG 3 of the PDF I sent you and follow them exactly. NOTE where it says to click "Have Disk". Most people click "Android Bootloader Interface" then click "NEXT" at the bottom, DON'T do that. You must click "Have Disk" and then follow the prompts that follow.
Also, did you make sure to set your "environment variables" in "windows adv. system settings? This is so windows knows where to find adb.exe and fastboot.exe to execute commands.
MoPhoMike said:
Open "device manager" with the phone in fastboot mode. Scroll down to "other devices" and you should see "Android" or something of that nature. Right click it and select "update driver" follow the steps on PG 3 of the PDF I sent you and follow them exactly. Or hit me up in chat to walk you through it over the phone. Also, did you make sure to set your "environment variables" in "windows adv. system settings? This is so windows knows where to find adb.exe and fastboot.exe to execute commands.
Click to expand...
Click to collapse
e
yes ,im that point where i browse for the drivers, i select the dowlnloaded drivers and windows says there are no drivers for the device
dokibull said:
e
yes ,im that point where i browse for the drivers, i select the dowlnloaded drivers and windows says there are no drivers for the device
Click to expand...
Click to collapse
I'm having the same issue with my Sony Pro-I (just here scrounging the webs for clues in other forums)
Got adb to work but windows refuses to recognise my sony driver folder as a valid driver for the device. Did you get past this point or give up? If you solved the issue, what helped?
Tsuchimursu said:
I'm having the same issue with my Sony Pro-I (just here scrounging the webs for clues in other forums)
Got adb to work but windows refuses to recognise my sony driver folder as a valid driver for the device. Did you get past this point or give up? If you solved the issue, what helped?
Click to expand...
Click to collapse
win7 did the trick
dokibull said:
win7 did the trick
Click to expand...
Click to collapse
welp. I'll try getting the fastboot drivers to work on my win10 for a whoile longer, I only have one PC and installing win7 would be a huge pain jsut for rooting a device... ^^;
thanks for the swift reply anyhow. Will keep that as an option in mind.
Tsuchimursu said:
I'm having the same issue with my Sony Pro-I (just here scrounging the webs for clues in other forums)
Got adb to work but windows refuses to recognise my sony driver folder as a valid driver for the device. Did you get past this point or give up? If you solved the issue, what helped?
Click to expand...
Click to collapse
Okay, simple mistake. Just had to follow the installation instructions more carefully, and not click "next" here, but go to a device list. I think this is where some of us think they know what they're doing and click forward
Tsuchimursu said:
Okay, simple mistake. Just had to follow the installation instructions more carefully, and not click "next" here, but go to a device list. I think this is where some of us think they know what they're doing and click forward View attachment 5708435
Click to expand...
Click to collapse
this didn't work for me
i tried on multiple windows 10 computers and mine just won't recognize, the driver just doesn't work. i tried on linux and i was able to get fastboot devices to recognize phone but when flashing, it just gets stuck on "sending boot", any ideas?

Categories

Resources