Related
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!
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
V0nice said:
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
Click to expand...
Click to collapse
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.
-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)
okantomi said:
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.
Click to expand...
Click to collapse
-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
Do you know what you did to be able to unlock? I think you really have to be careful to type commands EXACTLY as shown. No extra spaces, but don't leave anything out either. Looks like commands aren't typed in correctly. Take your time. You'll do it.
V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.
eqppwqqep said:
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.
Click to expand...
Click to collapse
So is everything ok now?
okantomi said:
So is everything ok now?
Click to expand...
Click to collapse
Yes. I am not rooted. am I supposed to change the thread to solved or something?
different error on trying to flash this recovery
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
If you haven't already. Delete the .img file. and reinstall it. try the process again.
make sure you're inputting the full command prompt from the beginning. That was my problem. Hope that helps.
jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
fastboot flash recovery(you missed this) recovery-Tiamat-R4c-100611-1150-cwm.im
Hello all
Trying to figure out some issues with my nexus 7.
I was loading up a game, and hit back. The device froze, and I attempted to reboot. Would freeze at "google" screen.
I've tried to do a factory reset via recovery mode, and it simply returns that it cannot mount the partitions, with the "invalid argument" as the reason.
I've attempted to manually wipe the directories via fastboot, but it always fails with the same error. Invalid argument.
It would appear my file structure is gone, and I cannot load the stock because when I attempt to unlock my fastboot it freezes on removing "userdata"
I've tried 3 PCs, all different cables, usb 1,2 and 3. I've used the Asus USB drivers, and the universal. I've tried Wugs methods, which simply render the same error, just quicker.
adb sideloading also fails. It just seems I cannot get anything to write on the sdcc.
fastboot oem ? - fails
fastboot oem h - fails
Only thing that works, is the listing of the device in adb/fastboot - It will prompt for the unlock, but once hitting yes it freeze. Sat for 2 hours, nothing.
Any ideas?
Wrong forum try the nexus 7 2013 forum. If fastboot OEM unlock fails and adb sideloading fails then its most likely a corrupted nand partition has made the internal memory unwritable that would mean RMA or a new motherboard
Sent from my C5303 using xda app-developers app
Hello guys,
I have tried flashing an image in Odin, it connects but odin immediately crashes.
Using the androidSDK ADB, it connects, wipes a few things in a fraction of a second, then takes forever to try to push Boot.img which is only 5mb! this never completes.
I have tried wugfresh nexus root toolkit, and starts working perfectly, sends bootloader, boot, cache, recovery, but then at system it says FAILED (data transfer failure (unknown error)) rebooting into bootloader...
and it never reboots.
EDITED:
I tried wugfresh nexus toolkit for the 8th time, and SOMEHOW it got through the whole lot and I managed to boot.
For the record, (not that these things may have made a difference) had powered the tablet off before, on several occasions, and this time, I had also booted to bootloader from the tablet in a powered off state. I had read elsewhere that this had made a difference for someone.
No idea why it worked now... but relieved.
Hey everyone,
Earlier today I was able to successfully root my Essential Ph-1 running Oreo 8.1, using Magisk and twrp-mata_11.img . Later on I tried to install Xposed framework, but found myself caught in a bootloop, when the flashed TWRP did not recognized my phone PIN and I tried to reboot the system and take the PIN out. I am able to access the bootloader and use the TWRP when I flash it, and that's it.
I do realize that it fixing it is not really a complex process, but I have been having trouble with flashing with fastboot. Every command I try to run ends up in failure, except the "fastboot devices" one. For example, when I tried to run the "fastboot -w" command, I received the following:
"wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))".
And all others commands showed the "FAILED (command write failed (No error))" message, including when I tried to run the "flash all" file as system admin.
Also, I have only tried to do it in Windows, to no avail, while I am still inexperienced with Linux and cannot connect fastboot to my device.
This is not the first time that I have rooted the device, I did it twice a couple months ago but lost the root because of updates. The difference is that I used my Nintendo Switch Pro Controller cable, which for some reason was the cable that worked the best, instead of the phone's factory cable with a Syntech USB - C to USB adaptor. this time. I found out later on that this cable had issues with this kind of process.
Also, when flashing TWRP in my oldest attempt at rooting, I got the message "system mount fail" when installing the magisk zip, but it never progressed beyond that and my at-the-time rooted phone worked perfectly.
This is my first Android phone after years of Apple(also my first thread here), and I have been excited and experimenting with it a lot, though I've only had it for less than 3 months. I would be really grateful if you guys could help me.
Thank you for the collaboration.
Do not turn it off. Seems that ends in instant brick. Try flashing the return to stock zip
crixley said:
Do not turn it off. Seems that ends in instant brick. Try flashing the return to stock zip
Click to expand...
Click to collapse
All right, will try. Thanks for the tip
Make sure you have a good cable and good fastboot in your computer
Sent from my PH-1 using XDA Labs
So I was able to pass through some problems from before, but one still persists. When I run the command "fastboot flash-all" on my command prompt, it shows all the options for fastboot, while only "flash-all" shows that there is no such command. I have also tried "fastboot flashall", but that shows the message:
error: neither -p product specified nor ANDROID_PRODUCT_OUT set.
Sorry, I know this is not the fastboot thread, but I'm really lost here.
Shiro744760 said:
So I was able to pass through some problems from before, but one still persists. When I run the command "fastboot flash-all" on my command prompt, it shows all the options for fastboot, while only "flash-all" shows that there is no such command. I have also tried "fastboot flashall", but that shows the message:
error: neither -p product specified nor ANDROID_PRODUCT_OUT set.
Sorry, I know this is not the fastboot thread, but I'm really lost here.
Click to expand...
Click to collapse
flash-all is a batch/script file, its not a fastboot command. You simply need to run on Windows
Code:
.\flash-all.bat
or Linux/MacOS
Code:
./flash-all.sh
Just open up a terminal/command prompt, type flash and then hit tab and it will autocomplete the full path.
It worked!
Thought it was already gone for good, I can barely believe it
Thank you very much for all of you, it really meant a lot your help!