Fastboot stopped working ? - Razer Phone 2 Questions & Answers

Mysteriously my fastboot stopped working?
I can adb devices works fine
Adb reboot bootloader works fine
Fastboot devices works fine
Fastboot flash boot filename I get FAILED (Write to device failed ( Invalid argument)) fastboot: error: Command failed
Stumped at this point
I'm completely stock and not rooted..
Flash_all gives same error and any other fastboot command as well :crying:
Edit: I've used the same USB to C cord I've always used BUT have tried another PC and different cords...No dice

Related

Help with fastboot ubuntu

does anyone know where to get help with fastboot in ubuntu? i have tried flashing a recovery image to my Dell Streak 7, but it keeps failing. fastboot is working, and when i send the command "fastboot reboot" it works fine. however, "fastboot devices" returns "????????????". when i try to flash the recovery, i get
"sending 'recovery' (3654 KB)...
FAILED (command write failed (No such device))
finished. total time: 0.000s"
"fastboot getvar version" returns version: LG7 0.4
so i know fastboot is working, and that it has at least some communication with the tablet, but something is not quite working. any ideas?
SOLVED
i'm not sure what happened differently, but i plugged the tablet into a different USB port, and then i got a max-download-size error when flashing the recovery. i came across another post that said to use "fastboot -S 0 flash..." to resolve that error, and it worked. everything seems to be good now

Unable to Root MRA58N

I have been going at it for a week straight and unable to find help. I am using Nexus Root Tool Kit 2.1.0. My Device is unlocked and OEM unlocked. However when i try to root the phone restarts into AP Fastboot Mode and nothing happens but the program seems like its trying but just unable to finish.
Log File:
Nexus Root Toolkit v2.1.0
Masterlists:
- LatestToolkitFiles.ini 3099
- AndroidDeviceListFull.ini 3099
- AndroidDeviceListFlash.ini 3099
SHAMU-SHAMU: Android 6.0.0 - Build: MRA58N
Live log initiated [2015-11-28]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Flashing Root Kernel to BOOT partition...
fastboot flash boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\root_kernel_shamu_mra58n.img"
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Rebooting your device...
Waiting for your device...
I have also tried to flash a custom boot.img but NRT stops at rebooting device.
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Flashing boot.img to BOOT partition...
fastboot flash boot "C:\Users\Dave\Desktop\volantis-mra58n-boot-system\boot.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
my screen just never does anything i remember last time i rooted on Android L it went with no problems.
just stays at
AP Fast boot Flash Mode (Secure)
BL: moto-apq8084-71.15 (sha-96f7faf, 2015-08-04 11:36:17)
Base Band : D4.01-9625-05.27+fsg-9625-02.104
just installed ADB and tried from command prompt to flash TWRP and i got failed (data transfer failure (unknown error) )
well, you are doing it wrong for a nexus owner, you dont need a root toolkit. to root m you need to flash any custom kernel for m as well as the latest supersu(as well as the latest twrp recovery so you can flash a custom kernel and supersu).
Don't use Root kits and follow these steps. Start from step 1 if you already have your bootloader unlocked and if you have SDK tools installed (adb and fastboot). And you should be fine...
yes wont let me install recovery TWRP
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11700 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.012s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
thats because you dont use adb for this. you have to use fastboot while you are in your recovery. read that again, FASTBOOT instead of ADB. you always use fastboot to flash the factory image or any part of it, or twrp recovery.
simms, the command he posted that failed WAS fastboot.
HOWEVER, if adb is reporting devices, you are likely either booted to android or recovery... reboot to the bootloader
(turn off device, then hold volume down and while holding vol down press and hold power until the device boots to the bootloader mode.
Make sure that you have twrp in the same folder, and that you have renamed it to recovery.img (not .img.img as a lot of people accidently do) That last part isn't completely necessary, as its really just "fastboot flash recovery <file name>", and you can replace <file name> with the name of the recovery image it doesn't HAVE to be recovey.img, and it doesn't have to be in the same folder if you include path... but people find it easier to just rename it to recovery.img, copy it to their platform tools folder and use the command you ran.
ahh.. yea @scryan i didnt see that fastboot was used(later in the post). now i see hes uding adb devices instead of fastboot devices.
As far as I can see, you are trying to flash recovery using fastboot flash recovery recovery.img while not in bootloader (or you didn't copy everything you did).
You should:
1. adb reboot bootloader (your phone will reboot into bootloader)
2. now you can write "fastboot devices" to see if your phone is recognized
2. then if it's there: "fastboot flash recovery recovery.img"
EDIT: If you still did everything correctly, quick google search said it could be problem with computer's USB port. Try another port...
I have tried every port on my pc some give unrecognized USB error while others work. If I am able to charge and transfer files along with send adb commands (restart phone,adb sees my phone) does that rule out the USB cable? I bought a pack of four on ebayhttp://m.ebay.com/itm/4x-6Ft-Micro-USB-Charger-Sync-Data-Cable-Nylon-Braided-for-Samsung-Galaxy-HTC-/221891441910?txnId=1650092351012
I no longer have the cable I used to flash marshmallow but I did use this to unlock the device.

[fastboot] problem with booting boot.img

When i use the command "fastboot boot boot.img" to boot twrp it loads endlessly until i interrupt it,
where it then gives me the error : FAILED (Status read failed (Too many links)).
My device is detected by "fastbood devices" and "adb devices".
I already tried to set the current slot to a with this: fastboot.exe --set-active=a
but it failed: FAILED (remote: 'unknown command').
My device is unlocked but when i check device status via "fastboot oem device-info" it tells me: (bootloader) 'device-info' is not a supported oem command.
Same goes for "fastboot oem help" which results in a : "FAILED (remote: 'unknown command')".
Right now i am using Havoc-OS which means it did work before.
Anyone else got any tips how i might get twrp to run again?
are you trying to boot fastboot boot boot.img ? or fastboot boot twrp.img ?
You need USB 2.0 hub.
Hello.Dear said:
You need USB 2.0 hub.
Click to expand...
Click to collapse
I've heard that before but I use a USB3.0 .
KrisM22 said:
I've heard that before but I use a USB3.0 .
Click to expand...
Click to collapse
Fastboot has a problem with USB 3.0. Same thing happened to me then i use usb 2.0 hub and everything works.

Question 'fastboot oem unlock' failing with remote: 'unknown command'

I just got my OnePlus 10 Pro, and am trying to unlock the bootloader. I've enabled USB debugging, and enabled the option to allow the bootloader to be unlocked in the Developer Settings.
I ran `adb reboot bootloader`, then ran `fastboot devices` to confirm the phone was connected and visible.
When I try to run `fastboot oem unlock`, I get this response:
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Fastboot version if necessary:
Code:
C:\Windows\system32>fastboot --version
fastboot version 33.0.2-8557947
Installed as C:\Program Files\Android Platform Tools\fastboot.exe
Thanks!
Fastboot flashing unlock
Awesome, thank you very much!

Question OnePlus 10 Pro Bootloader Unable to unlock [NE2215]

Hi,
I am trying to unlock the bootloader as it show status as "Device Lock"
When I try to use the command "fastboot oem unlock", it showed
"
...
FAILED (remote: unknown command)
finished. total time: 0.001s
I then tried "fastboot flashing unlock" but it showed this
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
Any solution to this?
fastboot flashing unlock
Make sure your platform tools are up to date as well - https://developer.android.com/studio/releases/platform-tools
Still the same. This is what I kept getting
When you type in fastboot press tab and it'll populate the actual filename.
I get this with certain setups. Same with ADB, just press tab after typing fastboot or ADB then continue with the same commands as you have..
Could just be your fastboot/ADB files.
. I've got the ones I use in my root guide in this forum, grab it and pop it in the root of C then give it another shot.
Hope you get it sorted
Jcddenton said:
Still the same. This is what I kept getting
Click to expand...
Click to collapse
Don't use PowerShell. Use command prompt. People using PS report nothing but problems.
You go into developer options and tick oem_unlock on?
EtherealRemnant said:
Don't use PowerShell. Use command prompt. People using PS report nothing but problems.
Click to expand...
Click to collapse
The above is what I have experienced myself.. Only ever happens with PS never CMD, not the end of the world though
Did this issue get resolved ? I am having the same issue. I am using CMD in admin mode.
Update your platform-tools. I had the same issue trying to unlock my pixel 7.
az_r2d1 said:
Did this issue get resolved ? I am having the same issue. I am using CMD in admin mode.
Click to expand...
Click to collapse
Everything you need is linked in my sig
Unlock oem from setting
ok, I figured out my issue. The root cause was the usb cable I was using. I used the oem cable that came with the 6t. IT refused to recognize the phone in bootloader mode ! As soon as I used an aftermarket stock usb-c cable, my pc recognized the phone in bootloader mode !
az_r2d1 said:
ok, I figured out my issue. The root cause was the usb cable I was using. I used the oem cable that came with the 6t. IT refused to recognize the phone in bootloader mode ! As soon as I used an aftermarket stock usb-c cable, my pc recognized the phone in bootloader mode !
Click to expand...
Click to collapse
In his case he is actually getting connect currently and it's visible..
As it's an unknown command then it's probably due to PowerShell,, when you type in the command, eg:
fastboot reboot
It won't see the word fastboot itself as the correct command. To fix this just click tab once and it'll populate it's actual name from the list of files in the active folder, so in actual fact the command would be
.\fastboot.exe reboot
Same thing with ADB as a command.
.\adb.exe devices
Just pressing the tab key would do the job.
Or just use CMD and navigate to the folder you'd like to be active
I'm afraid I don't understand. Brand new 10 Pro, have tried multiple cables, OEM unlocked, boot into fastboot and type "fastboot oem unlock" and it returns "FAILED (remote: 'unknown command')
I can't figure out from this thread whether anyone has a solution. I'm not using powershell, cables changed, so I'm clueless....and don't want to set up the 10 Pro knowing that (hopefully) it will be wiped when the bootloader is unlocked.
Many thanks for any help!
BeachNYC said:
I'm afraid I don't understand. Brand new 10 Pro, have tried multiple cables, OEM unlocked, boot into fastboot and type "fastboot oem unlock" and it returns "FAILED (remote: 'unknown command')
I can't figure out from this thread whether anyone has a solution. I'm not using powershell, cables changed, so I'm clueless....and don't want to set up the 10 Pro knowing that (hopefully) it will be wiped when the bootloader is unlocked.
Many thanks for any help!
Click to expand...
Click to collapse
Install platform tools, go into the directory that platform tools was installed, and run adb and fastboot thru that, i was getting same error and then went from directory platform tools was unzipped at and it worked fine...fastboot flashing unlock though
fastboot flashing unlock don't work for me!
adb is ok
fastboot reboot and fasboot devices is ok all commands
but not fastboot flashing unlock! on power shell or cmd always the same!
no error just the list
i test different cable or usb plug
i go crazy...
Damned fastboot flashing unlock passed. Don't ask me when. verified all 10 time and voilà !?
First time I like erase all my data
Just CMD like the undred before, but why this time?
I don't know really.
Though lock.

Categories

Resources