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
Related
My phone died and requires me to flash boot.img in order to bring it back to Android. To my surprise, I couldn't get it to go, and after some testing it seems my USB port is having an issue where it won't connect data, but will charge. Both of my computers with seperate USB cords are stating that the USB device has malfunctioned. Does anyone know of a good solution? I know there are the pogo pins on the back, but I don't know if there is anything that connects to them or if they transfer data. Is my only option at this point looking for someone to do a USB port repair for me? Any ideas would be very welcomed. Thanks!
Not sure exactly what your problem is? Boot.bin? What exactly is that?
RollTribe said:
Not sure exactly what your problem is? Boot.bin? What exactly is that?
Click to expand...
Click to collapse
Probably boot.img
Sent from my HTC One XL using xda premium
serotoninzero said:
My phone died and requires me to flash boot.img in order to bring it back to Android.
Click to expand...
Click to collapse
Where is it now if not Android? There are only certain instances that the computer will recognize it. Try a different computer as well (fresh install of HTC drivers).
chris948 said:
Where is it now if not Android? There are only certain instances that the computer will recognize it. Try a different computer as well (fresh install of HTC drivers).
Click to expand...
Click to collapse
Sitting at the bootloader as well as TeamWin recovery usb mount. Both times comes up as USB device not recognized.
serotoninzero said:
Sitting at the bootloader as well as TeamWin recovery usb mount. Both times comes up as USB device not recognized.
Click to expand...
Click to collapse
You are trying to go into fastboot, right, and not just regular bootloader.
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..
I was flashing something onto my device and now I only get the "A error has occurred while updating the device software" screen and I've tried using Odin to flash the original firmware on os but Odin gives me this error: "Can't open the serial(COM) port" I tried every fix and none of them worked. Can anyone help me to fix this?
Did you install the usb drivers first? If not here:
http://www.mediafire.com/?6onrjbyd46j4lhj
try a different usb port on the computer, and if that doesn't work try a different cable.
Do you have samsung kies or smth installed?
Kenora_I said:
Did you install the usb drivers first? If not here:
http://www.mediafire.com/?6onrjbyd46j4lhj
try a different usb port on the computer, and if that doesn't work try a different cable.
Do you have samsung kies or smth installed?
Click to expand...
Click to collapse
yes, I did
Do you have samsung Kies installed?
Have you tried a different pc or cable?
Kenora_I said:
Do you have samsung Kies installed?
Have you tried a different pc or cable?
Click to expand...
Click to collapse
I did that, still didn't work.
Retroguy129 said:
I did that, still didn't work.
Click to expand...
Click to collapse
Also, someone helped me now so it's all good now. But thanks for trying to help me though!
Oh okay.
If you're wondering, how i got my phone fixed someone dmed me on xda telling me to add him and then I followed what he was saying.
So thank you, @hainguyenthao for fixing my problem.
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
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