Database Users

[Q] Fastboot Device not Recognized

I was trying to flash a new splash screen for my phone and I was getting the error below. I got a similar error when trying to flash a new kernel earlier this week. I always get the "FAILED (status malformed (1 bytes)) finished" error.
I have been searching for about three hours for a fix to this problem to no avail. Right now I'm thinking it could be my drivers, but I can't find HTC Sync for the MT4G. Also, I can use ADB and my phone is recognized there, which made me think it was not my drivers. Ugh, I'm just so confused.
Here is the error:
"C:\AndroidSDK\tools>fastboot flash splash1 rootedmytouchsplash.img
sending 'splash1' (750 KB)... FAILED (status malformed (1 bytes)) finished. total time: 0.021s"

Just to make sure, did you put your device in fastboot mode before flashing image?
What does "fastboot devices" return?

borodin1 said:
Just to make sure, did you put your device in fastboot mode before flashing image?
What does "fastboot devices" return?
Click to expand...
Click to collapse
Yes, I was in fastboot. It shows my options in fastboot as (Bootloader, Reboot, reboot bootloader, and Power Down). When I input fastboot devices this is what returns.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Brian>cd..
C:\Users>cd..
C:\>cd AndroidSDK\tools
C:\AndroidSDK\tools>fastboot devices
C:\AndroidSDK\tools>

ihidbehindmusic said:
I was trying to flash a new splash screen for my phone and I was getting the error below. I got a similar error when trying to flash a new kernel earlier this week. I always get the "FAILED (status malformed (1 bytes)) finished" error.
I have been searching for about three hours for a fix to this problem to no avail. Right now I'm thinking it could be my drivers, but I can't find HTC Sync for the MT4G. Also, I can use ADB and my phone is recognized there, which made me think it was not my drivers. Ugh, I'm just so confused.
Here is the error:
"C:\AndroidSDK\tools>fastboot flash splash1 rootedmytouchsplash.img
sending 'splash1' (750 KB)... FAILED (status malformed (1 bytes)) finished. total time: 0.021s"
Click to expand...
Click to collapse
Is your S=OFF?

My s=off. Otherwise I would get an error saying that the command is not allowed I believe. But yes, s=off.

ihidbehindmusic said:
I was trying to flash a new splash screen for my phone and I was getting the error below. I got a similar error when trying to flash a new kernel earlier this week. I always get the "FAILED (status malformed (1 bytes)) finished" error.
I have been searching for about three hours for a fix to this problem to no avail. Right now I'm thinking it could be my drivers, but I can't find HTC Sync for the MT4G. Also, I can use ADB and my phone is recognized there, which made me think it was not my drivers. Ugh, I'm just so confused.
Here is the error:
"C:\AndroidSDK\tools>fastboot flash splash1 rootedmytouchsplash.img
sending 'splash1' (750 KB)... FAILED (status malformed (1 bytes)) finished. total time: 0.021s"
Click to expand...
Click to collapse
fastboot.... you're doing it wrong... I would be glad to help, but troubleshooting over forums is annoying. hit me up on aim, yahoo, msn, gtalk, IRC, etc

I would also be hugely interested in a solution or fastboot instruction sheet. I have similar problems on my 4G trying to flash to stock Glacier 2.2.1 (post OTA).
Thanks!

ihidbehindmusic said:
Yes, I was in fastboot. It shows my options in fastboot as (Bootloader, Reboot, reboot bootloader, and Power Down). When I input fastboot devices this is what returns.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Brian>cd..
C:\Users>cd..
C:\>cd AndroidSDK\tools
C:\AndroidSDK\tools>fastboot devices
C:\AndroidSDK\tools>
Click to expand...
Click to collapse
Yeah, you're not doing something right. fastboot devices should return the serial number of your phone followed by the word fastboot. Your command returned nothing. Make sure you have the proper drivers installed. It will install new drivers the first time you hook up the phone while in fastboot, and those are necessary.

So yea I just had a breakthrough about 2 mins ago and thought I would share. I too had the same problem exactly to the T of what you where having. Then I shyte you not, I had an epiphany. While in bootloader on my phone not attached I clicked on fastboot then plugged my phone in(i am using Win7 Home 64-bit) and nothing popped up in my start bar. So I went to control panel and then to hardware and Right clicked on the Android hardware and updated my drivers automatically and viola my problem was solved.

I think I figured out my problem. When in fastboot, my phone isn't recognized by my computer. I went into manage devices, but Android Device isn't showing up at all. When I go back to bootloader, it recognizes my phone, and says its drivers are up to date. The only problem is, fastboot commands can only be used while in fastboot. If my phone isn't recognized while in fastboot, then I can't apply any fastboot commands. How can I get my computer to recognize my phone while in fastboot?
jc_byrd said:
So yea I just had a breakthrough about 2 mins ago and thought I would share. I too had the same problem exactly to the T of what you where having. Then I shyte you not, I had an epiphany. While in bootloader on my phone not attached I clicked on fastboot then plugged my phone in(i am using Win7 Home 64-bit) and nothing popped up in my start bar. So I went to control panel and then to hardware and Right clicked on the Android hardware and updated my drivers automatically and viola my problem was solved.
Click to expand...
Click to collapse

Are you sure you are in fastboot mode? I had the exact same problem and actually took the Nexus S back because I could not get fastboot to work(have to use fastboot to unlock bootloader). After reading numerous threads I booted my MT4G into recovery and cursored down to fastboot and actually clicked on fastboot and then connected the device to the usb which was already connected to the PC and lo and behold it loaded the drivers and away we went. I did the same thing with my Nexus one and my Vibrant and all now are recognized by fastboot. I do not know if this will help you but just wanted to share what worked for me.

Just had the same issue with my Incredible 2, followed the above, and worked just fine.

k3n85 said:
Just had the same issue with my Incredible 2, followed the above, and worked just fine.
Click to expand...
Click to collapse
i got a weird error,
"sending splash1...OKAY"
"writing splash1"...FAILED <remote not allowed>
phone is recognised in fastboot etc...
any ideas?
thanks

removed

fastboot device is not recognized
Here' s my case
Initially unlocked bootloader, rooted through kingroot; tried to flash xposed framework through twrp but the zip file was not compatible. hence phone was bricked.
restored my moto g updated to 5.1.1 through OTA update.
Again rooted through Kingroot, bootloader is still unlocked but now when i'm trying to again install twrp i'm getting a message that
""'fastboot' is not recognized as an internal or external command,operable program or batch file.""
the procedure i'm following is correct. Prerequisite requirements are also installed.
Please help!

Fastboot flash recover fails - any help please?

Hi Guys,
I've got a brand new Nexus 7 (2013) flo/wifi version.
I'm trying to add Timur's kernel to it however I'm struggling.
I've installed ADB to my windows 10 pc and when I type adb devices I see the device, so I type adb reboot bootloader, thats fine.
I downloaded twrp-2.8.7.0-flo.img from the twrp.me site and and renamed it to twrp.img, then I moved it in to the same directory that adb and fastboot are running in.
I type fastboot flash recover twrp.img and I get this below:
Code:
sending 'recovery' (8956 KB)...
FAILED (data transfer failure (Unknown error))
finsihed. total time: 5.011s
I've tried 3 different USB ports and 2 different cables - I restarted my desktop pc too
Can anyone help me out please?

ok, scrub that I've managed to get a good connection now and its worked however when I now try to get to the recovery screen I get an android robot laying down with a red triangle and ! in it....
Any ideas what I've done?

itnorfolk said:
Hi Guys,
I've got a brand new Nexus 7 (2013) flo/wifi version.
I'm trying to add Timur's kernel to it however I'm struggling.
I've installed ADB to my windows 10 pc and when I type adb devices I see the device, so I type adb reboot bootloader, thats fine.
I downloaded twrp-2.8.7.0-flo.img from the twrp.me site and and renamed it to twrp.img, then I moved it in to the same directory that adb and fastboot are running in.
I type fastboot flash recover twrp.img and I get this below:
Code:
sending 'recovery' (8956 KB)...
FAILED (data transfer failure (Unknown error))
finsihed. total time: 5.011s
I've tried 3 different USB ports and 2 different cables - I restarted my desktop pc too
Can anyone help me out please?
Click to expand...
Click to collapse
U are in wrong section man
Go to nexus 7 2013
Sent from my Nexus 7 using Tapatalk 2

Help with rooting P8-lite Ale L21 dual-sim C432B564

I have a relatively new P8-lite L21 dual sim phone and I am quite happy with it. It came with C432B170 which is Lollipop I think 5.01. After a few days it updated to B172. I have unlocked the bootloader after registering with Huawei and waiting 2 weeks. Then I have successfuly rooted the phone with Kingroot phone version. Two or three weeks ago I have updated the phone to MM (6) and Emui 4 with local update (B560) that I have gotten from this forum. 2 days ago I recieved the notification of OTA B564 which went smoothly beside the fact that it reset the phone but i have succesfully restored (contacts, data etc.) All of this time since I upgraded to MM i have tried to root the phone but I was unsuccesful either with any software solution ( Kingroot, Kingoroot or others). After reading most if not all discussions on this forum and several blogs and how -tos, I tried the so called fastboot method others have recommended but here is now the gist of my problem. My phone is seen by my PC - OK so USB drivers are properly installed (by the way my PC is Win 10) and I have installed Android SDK as well as minimal ADB. When i try to flash TWRP 3.00.2 I can not do it (the message says something about not able to access or i think remote command not allowed. So since I cannot flash TWRP i am unable to put SU on the phone and root it. I hope someone more experienced and skillfull in Android world can point me in the right direction and help me. Thank you

Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.

VladHD said:
Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.
Click to expand...
Click to collapse
Downloaded minimal adb fastboot and installed it. Tried the procedure. Copied TWRP recovery to the minimal folder. Shift right clicked in the folder of minimal and opened command window. Adb rebooted to bootloader. Phone shows it is unlocked. The device is seen in fastboot window but flashing recovery doesn't work (same message) I am really confused. How do I give adb full permissions ?
Any way thanks in advance.

Did you activate usb debugging ?

VladHD said:
Did you activate usb debugging ?
Click to expand...
Click to collapse
Yes of course !

Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.

VladHD said:
Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.
Click to expand...
Click to collapse
The drivers were reinstalled. My bootloader shows unlocked on bootloader (bottom of fastboot screen). Fastboot devices does nothing. Adb devices shows my phone serial number correctly (I have it written down). But then when i try to flash recovery it is unsuccessfull. It says "FAILED (remote: Command not allowed)"

What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app

amageek said:
What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img

doomking_99 said:
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img
Click to expand...
Click to collapse
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)

amageek said:
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)
Click to expand...
Click to collapse
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.

doomking_99 said:
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.
Click to expand...
Click to collapse
ahhh... sorry mate, dont know the solution.. but try re-installing adb drivers again ...

Are you logged as adminstrator on pc?
Try to plug usb into different slots.

VladHD said:
Are you logged as adminstrator on pc?
Try to plug usb into different slots.
Click to expand...
Click to collapse
I am and I have. I am stumped. Obviously something is wrong with windows permissions I think. Is it possible to put recovery. img on sd card or on phone and flash recovery from the phone ?

This is the output every time no matter which usb port
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
W3D7N15C08019820 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.624s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
C:\Program Files (x86)\Minimal ADB and Fastboot>
The thing i don't understand is why fastboot command doesn't show device while adb command does.

You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app

amageek said:
You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.

doomking_99 said:
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.
Click to expand...
Click to collapse
Sorry for the zombiethreading here, but... what whas the solution? I'm curious

For the time being there is no solution. Can not flash TWRP - phone not rooted

doomking_99 said:
For the time being there is no solution. Can not flash TWRP - phone not rooted
Click to expand...
Click to collapse
Weird... i can't think of anything else myself that hasn't been said. Perhaps... redownloading twrp? Maybe the image is corrupted by something... ot's a long shot because ot should flash everytging that comes its way. But it's the only thing you hven't tried.

v20 H918 fastboot/twrp/bootloop brick

i have 3 lg
one of them is seen by my linux mint 20.1 desktop. this is my good stable and never touches any mods till my two better phones are running.
the other 2 i can get into fast boot, they were previously rooted & running orea/8 stock rooted
neither of those other 2 phones are recognized by my pc
i am using the adb reboot bootloader and get no joy on the 2 suborn phones.
both of the two phones refused to flash roms of any sort or type after a twrp wipe.
one of the phones is now fastboot only and nothing else ever happens and no connection to the pc is ever made
the other phone still goes into twrp most of the time,,sometimes fastboot only,,and still refuses to take any rom of any sort at all
my goal is to reflash twrp, and throw on lineage stable
BUT
not desktop connection?
someone pleas help me unbrick these two

updot
i found a way to get coms, but it is still failsauce.
.
the instructions on twrp page failed because my system could not read that far into my hard drive
.
TWRP Installation Tutorial for Linux Mint and Ubuntu users » AndroidGuru.eu
TWRP (Team Win Recovery Project) is an open-source custom recovery image for Android devices. It is a replacement for the stock recovery mode that is installed on most Android devices by the manufacturer. TWRP provides various advanced features and options that are not available in the stock...
www.androidguru.eu
.
seeing the fail sequence @ terminal feedback info i used that to go to where it WAS reading from, pasted the .img file there, then ran the commands @ that point
result was
.
[email protected]:~$ sudo fastboot flash boot /home/twrp-3.5.0_9-0-h918.img
target reported max download size of 536870912 bytes
sending 'boot' (23540 KB)...
OKAY [ 0.681s]
writing 'boot'...
FAILED (remote: unknown command)
finished. total time: 0.700s
[email protected]:~$
now i need to troubleshoot /fix why my phone is refusing to accept a flash,,even though it is correctly responding back to
sudo fastboot devices
any advice would be GREATLY appreciated.
will update as possible.if the Lord be willing.
event time stamp @ 4:30 - 2/9/21

notes :
adb sideload Full-Path-to-the-file.zip
CommandFunctionsADB Commandsadb devicesShows attached devicesadb shellTo jump from windows command prompt to android device shell:adb reboot bootloaderTo boot into bootloader modeadb reboot recoveryTo boot into recoveryadb get-serial noGet Serial Number of your connected deviceadb installTo install apps over adbadb install -rTo update the existing apps with new versionadb uninstall package_name.hereTo uninstall any apps or packages from the connected deviceadb uninstall -package_name.hereKeep the data and cache directories after uninstalling appsadb push <local> <remote>Upload a specified file from your computer to deviceadb pullDownload a specified file from your device to your computer.adb backupTake backup from your device to PCadb restoreRestore the backup to your phoneadb sideloadTo sideload apps or flashable zip file to your deviceadb logcatTake the realtime log from your phoneadb start-serverstart adb servers processesadb kill-serverstop adb server processesadb reboot fastbootreboot your device into fastboot modeadb usbshows all devices connected to your computer via a USB cable.adb devices //show devices attachedIt will display the list of all devices attached to your PC.adb connect ip_address_of_deviceconnect the IP address of your Android device to your computer.Fastboot commandsfastboot devicesShows connected devices on your PC/Laptopfastboot rebootTo reboot your devicefastboot reboot recoveryTo boot your device into recovery modefastboot oem device-infoTo check the bootloader unlock status:fastboot oem unlockIf the above command returns fall, run the following to unlock the bootloaderfastboot flashing unlockFew OEM may use this command to unlock bootloaderfastboot flashing unlock_criticalAllow flashing of bootloader related partitions too:fastboot oem device-infocheck bootloader lock/ unlock statusfastboot flash recovery [recovery.img]To flash recovery on your devicefastboot boot [boot.img]To test the recovery without permanently flashingfastboot format:ext4 userdataTo format data partitionfastboot flash boot [boot img name]flash flashable boot.img from fastboot modefastboot getvar cidTo display CID of your deviceFlashing ROM via Fastboot ROM zip packagefastboot -w
fastboot update </path/to/your/Rom.zip>
ref :
Basic ADB and Fastboot commands that you should learn to become Android Pro
Basic ADB command that you should learn to become Android Pro: Every Android developer or Android enthusiast should know some basic ADB comma
www.getdroidtips.com

thinking out loud.
everything i am seeing sais if my handset is not recognized by the desktop PC then my drivers are not correct.
problem with that statement is one of my 3 V20's does connect. correctly.
the other two are
FAILED (remote: unknown command)
as if there was no phone connected
but they are recognized under the fastboot devices, showing the connection is recognized by the PC, but not recognized by the phone.
how?
someone tell me pleas?
how do i get the 2 derpy phones to recognize the pc?

i am very much in a less then 3rd world country circumstance. (16 kbps max download speed for more then a week now) connecting to the internet is almost impossible as it is under excellent circumstances. for me to reboot into a Live os, and then set up a full NIC config before the Live freezes, glitches out or other wise kicks me in the face is almost impossible.
i am guna try to make an install. drag copy everything from the install to my os. this arch distro is built super similar to parrot os, so i might be able to make something work.
time will tell.
so far i have a failed atempt at this point
--------------------------------------------------------------------------------------------------------------------------------
[email protected]:/home/lglaf$ cd lglaf
bash: cd: lglaf: No such file or directory
[email protected]:/home/lglaf$ sudo git checkout h918-miscwrte #for the TMO V20
error: pathspec 'h918-miscwrte' did not match any file(s) known to git
--------------------------------------------------------------------------------------------------------------------------------
the lafsploit is not able to "get" from the hub. looks like files have been removed?
now how do i get what i need?
took me an hour and a half to run less than 10 cmd lines.
not to mention thes fails are forcing me to unplug a phone while in download mode.
this is not fun.
any one know where i can download the file "h918-miscwrte"
looks like it is no longer on github
[email protected]:/home/lglaf# git pull
Already up to date.
[email protected]:/home/lglaf# git checkout h918-miscwrte
error: pathspec 'h918-miscwrte' did not match any file(s) known to git
hard thing waiting.

return from lineage os to oxygen. problem with twrp installation

hello everyone. I haven't modded a smartphone for a long time and I need some help.
after installing lineage os a few years ago now i would like to go back with oxygen but i have problems with the installation of twrp.
I installed the platform tools and drivers and placed the twrp image in the (platform tools) folder.
debugging enabled
launching the command in the windows prompt: adb reboot bootloader the smartphone restarts correctly and shows me the screen with the choice START RESTART RECOVERY POWER OFF
the fastboot devices command, however, does not return any results
inserting the adb rebbot fastboot command instead the phone starts correctly in lineage os fastboot mode and now the fastboot devices command gives the result
now I enter the folder where I copied the twrp image cd c:\platform-tools and I give the command fastboot boot twrp.img (the file is renamed TWRP)
but this is the result
c:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (33116 KB) OKAY [ 0.995s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
Can someone be kind enough to help me. I have made many different attempts to no avail.
Thank you!

sun-k said:
hello everyone. I haven't modded a smartphone for a long time and I need some help.
after installing lineage os a few years ago now i would like to go back with oxygen but i have problems with the installation of twrp.
I installed the platform tools and drivers and placed the twrp image in the (platform tools) folder.
debugging enabled
launching the command in the windows prompt: adb reboot bootloader the smartphone restarts correctly and shows me the screen with the choice START RESTART RECOVERY POWER OFF
the fastboot devices command, however, does not return any results
inserting the adb rebbot fastboot command instead the phone starts correctly in lineage os fastboot mode and now the fastboot devices command gives the result
now I enter the folder where I copied the twrp image cd c:\platform-tools and I give the command fastboot boot twrp.img (the file is renamed TWRP)
but this is the result
c:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (33116 KB) OKAY [ 0.995s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
Can someone be kind enough to help me. I have made many different attempts to no avail.
Thank you!
Click to expand...
Click to collapse
Hello,
let me see if i can help,
but i need some info....
Which the LineageOS version
your device currently running ?
Is your 6T a global or T-Mobile version ?

hi, thanks for the reply. it is a secondary phone and has an old lineage version. yesterday with a different PC than usual I managed to install the latest version of twrp from cmd after solving a partition problem. i installed twrp only theoretically since after reboot the lineage prompt doesn't start and the boot stops at the screen with fastboot written... by forcibly turning it off I can access the bootloader. this is the current situation. 6t golobal...

developments ... from what I wrote above I could not get any progress. the device goes into bootloader mode manually but from the windows prompt it is not detected by the adb device command or by fastboot device .. so I can't advance ...

Going back to stock version does not necessarily
imply the use of a custom recovery,
you just need to use the MSM/rollback tool.
You can download it from THIS thread.
Use the earlier version of the tool as
you don't know wich exactly the
version of android installed in your device,
9.0.16 suggested.
When you will have a running device,
manually download and install OOS 9.0.17 firmware,
which will let your device to upgrade to android 10 and so on...
READ carefully @iaTa THREAD to follow exact MSM procedure.
Use a Windows pc and be sure
you have installed Oneplus driver.
Feel free to ask.