C:\adb>fastboot flashing unlock
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
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> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
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:\adb>
That means your version of fastboot doesn't understand the command. You'll need to update it.
Related
Well I have 2yrs(noob) in flashing roms thru CWM recovery but I have nevr used fastboot I would like to understand how to flash using fadtboot
Sent from my R800x using XDA Premium App
I just copied this from fastboot in the command prompt
These are the basic commands you can tell it to do. I underlined the actual command you type and what it does, to give you a better understanding of what you are doing.
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
continue continue with autoboot
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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
Click to expand...
Click to collapse
I used to be a noob too and not understand fastboot, and I still don't, but now I are one.
Hi,
I just tired to compile and repack the LL-Kernel for Z1c into a boot.img.
But I can't get it to start. I only see red LED blinken when I try to boot.
I used following sources:
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-14-5-a-0-242/
And did it like it is mentioned in README_Xperia, which was all working fine and without errors.
Code:
### get defconfig
ARCH=arm CROSS_COMPILE=./arm-eabi-4.6/bin/arm-eabi- make rhine_amami_row_defconfig
### compile kernel
ARCH=arm CROSS_COMPILE=./arm-eabi-4.6/bin/arm-eabi- make
echo "checking for compiled kernel..."
if [ -f arch/arm/boot/zImage ]
then
echo "generating device tree..."
./dtbTool -o dt.img -s 2048 -p ./scripts/dtc/ ./arch/arm/boot/
echo "DONE"
fi
### D5503
./mkbootimg --cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3b7 ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 vmalloc=300M dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" --base 0x00000000 --kernel arch/arm/boot/zImage --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x02000000 -o boot.img --dt dt.img --tags_offset 0x01E00000
The ramdisk.img I got from http://forum.xda-developers.com/son...5-0-242-generic-1279-6978-pre-rooted-t3083764
And I extracted the boot.elf with "Andrid Kitchen", which was working almost:
Code:
7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
p7zip Version 9.20 (locale=de_DE.UTF-8,Utf16=on,HugeFiles=on,4 CPUs)
Processing archive: kernel.elf
Extracting 0
Extracting 1
Extracting 2
Everything is Ok
Files: 3
Size: 11304622
Compressed: 11308906
mv: call of stat for »3“ not possible: File or Directory not found
mv: call of stat for »cmdline.txt“ not possible: File or Directory not found
After that there was a ramdisk.img in output folder which I used for mkbootimg.
After getting boot.img I tried to flash/load it via fastboot, which was not working. Can't figuere aout why.
Bootloader is unlocked.
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.349s]
booting...
FAILED (status read failed (No such device))
finished. total time: 5.437s
Code:
fastboot flash boot boot.img
sending 'boot' (11044 KB)...
OKAY [ 0.349s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.352s
And because of that I tried to flash it via TWRP/CWM/... with following updater-script:
Code:
show_progress(0,0);
ui_print(" flashing boot.img...");
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
ui_print(" finished");
show_progress(10.000000, 1);
So maybe anyone can point me to mistake I make?
EDIT:
Problem solved and Kernel is working. I must have relocked my bootloader in the past and couldn't remember it^^
So now I was able to flash the boot.img via fastboot.
I have tried 2 version of MiFlash :
7.4.25 gave me "Length cannot be less than zero error", so I changed to MiFlash Beta as has been suggested here
My PC definitely reckon the device in fastboot mode. fastboot devices showed the device is detected. It's just both version of MiFlash failed to recognize it.
I have tried to Update Driver on "Android Bootloader Interface". Out of 4 similar options I have tried (see attached pic), it doesn't make MiFlash recognize the phone. I have also tried to "search automatically" for updated driver.
MiFlash still doesn't recognize the phone.
second pic :
adb devices from the system -> recognized
fastboot devices from fastboot mode -> recognized
but MiFlash didn't detect the device.
So I'm kinda stuck. Any suggestion?
I'm using Win7 SP1, Official TWRP 3.1.1, and Xiaomi.eu ROM 7.5.19
If your device is recognized in fastboot /device manager then I guess it's a Mi flash problem. Try other Mi flash version. Maybe will do the trick.
Additional attempts I have tried :
- Install Mi PC Suit manager : nope, Mi PC Suite manager can't detect the device
- fastboot oem edl : command prompt says OKAY, but the device is turned off
- Because the adb and fastboot in MiFlash's Source\ThirdParty\Google\Android folder can't detect my device, I tried to replace them with the working adb and fastboot. Executing adb and fastboot via cmd can detect my device, but MiFlash still can't detect the device.
Tried to install MiFlash on my laptop, got the phone detected. But flashing China Dev 7.6.8 has problem
If I go with clean all but save user data, I got this from the log
Code:
[20:57:25 a3f1f00c]:MiFlash 2017.4.25.0
[20:57:25 a3f1f00c]:image path:C:\Mi6ROM\sagit
[20:57:25 a3f1f00c]:env android path:"C:\Mi6\XiaoMiFlash\Source\ThirdParty\Google\Android"
[20:57:25 a3f1f00c]:script :C:\Mi6ROM\sagit\flash_all_except_storage.bat
[20:57:26 a3f1f00c]:Physical Memory Usage:147456 Byte
[20:57:26 a3f1f00c]:$fastboot -s a3f1f00c getvar product 2>&1 | findstr /r /c:"^product: *sagit" || echo Missmatching image and device
[20:57:26 a3f1f00c]:product: sagit
[20:57:26 a3f1f00c]:$fastboot -s a3f1f00c getvar product 2>&1 | findstr /r /c:"^product: *sagit" || exit /B 1
[20:57:26 a3f1f00c]:product: sagit
[20:57:26 a3f1f00c]:$set CURRENT_ANTI_VER=1
[20:57:26 a3f1f00c]:$for /F "tokens=2 delims=: " %i in ('fastboot -s a3f1f00c getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
[20:57:26 a3f1f00c]:$(set version=1 )
[20:57:26 a3f1f00c]:$if [1] EQU [] set version=0
[20:57:26 a3f1f00c]:$if 1 GTR 1 (
[20:57:26 a3f1f00c]:echo current device antirollback version is greater than this pakcage
[20:57:26 a3f1f00c]: exit /B 1
[20:57:26 a3f1f00c]:)
[20:57:26 a3f1f00c]:$fastboot -s a3f1f00c erase boot ||
[20:57:26 a3f1f00c]:erasing 'boot'...
[20:57:26 a3f1f00c]:eek:KAY [ -0.000s]
[20:57:26 a3f1f00c]:finished. total time: -0.000s
[20:57:26 a3f1f00c]:$fastboot -s a3f1f00c flash crclist C:\Mi6ROM\sagit\images\crclist.txt ||
[20:57:26 a3f1f00c]:target reported max download size of 536870912 bytes
[20:57:26 a3f1f00c]:sending 'crclist' (0 KB)...
[20:57:26 a3f1f00c]:eek:KAY [ 0.000s]
[20:57:26 a3f1f00c]:writing 'crclist'...
[20:57:26 a3f1f00c]:error:FAILED (remote: update crc list failed)
[20:57:26 a3f1f00c]:"Flash crclist error"
[20:57:26 a3f1f00c]:error:FAILED (remote: update crc list failed)
[20:57:26 a3f1f00c]:process exit.
[20:57:26 a3f1f00c]:flashSuccess False
[20:57:26 a3f1f00c]:isFactory False CheckCPUID False
[20:57:26 a3f1f00c]:before:flashSuccess is False set IsUpdate:True set IsDone True
[20:57:26 a3f1f00c]:after:flashSuccess is False set IsUpdate:false set IsDone true
If I go with clean all, I got this
Code:
[21:00:53 a3f1f00c]:MiFlash 2017.4.25.0
[21:00:53 a3f1f00c]:image path:C:\Mi6ROM\sagit
[21:00:53 a3f1f00c]:env android path:"C:\Mi6\XiaoMiFlash\Source\ThirdParty\Google\Android"
[21:00:53 a3f1f00c]:script :C:\Mi6ROM\sagit\flash_all_except_storage.bat
[21:00:53 a3f1f00c]:Physical Memory Usage:147456 Byte
[21:00:53 a3f1f00c]:$fastboot -s a3f1f00c getvar product 2>&1 | findstr /r /c:"^product: *sagit" || echo Missmatching image and device
[21:00:53 a3f1f00c]:product: sagit
[21:00:53 a3f1f00c]:$fastboot -s a3f1f00c getvar product 2>&1 | findstr /r /c:"^product: *sagit" || exit /B 1
[21:00:53 a3f1f00c]:product: sagit
[21:00:53 a3f1f00c]:$set CURRENT_ANTI_VER=1
[21:00:53 a3f1f00c]:$for /F "tokens=2 delims=: " %i in ('fastboot -s a3f1f00c getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
[21:00:53 a3f1f00c]:$(set version=1 )
[21:00:53 a3f1f00c]:$if [1] EQU [] set version=0
[21:00:53 a3f1f00c]:$if 1 GTR 1 (
[21:00:53 a3f1f00c]:echo current device antirollback version is greater than this pakcage
[21:00:53 a3f1f00c]: exit /B 1
[21:00:53 a3f1f00c]:)
[21:00:53 a3f1f00c]:$fastboot -s a3f1f00c erase boot ||
[21:00:53 a3f1f00c]:erasing 'boot'...
[21:00:53 a3f1f00c]:eek:KAY [ 0.002s]
[21:00:53 a3f1f00c]:finished. total time: 0.002s
[21:00:53 a3f1f00c]:$fastboot -s a3f1f00c flash crclist C:\Mi6ROM\sagit\images\crclist.txt ||
[21:00:53 a3f1f00c]:target reported max download size of 536870912 bytes
[21:00:53 a3f1f00c]:sending 'crclist' (0 KB)...
[21:00:53 a3f1f00c]:eek:KAY [ 0.000s]
[21:00:53 a3f1f00c]:writing 'crclist'...
[21:00:53 a3f1f00c]:error:"Flash crclist error"
[21:00:53 a3f1f00c]:"Flash crclist error"
[21:00:53 a3f1f00c]:error:"Flash crclist error"
[21:00:53 a3f1f00c]:process exit.
[21:00:53 a3f1f00c]:flashSuccess False
[21:00:53 a3f1f00c]:isFactory False CheckCPUID False
[21:00:53 a3f1f00c]:before:flashSuccess is False set IsUpdate:True set IsDone True
[21:00:53 a3f1f00c]:after:flashSuccess is False set IsUpdate:false set IsDone true
Notice that crclist being sent is empty (0 KB), but the path (C:\Mi6ROM\sagit\images\crclist.txt) is correct.
Here's the content of crclist.txt
Code:
CRC-LIST
cmnlib 0x7d88792d
storsec 0x35f86924
keymasterbak 0x372ec484
cust 0xc1e5c6bc
abl 0xb36e450d
misc 0xd8f49994
pmicbak 0x8512f438
keymaster 0x372ec484
bluetooth 0x796c778e
cmnlib64 0xd2b02789
logo 0x57035ea1
cmnlib64bak 0xd2b02789
rpm 0x630680f
hypbak 0xf7b9a0a0
userdata 0xf671e3a1
tz 0x794c524a
recovery 0xb0584b02
cmnlibbak 0x7d88792d
ablbak 0xb36e450d
cache 0xc7fcb051
boot 0x430e7a99
xblbak 0xd1d418e2
dsp 0xaa1f8735
tzbak 0x794c524a
hyp 0xf7b9a0a0
xbl 0xd1d418e2
splash 0xe75e093d
rpmbak 0x630680f
modem 0x39d79144
pmic 0x8512f438
devcfg 0x2ccefd3b
Phone couldn't enter system, good thing I backed up boot, recovery, and EFS in TWRP, so that's easily got solved.
Anyway, any idea what can I do to solve this crclist error?
I'm wondering if my target reported max download size 536870912 bytes is actually an error.
This guy said it's an error. But from my log, it doesn't say it's an error.
Maybe I should try the other version of MiFlash (Beta) for this? :/
when i type fastboot reboot fastboot my phone does nothing and that's what i get:
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
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> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
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
It seems like i do not enter fastbootd. any solution?
altojd said:
when i type fastboot reboot fastboot my phone does nothing and that's what i get:
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
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> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
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
It seems like i do not enter fastbootd. any solution?
Click to expand...
Click to collapse
Download latest fastboot version
Kollachi said:
Download latest fastboot version
Click to expand...
Click to collapse
Thanks but where do i find the latest fastboot version? if u mean fastboot.exe in platform tools i am on the latest one (r30.0.4)
altojd said:
Thanks but where do i find the latest fastboot version? if u mean fastboot.exe in platform tools i am on the latest one (r30.0.4)
Click to expand...
Click to collapse
Download the All in one tool from the forums here, it contains all of the drivers and files you need.
When you open up a command window, drag the fastboot.exe into command and then leave a space
Type fastboot reboot fastboot
Same thing happened with me it's weird but I use this is as a workaround
i solved my problem by flashing msm extended recovery. it has the function in advance to reach fastbootd.
T-Mobile LE2127 PERMANENTLY Networked unlocked. I have the bootloader unlocked from ONEplus / T-Mobile directly (applied the unlock.bin). I have the phone rooted (made my rooted image and applied in fastboot). I have also tried with and without converting to Global with the carrier policy and lte features restrictions modified for 5G. I have successfully been able to (and learn) how to EDL and apply the MSM Tool with T-Mobile build.
I am on T-Mobile software version 11.2.3.3.LE5ACB and both times when trying the flash_all.bat file, according to the "Convert T-Mobile OnePlus 9 to Global (or other) firmware" How To, I get various errors while flashing with things like...
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
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> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
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
PS C:\platform-tools>
All to say, it doesn't work and it's a lot of work resetting up everything over and over again on T-Mobile (restoring, re-entering various passwords, and updating the 100's of programs etc..)
Is it really possible to convert? Am I supposed to be on a different build?
Cheers,
Have you tried flashing with Command Prompt instead of PowerShell? Sometimes batch files don't work the way you would expect them to in PS. Also make sure you have the latest platform tools.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
No I did not... I might give that a try if I have the time.
thank you