fastboot flash boot - data transfer failure unknown error - Android Q&A, Help & Troubleshooting

Hello,
i used insecure boot and root trying to root my phone, which was a huge mistake as i noticed a few minutes later since i cant startup anymore and only get into bootloader.
Now I'm trying to flash my stock rom back.
My CID is VODAP102 and my Version is 3.14.161.27 so i downloaded the rom and tried "fastboot flash boot boot.img" the result is:
sending 'boot' <8192 KB>...
FAILED <data transfer failure <Unknown error>>
finished. total time: 0.158s
So well yeah, can anyone tell me why I get this error and how to fix it?

anyone?

push

so this is a rather rare problem it seems?

Ok try flashing rom using android download tool.
Sent from moon to earth........

Not working, which is probably no suprise since it works with the normal files.

Related

[Q] Problems flashing radio.img. Help please!

I have successfully unlocked my bootloader using the htcdev.com way. Then I tried to flash FlyHigh ROMv1.2, unfortunately my Wi-Fi is unable to turn on. I get Error everytime I try to turn on my wi-fi. Then I tried to flash radio.img using the fastboot command: "fastboot flash radio radio.img" but it gives me an error message.
Code:
sending 'radio' (256000 KB)...
OKAY [ 4.161s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.082s
I was able to flash boot, recovery, the only thing that failed was radio.
Help me please.
EDIT: I got HC working, so nevermind.
i too have the same problem and am going round in circles please help
You need to flash the boot.img
mcord11758 said:
You need to flash the boot.img
Click to expand...
Click to collapse
thanks for the reply so i flash he boot.img rather than radio.img ie fastboot flash boot boot.img rather than fastboot flash radio radio.img
Correct

[Q] recovery flash failed.

Current state:
Hboot 1.50 Unlocked S-ON
Boots into stock ROM
I was stuck in a boot loop and couldn't get into recovery so I relocked my phone and ran RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.
Phone booted correctly after the RRU and was able to unlock the device. I went back and followed the instructions HERE to flash TWRP recovery. The exact same way that I had originally flashed.
When I was trying to Flash my recovery I received this:
Code:
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5068 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
1. Am I screwed?
2. What can I do to prevent this in the future?
3. How do I fix it?
franciumgoesboom said:
Current state:
Hboot 1.50 Unlocked S-ON
Boots into stock ROM
I was stuck in a boot loop and couldn't get into recovery so I relocked my phone and ran RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.
Phone booted correctly after the RRU and was able to unlock the device. I went back and followed the instructions HERE to flash TWRP recovery. The exact same way that I had originally flashed.
When I was trying to Flash my recovery I received this:
Code:
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5068 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
1. Am I screwed?
2. What can I do to prevent this in the future?
3. How do I fix it?
Click to expand...
Click to collapse
1. No.
2. Nothing, it happens sometimes.
3. Maybe a corrupt download? Try again with a new copy of recovery.
If that doesn't work, try a different recovery.
I receive that error no matter which recovery I try.
The first file I tried in the OP was the same file that I had used when I originally started flashing. I just tried with twrp 2.0 and the same thing happens.
Code:
C:\Android>fastboot flash recovery twrp-shooter-2.0.0RC0.img
sending 'recovery' (5122 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.012s
Maybe it is time to start looking at the downgrade process.

[Q] Can't flash kernel fastboot.. genius needed!! :p

Hey guys, I can't seem to flash a kernel via fastboot.
Here's my info
Phone : Xperia Mini Pro
Root : Rooted
Bootloader : Unlocked
Android Version : 2.3.4 (but have tried with 4.0.4 too)
USB debugging on
MSC mode activated
Unknown souces : checked
LOG :
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
I'm trying to install CM9, I extracted boot.img
fastboot detects device but fails when trying to flash
Any ideas please?
(if you need more info, more than welcome)
Try to redownload the kernel,Maybe that will work Or try to use Flashtool to flash the kernel
Sent from my Xperia Mini using XDA Premium
Singgih4050 said:
Try to redownload the kernel,Maybe that will work Or try to use Flashtool to flash the kernel
Sent from my Xperia Mini using XDA Premium
Click to expand...
Click to collapse
I've tried several different kernels and I've tried with flashtool and Command Prompt
Mikeboss71 said:
I've tried several different kernels and I've tried with flashtool and Command Prompt
Click to expand...
Click to collapse
Do you have tried to install other kernel?
Sent from my Xperia Mini using XDA Premium
Singgih4050 said:
Do you have tried to install other kernel?
Sent from my Xperia Mini using XDA Premium
Click to expand...
Click to collapse
yeah i've tried to flash different kernels but still the same problem :/
which method you are using?
Try with my tool' in my signature
Sent from my WT19a using xda app-developers app
Did you unlock your bootloader via sony or via testpoint method?
Have you checked *#*#7378423#*#* and then Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, it's another problem...
To all the ppl who replied before - Did you even read the log?
Mikeboss71 said:
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
Click to expand...
Click to collapse
"Unrecognized command"
You need to use the following command:
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Someguyfromhell said:
To all the ppl who replied before - Did you even read the log?
"Unrecognized command"
You need to use the following command:
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Click to expand...
Click to collapse
But normally it should have worked, cause with flashtool it should work. Doesn't flashtool do same command like
Code:
fastboot flash boot boot.img
?
Mikeboss71 said:
Hey guys, I can't seem to flash a kernel via fastboot.
Here's my info
Phone : Xperia Mini Pro
Root : Rooted
Bootloader : Unlocked
Android Version : 2.3.4 (but have tried with 4.0.4 too)
USB debugging on
MSC mode activated
Unknown souces : checked
LOG :
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
I'm trying to install CM9, I extracted boot.img
fastboot detects device but fails when trying to flash
Any ideas please?
(if you need more info, more than welcome)
Click to expand...
Click to collapse
I believe it is a problem with your controller manager kernel. This can occur because of a problem with the remote connections with the driver files. Try flashing your ROM STOCK then do root and then try to apply the kernel
Sorry guys I've been away for a while so I've kinda had to put this on the back burner. but I'm back now
@daydu19
I've tried both methods, Flashtool and through Command Prompt using
Code:
fastboot flash boot boot.img
&
Code:
fastboot -i 0x0fce flash boot boot.img
but no joy
EDIT: I can't unlock my phone with testpoint because of the new securities, my phone is "12W27" :/
@mihahn
I'm not quite sure how I unlocked it I tried several ways, testpoint & sony, the weird thing is that I didn't think that either of them worked but I'm able to flash FTF files with flashtool and also Flashtool says that my bootloader is already unlocked...
Code:
Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
And lastly
Have you checked *#*#7378423#*#* and then Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, it's another problem...
Click to expand...
Click to collapse
It says that it is allowed
@xdevilium
Thanks, I'll try this out and let you know if that helps
EDIT: Nope, doesn't work either
@eltonpestana
I've flashed my device multiple times back to stock to 2.3.4 and 4.0.4, they're FTF files that I found on here but that was the only way I managed to get my phone to work again, When I tried flashing the kernels through fastboot, it came up the errors I mentioned and by so Bricked my phone...
The one thing I haven't tried yet is to use Sony PC companion to "reset" my phone (mainly due to my painfully slow internet connection) but I'm not sure that will do much good seeing as it will restore it to 4.0.4 making it impossible to root and I'll end up having to flash the other FTF again.. no?
is it possible to download a custom kernel as a FTF file and then flash it rather than going through fastboot?
because I can flash the stock kernels (that are in the FTF files) that I got
Worst case scenario are there any good ICS ROMS that will work with the stock kernel?
Try flashing stock ftf and then it should get work done.
Sent from my WT19i using xda app-developers app
---------- Post added at 05:58 PM ---------- Previous post was at 05:51 PM ----------
Apparently not . But cm 7.2 works with stock kernel.
Sent from my WT19i using xda app-developers app
I've already tried :/
thanks, CM 7.2 is gingerbread though, ICS is nicer
anyone?
Heres the new log
C:\Users\Mike\Desktop\fastboot>fastboot devices
YT9001KGWM&ZLP fastboot
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.001s
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
(bootloader) USB download speed was 2505kB/s
OKAY [ 2.030s]
writing 'boot'...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 2.032s
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
FAILED (unknown status code)
finished. total time: 1.005s
mihahn said:
But normally it should have worked, cause with flashtool it should work. Doesn't flashtool do same command like
Code:
fastboot flash boot boot.img
?
Click to expand...
Click to collapse
I wonder can anyone help me with this? I recently unlocked my bootloader (with wotanserver.com - test point method) and have since been trying out new kernels.
Unfortunately, I've had some problems with Sirkay's Advanced Stock .587 Kernel when I flash it. http://forum.xda-developers.com/showthread.php?t=1544513
I followed his flashing with flashtool instructions (standard procedure). My phone appears to boot up as normal at first, (the kernel's preinstalled CWM recovery works too) but after the initial boot logo & brightening screen that indicates CWM is present - the screen then just goes black with white LED on (with screen backlight v. slightly on) and nothing else happens, i.e. the phone is well and truly stuck.
The end result is that I have to flash back to the kernel I was previously using. There's nothing in the Flashtool log to suggest any problem with the flashing either, and there's been no problem flashing any .img or .sin files until now - so I assume I have all the correct drivers etc.
Am I overlooking something obvious here? Would be very glad to someone's opinion, this is driving me nuts!
Device: ST18i (unlocked bootloader)
ROM version: Iced Bean 2.1 [.587] - Can be used with any kernel (according to the author)
Baseband version: .77

Am I done with my phone?

Long story short, I tried to flash new rom on my Mt2-L02 mate2 and failed and its bootlooping (at Huawei Ascend screen and keep rebooting) now. using the SDcard udload to load new rom don't work either. I cannot go into recovery, or boot into system.
My phone is bootloader unlocked, so I tried to flash (extract from a rom) boot.img, recovery.img and is ok but when flashing system.img, it stucked in writing 'system'... for long time.... so I tried fastboot erase system -w and get FAILED (remote: Command not allowed)... why is it so? my phone is already unlocked. I tried unlock again and flash the system.img, same problem.
So... I'm screwed?
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
kimtyson said:
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
Click to expand...
Click to collapse
Only have 1 pc, yes, I'm flashing MT2-L02 ROM, tried alot of version but discovered only these version rom (b408, b603, b606, b607) able to write the system.img, original out of box android version for my phone is 4.4.2. but still bootlooping after flashing boot.img, recovery.img and system.img. I think only custom recovery can save now, but there is none for this model... or maybe there is no hope for my phone? Maybe my phone got some system modified lock so that I'm not able to erase using flashboot?
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
C:\adb>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
If I'm able to erase those, I'm might solved the bootlooping problem..
Try using this thread as reference, http://forum.xda-developers.com/asc...to-fix-soft-bricked-phone-using-twrp-t2886630. It's for a different model so just use your stock ROM in place of the L03 ROM. I'm not sure how to help beyond that. There has to be a way to return to stock on the L02.
Maybe this message is late, pls try following
http://pan.baidu.com/s/1dDpc4eP
http://www.huaweirom.com/rom/mate2/2619.html
usb flash instructions:
http://www.huaweirom.com/guide/2621.html
You may need to use google translate since all the info is in Chinese
Basically they are saying you should use B117 if B4xx not working.

Bricked p20 lite

Hello first time here
i am stuck on fastboot
i was following this guide
My complete bootloader unlock and root guide.
So I just got this phone just for fun, it was 75 USD, and went straight to XDA to root it so i can remove some bloat etc. but holy moly i ended up have 10 tabs with different guides open, i have compiled what I did to get this phone rooted. I...
forum.xda-developers.com
i flashed magisk from fastboot after that i fastboot into recovery ...nothink happen its just say the unlock waring and never boot i tried boot into bootloader too didnt fix it .
Please help me its my daily phone
Thank you
deadweiler said:
Hello first time here
i am stuck on fastboot
i was following this guide
My complete bootloader unlock and root guide.
So I just got this phone just for fun, it was 75 USD, and went straight to XDA to root it so i can remove some bloat etc. but holy moly i ended up have 10 tabs with different guides open, i have compiled what I did to get this phone rooted. I...
forum.xda-developers.com
i flashed magisk from fastboot after that i fastboot into recovery ...nothink happen its just say the unlock waring and never boot i tried boot into bootloader too didnt fix it .
Please help me its my daily phone
Thank you
Click to expand...
Click to collapse
Try to flash from fastboot kernel, ramdisk and recovery_ramdisk (EMUI 8.0, right?)
https://mega.nz/file/4w9SWAxS#WlHTqaQBGk31Wi6qohVgwbOEubiS2fnKhHTlMBWe2CY
https://mega.nz/file/4h9wGKIa#VMNFjHk0IfyHBWT5JjiJGKveN4jMt9dCXmyl84D7vlE
https://mega.nz/file/BklwBb6Z#S0ZrfWNik5Wd5R_MO7wmmn9432uAcV8qyyvqxy9VwqU
thanks for fast response i ll try it now
yes i am on 8.0.0
C:\platform-tools>fastboot flash recovery RECOVERY_RAMDISK-ANE-8.0.img
Sending 'recovery' (32768 KB) OKAY [ 0.961s]
Writing 'recovery' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
deadweiler said:
yes i am on 8.0.0
C:\platform-tools>fastboot flash recovery RECOVERY_RAMDISK-ANE-8.0.img
Sending 'recovery' (32768 KB) OKAY [ 0.961s]
Writing 'recovery' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
Click to expand...
Click to collapse
Wrong command
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
iflash all u send .my device is trying to boot now but its just shows the huawei logo and then again it say the device is unlocked warning
After a lot of bootloops it gave me an option to download latest recovery and firmware so i am downloading it ... You are the best !
Null.

Categories

Resources