Get this error when trying to unlock OEM via fastboot. I've tried to change the usb port, change the cable (one that i am currently using is original), but still no luck. Any advice?
Try disconnecting all cables
ignaty_b said:
Get this error when trying to unlock OEM via fastboot. I've tried to change the usb port, change the cable (one that i am currently using is original), but still no luck. Any advice?
Click to expand...
Click to collapse
were able to fix this by just waiting
Related
Hello,
I want to install HBOOT 2.16.
When i try to push the firmware.zip trough fastboot.
I get this error:
start check_usb: usb_ep0: type=128, request=6
Click to expand...
Click to collapse
And then it does nothing anymore.
I tried a samsung cable, no success. Tried a LG cable, no success. Lost my HTC cable. Is it cable related?
Tried different USB ports, no success.
yooouuri said:
Lost my HTC cable. Is it cable related?
Tried different USB ports, no success.
Click to expand...
Click to collapse
No
Hello,
I received my NVIDIA Shield K1 a couple of days ago and upgraded to Android 6.0. I wanted to root my device, but when I try flashing the img file found in the Android 6.0 Marshmallow Update thread, it gives me an error. I noticed that when I put the phone in bootloader mode, it says "Device - locked," so I followed the instructions on how to unlock it using the "fastboot oem unlock" command, however, I keep getting the follow error message: FAILED (command write failed (Unknown error)
When I enter "fastboot devices" in command prompt, my device's serial does come up, so it is recognized. I just don't know what to do from this point on.
I would appreciate any help (step-by-step if possible, please).
Thanks
I'm having the same problem and am currently hung-up on unlocking the bootloader
Glitterjesus said:
I'm having the same problem and am currently hung-up on unlocking the bootloader
Click to expand...
Click to collapse
Were you able to figure it out, Glitterjesus? No luck here.
Two guesses
Be sure you are using a high quality USB cable and or try another port in pc, also be sure you have latest adb/fastboot binaries on pc
demkantor said:
Two guesses
Be sure you are using a high quality USB cable and or try another port in pc, also be sure you have latest adb/fastboot binaries on pc
Click to expand...
Click to collapse
Hi demkantor...I was using the cable that came with the controller and had it plugged into a USB 2.0 port. I'll try it when I get home and let you know.
Seems like your going to have to restore 5.1.1, unlock, and then root via flashing the available files
demkantor said:
Two guesses
Be sure you are using a high quality USB cable and or try another port in pc, also be sure you have latest adb/fastboot binaries on pc
Click to expand...
Click to collapse
I tried using it in a USB 3.0 port and it was able to unlock. Thanks for the recommendation, demkantor.
Hi all,
I have a Pixel 2, at January 8.1.0 version (OPM1.171019.013). It was rooted with Magisk latest version. Today I decided to reflash the firmware, without wipe, and the flashing was not successful. Now I'm afraid I have a small brick in my hands.
I'm now using the latest fastboot (0.0.1-4500957) and adb (1.0.39 / 0.0.1-4500957) versions. I don't know if I was on the latest versions when I tried to flash the firmware.
I always flashed the firmware using a USB A port on my Dell XPS 9560 notebook. Today I flashed from a USB C port, I don't know if this was the cause for the failed flash. I'm at the office, and I don't have a USB A x USB C cable available.
My Pixel 2 is stuck at the bootloader. Recovery mode and Download mode options don't do anything, it just goes back to the bootloader screen. Bootloader version is mw8998-002.0059.00. It tells me I'm on slot b, and I can't change slots, issuing fastboot --set-active=a either returns:
Code:
error: Device does not support slots
OR:
Code:
FAILED (remote: unknown command)
When I issue fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img either one of these messages is displayed:
Code:
error: Failed to identify current slot
OR:
Code:
target didn't report max-download-size
sending 'bootloader' (38644 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
I'm almost returning home early to try my USB A x USB C cable and see if anything changes. Am I without hope?
Never mind, the culprit was the USB C x USB C cable I was using at the office. Back home, I used my USB A x USB C cable and was able to recover the device.
I am having this exact same problem right now. Switching cables doesn't seem to help. Any advice in relation to the OP's first post?
rg2 said:
I am having this exact same problem right now. Switching cables doesn't seem to help. Any advice in relation to the OP's first post?
Click to expand...
Click to collapse
Try using the flash-all script that comes with the factory image from google. This will wipe your data unless you remove the -w option.
enzyne said:
Try using the flash-all script that comes with the factory image from google. This will wipe your data unless you remove the -w option.
Click to expand...
Click to collapse
Thanks for the reply. I have tried this already; I get FAILED with the following "Uploaded data exceeds max-download-size", along with error "Failed to identify current slot".
rg2 said:
Thanks for the reply. I have tried this already; I get FAILED with the following "Uploaded data exceeds max-download-size", along with error "Failed to identify current slot".
Click to expand...
Click to collapse
Just did a quick search. Seems that the cables have been the culprit or it could be the computer your using. Are your drivers up to date? Can you use another PC? What kind of cables have you used specifically?
enzyne said:
Just did a quick search. Seems that the cables have been the culprit or it could be the computer your using. Are your drivers up to date? Can you use another PC? What kind of cables have you used specifically?
Click to expand...
Click to collapse
Tried switching cables, no luck. Will try a different computer when I get home, and will let you know. I have been using an Anker c-->a USB cable, worked flawlessly until now. Tried another brand c-->a cable, same result.
No way to use the included USB-C to C cable?
enzyne said:
No way to use the included USB-C to C cable?
Click to expand...
Click to collapse
I don't have an adapter, and my computer(s) don't have a native port.
rg2 said:
I don't have an adapter, and my computer(s) don't have a native port.
Click to expand...
Click to collapse
Ok. Well I would try a different PC if you can. That will help to narrow down the issue. If that doesn't work let me know. I will try to figure something else out.
rg2 said:
I don't have an adapter, and my computer(s) don't have a native port.
Click to expand...
Click to collapse
Did you try flashing an older version of a factory image for the Google pixel 2?
Just do the same process you would usually do to flash a factory image but flash a build with an older version of your bootloader.
I had the same issue and used the November build
enzyne said:
Ok. Well I would try a different PC if you can. That will help to narrow down the issue. If that doesn't work let me know. I will try to figure something else out.
Click to expand...
Click to collapse
Thanks so much for the assistance. Late last night I tried another computer; this time it worked! I utilized Deuces Bootloop tool found here:
https://forum.xda-developers.com/pixel-2/development/tool-deuces-bootloop-recovery-flashing-t3725778
Then just to be safe I flashed the latest Factory image, and all is well again.
---------- Post added at 10:34 AM ---------- Previous post was at 10:32 AM ----------
Colday96 said:
Did you try flashing an older version of a factory image for the Google pixel 2?
Just do the same process you would usually do to flash a factory image but flash a build with an older version of your bootloader.
I had the same issue and used the November build
Click to expand...
Click to collapse
Just saw your reply. I fixed my issue, but FYI I did try older images, to no avail. Everything ended up working on another computer.
i am stuck at this bootloader nothing is working tried all the solutions mentioned above please help..
As I mentioned I my pc can't seem to detect my phone at all..it just goes into charging mode as soon as I connect..no adb no MTP or anything.
But my other phone connects just fine.
Things I've tried but failed,
Turning on adb debugging
Setting default usb configuration to MTP
Installing OnePlus drivers in pc
Adb and fastboot drivers along with qfil and miflash tool installed.
Pls guys help me figure this out.
I'm using latest oxygen os 11.1.1.1
Did you boot into other modes and tried to connect? recovery, fastboot etc.
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot etc.
Click to expand...
Click to collapse
Havnt tried this..I'll get back to u soon...my bootloader is locked btw
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot
Click to expand...
Click to collapse
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot etc.
Click to expand...
Click to collapse
I've tried bro but doesn't detect there either
i.Desygner said:
I've tried bro but doesn't detect there either
Click to expand...
Click to collapse
If it's stock then i'm thinking hw issue but keep trying things.
Try this:
Fastboot Not Recognized
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so...
forum.xda-developers.com
And maybe another computer just in case.
Thanks bro..but somehow I managed to get it to work with another usb cable..even that wasn't recognised at first,had to try and install various drivers and update them manually.
Do u think my one plus cable is broken now
i.Desygner said:
Thanks bro..but somehow I managed to get it to work with another usb cable..even that wasn't recognised at first,had to try and install various drivers and update them manually.
Do u think my one plus cable is broken now
Click to expand...
Click to collapse
Could be but keep in mind it has several pins so even if the data is broken or iffy you could always use it as a charging cable.
Either way use it as backup since it's less reliable
Just as the title says; I have the unlock token and I've tried everything I can think of to flash it and nothing's worked. I have OEM unlocking enabled, the phone is permanently carrier unlocked, USB debugging is enabled, I've made sure to download a new version of Platform Tools, I've moved the .bin file to the same directory as Platform Tools, the phone comes up in ADB and fastboot when I check, it just won't write and I can't figure out why... usually it just hangs at sending 'cust-unlock' etc. but never progresses past that. Can anyone help me figure this out?
EDIT: Resolved! Me being dumb, not realized I'd only tried USB 2.0 ports; using a 3.2 port did the trick instantly.
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
FoxyDrew said:
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
Click to expand...
Click to collapse
Yea, that's what's baffling; I can jump back and forth between adb and bootloader/fastboot pretty easily but I just can't send the unlock token. I have seen a couple weird errors though, like if I'm in bootloader and do 'fastboot OEM unlock' and it fails (since I can't get the token to flash) and afterward I try 'fastboot devices' sometimes fastboot crashes to the 'press any key to reboot' screen.
Could this just be an outdated driver issue? I thought they were up to date...
Have u try using other cable or even try on different PC?
hendavi said:
Have u try using other cable or even try on different PC?
Click to expand...
Click to collapse
I've tried multiple USB ports and the original cable as well as others; I've confirmed commands like 'ADB reboot bootloader' and 'fastboot reboot bootloader' work and I've even updated the ADB/fastboot drivers just in case... still nothing. I haven't tried a different PC yet but I suppose that's next
No matter what I try, this is what I get every time I try it from the bootloader. I've tried from bootloaderd/recovery, but it fails there too saying something like 'writing not allowed' or something... I have OEM unlock turned on and it's carrier unlocked, so I have no clue what's stopping this from working.
What's really weird is I actually got this to work once before on this same device, but had to reset the phone back to stock T-Mobile branded software using the MSM tool; the first time around, I was able to enter the unlock token and just unlock it like normal (fastboot OEM unlock). Now that I've reset the phone and I'm trying again, it just won't work... really perplexed on this one.
UPDATE
I had to pull up an image of my mobo's io panel because I couldn't remember and couldn't see which ports were which; once I moved the cable to a USB 3.2 port, it worked... I guess I'd only been trying it on USB 2.0s before so it didn't work.
Thanks for your help!
I had same issue on my OnePlus 8 TMobile. Have to disable driver signatures. This shows you how. Yes, the link is for a diff phone, but just follow the disable driver signatures part of it and it will then show up in fastboot
https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
EDIT: False alarm. I was sent an unlock code for an older device I have instead of the one I just bought. Should've double checked it first.