Related
Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)
AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app
Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?
Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment
I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)
The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?
Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"
it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?
I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!
AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.
It's been over a week I am struggling with this bullsh*t. Don't mean to be rude, just I am nervous, because I read countless of guides and Q&A's; but I couldn't make this work.
I am just and only trying to install a basic kernel/Rom, but no luck for about 1 week.
Sony Xperia X10.
I am using Flashtool .0.9.11, installed drivers selecting "Flashmode driver, Fastboot driver, Xperia X10 driver". Installation fine, on the device management, it's seen as "SEMC Flash Device". Flashtool recognizes the phone as ADB.
I flash the FTF kernel by placing it into firmware folder and running Flashmode in Flashtool. It says flashing was successful, but it still boots with the old kernel. And in the kernel selection list, it doesn't show the new kernel I flashed.
I try fastboot mode, but the hell it never accepts that the device has fastboot mode. I plug the phone closed pressing the back key while plugging; I try to update the SEMC Flash Device with the "fastboot driver" that Sony supplies, but it says its not a valid driver. Though I had already installed the fastboot driver from Flashtool/Drivers folder; but it insists on saying fastboot is not available.
Hell what now?
Btw I tried Doomlard's modified Recovery which has the option "boot into fastboot mode"; I thought this time it's gonne be, but it just cut the power off; did not start back.
pisisler said:
It's been over a week I am struggling with this bullsh*t. Don't mean to be rude, just I am nervous, because I read countless of guides and Q&A's; but I couldn't make this work.
I am just and only trying to install a basic kernel/Rom, but no luck for about 1 week.
Sony Xperia X10.
I am using Flashtool .0.9.11, installed drivers selecting "Flashmode driver, Fastboot driver, Xperia X10 driver". Installation fine, on the device management, it's seen as "SEMC Flash Device". Flashtool recognizes the phone as ADB.
I flash the FTF kernel by placing it into firmware folder and running Flashmode in Flashtool. It says flashing was successful, but it still boots with the old kernel. And in the kernel selection list, it doesn't show the new kernel I flashed.
I try fastboot mode, but the hell it never accepts that the device has fastboot mode. I plug the phone closed pressing the back key while plugging; I try to update the SEMC Flash Device with the "fastboot driver" that Sony supplies, but it says its not a valid driver. Though I had already installed the fastboot driver from Flashtool/Drivers folder; but it insists on saying fastboot is not available.
Hell what now?
Click to expand...
Click to collapse
Upgraded to Windows 8 and didn't install the flash tool drivers for it?
say no to Drugs and ICS!
What is your phone actually?
Sent from my MT11i using xda app-developers app
I just realised by your question that I've posted in a wrong forum. The phone is Xperia X10i. I think it's not so much important anymore.
Hello there
My name is Kareem and I'm using a Sony Xperia U 4.0.4 and build number 6.1.1.B.1.10.
So the thing is that I want to update my phone to 4.4 Kitkat and I'm following this thread.
I rooted my device, and I'm now trying to unlock bootloader. My devices says that I'm able to bootload but I still need to unlock it. So I googled around and came across this video which shows me how to unlock bootloader. First I had problems with installing the drivers because I am using windows 8.1 64-bit, but after I disabled “Driver Signature Enforcement” I managed to install the drivers.
And here the problem starts... I have to press the up volume button while plugging in so I can start fastboot. As what I was told, I did and the blue led on the left side turned on. But when I look on my desktop I get a notification that my usb device is not recognized.
Can anyone tell what causes this issue? Otherwise, is there another and maybe an easier way to unlock bootloader?
Kind regards
Kareem
P.s. I'm using that flashtool software to unlock bootloader. It's called "Sony Mobile Flasher by Androxyde".
I prefer to use this.
Is the official method for unlocking the bootloader, includes the drivers and stuff, just follow that tutorial and you're good to go.
Also you have to make sure that your phone can have unlocked bootloader first, if not, then, you have to stick to locked bootloader ROM's.
Now, sorry for saying like this but Windows 8.1 is such a pain in the a**, it always gives error because the drivers isn't signed, if you get problems with that again use this.
USB not recognized, well the solutions for that problem can be:
Use other USB port, if still doesn't work on any of the ports, then can be the slots or bad placement of pins in the motherboard, almost never is a problem of internal dust in the computer but you can try these.
Try other USB cable, may be the cable is failing, try other from another Android phone to complete the process.
Try using other computer with WIndows 7 or Ubuntu.
If you were not able to get working, then tell me.
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with
browse from disk and select "android_winusb.inf" from "...\android-sdk\extras\google\usb_driver" and select "android bootloader interface.
Click to expand...
Click to collapse
There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Kareem_XperiaU said:
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Click to expand...
Click to collapse
Windows key + R, write devmgmt.msc, enter.
Plug your phone and look if some device is recognized in the list, it may appear as Android or something like that, if you got it, then follow me.
Right click to it, Update driver, select from computer, use a list from the PC, and "Use disk", see if there's something that says like that because I got Windows 7 in spanish so it's different.
In that browse for the folder that has the .inf file and open it, it returns a list that you have to select the interface, next and your driver may be installed.
Understand? I can explain more but I have Windows in spanish so I don't know how is in english.
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Kareem_XperiaU said:
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Click to expand...
Click to collapse
Tried to unlock the bootloader with the Sony method?
manudo said:
Tried to unlock the bootloader with the Sony method?
Click to expand...
Click to collapse
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
Sony website said:
9. Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. 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.
10. Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager.
11. Turn off your device.
12. On your device, push and hold the Fastboot button at the same time as you connect the device to the computer with a USB-cable. The Fastboot button may differ between different device models. See the Fastboot buttons page for more information on what button use on your device.
13. On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
14. Open a command window and go to the tools folder within the Android SDK folder.
15. 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.
Click to expand...
Click to collapse
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Kareem_XperiaU said:
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Click to expand...
Click to collapse
13. If your phone is recognized in fastboot mode then continue, if not, update the driver.
14. Know the command "cd"? Is for accesing directories, you can use "dir" to see whats in the folder. Example, you downloaded the Android SDK bundle in the Desktop, then "cd" to the "tools" directory, that contains the binary to unlock the bootloader. That's in cmd.
Like:
Code:
cd /SDK/adt-bundle-blah-blah/sdk/tools
And, you're using Windows 8, again, your device is recognized in fastboot mode?
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Kareem_XperiaU said:
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Click to expand...
Click to collapse
Right, if anything goes wrong, feel free to ask!
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Kareem_XperiaU said:
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Click to expand...
Click to collapse
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
manudo said:
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And how can I do that to be honest?
Kareem_XperiaU said:
And how can I do that to be honest?
Click to expand...
Click to collapse
In this post, there are a list with all stock and custom ROM's available in XDA forum, you should download stock and if anything goes wrong then flash the stock ROM with flashtool. You know, flashmode, select kernel, connect to green led, let it boot, and you have stock.
By now, try to unlock the bootloader, if you need help with the flashing then you can ask by here or create another thread.
Has anyone managed to get ABD sideload working from stock recovery?
I'm trying to sideload the latest OTA.
I have ADB up and running fine when the N9 is fully booted, but when I drop into recovery and select the option to sideload via ADB, I get the Windows "chime" for a new device, and unknown device (Volantis) appears in the device manager, for which I can find no driver.
No driver means no ADB and thus no sideload.
Thanks,
Hi, replace the original android_winusb.inf file with this modified one in your google usb drivers folder. Right click on it and select install.
Modified it for myself right now, because I had exactly the same problem like you.
Please let me know if it was successful...
daniii88 said:
Hi, replace the original android_winusb.inf file with this modified one in your google usb drivers folder. Right click on it and select install.
Modified it for myself right now, because I had exactly the same problem like you.
Please let me know if it was successful...
Click to expand...
Click to collapse
Thanks for trying but it doesn't work for me, when I try to install I get an error dialog :-
"The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tampered with"
I'm also getting this problem. Any solution?
I have same problem... waiting for solution....
bobjbain said:
Thanks for trying but it doesn't work for me, when I try to install I get an error dialog :-
"The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tampered with"
Click to expand...
Click to collapse
I had the same issue and have now successfully been able to sideload (Windows 8.1).
The original issue seems to be that the latest google driver I downloaded did not have the correct device id in the android_winusb.inf for the nexus 9 when in recovery mode (though the driver did work for issuing adb commands to unlock the bootloader; I guess the hardware id is different when connected in adb recovery mode?). The file daniii88 provided presumably fixes this in the same way I did, by adding the device id reported under device manager to the generic nexus devices listed in the android_winusb.inf file as follows:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
I did this under both the 32 and 64 bit headers just in case. I made an account just to post this solution, so I can't post links, but searching for "nexus 7 adb recovery driver" shows the same thing happened with the nexus 7 at one point.
Now, with the modified version of the android_winusb.inf file windows won't let the driver install because the driver signature does not match since it's been altered. The trick to forcing windows to use the driver anyways is to reboot windows in "disable driver signature verification" mode. Search for "how to disable driver signature verification on 64 bit windows 8.1 so that you can install unsigned drivers". Once rebooted, reinstall the altered driver under device manager (I did this while the device was in recovery mode waiting for adb sideload). Windows will warn you along the lines of the driver has been tampered with, but will allow you to use it. The driver should successfully install and the device should appear under "adb devices" from the command line. Furthermore, sideload should now work.
Hopefully this helps anyone else encountering this.
ManBearBull said:
I had the same issue and have now successfully been able to sideload (Windows 8.1).
The original issue seems to be that the latest google driver I downloaded did not have the correct device id in the android_winusb.inf for the nexus 9 when in recovery mode (though the driver did work for issuing adb commands to unlock the bootloader; I guess the hardware id is different when connected in adb recovery mode?). The file daniii88 provided presumably fixes this in the same way I did, by adding the device id reported under device manager to the generic nexus devices listed in the android_winusb.inf file as follows:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
I did this under both the 32 and 64 bit headers just in case. I made an account just to post this solution, so I can't post links, but searching for "nexus 7 adb recovery driver" shows the same thing happened with the nexus 7 at one point.
Now, with the modified version of the android_winusb.inf file windows won't let the driver install because the driver signature does not match since it's been altered. The trick to forcing windows to use the driver anyways is to reboot windows in "disable driver signature verification" mode. Search for "how to disable driver signature verification on 64 bit windows 8.1 so that you can install unsigned drivers". Once rebooted, reinstall the altered driver under device manager (I did this while the device was in recovery mode waiting for adb sideload). Windows will warn you along the lines of the driver has been tampered with, but will allow you to use it. The driver should successfully install and the device should appear under "adb devices" from the command line. Furthermore, sideload should now work.
Hopefully this helps anyone else encountering this.
Click to expand...
Click to collapse
After you did this. You were able to side load the OTA even with the non upgraded recovery?
Sent from my Nexus 7
109
ram130 said:
After you did this. You were able to side load the OTA even with the non upgraded recovery?
Click to expand...
Click to collapse
Sorry, should have said I was already on the upgraded (LRX21Q) recovery before going through these steps. The unaltered driver i initially used worked to communicate with the nexus 9 when booted or at the bootloader screen, but not when I was in recovery. Therefore i was able to unlock my bootloader and update the recovery with unaltered drivers, but had to change the driver to get adb to work when in recovery.
ManBearBull said:
I had the same issue and have now successfully been able to sideload (Windows 8.1).
The original issue seems to be that the latest google driver I downloaded did not have the correct device id in the android_winusb.inf for the nexus 9 when in recovery mode (though the driver did work for issuing adb commands to unlock the bootloader; I guess the hardware id is different when connected in adb recovery mode?). The file daniii88 provided presumably fixes this in the same way I did, by adding the device id reported under device manager to the generic nexus devices listed in the android_winusb.inf file as follows:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
I did this under both the 32 and 64 bit headers just in case. I made an account just to post this solution, so I can't post links, but searching for "nexus 7 adb recovery driver" shows the same thing happened with the nexus 7 at one point.
Now, with the modified version of the android_winusb.inf file windows won't let the driver install because the driver signature does not match since it's been altered. The trick to forcing windows to use the driver anyways is to reboot windows in "disable driver signature verification" mode. Search for "how to disable driver signature verification on 64 bit windows 8.1 so that you can install unsigned drivers". Once rebooted, reinstall the altered driver under device manager (I did this while the device was in recovery mode waiting for adb sideload). Windows will warn you along the lines of the driver has been tampered with, but will allow you to use it. The driver should successfully install and the device should appear under "adb devices" from the command line. Furthermore, sideload should now work.
Hopefully this helps anyone else encountering this.
Click to expand...
Click to collapse
So, the original attachment works properly, it was unsigned driver verification that was stopping it being installed, should have realised that from the start, thanks for pointing me in the right direction.
ram130 said:
After you did this. You were able to side load the OTA even with the non upgraded recovery?
Sent from my Nexus 7
Click to expand...
Click to collapse
No, it was telling me my old version isn't what it was expecting. I must be suffering from the recovery not being updated properly "bug".
My build.prop definitely has the right release keys in it.
Once question for those that know, in the update package there is a metadata file which contains :-
Code:
post-build=google/volantis/flounder:5.0/LRX21Q/1573789:user/release-keys
post-timestamp=1415397802
pre-build=google/volantis/flounder:5.0/LRX21L/1546449:user/release-keys
pre-device=flounder
Can we just not change the pre-build to that that is in the error message? (flounder:L/LFW73W/1491895:user/release-keys)??
So I replaced the android_winusb with the file provided and rebooted without driver verification mode. But it is still not working.
Under device manager it still shows the exclamation mark on Volantis. Did I miss a step?
ForcedZucchini said:
So I replaced the android_winusb with the file provided and rebooted without driver verification mode. But it is still not working.
Under device manager it still shows the exclamation mark on Volantis. Did I miss a step?
Click to expand...
Click to collapse
Maybe you have another Device ID... try to follow this procedure http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
This is Googles fault:
You remember the very first update you received during setup?
Yeah, and Google made a mistake with this update: They updated the system, but not the recovery, which means, there is now a version conflict between the recovery and the system, which prevents OTAs from installing.
You can't do anything about it until Google fixes this with another Update, except flashing the new recovery from the image.
ForcedZucchini said:
So I replaced the android_winusb with the file provided and rebooted without driver verification mode. But it is still not working.
Under device manager it still shows the exclamation mark on Volantis. Did I miss a step?
Click to expand...
Click to collapse
Have you tried updating the driver in device manager?
ForcedZucchini said:
So I replaced the android_winusb with the file provided and rebooted without driver verification mode. But it is still not working.
Under device manager it still shows the exclamation mark on Volantis. Did I miss a step?
Click to expand...
Click to collapse
After replacing the android_winusb file and rebooting the PC without driver verification mode, did you go back into Device Manager and update the driver using the modified driver version for ADB? I manually entered the device ID info into the winusb file instead of using the provided file, so I'm not entirely sure that the process is the same, but it seems like it should work.
1. Replace the android_winusb file with the attached version. If that doesn't work, open the file in notepad and manually enter the device id IAW ManBearBull's post;
2. Reboot without driver verification mode; and
3. Go into device manager and update the ADB driver with the modified driver file.
Finally worked, running "R" firmware now. There is not even een factory image available, just this OTA upgrade R-from-Q.
Cannot imagine why the device in recoverymode is not recognised ( unknown device Volantis ) and we need to play "dirty" to install the driver.
Seems so "immature" from Google.
Different Hardware ID?
So I replaced the android_winusb and it's still not letting me see the device in adb in fastboot. I can see it when it boots up normally. However, I am seeing that when I boot into fastboot, it gives me a hardware id of USB\VID_18D1&PID_4EE0 and not USB\VID_18D1&PID_D001 that was said in previous posts. Right now in Device Manager it's seeing the tablet as an "Android Bootloader Interface" instead of the CompositeAdbInterface I want. Should I change the inf file to put that hardware id as a CompositeAdbInterface instead of a SingleBootLoaderInterface like it currently is?
lotrfan18 said:
So I replaced the android_winusb and it's still not letting me see the device in adb in fastboot. I can see it when it boots up normally. However, I am seeing that when I boot into fastboot, it gives me a hardware id of USB\VID_18D1&PID_4EE0 and not USB\VID_18D1&PID_D001 that was said in previous posts. Right now in Device Manager it's seeing the tablet as an "Android Bootloader Interface" instead of the CompositeAdbInterface I want. Should I change the inf file to put that hardware id as a CompositeAdbInterface instead of a SingleBootLoaderInterface like it currently is?
Click to expand...
Click to collapse
That's because you're in bootloader not recovery, when you go into recovery and then do the "adb sideload" option that is when you get the D001 device ID.
I was able to resolve my problem, thanks for everyone's help.
I simply went into device manager>update driver software>browse my computer for driver software>let me pick>select "ADB Android Device"
After this I downloaded Minimal ADB and Fastboot from here http://forum.xda-developers.com/showthread.php?t=2317790 and it was able to work successfully.
Hi,
i have a problem with ADB drivers for the phone. i have downloaded it from Sony (Link:https://developer.sonymobile.com/downloads/drivers/xperia-x-driver/) and install it like they said (by going in to device manager and manually installing it). after booting it to Fastboot, Flashtool says i have to install them from the drivers folder, which however, does not contain the Xperia X driver. Also, when selecting the Flashboot and Flashmode drivers, one installs but the other doesn't which is "Google, Inc, (WinUSB) Android UsbDeviceClass".
While in Fastboot, i tired to delete it, then update it using the download driver from Sony which failed to install. Also, in device manager it say something like S1 fastboot driver with a Waring symbol (it's not recognised), and upon checking in flashtool while in Fastboot, it says there is no ADB drivers installed, just Fastboot.
i have tried booting the phone with USB debugging and it does recognise it, but still doesn't work when booting to Fastboot.
BTW i am on Windows 10
any information would be useful.
Force install adb driver over device manager
max26292 said:
Force install adb driver over device manager
Click to expand...
Click to collapse
thanks, just to confirm, by force install do you mean to download from sony and install within device manager, by 'adding legacy software' ?
if so, i have done that and the driver appears, and shows the following error:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Also, still and unrecognised 'S1 fastboot ' driver appeared when in Fastboot.
thank you again.
remar786 said:
thanks, just to confirm, by force install do you mean to download from sony and install within device manager, by 'adding legacy software' ?
if so, i have done that and the driver appears, and shows the following error:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Also, still and unrecognised 'S1 fastboot ' driver appeared when in Fastboot.
thank you again.
Click to expand...
Click to collapse
If you install Jdk you already have driver, you just right click choose update driver> choice option 2 ( I choose driver from my computer > choose from list device > android > adb. Next, it will show a alert message bla bla > yes :3 use flash tools again to see the magic
max26292 said:
If you install Jdk you already have driver, you just right click choose update driver> choice option 2 ( I choose driver from my computer > choose from list device > android > adb. Next, it will show a alert message bla bla > yes :3 use flash tools again to see the magic
Click to expand...
Click to collapse
quick question, what is JDK?
hopefully i will try when i hear back, thanks again .
How to install ADB Xperia x
finally!!!
it's worked. Thanks for your help max26292 (although would have been nice to hear back but a huge thank you!)!
Here's what i did (not in the exact order though)
i used the instruction from Sony - http://support.sonymobile.com/global-en/xperiae3dual/kb/0231018805656b91c0145c620eeaf004cb9/(Not for the Xperia X though but usable) on how to install the Xperia driver, and after restarting the PC, Flashtool still didn't recognise while in Fastboot. Also, in device manage there, was a Waring sign next to it, and gave the error as mentioned previously. image is below of the sign.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then installed the 15 seconds ADB from https://forum.xda-developers.com/showthread.php?t=2588979 ( i keptpressing Y) after a reboot and putting the phone in Fastboot, still Flashtool had the same messages about drivers, like i said in the first post.
i then tired out max26292's method, which there are images below to show the process. i put the phone in Fastboot, and where the warning sign was, NOT THE SAME PLACE AS THE IMAGE SHOWN ABOVE, rather where it said "S1Boot Fastboot" . using the steps you mentioned (THANKS ALOT BTW!) :
i right clicked on the s1 fastboot> clicked update driver> chose the second option - browse my computer>
the clicked on "let me pick from a list of device drivers on my computer"> then browsed for the driver i'd already installed from Sony - the "Sony sa0114> kept clicking next, and yes to a warning message> restarted computer and BANG! it worked!
i however should mention that i did try to install the flashmode and fastboot driver from flashtool, but one of them failed to install - i have mentioned n my previous post, please refer back. so, you may want to do that, but i think the 15 seconds ADB will do it for you. also, i have not done commands so i can't test it out fully, bu when i do, i will let you know.
again i would like to thank everyone for your help, really appreciate it!
P.S. Please put a F U C K ING updated guide up Sony, T W A T s.
remar786 said:
finally!!!
it's worked. Thanks for your help max26292 (although would have been nice to hear back but a huge thank you!)!
Here's what i did (not in the exact order though)
i used the instruction from Sony - http://support.sonymobile.com/global-en/xperiae3dual/kb/0231018805656b91c0145c620eeaf004cb9/(Not for the Xperia X though but usable) on how to install the Xperia driver, and after restarting the PC, Flashtool still didn't recognise while in Fastboot. Also, in device manage there, was a Waring sign next to it, and gave the error as mentioned previously. image is below of the sign.
I then installed the 15 seconds ADB from https://forum.xda-developers.com/showthread.php?t=2588979 ( i keptpressing Y) after a reboot and putting the phone in Fastboot, still Flashtool had the same messages about drivers, like i said in the first post.
i then tired out max26292's method, which there are images below to show the process. i put the phone in Fastboot, and where the warning sign was, NOT THE SAME PLACE AS THE IMAGE SHOWN ABOVE, rather where it said "S1Boot Fastboot" . using the steps you mentioned (THANKS ALOT BTW!) :
i right clicked on the s1 fastboot> clicked update driver> chose the second option - browse my computer>
the clicked on "let me pick from a list of device drivers on my computer"> then browsed for the driver i'd already installed from Sony - the "Sony sa0114> kept clicking next, and yes to a warning message> restarted computer and BANG! it worked!
i however should mention that i did try to install the flashmode and fastboot driver from flashtool, but one of them failed to install - i have mentioned n my previous post, please refer back. so, you may want to do that, but i think the 15 seconds ADB will do it for you. also, i have not done commands so i can't test it out fully, bu when i do, i will let you know.
again i would like to thank everyone for your help, really appreciate it!
P.S. Please put a F U C K ING updated guide up Sony, T W A T s.
Click to expand...
Click to collapse
Please read carefully =-= I told Android driver not sony =-=
max26292 said:
Please read carefully =-= I told Android driver not sony =-=
Click to expand...
Click to collapse
thank you, but i don't have them. i only have the Sony ones and ADB by Samsung, which the 15 seconds ADB program installed.
when i connected to Fastboot, Flashtool does recognise it, so it should work right?
thanks again
pm me on facebook when you onl I think we should do a private mess and teamview
max26292 said:
pm me on facebook when you onl I think we should do a private mess and teamview
Click to expand...
Click to collapse
Thank you but it's working fine with the way I installed it (by installing the Sony driver from the list)
remar786 said:
Thank you but it's working fine with the way I installed it (by installing the Sony driver from the list)
Click to expand...
Click to collapse
you also use driver pack in flashtool because it include android driver
max26292 said:
you also use driver pack in flashtool because it include android driver
Click to expand...
Click to collapse
yes i did use it, but only one installed. i did before i installed both drives, (Fastboot and ADB) but one installed and one didn't ( i think the ADB driver failed and the other one installed).
remar786 said:
Hi,
i have a problem with ADB drivers for the phone. i have downloaded it from Sony (Link:https://developer.sonymobile.com/downloads/drivers/xperia-x-driver/) and install it like they said (by going in to device manager and manually installing it). after booting it to Fastboot, Flashtool says i have to install them from the drivers folder, which however, does not contain the Xperia X driver. Also, when selecting the Flashboot and Flashmode drivers, one installs but the other doesn't which is "Google, Inc, (WinUSB) Android UsbDeviceClass".
While in Fastboot, i tired to delete it, then update it using the download driver from Sony which failed to install. Also, in device manager it say something like S1 fastboot driver with a Waring symbol (it's not recognised), and upon checking in flashtool while in Fastboot, it says there is no ADB drivers installed, just Fastboot.
i have tried booting the phone with USB debugging and it does recognise it, but still doesn't work when booting to Fastboot.
BTW i am on Windows 10
any information would be useful.
Click to expand...
Click to collapse
1. install XPERIA COMPANION
2. INSTALL FLASHTOOL (www.flashtool.net)
3. after installing flastool goto C:\Flashtool\drivers and you will find "Flashtool-drivers.exe" / run it and install from list "common fastboot drivers", "common flashmod drivers" and xperia z series with Xperia X series motherboard drivers.
windows 10 gives digital signature verification errors so you have to
Use the following steps to disable driver signature enforcement.
Click the Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
Click to expand...
Click to collapse
then repeat point "3"
you should be ok
frp locked huawei honor 20 wont connect to laptop
hi mate im trying to connect my huawei honor 20 to my laptop but it doesnt even come up with anything in device manager. its frp locked and i need to access fastboot mode to enter the frp key. can anyone please help me.