Hi there,
Need help with showthread.php?t=1785010
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
at first glance it sounds like your file is corrupt, have you already tried to redownload it?
as long as fastboot stops immediately and does not actually write stuff in your phone you should be safe anyway
Check the file for any possible download errors.
abr4xas said:
Hi there,
Need help with showthread.php?t=1785010
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
Click to expand...
Click to collapse
Try upgrading bootloader / redownloading file and flashing
abr4xas said:
Hi there,
Need help with showthread.php?t=1785010
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
Click to expand...
Click to collapse
This happened to me too, it was just that the file was not there, I had SU and path was not correct. So the next person who comes here looking for the solution for this.... yes you! do a "ls" or "dir" and see that the recovery.img or boot.img or whatever you are trying to flash is even there. :victory:
shieraz said:
This happened to me too, it was just that the file was not there, I had SU and path was not correct. So the next person who comes here looking for the solution for this.... yes you! do a "ls" or "dir" and see that the recovery.img or boot.img or whatever you are trying to flash is even there. :victory:
Click to expand...
Click to collapse
Did anybody find a solution to this problem, yet??
BTW: it says "error: cannot load 'xxxxx.img': No such file or directory" if it can't find the file. "FAILED (command write failed (Bad file descriptor))" seem to be a different issue. Maybe inside the phone, when it can't find the partition it should flash. No idea. However, I'm stuck with "FAILED (command write failed (Bad file descriptor))" and appreciate your help!
I'm trying to run it on Debian 8.1 AMD64. Here is some code:
[email protected]# fastboot -i 0x413c flash recovery 407recov.img
sending 'recovery' (3660 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[email protected]# file 407recov.img
407recov.img: Android bootimg, kernel (0x20008000), ramdisk (0x21000000), page size: 2048, cmdline (androidboot.hardware=streak)
[email protected]# cat /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", MODE="0666"
[email protected]# ls -l /etc/udev/rules.d/51-android.rules
-rw-r--r-- 1 root root 56 Sep 17 15:51 /etc/udev/rules.d/51-android.rules
[email protected]# fastboot -l devices
Default# fastboot usb:1-10
[email protected]# fastboot -i 0x413c reboot
rebooting...
finished. total time: 0.002s
[email protected]#
As you can see, "fastboot reboot" works, but not "fastboot flash". This dies with that pesky message "FAILED (command write failed (Bad file descriptor))".
[email protected]# fastboot -i 0x413c flash recovery 407recov.img
Click to expand...
Click to collapse
I don't use Debian/Linux but... Fastboot command to flash a partition would be
Code:
fastboot flash recovery 407recov.img
as I've never had to type in anything else as -i 0x413c
Sent from my HTC One_M8 using XDA Free mobile app
Antagonist42 said:
I don't use Debian/Linux but... Fastboot command to flash a partition would be
Code:
fastboot flash recovery 407recov.img
as I've never had to type in anything else as -i 0x413c
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
This "-i 0x413c" part makes the device selection specific. It's not needed if there is only one device connected.
However, I found (and fixed) the problem. More detail here:
bugs.debian.org/cgi-bin/bugreport.cgi?bug=800661
bomilkar said:
However, I found (and fixed) the problem. More detail here:
bugs.debian.org/cgi-bin/bugreport.cgi?bug=800661
Click to expand...
Click to collapse
How did you fix it? Corrected the sourcecode and recompiled android-tools-fastboot?!
PeterCxy said:
Check the file for any possible download errors.
Click to expand...
Click to collapse
Sir I want your help
E:\Mobile\adb>fastboot -i 0x2A96 boot twrp.img
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
This is show on my yophoria when I flash custom recovery
My phone is Desire HD, but this worked for me to solve the problem.
Try this:
http://forum.xda-developers.com/showthread.php?t=1474490
Originally Posted by CostaTX
Connect phone via usb and turn on debugging/just charging
Open up cmd (eventually as administrator) and type in "adb shell"
Find out how your system partition is named: "cat /proc/mounts | grep /system"
Mount system partition write/read. replace the X's "mount -o remount,rw -t yaffs2 /dev/block/XXXXX /system"
Use the terminal emulator to install the recovery:
su
flash_image recovery /sdcard/touch.img (or whatever the recovery image is named)
remount the system partition again as read only "mount -o remount,ro -t yaffs2 /dev/block/XXXXX /system
and you're done
Click to expand...
Click to collapse
"cat /proc/mounts |grep system" and command "mount -o remount,rw ..."
You can change by "mount -o remount,rw /system"
"mount -o remount,ro" by "mount -o remount,ro /system"
Code:
adb shell
$ su
# mount -o remount,rw /system
# flash_image recovery /sdcard/recovery.img
# mount -o remount,ro /system
# exit
$ exit
pls help..how to solve this.
writing 'userdata'...
FAILED (remote: flash_cmds error!
it fail when i using fastboot -w command.
my phone bricked, can use fastboot and adb.
but when i apply "update.zip via adb" using "adb sideload update.zip" it cannot read "update.zip" .
so i start using fastboot to flash but it failed.
fastboot FAILED (in various ways for various versions)
I've now tried 3 releases of android platform-tools. I had hoped that one of these included the fix posted on XCSoar forum (for the original reason for this thread) but I'm not convinced that's so. I tried both:
1) platform-tools issued with ubuntu 14.04
2) platform-tools_r25.0.5-linux
3) platform-tools_r26.0.0-rc1-linux.
When trying to upgrade my Dell Streak 5 beyond 2.2, none of these work, but of course they fail in different ways to fastboot released with ubuntu 14.04 (which is my main machine, I don't have a windows machine).
Running platform-tools_r25.0.5 or platform-tools_r26.0.0-rc1, I get:
/bin/platform-tools_r26.0.0-rc1$ sudo ./fastboot -i 0x413c flash recovery ~/recovery.img
target didn't report max-download-size
sending 'recovery' (3668 KB)...
FAILED (command write failed (Success))
finished. total time: 0.000s
Whereas running the (14.04) issued fastboot I get (notice the use of DOT/fastboot and fastboot to select the right one), I get:
sudo fastboot -i 0x413c flash recovery ~/recovery.img
sending 'recovery' (3668 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
Interestingly when I run /(25.0.5 or 26.0.0) :
$ ./fastboot -i 0x413c reboot
the DS5 doesn't reboot.
However if I run the 14.04 fastoot, ie:
$ fastboot -i 0x413c reboot
the DS5 reboots.
Has anyone else come across these problems? If so what's the solution?
SK_Raj said:
Sir I want your help
E:\Mobile\adb>fastboot -i 0x2A96 boot twrp.img
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
This is show on my yophoria when I flash custom recovery
Click to expand...
Click to collapse
solved?
Related
Feeling brave? Help me test / develop my superboot!
http://android.modaco.com/content/h...9976/13-jan-1-0-superboot-rooting-the-tattoo/
P
sorry, but your batch makes problemm...
and when i make it manual:
C:\Android\superboot>fastboot-windows boot tattoo.superboot.img
downloading 'boot.img'... OKAY
booting...
then nothing
for me doesn't work... i've got mac and the message in terminal is:
./install-superboot-mac.sh: line 3: unexpected EOF while looking for matching `''
./install-superboot-mac.sh: line 14: syntax error: unexpected end of file
and if i try to do the steps inside the script terminal says:
bash-3.2# chmod +x fastboot-mac
bash-3.2# chmod +x adb-mac
bash-3.2# ./adb-mac shell reboot oem-78
error: device not found
bash-3.2# ./fastboot-mac oem-78
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
bash-3.2# ./fastboot-mac boot tattoo.superboot.img
downloading 'boot.img'... FAILED (remote: not allow)
bash-3.2# ./fastboot-mac reboot
rebooting... (here with no reboot)
i hope this could help you...
You could try fastboot oem boot superboot.img allthough I don't think it will work, we have tried this on the Eris but who knows maybe yours will be different
Any advance on this guys?
If you need my help, just tell me, I'm newbie but I love to take risks!
I tried this method on my HTC.
downloading 'boot.img'... OKAY
booting.....
Click to expand...
Click to collapse
I waited for few min nothing happen.so un plug the cable it goes to RUU.
And then i insert the cable it rebooted.
What about this?
i'm New
Did anyone try what I said, "fastboot oem boot superboot.img" make sure you have oem in there otherwise it will just hang at booting..... I'm just curouse if it works for you guys.
I have a feeling there stuck on it same as we are, the tattoo and eris are more alike than either to the hero
binny1007 said:
Did anyone try what I said, "fastboot oem boot superboot.img" make sure you have oem in there otherwise it will just hang at booting..... I'm just curouse if it works for you guys.
Click to expand...
Click to collapse
Yup, tried that. It just boots the phone to it's current (flashed) rom
I tried using the boot command and, while it's hanging at "booting...", I sent a oem boot, but no luck
If it boots to the current flashed rom then it might have worked. you wont notice a physical different if superboot boots.
FireSokar said:
If it boots to the current flashed rom then it might have worked. you wont notice a physical different if superboot boots.
Click to expand...
Click to collapse
Interesting. When I get mine (tattoo), I'll try it out. Superboot just allows us superuser access, doesn't it? If we boot with this, then run a Terminal emulator, type 'su', we'll be able to get root (temporarily)?
Im pretty sure thats how it works, im not 100% sure im following this thread closely as we are stuck @ the exact same point on getting the droid eris rooted, better side of 2 months working on it.
The wait for my HTC Tattoo is killing me. I really want to try this out before I go back to school...
I ordered it last week sometime and it's supposedly coming next week... If it all comes to the worse, I'll just try this at school.... Hehe
Alright, I did this, and I think it may get me somewhere.
I did this while on the home screen, with USB debugging enabled. I ran the mac fastboot script, and it booted into the HTC logo screen. It said "Booting..." and got stuck.
After a minute, I yanked the USB cord out, and it dumped me at the RUU screen with text like this in my Terminal:
Terminal said:
Matthew-Coburns-MacBook:1.2-tattoo-superboot matthew$ ./install-superboot-mac.sh
Superboot for HTC Tattoo by Paul O'Brien @ http://www.MoDaCo.com
----------------------------------------------------------------
Rebooting device...
* daemon not running. starting it now *
* daemon started successfully *
0
Waiting 10 seconds for reboot...
Booting superboot...
ERROR: could not get pipe properties
downloading 'boot.img'... OKAY
booting... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
ERROR: could not get pipe properties
< waiting for device >
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
Click to expand...
Click to collapse
I then reinserted the USB cable and got this:
rebooting...
Done!
Click to expand...
Click to collapse
After that, I did some exploring with adb-mac:
Matthew-Coburns-MacBook:1.2-tattoo-superboot matthew$ ./adb-mac shell
$ ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.rc
init.goldfish.rc
init.bahamas.rc
init
default.prop
data
root
dev
$ su
su: permission denied
Click to expand...
Click to collapse
And so, I got the dreaded permission denied error! Oh well, at least I tried...
Any suggestions?
EDIT: I can do 'cat /proc/cpuinfo' and get:
Processor : ARMv6-compatible processor rev 2 (v6l)
BogoMIPS : 244.94
Features : swp half thumb fastmult edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x1
CPU part : 0xb36
CPU revision : 2
Hardware : bahamas
Revision : 0080
Serial : 0000000000000000
Click to expand...
Click to collapse
Interesting...
I have updated my nexus one to Ginger bread image GRI40 from http: //android.clients.google.com/pa...8.656099b1.zip
following this thread http: //forum.xda-developers.com/showthread.php?t=966939&page=4
But when I tried to open adb shell and want to list the content of '/data/data' directory. I get the following error:
Code:
$ adb shell
$ cd /data/data
$ su
su: permission denied
$ ls
opendir failed, Permission denied
$
and when i do 'adb remount' i get
Code:
$ adb remount
remount failed: Operation not permitted
Can you please tell me how can I open 'adb shell' to Nexus one
Thank you.
You're not rooted. That's your problem.
If you have rooted earlier, then most probably you need to re-root.
Sent from my Nexus One using XDA App
I did
$ fastboot oem unlock
...
(bootloader) Erasing userdata...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 15.000s
Click to expand...
Click to collapse
And then the phone reboots.
But I still can't get to /data/data
$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ cd /data/data
$ ls
opendir failed, Permission denied
$
Click to expand...
Click to collapse
No.
10chars...
Unlocking the bootloader disables security on the bootloader.
Rooting a phone effectively disables security on the system.
They are not the same thing...
With an unlocked bootloader you can use fastboot to flash a custom recovery, rooted system, or any other image you wish (provided it it's for your phone).
Sent from my Nexus One using XDA App
So i have installed GRI40 myself and then have done 'fastboot oem unlock'. What else do I need to do in order to root my phone?
Install custom recovery and flash su.zip through recovery...
It's all in the wiki, and many threads...
Sent from my Nexus One using XDA App
Thanks.
I have installed recovery rom recovery-RA-passion-v2.2.1.img by following this http://forum.xda-developers.com/showthread.php?t=611829
$ fastboot flash recovery recovery-RA-passion-v2.2.1.img
sending 'recovery' (3366 KB)...
OKAY [ 0.493s]
writing 'recovery'...
OKAY [ 1.261s]
finished. total time: 1.754s
Click to expand...
Click to collapse
But it still does not let me see the content of /data/data
$ adb shell
$ cd /data/data
$ ls
opendir failed, Permission denied
$ su
su: permission denied
$ exit
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Again, I am using the GingerBread build on Nexus One. Ginger bread image GRI40 from http: //android.clients.google.com/pa...8.656099b1.zip
Read post 8 again.
I have gotten the su.zip file from
http://forum.xda-developers.com/showthread.php?t=968396
put it to my sd card. 292KB
And I have booted my nexus one (installed it with ginger bread with a 0.35 HBoot loader).
And when i try to 'apply sdcard:update.zip', I selected the zip file I put in my sd card.
It sid
'Verifying update package...' E:signature verification failed. Installation aborted'.
He did say you have to flash su though...
from here http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images it said i need to also execute 'fastboot reboot recovery' after I fastboot flash install the recovery rom.
But when i execute 'fastboot reboot recovery' i get
$ fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
Click to expand...
Click to collapse
I think the 'fastboot ' command only takes 'fastboot reboot'?
You don't need to rename to update, but it doesn't matter either way. In your custom recovery, select the option to flash any zip and select the su file. If you get a verification error, turn off signature verification in your custom recovery...
The command to boot into recovery is:
fastboot boot recovery.img
(where recovery.img is the name of your recovery file)
Sent from my Nexus One using XDA App
OK, you seriously don't know what you are doing.
Follow this to the letter:
Flash your recovery.
Pick the bootloader option.
Pick the recovery option.
Download su files from: http://forum.xda-developers.com/showthread.php?t=682828
Mount the USB storage
Copy the zip file over.
Unmount USB storage.
Flash the zip you just downloaded.
You might want to flash this file, also, while you are in recovery. It will make sure your recovery doesn't disappear the next time you boot your phone...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA App
I have updated my nexus one to gingerbread 2.3.3. Is there any possible way to root without unlocking my bootloader. Thanks I'm advance.
Sent from my Nexus One using Tapatalk
If you can roll back to 2.2, yes. Not everyone can for some reason though. If you're one that can't, then you have to unlock.
Rusty! said:
If you can roll back to 2.2, yes. Not everyone can for some reason though. If you're one that can't, then you have to unlock.
Click to expand...
Click to collapse
Hmmmmm thanks rusty but I think I will wait for a possible way to root rather than unlocking my bootloader. Thanks again.
Sent from my Nexus One using Tapatalk
Most people seem to be able to roll back. You might as well try, since it won't do any harm...?
Sent from my Nexus One using XDA Premium App
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
I've been trying other things with no success.
I've installed windows on a VM and rebooted the phone into fastboot mode. When I try to list devices in fastboot I get the '?' answer as if the phone wasn't recognised.
Device drivers seem to be installed as no missing drivers appear in the device manager.
How can I fix this?
Thanks in advance!
UPDATE: Added some more info
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.017s
antoniovazquezblanco said:
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
Click to expand...
Click to collapse
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
g4b3rm4n said:
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
Click to expand...
Click to collapse
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
antoniovazquezblanco said:
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
Click to expand...
Click to collapse
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
g4b3rm4n said:
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
Click to expand...
Click to collapse
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
antoniovazquezblanco said:
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
Click to expand...
Click to collapse
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
g4b3rm4n said:
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
Click to expand...
Click to collapse
Is this also happening to you?
I would like to be able to use fastboot boot for some kernel testing... It seems there's source code for kernel building both from Huawei and the comunity and it would be nice to have a free kernel as a base for cm devel...
It is also 00:50 here (Spain)... Tomorrow will be another day, no hurry
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Kostyan_nsk said:
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Click to expand...
Click to collapse
Thank you Kostyan_nsk! I really appreciate you sharing your knowledge .
About 2 I thought the same but I was not sure... so why not trying...
About 3 do you know what are the supported commands or where to find that information? It would be nice to have a post in the developers section with some documentation for those who want to perform tests with the device .
Hi friends,
The app recommended by BQ "MTK Tool Flash" (SP_Flash_Tool_exe_Linux_v5.1612.00.100.zip) just didn't work for me on my Debian PC. There were always some excuses. So I tried some black command-line magic with fastboot and now I'm with a bricked device.
See ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5 link I cannot post...
The good news is, I have installed the TWRP (twrp-3.1.1-0-freezerfhd.img) before I shot myself in the toe. So power + volume up gives me the comforting bluish screen of TWRP.
Question is, how can I bring the lovely device back to life? I wanted to flash official Android on it (which failed - 2.3.0_20170405-1553_bq_aquaris_m10_FHD_-FW.zip) and I'd like to complete that, but if it's a no go, I can go back to Ubuntu.
I have tried installing the image zip from twrp, but it said the image has invalid zip file format!
Thanks a lot for your help
Rob
failures
I've been struggling with this one. So I can switch to the bootloader mode and run fastboot commands. However, when I try to flash the system image I get some funny error:
Code:
sudo fastboot flash system ./system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
With the flash tool (after fixing all it's complaints) I'm stuck with a timeout on detecting the USB port (while fastboot works just fine)
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
And with TWRP as mentioned earlier:
Code:
Invalid zip file format
I read the stock rom can be adjusted somehow to allow TWRP to flash it but I'm quite like what...? Android kitchen doesn't list my device as supported.
progress
Aha! This got us further:
Code:
sudo fastboot flash system -u -S 1G ./system.img
Which means do not erase the partition upfront, and sparse the file at max 1 GB.
Code:
sudo fastboot flash userdata -u -S 1G ./userdata.img
sudo fastboot flash boot -u -S 1G ./boot.img
sudo fastboot reboot
Now device is "powered by ubuntu" and stuck there... not sure what's happening
S now I tried flashing some more exotic partitions and the device is completely dead. I hope BQ can help...
undead
Wow, so BQ contacted me right away with a hard reset procedure. The key bit of information I must have overlooked somewhere is that for the flash tool to detect the device, the device must be plugged in while it's off and while the tool is waiting. We're now "powered by android" and system is ready to use. Oh my... thanks BQ
Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.
Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445