Hello.
I've built a custom kernel for Dell Streak.
When I try to boot it I get a message:
Code:
$ ./fastboot-linux -i 0x413c -c 'root=/dev/mmcblk0p2 rw rootfs=ext2 init=/sbin/init rootwait noinitrd' boot arch/arm/boot/zImage
creating boot image...
creating boot image - 2144256 bytes
downloading 'boot.img'... OKAY
booting... FAILED (remote: invalid command)
Does this mean that Streak fastboot does not support booting custom kernel?
- -
Anyway, I flashed it with:
Code:
$ ./fastboot-linux -i 0x413c -c 'root=/dev/mmcblk1p2 rw rootfs=ext2 init=/sbin/init rootwait noinitrd' flash:raw boot arch/arm/boot/zImage
creating boot image...
creating boot image - 2144256 bytes
sending 'boot' (2094 KB)... OKAY
writing 'boot'... OKAY
After booting I have a "Dell logo reboot loop".
Is there a way of getting kernel messages somehow, to see why is it failing?
Sent from my Dell Streak using XDA App
I`d love to know more about this as well. Did some Dev`ing many years ago in a galaxy far far away.
I was talking to defet at #modaco, and apparently ARM kernel needs board specific files in arch/arm/mach-msm/ that describe the hardware board name/id, features and memory layout.
Without this, there is no way of running a kernel on Streak board, because kernel just is unaware of the board features. The kernel checks the board name on boot and if it is not compiled for this exact board it just stops booting.
So, without kernel sources from Dell, we are totally screwed.
You may want to support http://forum.xda-developers.com/showthread.php?t=761856 because without this you may as well dream of running Linux or Froyo on Streak.
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.
Hi,
I'm fairly green when it comes to Android devices, but my understanding is that when using "fastboot," I ought to be able to select "hot boot" a kernel and ramdisk using the "boot kernel <ramdisk.gz> command. However, for my Xperia Z Ultra, I'm finding that when I attempt this, I am told:
"FAILED (remote: dtb not found)"
A bit of research indicates that this probably refers to a "device tree blob", something which I understand is used to inform the kernel as to how to access devices (http://xillybus.com/tutorials/device-tree-zynq-1). However, I can't find any information pertaining to the inclusion of a "dtb" when using fastboot.
In my probing of various "sin" files, I've managed to extract the kernel.sin for the HK 461 amd 471 ROM versions. They present me with an elf file. This elf file, in turn, can be extracted into three files. The kernel image, the ramdisk gzip and a ".3" file, which I can only assume is the dtb.
My question is whether it is possible to reassemble these files into an elf, and subsequently a sin file so that I can then put this back into the original ROM ftf. Failing this, I'd like to be able to simply hotboot the kernel and a modified ramdisk (that leaves / and /system mounted as rw and runs adb as "root" rather than "shell").
I'm not asking for a handout or a painstakingly written HOWTO, just a pointer in the right direction, if possible.
Interestingly, if I try to simply "hot boot" the extracted elf, it seems to upload perfectly to the phone, but then the phone hangs when trying to boot:
Code:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce boot D:\kernel-461.elf
creating boot image...
creating boot image - 8663040 bytes
downloading 'boot.img'...
OKAY [ 0.283s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 413.509s
The "FAILED" is reported after I simply unplug the phone. At this point, the phone is very much locked up with the blue LED illuminated. After a few panicked moments, I realised that Vol-Up + Power is a force-reset key combination (it causes the vibration motor to pulse three times, then reboots).
For completeness, here's what happens when I try "hot booting" the extracted kernel and my custom ram disk:
Code:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce boot D:\kernel-461.elf.Image D:\ramdisky.gz
creating boot image...
creating boot image - 8329216 bytes
downloading 'boot.img'...
OKAY [ 0.274s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.322s
Chinese, all i see here i chinese One thought though, wouldn't the guys over at the Xperia Z forum be at any assistance? They are working with Sony hardware after all, and maybe they can give you some tips and ideas? I'm just thinking here though
Anywho, keep it up. It's only a matter of time until you crack the code!
ShALLaX said:
Hi,
I'm fairly green when it comes to Android devices, but my understanding is that when using "fastboot," I ought to be able to select "hot boot" a kernel and ramdisk using the "boot kernel <ramdisk.gz> command. However, for my Xperia Z Ultra, I'm finding that when I attempt this, I am told:
"FAILED (remote: dtb not found)"
A bit of research indicates that this probably refers to a "device tree blob", something which I understand is used to inform the kernel as to how to access devices (http://xillybus.com/tutorials/device-tree-zynq-1). However, I can't find any information pertaining to the inclusion of a "dtb" when using fastboot.
In my probing of various "sin" files, I've managed to extract the kernel.sin for the HK 461 amd 471 ROM versions. They present me with an elf file. This elf file, in turn, can be extracted into three files. The kernel image, the ramdisk gzip and a ".3" file, which I can only assume is the dtb.
My question is whether it is possible to reassemble these files into an elf, and subsequently a sin file so that I can then put this back into the original ROM ftf. Failing this, I'd like to be able to simply hotboot the kernel and a modified ramdisk (that leaves / and /system mounted as rw and runs adb as "root" rather than "shell").
I'm not asking for a handout or a painstakingly written HOWTO, just a pointer in the right direction, if possible.
Interestingly, if I try to simply "hot boot" the extracted elf, it seems to upload perfectly to the phone, but then the phone hangs when trying to boot:
Code:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce boot D:\kernel-461.elf
creating boot image...
creating boot image - 8663040 bytes
downloading 'boot.img'...
OKAY [ 0.283s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 413.509s
The "FAILED" is reported after I simply unplug the phone. At this point, the phone is very much locked up with the blue LED illuminated. After a few panicked moments, I realised that Vol-Up + Power is a force-reset key combination (it causes the vibration motor to pulse three times, then reboots).
For completeness, here's what happens when I try "hot booting" the extracted kernel and my custom ram disk:
Code:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce boot D:\kernel-461.elf.Image D:\ramdisky.gz
creating boot image...
creating boot image - 8329216 bytes
downloading 'boot.img'...
OKAY [ 0.274s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.322s
Click to expand...
Click to collapse
yes, same thing in here (it seems newer kernel with dtb)
how to extract them correctly and re-pack to work?
http://forum.xda-developers.com/showthread.php?t=2428117
hkfriends said:
yes, same thing in here (it seems newer kernel with dtb)
how to extract them correctly and re-pack to work?
http://forum.xda-developers.com/showthread.php?t=2428117
Click to expand...
Click to collapse
Why extract it at all? Sony has released the kernelsourcecode and we can create a dtb from scratch. Btw dtb and kernel are corresponding, so better not always use 475 dtb for ever!
So you guys better grab the kernel opensource and compile it sourself instead breaking heads on howto extract.
See our repos custombootimg.mk for the mkbootimg parameters once you compiled dt.img
Regards
Gesendet von meinem C6833 mit Tapatalk 4
I wasn't looking at how to extract it, but how to include it in the ELF. I'll take a look at the mk file, got a link?
Sent from my GT-I9500 using xda app-developers app
Hey all i ran into a problem yesterday i downgraded my fire hdx tablet to 13.3.2.8 and everything went fine except that my boot image and recovery partitions got messed up so now when i turn it on it goes straight into fastboot mode i have the 32 GB model 2013 edition which is a 7 inch thor based tablet i heard someone was able to flash fastboot via linux but i cant get it to work on windows 7 64 bit so im going to try flashing a new boot image and recovery partition via linux to see if that will fix the problem but i would appreciate the assistance. Thanks
blue9a said:
Hey all i ran into a problem yesterday i downgraded my fire hdx tablet to 13.3.2.8 and everything went fine except that my boot image and recovery partitions got messed up so now when i turn it on it goes straight into fastboot mode i have the 32 GB model 2013 edition which is a 7 inch thor based tablet i heard someone was able to flash fastboot via linux but i cant get it to work on windows 7 64 bit so im going to try flashing a new boot image and recovery partition via linux to see if that will fix the problem but i would appreciate the assistance. Thanks
Click to expand...
Click to collapse
There is no known (or at least widely recognized) recovery from a catastrophic 3.2.8 boot failure. As the bootloader remains locked (and hence fastboot crippled) I do not believe you will have success restoring recovery or flashing a new boot image. Sorry - I'm afraid you now own a brick.
Davey126 said:
There is no known (or at least widely recognized) recovery from a catastrophic 3.2.8 boot failure. As the bootloader remains locked (and hence fastboot crippled) I do not believe you will have success restoring recovery or flashing a new boot image. Sorry - I'm afraid you now own a brick.
Click to expand...
Click to collapse
im testing it on ubuntu linux 14.04 LTS its reporting failure unknown command then ready so i guess thats something
blue9a said:
im testing it on ubuntu linux 14.04 LTS its reporting failure unknown command then ready so i guess thats something
Click to expand...
Click to collapse
Believe response would be similar regardless of host. With a locked bootloader only a few fastboot commands work - none of them useful. Maybe you'll find a workaround!
Davey126 said:
Believe response would be similar regardless of host. With a locked bootloader only a few fastboot commands work - none of them useful. Maybe you'll find a workaround!
Click to expand...
Click to collapse
python3 /home/jeremy/Desktop/cuberHDX.py 0x45202b1325
File "/home/jeremy/Desktop/cuberHDX.py", line 64
print 'Usage: %s [boot.img|serial]' % path.basename(argv[0])
^
SyntaxError: invalid syntax
hmm not sure if i did this right
[email protected]:~$ fastboot -i 0x1949 oem device-info
...
(bootloader) Device tampered: true
OKAY [ 0.036s]
finished. total time: 0.036s
[email protected]:~$ -i 0x1949 oem unlock 0x45202b1325
-i: command not found
[email protected]:~$ /fastboot -i 0x1949 devices
bash: /fastboot: No such file or directory
[email protected]:~$ fastboot -i 0x1949 devices
D0FCA0A03523013E fastboot
[email protected]:~$ fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
error: cannot load 'unlock.signed': No such file or directory
[email protected]:~$ fastboot -i 0x1949 flash boot '/media/jeremy/MULTIBOOT/boot.img'
target reported max download size of 536870912 bytes
sending 'boot' (6884 KB)...
OKAY [ 0.290s]
writing 'boot'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.341s
[email protected]:~$ fastboot -i 0x1949 flash unlock '/media/jeremy/MULTIBOOT/unlock.img'
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.084s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.141s
[email protected]:~$ python cuberHDX.py 45202b1325
python: can't open file 'cuberHDX.py': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py 45202b1325
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ '/media/jeremy/MULTIBOOT/cuber.py' 45202b1325
bash: /media/jeremy/MULTIBOOT/cuber.py: Permission denied
[email protected]:~$ '/home/jeremy/Desktop/cuber.py' 45202b1325
bash: /home/jeremy/Desktop/cuber.py: Permission denied
[email protected]:~$ python '/home/jeremy/Desktop/cuber.py' 45202b1325
Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Your unlock code is in '45202b1325.unlock'.
[email protected]:~$ fastboot -i 0x1949 flash unlock '/home/jeremy/45202b1325.unlock'
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.085s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.142s
[email protected]:~$ /cuber_unlockbl --sign ./'/home/jeremy/Desktop/unlock.img' ./ '/home/jeremy/45202b1325.unlock'
bash: /cuber_unlockbl: No such file or directory
[email protected]:~$ python ./cuber_unlockbl --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file './cuber_unlockbl': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py ./cuber_unlockbl --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py ./cuber_unlockbl --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cuberHDX.py [boot.img|serial]
[email protected]:~$ python /home/jeremy/Desktop/cuber.py ./cuber_unlockbl --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cuber.py --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cublock.py --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cublock.py manfid serial
[email protected]:~$
well i added a txt file that contains my device info if you can get a .unlock and .img file that would really help me btw my fire os was 13.3.2.8
blue9a said:
well i added a txt file that contains my device info if you can get a .unlock and .img file that would really help me btw my fire os was 13.3.2.8
Click to expand...
Click to collapse
Can't unlock bootloader versions >3.2.3.2; can't flash with a locked BL. Your device is bricked.
Hi,
I wanted to test if I could build and run a kernel (unmodified).
These were my steps:
Install image on device (LineageOS 15.1 in my case)
Get kernel sources
Cloned the kernel repository that the developer of the image provided.
Build kernel
Try and run kernel directly with 'fastboot boot' (failed)
Modify boot.img from installed image with self compiled kernel
Try to run the modified boot.img with 'fastboot boot'
Code:
downloading 'boot.img'...
OKAY [ 0.589s]
booting...
OKAY [ 0.019s]
finished. total time: 0.608s
My problem is now that, although fastboot reports success and the device boots from fastboot mode a few seconds after issuing the command on the host(not before printing 'Booting downloaded image' on the top of the bootloader screen), the kernel didn't seem to have changed (judging from 'Kernel version' in the 'About' device dialog).
What could have gone wrong? Is my workflow ok?
Could anyone point me in the right direction?
Thanks in advance!
Device: Nexus7 / grouper
Resources used:
Image: https://forum.xda-developers.com/nexus-7/development/rom-lineageos-15-1-t3975207
Kernel: https://github.com/surblazer/android_kernel_nvidia_tegra3
mkbootimg_tools: https://github.com/xiaolu/mkbootimg_tools
Need some help please with something that has gone wrong with my first attempt to alter Android. I wanted to install a custom recovery, root the phone and take it from there.
I have a Moto e 1st edition, xt1021, system info given below.
I unlocked the boot loader, installed Minimal ADB Fastboot 1.4.3, downloaded the latest TWRP image 3.3.1.-condor for the Moto e from the TWRP website.
I used flashboot flash recovery initially to install the TWRP image, which failed, but has wiped the stock recovery. I cannot boot into recovery or do a factory reset.
The phone will boot normally. If I try a factory reset, it boots normally. If I boot into recovery, I get the Android image on his back with a red triangle, and “no command”. If I go into system recovery from here, and try both 'update by adb sideload' or 'update from sd card', both fail.
I have tried flashboot boot recovery using a stock recovery, but the phone is stuck on the initial Moto logo.
I have also tried to install an earlier TWRP recovery, 2.7.1-condor and CWM 6.o.4.7 falcon but this has failed to install also.
I have now reached the limit of my abilities – any help much appreciated, but please spell out in words of one syllable if possible.
=========================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb devices
List of devices attached
ZX1B245XHK device
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb shell pm list features
feature:reqGlEsVersion=0x30000
feature:android.hardware.audio.output
feature:android.hardware.bluetooth
feature:android.hardware.bluetooth_le
feature:android.hardware.camera
feature:android.hardware.camera.any
feature:android.hardware.faketouch
feature:android.hardware.location
feature:android.hardware.location.gps
feature:android.hardware.location.network
feature:android.hardware.microphone
feature:android.hardware.screen.landscape
feature:android.hardware.screen.portrait
feature:android.hardware.sensor.accelerometer
feature:android.hardware.sensor.light
feature:android.hardware.sensor.proximity
feature:android.hardware.telephony
feature:android.hardware.telephony.cdma
feature:android.hardware.telephony.gsm
feature:android.hardware.touchscreen
feature:android.hardware.touchscreen.multitouch
feature:android.hardware.touchscreen.multitouch.distinct
feature:android.hardware.touchscreen.multitouch.jazzhand
feature:android.hardware.usb.accessory
feature:android.hardware.usb.host
feature:android.hardware.wifi
feature:android.hardware.wifi.direct
feature:android.software.app_widgets
feature:android.software.backup
feature:android.software.connectionservice
feature:android.software.device_admin
feature:android.software.home_screen
feature:android.software.input_methods
feature:android.software.live_wallpaper
feature:android.software.managed_users
feature:android.software.print
feature:android.software.sip
feature:android.software.voice_recognizers
feature:android.software.webview
feature:com.motorola.camera
feature:com.motorola.camera.chalmers
feature:com.motorola.context
feature:com.motorola.hardware.tier.
feature:com.motorola.hardware.wave.0
feature:com.motorola.smartaction2
feature:com.motorola.smartactions2_1.1
feature:com.motorola.software.bodyguard
feature:com.motorola.software.device.condor_umts
feature:com.motorola.software.fmradioservice
feature:com.motorola.software.fmrecording
feature:com.motorola.software.guideme
feature:com.motorola.software.product.condor_tescogb
feature:com.motorola.software.storageoptimizer
feature:com.motorola.software.x_line
==================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb reboot bootloader
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot flash recovery C:
\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\twrp-2.7.2.0-hlte-4.3.img
target reported max download size of 299892736 bytes
sending 'recovery' (10738 KB)...
OKAY [ 0.608s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) image size exceeds limit
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.686s
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot boot C:\Users\ME\
Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\recovery-clockwork-6.0.4.7-falcon.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.499s]
finished. total time: 0.920s
========================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>FASTBOOT GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
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
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>