[Q] Fastboot 'Bad File Discriptor', or Freezing on Flash - Streak 5 Q&A, Help & Troubleshooting

Hi All,
I've just got myself a Dell Streak, which I am trying to flash with the elloh ROM (following steps 1-8 here http://forum.xda-developers.com/showpost.php?p=23527490&postcount=216). I'm using Linux (Ubuntu), and have all the Android SDK etc installed, and appearing to be working.
When I " sudo fastboot -i 0x413c flash recovery recovery.img " I get the following:
Code:
sending 'recovery' (3434 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I have also tried running the same command through VirtualBox (running WinXP), which seems to get much further. I get:
Code:
sending 'recovery' (3434 KB)
OKAY [0.230s ]
writing 'recovery'...
at which point the Streak displays 'Download RECOVERY Done', and nothing else happens. The DOS prompt appears to still be 'writing', and the only way of getting out is a Ctl+C. Having tried this and continued with the instructions, the Streak produces a lot more errors during the update (which I am assuming are related to this, and have ended up bricking my device).
Does anyone have any suggestions as to what my problem might be? Either with VM or running in 'pure linux'?
Cheers
Adam

webbsimax said:
Hi All,
I've just got myself a Dell Streak, which I am trying to flash with the elloh ROM (following steps 1-8 here http://forum.xda-developers.com/showpost.php?p=23527490&postcount=216). I'm using Linux (Ubuntu), and have all the Android SDK etc installed, and appearing to be working.
When I " sudo fastboot -i 0x413c flash recovery recovery.img " I get the following:
Code:
sending 'recovery' (3434 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I have also tried running the same command through VirtualBox (running WinXP), which seems to get much further. I get:
Code:
sending 'recovery' (3434 KB)
OKAY [0.230s ]
writing 'recovery'...
at which point the Streak displays 'Download RECOVERY Done', and nothing else happens. The DOS prompt appears to still be 'writing', and the only way of getting out is a Ctl+C. Having tried this and continued with the instructions, the Streak produces a lot more errors during the update (which I am assuming are related to this, and have ended up bricking my device).
Does anyone have any suggestions as to what my problem might be? Either with VM or running in 'pure linux'?
Cheers
Adam
Click to expand...
Click to collapse
I have the same issue. I mean I didn't tried to copy with windows because I don't have it.
I'm trying to find any usefull information how to flash recovery with fastboot to my dell streak 5 under ubuntu for 2 days but I haden't found solution.
Whenever I want to send file in fastboot mode I get:
Code:
[email protected]:~/Pobrane/DSC_flashme2$ sudo fastboot -i 0x413c flash amss amss.mbn
sending 'amss' (15780 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
any ideas what to do?
Code:
sudo fastboot -i 0x413c reboot
works fine

I have the same issue
i´m using Stable Clockwork Mod Recovery for Desire C from here but, i get this error:
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
im using linuxmint x86

abr4xas said:
i´m using Stable Clockwork Mod Recovery for Desire C from here but, i get this error:
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
im using linuxmint x86
Click to expand...
Click to collapse
obviously it will fail because you are not using the one for streak 5. we have our own working recovery you know.

Had the same problem, using an other fastboot (the one found on http://forum.xda-developers.com/showthread.php?t=1067273) was the solution for me. I'm using a 64-bit Ubuntu 12.04.

Related

Anybody having tried fastboot oem format

Getting frustrated with the likes of:
$ fastboot flash tombstones tombstones.img.ext4
sending 'tombstones' (114688 KB)...
OKAY [ 28.674s]
writing 'tombstones'...
FAILED (remote: size too large)
finished. total time: 28.679s
I was wondering if in all failed attempts to manually make space for such using:
$ fastboot erase system/cache/data/etc.,
I wouldn't be better off doing a:
$ fastboot oem format ?!?
Your mediapad bricked now.
You need linux-pc & try to use "dd" command for restore all partitions of your pad.

TWRP Flash with too many link at boot

Hello,
I ‘ve tried to flash ma XIAOMI REDMI 3 PRO with twrp_ido, and now my phone cannot start, it is blocked on MI logo.
My phone is unlocked.
Fastboot is available.
Flash is Ok, but the recovery fastboot boot command is on error :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (15502 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.204s]
finished. total time: 0.744s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.626s
I’ve tried to flash manually all IMG from a stable fastboot ROM. Everythings rules but I’m staying blocked on the MI logo after rebooting
I’ve tried many cable, many computers, many MIFLASH, many TWRP sources many forums but still on same error after rebooting :
I’ve tried also to install several rom Stable /DEV fastboot with fastboot option, it doesn’t work, a readrobust js encountered
I’m blocked since several weeks and I don’t know what to do.
Could you help me your assistance will be very (very very) appreciated.
Thanks in advance
Philippe

YuYureka stuck in FASTBOOT

Hi everyone.
I had a working Lineage OS 14.1 installed on my yureka device.
I got the newer version TWRP and instead of going to install the latest update from COMMAND PROMPT , i used FLASFHFIRE and this corrupted my device.
My phone when switched OFF shows the battery indications of charging, when connected to charger.
But, doesn't start when switched ON and when connected to laptop, shows the YU logo and goes into FASTBOOT mode.
Code:
$ fastboot devices & $ fastboot -i 0x1ebf devices
detects the phone and gives this
4a252f6 fastboot
Click to expand...
Click to collapse
But, any other FASTBOOT command to flash the boot or recovery fails with error , for the first run
Error 1 :
Code:
D:\RootingKit\platform-tools>fastboot flash boot 15_April_2018_Boot.img
target reported max download size of 268435456 bytes
sending 'boot' (20480 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 5.001s
And successive runs shows a different error
Error 2:
Code:
D:\RootingKit\platform-tools>fastboot flash boot 15_April_2018_Boot.img
target didn't report max-download-size
sending 'boot' (20480 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s
Now, when i remove the cable and connect it back then again the first error message is observed.
I have tried all cables from different phones, samsung xperia yureka and others and not able to flash. Also, i have tried on different USB ports of my laptop and no SUCCESS.
Please help me out here.

bricked p20 lite

Hello guys, i bricked my phone and now i get errors:
Error!
Func NO : 11 (reovery image)
Error NO : 2 (load failed!)
I have unlocked bootloader, access to fastboot and stock recovery. Any idea how to fix it?
I can't flash anything becouse i get error FAILED (remote: Command not allowed). I have driver for my phone (Android ADB Interface)
D:\ROOT\Minimal ADB and Fastboot>fastboot devices
9WV7N18425025395 fastboot
D:\ROOT\Minimal ADB and Fastboot>fastboot flash ramdisk patched_ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (8638 KB)...
OKAY [ 0.268s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.276s
D:\ROOT\Minimal ADB and Fastboot>
edit.
I had to relock bootloader and i get access to stock recovery, form there i can dowload software last version
IDeeJay91 said:
Hello guys, i bricked my phone and now i get errors:
Error!
Func NO : 11 (reovery image)
Error NO : 2 (load failed!)
I have unlocked bootloader, access to fastboot and stock recovery. Any idea how to fix it?
I can't flash anything becouse i get error FAILED (remote: Command not allowed). I have driver for my phone (Android ADB Interface)
D:\ROOT\Minimal ADB and Fastboot>fastboot devices
9WV7N18425025395 fastboot
D:\ROOT\Minimal ADB and Fastboot>fastboot flash ramdisk patched_ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (8638 KB)...
OKAY [ 0.268s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.276s
D:\ROOT\Minimal ADB and Fastboot>
edit.
I had to relock bootloader and i get access to stock recovery, form there i can dowload software last version
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p20-lite/help/solution-nova-3e-p20-lites-brock-bolt-t3816608 my Solution
César Terrazas said:
https://forum.xda-developers.com/huawei-p20-lite/help/solution-nova-3e-p20-lites-brock-bolt-t3816608 my Solution
Click to expand...
Click to collapse
i cant used this method becouse i had FRP locked and i cant flash anything...
IDeeJay91 said:
Hello guys, i bricked my phone and now i get errors:
Error!
Func NO : 11 (reovery image)
Error NO : 2 (load failed!)
I have unlocked bootloader, access to fastboot and stock recovery. Any idea how to fix it?
I can't flash anything becouse i get error FAILED (remote: Command not allowed). I have driver for my phone (Android ADB Interface)
D:\ROOT\Minimal ADB and Fastboot>fastboot devices
9WV7N18425025395 fastboot
D:\ROOT\Minimal ADB and Fastboot>fastboot flash ramdisk patched_ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (8638 KB)...
OKAY [ 0.268s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.276s
D:\ROOT\Minimal ADB and Fastboot>
edit.
I had to relock bootloader and i get access to stock recovery, form there i can dowload software last version
Click to expand...
Click to collapse
I've the same problem if you get the solution please inform me as well
Thanks
IDeeJay91 said:
i cant used this method becouse i had FRP locked and i cant flash anything...
Click to expand...
Click to collapse
Watch a YouTube tutorial to umlock FRP

Download Mode - Restart loop after installing OS

Adroid One 10
Unlock solved and installed the lineage OS a several times in twrp with success according to the given instruction here:
https://raw.githubusercontent.com/RaghuVarma331/changelogs/master/crossdevelopment/abcrins.txt
but the phone didnt boot the OS after restarting neither in slot A nor B. In twrp u could read that there was "no OS installed" (??).
In the last try i changed the slot before installing and now the phone hangs in a restart loop with download mode and i connot turn down the phone or get back to twrp. Trying to connect it by adb to restart twrp is not working....
=========================
My errors while trying to get out:
=========================
fastboot boot twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot B:\Various\Nokia\TWRP\twrp.img
downloading 'boot.img'...
OKAY [ 0.969s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.011s
fastboot flash recovery twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery B:\Various\Nokia\TWRP\twrp.img
target reported max download size of 402653184 bytes
sending 'recovery' (42412 KB)...
OKAY [ 0.953s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.968s
So right now I'm at the end with my rudementary skills here.
Any idea how to get back to the point with twrp and installing an OS?
Thanks.
In case that no one else answers but someone else have the same problems , I write my solutions here.
.......
I got back to twrp by changing the slot in ADB
fastboot --set-active=a
unfortunately the restart loop doesn't end and no OS starts wether in slot a or b.

Categories

Resources