Related
My wifi xoom is soft bricked. I can get into fastboot no problem. However the MotoDev download has a broken system.img file.
Stuck on the M/Dual Core Screen.
Any Advice.
Edit - Used chrome to download from MotoDev.
Unbricked, all is good
automatikdonn said:
My wifi xoom is soft bricked. I can get into fastboot no problem. However the MotoDev download has a broken system.img file.
Stuck on the M/Dual Core Screen.
Any Advice.
Edit - Used chrome to download from MotoDev.
Unbricked, all is good
Click to expand...
Click to collapse
When you were having this issue, what was the error you were getting when you tried to flash the system.img file?
My xoom is currently soft-bricked (I hope thats all it is at least), and when I go to flash system.img it basically will not let me. I've tried the "fastboot flash system system.img" technique and it simply doesn't work.
It shows: "sending 'system' <262144 KB>... FAILED <data transfer failure <Too many links>>"
I don't think I'm COMPLETELY screwed because I still have access to fastboot, and it still lets me flash my boot.img files. Any thoughts based on your experience?
how many devices have you connected with pc while doing this?
regarding corrupt download there is checksum at motodev site from where you have downloaded zip.
just ensure while downloading that file is saved as .zip.
there are 4 files inside zip which you need to put in "tool" folder of adb
Well I'm running Windows 7 64bit, and I would say I have a few devices plugged in, but nothing extraordinary? The only things running USB besides the xoom are keyboard, mouse, and wifi adapter. It also doesn't give me that error when I tried flashing any other file, which is why I think maybe I just have miserable luck and keep downloading bad files system.img files. I'll try re-downloading from motodev and give it another shot tonight.
hello xda community
I made sure to try everything (or almost) before post here
my ZenFone 5 show a message that it cannot mount the cache partition and I am stuck on the Asus logo (I can access droidboot and recovery but I cannot replace them)
factory reset and cache wipe does not make any change (they return the same "can't mount cache" error.
I am trying to change the current droidboot and recovery to fastboot and TWRP but not matter how much I flash them, it does not take change (yes, I am unlocking the bootloader)
I am also executing a script to get the original partitions table back but when sec_offline_update_image.cmd executes the command "fastboot oem partition /tmp/partition.tbl" I get the error "FAILED(remote: GPT command failed)"
as this came out of thin air, I didnt have the chance to activate developer mode on my phone
I starting to get concerned .... any help?
thnk you very much in advance
@dgadelha any help ?
What are the specs of your Zen 5?
dgadelha said:
What are the specs of your Zen 5?
Click to expand...
Click to collapse
ZenFone 5 - A501CG T00J
Serial # with 0123456789ABCDEF issue
Box info: A501CG2 / A501CG-1F589 / CPU Intel Clover Trail Plus + Dual Core 1.6 Ghz, Purple, 8GB RAM
I already checked basically all links on Google related to the above issues (4 days Googling it already).
I really don't know what to do anymore.
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Hi,
Did you have any kernel mods when using BlueLight?
Sorry but I don't know if it had a custom kernel, but a custom one could have lead a storage drive crash.
Also, xFSTK will just attempt to restore your droidboot and dnx/ifwi, not the partition table or w.e.
Maybe you could try extracting the Jelly Bean RAW file with 7-Zip, flash the droidboot signed image (should be like, fastboot flash fastboot file.img, or fastboot flash droidboot file.img), the droidboot signed image name might be something like droidboot.signed_POS.bin (it's an img file too, but with a bin extension).
After flashing that droidboot image, reboot your bootloader and try running the sec_offline_image_update.cmd again.
I wish I had Zenfone Assist active yet, but had to take down it.
Thanks
Hey jaabax, were you able to fix your device ?
Hi @vikrammarkiv.
Sorry for the big delay in response... I am not using this e-mail anymore and I quit fixing my phone.
Unfortunately I could not fix it and I ended up buying another phone.
Could you fix it?
Sorry again and hope you fixed it.
Best regards.
same issue, anyone got any update on fix?
jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Same problem, only fastboot and GPT failed (Asus zenfone 2 ze551ml). No solution
Exactly the same problem. It appears there are no fixes. How did the xf... thingy go?
Оh man.. I have the same issue, and can't fix it...
I have two Shield TV 2015 16 Gb boxes that were rooted.
On both boxes – the 5.2 upgrade doesn’t actually install. It downloads, reboots, says upgrading, reboots then prompts to install again.
I tried installing the 5.2 Stock Recovery via fastboot – and in the process it seems I have bricked the device.
When I press the on button – green light comes on for half a second then powers off immediately.
I don’t want to even start the stock recovery process on the other box because the same thing might happen.
Only thing I can think of is I used the 5.2 recovery file instead of the 5.1.
Just a heads up.
When you plug it into your computer, can the computer recognize the device at all?
Try swap the power supply..
ThermoDyn said:
I have two Shield TV 2015 16 Gb boxes that were rooted.
On both boxes – the 5.2 upgrade doesn’t actually install. It downloads, reboots, says upgrading, reboots then prompts to install again.
I tried installing the 5.2 Stock Recovery via fastboot – and in the process it seems I have bricked the device.
When I press the on button – green light comes on for half a second then powers off immediately.
I don’t want to even start the stock recovery process on the other box because the same thing might happen.
Only thing I can think of is I used the 5.2 recovery file instead of the 5.1.
Just a heads up.
Click to expand...
Click to collapse
I have the same problem...You found a solution???
nVidia shield tv 1st gen 16 gb
Increased the amount of internal memory due to microsd 128gb as an internal storage.
When I tried to upgrade from 5.1 to 5.2, nothing happened. There was a download of files, the beginning of the installation, a request to reboot. During the reboot, the logo with the robot did not appear as it was on previous updates.
Next, the console was loaded normally but the update was not installed. Accordingly, there was another request to install the update 5.2.
After several unsuccessful attempts, the console hangs on the logo Nvidia.
Disconnecting and connecting the power cord does not help.
At this stage, I decided to install stock recovery OS 5.1.0 .
Downloading the NVIDIA SHIELD ANDROID TV Image Recovery OS Image 5.1.0 image was taken from...
Https://developer.nvidia.com/gameworksdownload#?search=NVIDIA SHIELD ANDROID
Instructions
Http://developer.download.nvidia.co...IELD_ATV/5.1.0/HowTo-Flash-Recovery-Image.txt
Flash-Recovery-Image.txt
I made the firmware according to the instructions ....
1. Execute these commands on the host PC:
Fastboot flash staging blob
Fastboot flash boot boot.img
Fastboot flash recovery.img
Fastboot flash system system.img
Fastboot flash vendor vendor.img
Fastboot reboot
On a command fastboot flash system system.img received the message ...
Target reported max download size of 67108864 bytes
FAILED (data transfer failure (Unknown error))
Finished. Total time: 5.012s
Tried to do this operation several times ... unsuccessfully.
At the next attempt, the console stopped turning on. When the power is connected, the green light illuminates for 2-3 seconds and the console completely turns off.
Video...
Other than that, I have a problem with the controller. The controller does
not turn off. I tried to reset the microcontroller in all ways that I found
in the nVidia faq and the Internet.
Video...
krest said:
nVidia shield tv 1st gen 16 gb
Increased the amount of internal memory due to microsd 128gb as an internal storage.
When I tried to upgrade from 5.1 to 5.2, nothing happened. There was a download of files, the beginning of the installation, a request to reboot. During the reboot, the logo with the robot did not appear as it was on previous updates.
Next, the console was loaded normally but the update was not installed. Accordingly, there was another request to install the update 5.2.
After several unsuccessful attempts, the console hangs on the logo Nvidia.
Disconnecting and connecting the power cord does not help.
At this stage, I decided to install stock recovery OS 5.1.0 .
Downloading the NVIDIA SHIELD ANDROID TV Image Recovery OS Image 5.1.0 image was taken from...
Https://developer.nvidia.com/gameworksdownload#?search=NVIDIA SHIELD ANDROID
Instructions
Http://developer.download.nvidia.co...IELD_ATV/5.1.0/HowTo-Flash-Recovery-Image.txt
Flash-Recovery-Image.txt
I made the firmware according to the instructions ....
1. Execute these commands on the host PC:
Fastboot flash staging blob
Fastboot flash boot boot.img
Fastboot flash recovery.img
Fastboot flash system system.img
Fastboot flash vendor vendor.img
Fastboot reboot
On a command fastboot flash system system.img received the message ...
Target reported max download size of 67108864 bytes
FAILED (data transfer failure (Unknown error))
Finished. Total time: 5.012s
Tried to do this operation several times ... unsuccessfully.
At the next attempt, the console stopped turning on. When the power is connected, the green light illuminates for 2-3 seconds and the console completely turns off.
Video...
Other than that, I have a problem with the controller. The controller does
not turn off. I tried to reset the microcontroller in all ways that I found
in the nVidia faq and the Internet.
Video...
Click to expand...
Click to collapse
The Shield TV is very VERY finicky about its MicroUSB Cables, thus the Data Transfer errors. I would recommend you to recheck your Connections, again, barring that swapping out the MicroUSB Cable for a different one. Say the One you use to share your other Phone up with. Then try again.
My 2017 model 16gb was rooted also and wouldn't take the update. So I went to the Nvidia site and downloaded the recovery image for 5.1 for my device and flashed it...
All flashed fine but when reboot was initiated the box died. Trying to update to 5.2 while rooted and then flashing 5.1 killed my device. U can plug it in and nothing.. no green light at all.
I think nividia poorly handled their update. It did something to my device. Either that or it was faulty to begin with and the update brought about it's demise..
Anyhow.. I got it replaced.. which they were very good about doing.. updated the replacement to 5.2 then rooted. Hopefully future updates won't be as finiky
I had the same issue you had, however, what I flashed was everything but the data. it worked perfectly
Ichijoe said:
The Shield TV is very VERY finicky about its MicroUSB Cables, thus the Data Transfer errors. I would recommend you to recheck your Connections, again, barring that swapping out the MicroUSB Cable for a different one. Say the One you use to share your other Phone up with. Then try again.
Click to expand...
Click to collapse
At this stage I can not do anything anymore, because the console is turned
off after 2 seconds after switching on.
Video
I think that this post will be of interest to many people
I recently got the Essential Phone and instinctively decided to mess around and flash a custom recovery. I then found out that TWRP is not compatible with the essential phone running 8.1 beta. I am now stuck in fastboot mode. However, when i enter recovery mode, it goes straight to the logo screen with powered by android underneath and nothing occurs. When I start the phone back up, it also goes to the powered by android screen and does not load up. My computer does not recognize my device through ADB. My bootloader is unlocked. Any help is much appreciated as I do not want to have a useless phone after having it for a day. Thank you
--from what i gathered, fixing the phone is a matter of flashing the stock.img, which i have downloaded. However, because my phone is unable to be recognized by adb/fastboot I am unsure how to accomplish this
nickyg101 said:
I recently got the Essential Phone and instinctively decided to mess around and flash a custom recovery. I then found out that TWRP is not compatible with the essential phone running 8.1 beta. I am now stuck in fastboot mode. However, when i enter recovery mode, it goes straight to the logo screen with powered by android underneath and nothing occurs. When I start the phone back up, it also goes to the powered by android screen and does not load up. My computer does not recognize my device through ADB. My bootloader is unlocked. Any help is much appreciated as I do not want to have a useless phone after having it for a day. Thank you
--from what i gathered, fixing the phone is a matter of flashing the stock.img, which i have downloaded. However, because my phone is unable to be recognized by adb/fastboot I am unsure how to accomplish this
Click to expand...
Click to collapse
Make sure not to use the cable that came with the phone.
Reboot the computer, try a different USB port.
tech_head said:
Make sure not to use the cable that came with the phone.
Reboot the computer, try a different USB port.
Click to expand...
Click to collapse
I am using a different cable; one i purchased separately from the phone. After rebooting computer, should i again attempt to connect via adb and fastboot and, if it connects, attempt to flash to stock? thank you very much for the quick response
nickyg101 said:
I am using a different cable; one i purchased separately from the phone. After rebooting computer, should i again attempt to connect via adb and fastboot and, if it connects, attempt to flash to stock? thank you very much for the quick response
Click to expand...
Click to collapse
after resetting my mac, it recognizes my phone in fastboot mode
- i believe now all i need to do is flash the stock image i downloaded, which im not sure how to do
nickyg101 said:
after resetting my mac, it recognizes my phone in fastboot mode
- i believe now all i need to do is flash the stock image i downloaded, which im not sure how to do
Click to expand...
Click to collapse
The stock image on essential website has fastboot script.
Joylesstuna said:
The stock image on essential website has fastboot script.
Click to expand...
Click to collapse
when i locate the file, how should i flash it as?
fastboot flash boot 'boot.img'
my phone is not recognized over adb; rather when i go to recovery i got the red triangle over the android with "no command" underneath it
update: thank you all for the help i appreciate it a lot. When i run the script that came with the download from the essential site, my phone will boot back up but the wifi does not work.
Macintosh-2:~ xxxxx$ #!/bin/bash
Macintosh-2:~ xxxxx$ fastboot flash nvdef nvdef.img
error: cannot load 'nvdef.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash boot boot.img
error: cannot load 'boot.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash system system.img
error: cannot load 'system.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash bluetooth bluetooth.img
error: cannot load 'bluetooth.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash abl abl.img
error: cannot load 'abl.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash dsp dsp.img
error: cannot load 'dsp.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash modem modem.img
error: cannot load 'modem.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.294s]
finished. total time: 0.294s
Macintosh-2:~ xxxxx$ fastboot reboot
rebooting...
This is what occured in terminal and then my phone subsequently booted up into the new phone setup screen. it looks like the problem is that its not flashing any of the required modules and is only erasing my phone?
i was able to flash each however it just keeps rebooting to the fastboot screen :/
nickyg101 said:
i was able to flash each however it just keeps rebooting to the fastboot screen :/
Click to expand...
Click to collapse
Which firmware are you trying to flash?
Are you using one of the back to stock ROM images?
That is what you should use.
Open the script and use the commands line by line in a terminal.
If you are using a Mac it is a good idea to reboot before you start flashing.
If you have used ads or fast boot, it can sometimes get into a state where it won't see the device.
My Mac (native USB-C) will often crash when trying to flash the system image.
Yes I am attempting to flash back to stock. I got the zip from the essential site https://www.essential.com/developer/current-builds
and this is what the package looks like
nickyg101 said:
Yes I am attempting to flash back to stock. I got the zip from the essential site https://www.essential.com/developer/current-builds
and this is what the package looks like
Click to expand...
Click to collapse
I would look here and flash one this post.
https://forum.xda-developers.com/showpost.php?p=74437484&postcount=1
Every time i try flashing the stock stuff back on to the device, it boots right into bootloader (my bootloader is unlocked) no matter what. Is there a way around this or do you know why this would occur?
tech_head said:
I would look here and flash one this post.
https://forum.xda-developers.com/showpost.php?p=74437484&postcount=1
Click to expand...
Click to collapse
I flashed the april version of oreo and it flashes everything but then still always just boots right into fastboot mode. thank you for your continued help
You need to use the command fastboot flashing unlock_critical
Then use the back to stock firmware from this thread
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page48
That should set you write and don't forget to fastboot -w as well just to make sure
We got it back to stock Thanks everyone. It was a small thing I was missing on my end
Also when going into recovery, when you get to the "no command" screen you to press a key combo to enter recovery mode. I think it was power then volume up. It's always like that even in a fully functional device.
Would you mind posting how you fixed it and what was wrong? This is how we learn!
Hi,
I follow this Tutorial to root my Moto g6 Plus.
I could unlock my bootloader, but i cant boot twrp-3.2.3-42-evert.img.
When I try "fastboot boot twrp-3.2.3-42-evert.img" , I get
Code:
Sending 'boot.img' (31100 KB) OKAY [ 0.878s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am using Windows 10, 64 BIt.
I use cmd in WIndows Terminal.
I used the ADB and Fastboot Installer for Windows to install adb and fastboot.
Can someone help me please?
autowert66
I ran into this when I was looking to replace HavocOS 2.7 on Moto G6 plus and fix a few issues after a failed update using the tutorial here.
Did you disable lockscreen?
Even though this did not fix this issue for me it is well documented that it can have an effect on adb/fastboot use.
Did you see the notice on your phone to trust the connecting device?
I missed it the 1st time I tried using adb and it didn't prompt me again after that.
Have you tried adb/fastboot on another (older) machine .
I could NOT use fastboot on my Ryzen 7 linux machine w/ native USB 3.0 (or the 2.0 ports) and was getting the same type of results as you, although "adb reboot bootloader" worked fine.
I ended up usng an old HP Celeron laptop booting FWUL (bootable linux dev enviroment, Search for it here on XDA) on a USB stick which recognized the phone no problem and allowed me to "fastboot boot twrp-3.2.3-42-evert.img" (although I did copy/rename it to boot.img to save typing time), use it to backup to sdcard, format data, and install "new" ROM.
WARNING:
The tutorial I used above also has directions for installing (Open)Gapps and Magisk which, even after 2X attempts had lawnchair crashing continuously.
The 3rd time I just installed the ROM and Magisk and it's working fine.
This will be a test to use the phone w/o any g00gle at all (g00gle is EVIL).
HTH!
i know this is not a solution, but this kind of issue is solve by using a different pc.
i got the same "bug" with my current pc (ryzen 5 + motherboard asus b450m-a)
but my wife's pc (intel+asus mb) have working fastboot commands like usual
also try (if you can) using a usb hub... in my case it did not work but i read some users do.
àutowert66 said:
Hi,
I follow this Tutorial to root my Moto g6 Plus.
I could unlock my bootloader, but i cant boot twrp-3.2.3-42-evert.img.
When I try "fastboot boot twrp-3.2.3-42-evert.img" , I get
Code:
Sending 'boot.img' (31100 KB) OKAY [ 0.878s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am using Windows 10, 64 BIt.
I use cmd in WIndows Terminal.
I used the ADB and Fastboot Installer for Windows to install adb and fastboot.
Can someone help me please?
autowert66
Click to expand...
Click to collapse
What is your pc specs? Are you using a Ryzen CPU? Idk why but this phone won´t pick fastboot commands with a Ryzen CPU. Get any Intel and you will be able perform the booting.
d_g_m_2000 said:
i know this is not a solution, but this kind of issue is solve by using a different pc.
i got the same "bug" with my current pc (ryzen 5 + motherboard asus b450m-a)
but my wife's pc (intel+asus mb) have working fastboot commands like usual
also try (if you can) using a usb hub... in my case it did not work but i read some users do.
Click to expand...
Click to collapse
You are tottaly right. It is a bug or a known issue but this pc won´t pick fastboot commands from Ryzen pc.
àutowert66 said:
Hi,
I follow this Tutorial to root my Moto g6 Plus.
I could unlock my bootloader, but i cant boot twrp-3.2.3-42-evert.img.
When I try "fastboot boot twrp-3.2.3-42-evert.img" , I get
Code:
Sending 'boot.img' (31100 KB) OKAY [ 0.878s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am using Windows 10, 64 BIt.
I use cmd in WIndows Terminal.
I used the ADB and Fastboot Installer for Windows to install adb and fastboot.
Can someone help me please?
autowert66
Click to expand...
Click to collapse
In my case fastboot got stuck at sending boot.img forever until I removed the cable and then I got a similar or the same error. I solved this problem by disconnecting the cable, then typing in the command and pressing enter and after that putting in the cable again. Then it sent successfully and booted. I hope this helped someone.
If you have ryzen get a usb hub. If you have intel, run the command and wat for the "<wating for device>" and plug in the phone there. Also use usb 2.0
Diego_992 said:
What is your pc specs? Are you using a Ryzen CPU? Idk why but this phone won´t pick fastboot commands with a Ryzen CPU. Get any Intel and you will be able perform the booting.
You are tottaly right. It is a bug or a known issue but this pc won´t pick fastboot commands from Ryzen pc.
Click to expand...
Click to collapse
this is exactly why i didnt chose ryzen for my latest build. i know ryzen is dominating rn, and i really wanted an amd cpu, but need fastboot commands to work since im a regular modder on my oneplus 6T and moto phones