Here is what I did.
Phone was running with Android 6.0+EMUI4.0 beta version. I unlocked the bootloader by acquiring unlock code from Huawei website.
After unlocking bootloader, when I try to flash TWRP, it says
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery kiwi_twrp_5-14_recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (45116 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
I tried above procedure several times but no luck. So I rebooted my devices, and then booted it again in bootloader mode and then fired command to flash recovery, but this time new error came:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery kiwi_twrp_5-14_recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (45116 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
In both of the above cases fastboot devices working good and showing my device in the list. Please help me here :crying:
[SOLVED]
WIth USB 3.0 ports on my computer, fastboot didn't seem to flash the recovery. @elry567 suggested to use USB 2.0 port and fastboot worked like a charm with that
pank.dhnd said:
[SOLVED]
WIth USB 3.0 ports on my computer, fastboot didn't seem to flash the recovery. @elry567 suggested to use USB 2.0 port and fastboot worked like a charm with that
Click to expand...
Click to collapse
but still on windows 10 unable to run Shift + Command Prompt on the adb folder aswell it reboots on adb but still not able to open the .img file
kartrikpal said:
but still on windows 10 unable to run Shift + Command Prompt on the adb folder aswell it reboots on adb but still not able to open the .img file
Click to expand...
Click to collapse
are you serious ? you can't right click and choose open command prompt here ?
and what .img are you trying to open ? are you trying to flash twrp ?
Code:
C:\fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\fastboot>adb devices
List of devices attached
GFMDU1********** device
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot boot C:\fastboot\kiwi_recovery.img
downloading 'boot.img'...
OKAY [ 1.433s]
booting...
OKAY [ 0.020s]
finished. total time: 1.455s
C:\fastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.002s
C:\fastboot>
clsA said:
are you serious ? you can't right click and choose open command prompt here ?
and what .img are you trying to open ? are you trying to flash twrp ?
Code:
C:\fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\fastboot>adb devices
List of devices attached
GFMDU1********** device
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot boot C:\fastboot\kiwi_recovery.img
downloading 'boot.img'...
OKAY [ 1.433s]
booting...
OKAY [ 0.020s]
finished. total time: 1.455s
C:\fastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.002s
C:\fastboot>
Click to expand...
Click to collapse
Yes, i'm unable to do that, instead just unlocked my Phone using Windows 10 and Flashed Twrp.img using Ubuntu - Using Linux its that easy but on Windows 10 it force closes ! I could not find solution .
@clsA
Anyways i'm done with Flashing but after first boot there was seemless WiFi speed seen as i have 2MbPs connection but after few hours of restoring my apps using PS it started to load slow - is there any fixes ?
pank.dhnd said:
[SOLVED]
WIth USB 3.0 ports on my computer, fastboot didn't seem to flash the recovery. @elry567 suggested to use USB 2.0 port and fastboot worked like a charm with that
Click to expand...
Click to collapse
Thank you very much...i should have come here before spending my 1 hour on trying everything else!!:good::good:
pank.dhnd said:
[SOLVED]
WIth USB 3.0 ports on my computer, fastboot didn't seem to flash the recovery. @elry567 suggested to use USB 2.0 port and fastboot worked like a charm with that
Click to expand...
Click to collapse
That is great, I'll keep it in mind always when I face issues
Related
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.
I am not able to install or boot TWRP recovery on my Redmi Note 5 Pro and I am getting this error on Linux terminal:
Code:
~$ sudo fastboot devices
2029cac7 fastboot
~$ sudo fastboot boot /home/ubuntu/Desktop/twrp.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time:0.001s
~$ sudo fastboot flash recovery /home/ubuntu/Desktop/twrp.img
target didn't report max-download-size
sending 'recovery' (36240 KB)...
FAILED (remote: unknown command)
finished. total time: 0.001s
Bootloader status says already unlocked on the settings screen and after MIUI update 8.5.2, I am facing this issue. And I was having the custom recovery already installed before I updated. Tried different cables, and different devices too :/
It seems none of the fastboot commands is now working(except the reboot commands) What to do now?
gavi7566 said:
I am not able to install or boot TWRP recovery on my Redmi Note 5 Pro and I am getting this error on Linux terminal:...
Click to expand...
Click to collapse
I don't have this device but, you should be able to obtain some member guidance within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3778049
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
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.
I've just unlocked the phone, via minimal ADB
tried fastboot getvar current-slot and got the output that my slot was a
then I've tried flashing TWRP at a utilizing
fastboot flash recovery twrp.img
then got the following output:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 803868672 bytes
sending 'recovery' (39780 KB)...
OKAY [ 1.663s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 1.695s
so, I've tried fastboot flash boot twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 803868672 bytes
sending 'boot_a' (35452 KB)...
OKAY [ 1.063s]
writing 'boot_a'...
OKAY [ 0.183s]
finished. total time: 1.254s
then I've manually pressed the power button + volume up and successfully entered TWRP
there, I've gone to advanced wipe and wiped
Dalvik / ART Cache, system, Data and Internal Storage
I didn't know Internal Storage would give me problems... After that, I couldn't access my internal storage from the PC to copy the .zip of the custom rom.
Tried going to mount into TWRP to mount different partitions, no succes.
Then I thought that maybe if I restarted the phone it would be ok. So I've restarted and TWRP told me "no system installed, do you wish to continue?" I said yes.
Now, I'm stuck at fastboot and can't boot into twrp anymore...
I've tried repeating the same commands above and got the same outputs.
fastboot flash boot twrp.img got me the "OKAY" messages. But now, even if I hold the power + vol up button, I won't get to recovery.
I've tried
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.291s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.298s
because my frient told me to do so, but this command does not exist.
How can I proceed?
Try using mi flash tool
I was also stuck in fastboot mode I then tried installing twrp again with no success.
So I then went and flashed stock rom again into my phone using mi flash tool.
(Having a new account, I can't post link to these files. So download the files from official mi website, it is available there)
Steps to flash
1- Place the Flash File on Desktop.
2- open flash tool application.
3- Assign the Folder path.
4-Go to slot a using adb
5- Click on refresh & then tap Flash button
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.