Hi guys,
I want to unlock the bootloader to flash a new recovery image and to flash lineageos on my device.
But connection to fastboot will not be established whatever approach I follow.
Stock Android is updated to the last version through update function.
I followed instruction on lineageos.org and on Sony side for my device to unlock bootloader,
I installed XZ2 device driver,
I used several versions of adb and fastboot (old and new versions)#
I tried Windows 7 prof. 32 bit, 64 bit, Windows 10 64 bit Prof.
I tried USB 2 and USB 3.0 ports
Don't know anymore what I should do to get things done.
If my XZ2 is running in normal Android mode, I'm able to access the internal memory via file explorer as well as
adb devices and
adb reboot bootloader is working.
Result: LED is almost not on, maybe one can detect a little bit of blue color and screen ist black.
Then
fastboot devices or
fastboot print-pit
will not give any answer. :-(
Does anyone have a good idea to proceed before I just give up?
Many thanks in advance
Illo
strange.
had the same issues with Windows 10. had to disable Win10 driver signature enforcement to install the correct Fastboot drivers for the Xz2.
So if it doesn't work in Windows 7 either you seem to have a different problem.
A. Try using different cable
B. Install 15sec adb installer
C. Reinstall the driver again after "adb reboot bootloader"
i had the same issue and tried various method. The thing that did for me was A. Weird, since the working cable was a cheap bundle one..
Related
Hi guys, got a slight problem with entering fastboot mode. I hold the volume-up key and connect me USB cable but rather than getting the noise verifying it's been connected ok, I get that dull sound it makes when it hasn't worked. It won't even let me install the drivers and in device manager it comes up as "S1boot Fastboot" for a few seconds before then going into battery charging mode. I downloaded the Android SDK latest and replaced the USB driver INF file with the one sony give you but it didn't work so reversed back to the other driver the SDK manager installs and that didn't work either.
I've been through the tutorials and even tried to update the driver in device manager in the few seconds it stays there but that didn't work either! USB debugging is enabled too!
Please help, I'm not a noob and have done fastboot booting before and yes for those who may ask have already checked to make sure the bootloader can be unlocked and yes it can also the phone is NOT branded and is unlocked to all networks.
Any help will be appreciated, thanks!
Dave.
Are you on Windows 8? Using USB 3.0?
"As your flesh bears the sigil....your name is that....of a recusant."
First be sure you're using a 2.0 usb port, if this is ok maybe it's a windows 8 driver problem, so you should try this http://forum.xda-developers.com/showthread.php?t=2170114. It works for me
For also fastboot and flashmode come for 5 Sec. So Make sure you prepare the file and attach the device to fastboot or flashmode when it is asked.
Still problems
I'm still working on a 2012 laptop with Windows 7 Premium installed. It's fully up to date and all the drivers are installed properly I just don't get it, I've tried everything and it's still making the noise as if it won't connect. I don't know what to do to be honest. Also yes it is USB 2.0.
darkdemon32 said:
I'm still working on a 2012 laptop with Windows 7 Premium installed. It's fully up to date and all the drivers are installed properly I just don't get it, I've tried everything and it's still making the noise as if it won't connect. I don't know what to do to be honest. Also yes it is USB 2.0.
Click to expand...
Click to collapse
Hmm...how many USB ports are being used when you're flashing the phone?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Fastboot with Xperia XP
I have the same problem, can't get it to fastboot mode.
Tried the Windows 8 zith USB 2, and also on XP machine where I was succesfully used it for a Xperia U.
Dump Windows..
Opensource rules!!! I switch on a VM with Windows only when I need Photohshop. Otw, Ubuntu and openSUSE FTW!!
sarkar1990 said:
Dump Windows..
Opensource rules!!! I switch on a VM with Windows only when I need Photohshop. Otw, Ubuntu and openSUSE FTW!!
Click to expand...
Click to collapse
Opensource forever)))
Sent from my ME371MG using xda app-developers app
same problem...
m having same kind of problem i was trying to flash boot img from cm 11 but fast boot isnt recognizing my device any more.my sp is rooted bootloader unlocked.fast boot was recognizing it yesterday.please tell me what to do
What I did was use a Windows XP machine.
Couldn't get it to work on my Windows 7/8, because of the restrictions in driver signatures.
Sent from my C5303 using Tapatalk
fastboot
darkdemon32 said:
Hi guys, got a slight problem with entering fastboot mode. I hold the volume-up key and connect me USB cable but rather than getting the noise verifying it's been connected ok, I get that dull sound it makes when it hasn't worked. It won't even let me install the drivers and in device manager it comes up as "S1boot Fastboot" for a few seconds before then going into battery charging mode. .
Click to expand...
Click to collapse
I have a similar problem. the power light lights up blue then passes into the phone starts loading mode
Sorry for bad English
The updated version (09.14) don't work properly. It doesn't enable me to go to Flashmode. Uninstalled and used the previous version and it worked as it should, no issues entering Flashmode.
i might have actually found the solution. im on the 4.3fw build version 12.1.a.1.201... in my case, my pc will automatically install the drivers for mass storage giving me no chance to update the driver to the one from sony.
you need to do step 9. and 10. if you havent done so from http://unlockbootloader.sonymobile.com/instructions
what i did was allow developer settings and allow debugging via usb.
plug in and attempt to go in to fastboot and obviously it'll fail.
go to device manager. (control panel->hardware and sound->device manager) quickly scroll down go to other devices. you will see s1fastboot (or something like that) if you're quick enough, if not, in my case, the phone will go in to charging mode.
what i did was to disable xperia sp mass storage from disk drives category too.
right click on it and select update driver software and you will select the file you've unzipped (following step 9 and 10 sony's instructions).
after it has finished updating, unplug your usb and attempt to enter fastboot, it should work.
PS: im no expert, this solution might be out there somewhere already or it could just be a great coincidence. some of these steps might not be useful even.
Had this problem and found a funny solution: I switched my cable and the port I was using. Both Ubuntu and Windoze 7 failed on both fastboot and flash mode, even though in both the phone would charge. I grabbed a spare micro USB cable and plugged it into the front of the PC; voila. Now the phone is rooted and running the latest CM.
Need a final solution for this problem
I don't know what to do!!! The problem is this, very similar to the others mentioned above,: When i conect my xperia sp to fastboot mode, pressing volume up while plugging in usb cable, the phone led turns to blue for few seconds and than it just turns to red showing on the screen the battery image( normal charging mode)...... I' m using windows xp and a rooted xperia sp whit cm11 (for locked bootloader obviously). Just two last things:
the phone can be unlocked( I checked it) and fastboot worked the same as now with stock xperia sp firmware.
Please i need a final and a certain solution for this problem!!!
i'll be very thankful to anyone who give me a hand!!!!
TheTras said:
I don't know what to do!!! The problem is this, very similar to the others mentioned above,: When i conect my xperia sp to fastboot mode, pressing volume up while plugging in usb cable, the phone led turns to blue for few seconds and than it just turns to red showing on the screen the battery image( normal charging mode)...... I' m using windows xp and a rooted xperia sp whit cm11 (for locked bootloader obviously). Just two last things:
the phone can be unlocked( I checked it) and fastboot worked the same as now with stock xperia sp firmware.
Please i need a final and a certain solution for this problem!!!
i'll be very thankful to anyone who give me a hand!!!!
Click to expand...
Click to collapse
Are you trying to unlock your phone?
Have you installed device specific/fastboot/flashmode drivers via FlashTool? If you are on Windows 8/8.1, you need to disable driver verification to get it done.
Alternatively if you just wanna unlock your bootloader, you can use the BLU option in FlashTool. Again all drivers will need to be properly installed for your phone to be detected correctly.
You say you had the same problem with stock firmware which means you probably haven't setup adb/fastboot properly on your PC. Does your phone get detected correctly in Device Manager? Have you tried installing drivers via Device Manager?
....
So the solution is installing flashtool and installato drivers via Emma?? Thanks forma the attention!!
TheTras said:
So the solution is installing flashtool and installato drivers via Emma?? Thanks forma the attention!!
Click to expand...
Click to collapse
I meant install drivers via FlashTool. Go to C:\Flashtool\drivers or wherever you have installed Flashtool and run the Flashtool-drivers.exe.
Select flashmode drivers, fastboot drivers and common drivers viskan board (SP drivers) and install them. Like I said if you are on Win 8/8.1, you will have to disable driver signature enforcement. Just look it up in YouTube and follow a tutorial.
Hey guys!
In advance I'm sorry for asking something that has probably been asked many times before, but I'm unable to find the right answer.
Okay let's start at the beginning. My HTC one with an unlocked bootloader on stock started to display a very irritating bug in that sometimes the screen would not rotate and was stuck in landscape mode. Nothing would help nor rebooting, nor calibrating the sensor. Only booting into the bootloader would somehow help.
Until it did not.
I tried a factory reset, which did not help and then tried just wiping Dalvik and Cache, which did not help too.
Then I tried wiping Data and System, which I now know was very stupid.
The current problem is that I can't figure out how to send a new ROM to my HTC one using adb, when typing adb devices the device does not show up.
My computer does see the device, listed under Android USB devices ad My HTC. I think Fastboot too, recognized the device, because I am able to get the Identifier token.
I have installed the drivers and installed HTC Sync manager. I have restarted my Pc multiple times and changed the USB port the device is connected to.
I too, tried mounting the USB, but either I'm doing it wrong, or it does not work.
Hope one of you can help me! I've been at this all day long...
Adb commands only work when you're booted in the rom or recovery. Fastboot uses fastboot commands. Do you have a custom recovery? If so, you can adb sideload a rom. If not, you can fastboot flash a custom recovery assuming your bootloader is unlocked. You may have mentioned it in your post I just can't remember. Good luck!
Sent from my HTC One using xda app-developers app
Thanks for the help!
Yes, I unlocked my bootloader and have twrp installed.
I think I have narrowed down the problem: that my device is not recognized by the computer in twrp.
When in fastboot, My computer does recognize the device, listed as an HTC one, so the drivers are not the problem.
When booting into recovery, me computer only recognizes the phone for about 3 seconds, when it dissapears.
I have been able to see the device in Adb (using Adb devices).
What could I do? Adb sideload does not work because the computer does not recognize the device.
Hi,
You're on Windows? If yes which version?
Windows 7, but if needed I do have access to a win 8 PC as well.
All x64 by the way.
Ok, maybe take a look here if you use USB 3.0?: [FIX]Fastboot problems on Windows 8 x64 with USB 3.0? Solution inside.
It might work on Windows 7 too, there is a link for the drivers for x64.
Maybe using a toolkit to use ADB/fastboot? Take a look here:
[TOOL]HTC One (M7) All-In-One Toolkit V3.1
[TOOL]HTC One (M7) AIO Toolkit | v1.4
Okay, from now on I'll only use USB 2.0.
I tried these two toolkits, but they suffer the same problem as me in that in order for adb sideload to work the device has to be recognized for longer than 3s after booting into recovery.
I just bought a female-female USB adapter, hopefully installing a rom from a usb stick will work
Ofcourse help would still be greatly appreciated as i will have to wait for over a week till the USB adapter arrives.
this is my frist time doing this. I follow step by step guide. I even look for solution online and still dont work. I dont know whats wrong. I want to unlock bootloader to install LOS 17.1.
im using windows 10. device not detected in fastboot.
I SURRENDER. I need help. T_T
thank you !
HELP...i tried installing flashtool driver and adb 1.4.3 still dont work
do you think I need original sony cable to be recognized?
ADB / FastBoot drivers are not all you need to access your phone via USB: you must also have the OEM specific "Android USB Driver" installed on your computer.
More here: https://www.getdroidtips.com/download-latest-sony-usb-drivers/
You mean OEM driver is, my device driver (viskan,Xperia sp driver)in picture 2.everytime I manually installed it (device can't start code error 10.)
pictures 3 and 4 show that I successfully installed the oem Sao sony adb driver and still device is not detected in fastboot mode?
I even tried it on windows 7 ultimate same problem.maybe I'm missing something?
Hi
I'm trying to flash TWRP on my CHe2-L11 via adb but it gets stuck at < Waiting for any device >.
I read somewhere that is because Windows lacks the necesary drivers (although Che2-L11 is listed as "MTP" in the devices connected to my computer).
Where can I find the necessary drivers for Win10?
Thanks a lot
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess? Windows can not automatically find drivers for this...
Then it make sense that I cannot flash the custom recovery until the phone is detected again.
What should I do to have my phone detected in Windows while it is in bootloader mode?
Thanks a lot
-a-
Running windows update found a driver for
Google Android Bootloader Interface
However, ADB still cannot detect it
EDIT: Actually it works! Even though
adb devices
would not list anything when the phone was in bootloader mode, I was able to flash twrp
Problem solved!
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers
Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who needs it
The first problem is OnePlus 6T not showing in MSM Tool and showing in device manager as QUSB_BULK_CID:xxxx_SN:xxxxxxxx
The solution I found here https://forum.xda-developers.com/t/guide-unlock-verizon-oneplus-8-5g-uw-in2019-bootloader.4409377/
is this :
Enter EDL mode with adb reboot edl or by powering the phone off and holding both volume up and down while connecting it to a PC
Next Open device manager and if you see "QUSB_BULK_CID:xxxx_SN:xxxxxxxx"
try to update the driver, it will not find one but choose the option to search Windows Update
It should open your settings to the Windows update page
You can open this manually and you should see the option to View Optional Updates
select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager
After this I thought I had solved my problems but then the OP6T was not showing in fastboot
I eventually found my solution here https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/
The issue is because of OnePlus having unsigned drivers and windows refusing to use them unless you disable driver signature enforcement
I recommend following the linked guide for this problem as the solution is identical for the 6T as well as the 8T, I couldn't write it any better and I wouldn't want to just copy their guide
But it essentially is as simple as disable driver signature enforcement and install the correct drivers with device manager so your device will show in fastboot
FireRattus said:
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers
Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who needs it
The first problem is OnePlus 6T not showing in MSM Tool and showing in device manager as QUSB_BULK_CID:xxxx_SN:xxxxxxxx
The solution I found here https://forum.xda-developers.com/t/guide-unlock-verizon-oneplus-8-5g-uw-in2019-bootloader.4409377/
is this :
Enter EDL mode with adb reboot edl or by powering the phone off and holding both volume up and down while connecting it to a PC
Next Open device manager and if you see "QUSB_BULK_CID:xxxx_SN:xxxxxxxx"
try to update the driver, it will not find one but choose the option to search Windows Update
It should open your settings to the Windows update page
You can open this manually and you should see the option to View Optional Updates
select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager
After this I thought I had solved my problems but then the OP6T was not showing in fastboot
I eventually found my solution here https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/
The issue is because of OnePlus having unsigned drivers and windows refusing to use them unless you disable driver signature enforcement
I recommend following the linked guide for this problem as the solution is identical for the 6T as well as the 8T, I couldn't write it any better and I wouldn't want to just copy their guide
But it essentially is as simple as disable driver signature enforcement and install the correct drivers with device manager so your device will show in fastboot
Click to expand...
Click to collapse
Per chance, would you know if this would also apply to the OnePlus One on Linux? I recently tried to gain root access but no matter what I did, I could not get the device to show up in fastboot or as an ADB device, for that matter. I tried both USB 2.0 ports and 3.0 ports, to no avail. It's obviously not my daily driver (based on release dates, etc.) so it's not a big deal but at the same time, I don't want to root my daily driver as it has enough trouble on stock OS as it is (Google Pixel 6 Pro). I don't need to go rooting it and introducing a whole new world of hurt, thus, the desire to root my recently resuscitated OnePlus One (I got it stuck in a boot loop one or maybe even two years ago but it wasn't my daily driver then, either and just kind of a tinker device, one of a couple at that. So rather than put in the minimal amount of effort to fix it, I just tossed in a drawer until a future need demanded that I give it the time and attention necessary, which happened to occur the other night. All went super smoothly until I hit this particular roadblock alluded to above while trying to gain root using Bacon Root Toolkit. Admittedly, I haven't tried going the old-fashioned route of gaining root but mostly because I couldn't get my computer to recognize that the device was connected to it, so that was no more an option than was going the easy route with BRT.)
Edited to mention that I successfully got it out of the boot loop by flashing cm12 and that booted up no problem. I also have TWRP installed, which actually may need updating as it was the version originally installed however many years ago prior to getting it stuck in the boot loop and subsequently getting the junk drawer treatment for 1-2 years but to my knowledge that would not cause the device to not be recognized as a fastboot/ADB device...
QneEyedJack said:
Per chance, would you know if this would also apply to the OnePlus One on Linux? I recently tried to gain root access but no matter what I did, I could not get the device to show up in fastboot or as an ADB device, for that matter. I tried both USB 2.0 ports and 3.0 ports, to no avail.
Click to expand...
Click to collapse
I am not exactly sure about this but I recommend you try what is suggested here if you haven't https://technastic.com/oneplus-usb-drivers-windows-mac-linux/
sudo apt-get install android-tools-adb android-tools-fastboot
QneEyedJack said:
Edited to mention that I successfully got it out of the boot loop by flashing cm12 and that booted up no problem. I also have TWRP installed, which actually may need updating as it was the version originally installed however many years ago prior to getting it stuck in the boot loop and subsequently getting the junk drawer treatment for 1-2 years but to my knowledge that would not cause the device to not be recognized as a fastboot/ADB device...
Click to expand...
Click to collapse
to my knowledge the recovery you have installed should not effect your device being recognized in fastboot mode
You should probably update your recovery to the latest official twrp imo