Hi,
I wanted to lock bootloader on my H930.I boot into fastboot mode, type the command "fastboot oem lock" and an error appears "FAILED (command write failed (Too many links))" then on the phone appears a screen with "LG v30 thinq" and a text i top left corner "press any button to continue", when i press it the phone boots and is still unlocked. I already installed a stock pie.
I want to lock the bootloader because even after unrooting, certain apps like google pay, still dont work.
Pele2115 said:
Hi,
I wanted to lock bootloader on my H930.I boot into fastboot mode, type the command "fastboot oem lock" and an error appears "FAILED (command write failed (Too many links))" then on the phone appears a screen with "LG v30 thinq" and a text i top left corner "press any button to continue", when i press it the phone boots and is still unlocked. I already installed a stock pie.
I want to lock the bootloader because even after unrooting, certain apps like google pay, still dont work.
Click to expand...
Click to collapse
You need to read the WTF Section 7 Trouble Shooting Tips. Many V30 have trouble communicating with PC during fastboot commands. Same error message as when unlocking bootloader.
That's what "too many links" always means. You'll need to try different cable, different PC port, different computer, etc. Reinstall drivers, blah, blah, blah.
Except for #1, all the dozen Section 7 Trouble Shooting Tips deal with ADB/fastboot flash commands communication issue.
ChazzMatt said:
You need to read the WTF Section 7 Trouble Shooting Tips. Many V30 have trouble communicating with PC during fastboot commands. Same error message as when unlocking bootloader.
That's what "too many links" always means. You'll need to try different cable, different PC port, different computer, etc. Reinstall drivers, blah, blah, blah.
Except for #1, all the dozen Section 7 Trouble Shooting Tips deal with ADB/fastboot flash commands communication issue.
Click to expand...
Click to collapse
Thanks,
What worked for me was just using a diffrent pc with windows 7 instead of one with windows 10.
After locking the bootloader all previously not working apps behave normaly.
Pele2115 said:
Thanks,
What worked for me was just using a diffrent pc with windows 7 instead of one with windows 10.
After locking the bootloader all previously not working apps behave normaly.
Click to expand...
Click to collapse
Yes, Win7 computer with Intel CPU and USB 2.0 ports is what usually works. But the other tips help.
However, even on my Win7 computer I've also had to change to different USB port sometimes or use different USB cable or reinstall drivers.
Related
When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
kayaven said:
When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
Click to expand...
Click to collapse
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Will_Xda said:
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Click to expand...
Click to collapse
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
kayaven said:
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
Click to expand...
Click to collapse
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
What are you trying or wish to do?
Which command?
Will_Xda said:
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
Click to expand...
Click to collapse
I'm using Windows 7 Ultimate x64, fastboot and adb are both running normal for the rest.
RuudM said:
What are you trying or wish to do?
Which command?
Click to expand...
Click to collapse
Well, i am trying to unlock my bootloader, but any command that writes to the phone will freeze it.
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
RuudM said:
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
Click to expand...
Click to collapse
I've already done that, but the command I need to run in order to get that code freezes it.
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
RuudM said:
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
Click to expand...
Click to collapse
I've got the original Android SDK fastboot, but that won't really matter, I suppose. The rest is the same. Furthermore, when i use the 'fastboot devices', it responds, but when i use something like 'fastboot oem get_identifier_token', it says FAILED (command write failed (Unknown error)), and the phone gets stuck.
I really have no idea why this is happening, i will now test if the official HTC fastboot works... :fingers-crossed:
-----------
Omg I'm an idiot, i just had it open on hboot and not fastboot >.<
I didn't know the difference Thanks a lot anyway everyone!
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
markbencze said:
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
Click to expand...
Click to collapse
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
wbexpress said:
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
Click to expand...
Click to collapse
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
markbencze said:
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Click to expand...
Click to collapse
Sure. Usually I am able to get into the bootloader(if adb devices recognized what's going on) where I get the LG logo and the words on the top left say "Welcome to Fastboot Mode". I put in adb reboot bootloader, which does get me there. Then, I put in fastboot oem unlock and that's when it hangs on waiting for device.
dillonorden said:
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
Click to expand...
Click to collapse
Exactly. I guess the "misery loves company" thing is operative here. If you do figure it out, PM me, I will do the same.
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
markbencze said:
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
Click to expand...
Click to collapse
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
wbexpress said:
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
Click to expand...
Click to collapse
Just follow the instructions in the "how to root..." thread. it goes step by step and I believe there is a video tutorial as well. You'll need to do a quick search for this.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
wbexpress said:
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
Click to expand...
Click to collapse
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
jkyoho said:
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
Click to expand...
Click to collapse
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
wbexpress said:
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
Click to expand...
Click to collapse
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Lorddyyy ive been trying this crap all day i have the same driver issue but it won't let me select the one i want it just says there are no drivers available in this folder! GRRRRR
---------- Post added at 08:37 PM ---------- Previous post was at 08:00 PM ----------
omg i think i got it! http://forum.xda-developers.com/lg-v10/help/phone-adb-fastboot-t3247732 went here and did what duece said above but choose choose from a list!> then i hit select all devices> the box said populating but i just clicked install from disk and changed it to the unzipped file folder that had the driver in it until i found this file android_winusb and selected it!> then low abd behold the box populated with the driver info and it became a samsung adb device! finalllyyyyyy!!!!!!!!!!! i'm so happy Ive been trying to root this damn thing all day!
jkyoho said:
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
Click to expand...
Click to collapse
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
wbexpress said:
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
Click to expand...
Click to collapse
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
jkyoho said:
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
Click to expand...
Click to collapse
Positive. The code I am putting in is twrp-2.8.7.1-h901.img. That's what most things I've read say to do. The other thing I have been thinking about is that KlicKit is supposed to have everything pre-loaded, and even it won't do it. KlicKit gets me into fastboot, then something really quick happens and the command prompt screen closes. What driver system do you use? I've installed a number of them, then deleted them as well, just to try to make sure there are no conflicts. However, I now have two devices in device manager: "android device.lge mobile adb interface" and "portable devices/v10. Does one need to go, maybe?
Power off your phone , hold volumn down and connect usb to PC.
Do you see "LOCK STATE - UNLOCKED" ?
if yes, type "fastboot.exe flash recovery twrp-2.8.7.1-h901.img "
Hey all i dont know what the deal is but ive got an lg g5 that just will not boot to the bootloader. I've tried factory resetting it and all the methods to get to bootloader just reboots the phone fully. Adb reboot booloader, key combos, nothing seems to work. Any ideas??
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
russy23 said:
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
Click to expand...
Click to collapse
Did all that.. I mean I've flashed custom recoveries and roms to other phones before and never really had a problem i couldn't google..this has me stumped. It simply refuses to even access the bootloader.
If it helps it was a koodo phone and is running the latest official patch from lg on nougat. The only thing i could find online was that sprint supposedly removed all access to the bootloader on theirs, but i cant find any real info on that either. It reboots when i send the adb reboot bootloader but its like fastboot just isn't there..?? It reboots right back to the android home screen. Ive tried all possible key combos as well... Ugh
Which model is it..mines the h850
Ive got the h831
I think I've sort of answered my own question. From browsing the forums it appears the Canadian variant has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
bproulx said:
... has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
Click to expand...
Click to collapse
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
logg.sar said:
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
Click to expand...
Click to collapse
Unless you're from Canada apparently ..lol
Brand new XZ1. Right after unpacking, it offered me to upgrade to Android 9, which I did. The next step was to unlock bootloader/root. So I enabled USB debugging, got my unlock code from Sony, enabled bootloader unlock via Developer options, rebooted into fastboot and entered oem unlock command. Nothing. I mean, it did absolutely nothing - system just kept waiting... and waiting... and waiting...
Rebooted computer and phone a few times, result was still the same; command "fastboot devices" finds phone, but further commands just don't work - system is waiting and waiting for command to finish executing, which never happens. So I connected my old XZ and fastboot worked perfectly. Connected Moto G5 Plus - all fastboot commands worked too. Connected XZ1 again - system kept waiting and waiting...
Tried this on 3 different computers (2xLinux, 1xWindows) using 3 different cables and result was always the same. Only 2 commands work for XZ1 - "fastboot devices" and "fastboot reboot". Any other fastboot command freezes... Any suggestions?
If you are using Linux, just use an usb hub and should work fine
manxp85 said:
Brand new XZ1. Right after unpacking, it offered me to upgrade to Android 9, which I did. The next step was to unlock bootloader/root. So I enabled USB debugging, got my unlock code from Sony, enabled bootloader unlock via Developer options, rebooted into fastboot and entered oem unlock command. Nothing. I mean, it did absolutely nothing - system just kept waiting... and waiting... and waiting...
Rebooted computer and phone a few times, result was still the same; command "fastboot devices" finds phone, but further commands just don't work - system is waiting and waiting for command to finish executing, which never happens. So I connected my old XZ and fastboot worked perfectly. Connected Moto G5 Plus - all fastboot commands worked too. Connected XZ1 again - system kept waiting and waiting...
Tried this on 3 different computers (2xLinux, 1xWindows) using 3 different cables and result was always the same. Only 2 commands work for XZ1 - "fastboot devices" and "fastboot reboot". Any other fastboot command freezes... Any suggestions?
Click to expand...
Click to collapse
Had the same problem on mine but I just pressed "enter" after a while and the phone booted with "bootloader unlock sign". Using windows 10.
WalterCool said:
If you are using Linux, just use an usb hub and should work fine
Click to expand...
Click to collapse
Hm, this one sounds unusual... Do you mean I should connect external USB device to my USB port? But for some reason, all other devices work fine (and yes, I tried switching USB ports too).
sinkoo1979 said:
Had the same problem on mine but I just pressed "enter" after a while and the phone booted with "bootloader unlock sign". Using windows 10.
Click to expand...
Click to collapse
Thanks, just tried... Now, I always get "command failed" message instantly and phone just turn offs (resets into "charging" mode). If I switch it on, everything works as usually, but after I reboot into fastboot again, all fastboot commands (that previously freezed) now display "command failed" messages... So, double-clicking Enter really had some effect, just not sure if it's good or bad
manxp85 said:
Hm, this one sounds unusual... Do you mean I should connect external USB device to my USB port? But for some reason, all other devices work fine (and yes, I tried switching USB ports too).
Click to expand...
Click to collapse
Correct, I had this discussion at xperia github, and we all found this as a solution. With Xperia phones seems to be a common issue at Linux, and usb-hub manage to solve this. That's just fastboot (blue light), using service mode (green-light) there is no problem.
Will give a try. Even if original Xperia works fine in fastboot.
So I just purchased this phone and am trying to follow the instructions on the Sony site. The rooting status in my service menu says my devices should be able to be unlocked.
Device is on android 13 on latest update, OEM unlock and USB debugging are both enabled.
I downloaded the usb drivers and the platform tools from the Sony site.
I opened a command prompt in the platform tools folder and when I run fastboot devices I get a response
When I run the command with my unlock code, I get the error
FAILED (remote: Command not supported in default implementation)
I tried to go to device manager to update the drivers, however when I do that it says the best driver is already installed.
I read in another thread to try to boot into the bootloader rather than fastboot. When I select reboot to bootloader the device seemingly shuts off.
EDIT: OK, I'm dumb and was in fastbootd mode rather than fastboot. I've now entered fastboot correctly (holding volume up while I plug it in, getting a black screen and a blue LED), updated the drivers correctly, and am now getting the error that the device is already unlocked. Now I guess I just need to verify that it is indeed unlocked, anyone have some advice on that?
EDIT 2: OK it seems to be going through the unlock process despite that error rather than the expected confirmation. After a few reboots it is now giving me the setup process again so I hope it worked. Leaving thread up for others who have the same issue to stumble accross.