Database Info

[Q] "fastboot boot" command

Has anyone used the "flashboot boot <kernel>" command with their xoom?
When I try booting a custom kernel and disk, I get this:
build> fastboot boot zImage zDisk
creating boot image...
creating boot image - 3014656 bytes
downloading 'boot.img'...
OKAY [ 0.451s]
booting...
FAILED (command write failed (Unknown error))
finished. total time: 0.983s​
So I figured I'd better check and make sure the xoom supports the boot command before trying anything more.
-Jim

BeagleBoy said:
Has anyone used the "flashboot boot <kernel>" command with their xoom?
When I try booting a custom kernel and disk, I get this:
build> fastboot boot zImage zDisk
creating boot image...
creating boot image - 3014656 bytes
downloading 'boot.img'...
OKAY [ 0.451s]
booting...
FAILED (command write failed (Unknown error))
finished. total time: 0.983s​
So I figured I'd better check and make sure the xoom supports the boot command before trying anything more.
-Jim
Click to expand...
Click to collapse
Koush had said a while ago that fastboot boot doesn't work on the Xoom (nfi why). But this isn't a big deal, is it, because you can just create a boot image and reboot after fastboot flash boot <image> it (right?)

Thread moved to General.

ydaraishy said:
Koush had said a while ago that fastboot boot doesn't work on the Xoom (nfi why). But this isn't a big deal, is it, because you can just create a boot image and reboot after fastboot flash boot <image> it (right?)
Click to expand...
Click to collapse
Yes and no. If I understand correctly, the "boot" command copies the image over and launches it without flashing. Which would be handy when hacking away at a custom kernel.
But, if it doesn't work, I'll live without it.
-Jim

Frustrated, can't get fastboot to work

NEVERMIND, I won at the game of android and fastboot.

Liquidmetal6 said:
NEVERMIND, I won at the game of android and fastboot.
Click to expand...
Click to collapse
I'm having an issue where fastboot seems to run, but it never actually flashes the new TWRP.
C:\Recovery1>fastboot -i 0x0b05 flash recovery twrp.img
sending 'recovery' (7872 KB)...
OKAY [ 2.070s]
writing 'recovery'...
OKAY [ 2.411s]
finished. total time: 4.482s
C:\Recovery1>fastboot -i 0x0b05 reboot
rebooting...
finished. total time: 0.550s
However, it acts like it's not really talking to the device. Device doesn't reboot, and the new TWRP isn't loaded.

jaa3rd said:
I'm having an issue where fastboot seems to run, but it never actually flashes the new TWRP.
C:\Recovery1>fastboot -i 0x0b05 flash recovery twrp.img
sending 'recovery' (7872 KB)...
OKAY [ 2.070s]
writing 'recovery'...
OKAY [ 2.411s]
finished. total time: 4.482s
C:\Recovery1>fastboot -i 0x0b05 reboot
rebooting...
finished. total time: 0.550s
However, it acts like it's not really talking to the device. Device doesn't reboot, and the new TWRP isn't loaded.
Click to expand...
Click to collapse
You have to issue the fastboot reboot command next it will flash on reboot.

sbdags said:
You have to issue the fastboot reboot command next it will flash on reboot.
Click to expand...
Click to collapse
Unless I'm misunderstanding you, I have issued the reboot command as indicated above, and it seems to take the command, but the reboot and/or flash never occurs. I've flashed multiple of version of TWRP on this tablet in the past, using the same pc. I just can't seem to figure out what's changed.
Thanks in advance for your help.

[Q] Cannot flash recovery after unlocking bootloader

I am having problem flashing recovery on my htc desire s hboot : 2.00.0002.
The problem is that whenever i type in fastboot flash recovery twrp.img it says
FAILED data transfer failed too many links (unlocked bootloader through htcdev)
here is the command window
C:\Users\Hashim Zia>cd C:\Android\android-sdk\platform-tools
C:\Android\android-sdk\platform-tools>fastboot devices
HT19MTJ00709 fastboot
C:\Android\android-sdk\platform-tools>fastboot flash recovery twrp.img
sending 'recovery' (4360 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.000s
C:\Android\android-sdk\platform-tools>fastboot devices
HT19MTJ00709 fastboot
C:\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.550s]
finished. total time: 0.550s
C:\Android\android-sdk\platform-tools>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (4360 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: -0.000s
PLEASE HELP!!!

simply the most awesome said:
I am having problem flashing recovery on my htc desire s hboot : 2.00.0002.
The problem is that whenever i type in fastboot flash recovery twrp.img it says
FAILED data transfer failed too many links (unlocked bootloader through htcdev)
here is the command window
C:\Users\Hashim Zia>cd C:\Android\android-sdk\platform-tools
C:\Android\android-sdk\platform-tools>fastboot devices
HT19MTJ00709 fastboot
C:\Android\android-sdk\platform-tools>fastboot flash recovery twrp.img
sending 'recovery' (4360 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.000s
C:\Android\android-sdk\platform-tools>fastboot devices
HT19MTJ00709 fastboot
C:\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.550s]
finished. total time: 0.550s
C:\Android\android-sdk\platform-tools>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (4360 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: -0.000s
PLEASE HELP!!!
Click to expand...
Click to collapse
So u know where you downloaded the zip file for the recovery extract it, then in that folder where the twrp.img is hold shift and right click and there should be an option for open command window here. Then type the command again fastboot flash recovery (name.IMG).
Sent from my HTC Desire S using XDA Free mobile app

lilsafbig said:
So u know where you downloaded the zip file for the recovery extract it, then in that folder where the twrp.img is hold shift and right click and there should be an option for open command window here. Then type the command again fastboot flash recovery (name.IMG).
Sent from my HTC Desire S using XDA Free mobile
That is just what I did
Plus thanks for quick reply
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse

simply the most awesome said:
lilsafbig said:
So u know where you downloaded the zip file for the recovery extract it, then in that folder where the twrp.img is hold shift and right click and there should be an option for open command window here. Then type the command again fastboot flash recovery (name.IMG).
Sent from my HTC Desire S using XDA Free mobile
That is just what I did
Plus thanks for quick reply
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
So it worked?
Edit: flash 4ext recovery instead. Make sure u fastboot erase recovery and then flash the recovery. Extract it and flash the .IMG file.
http://forum.xda-developers.com/showthread.php?p=41343637
from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse

lilsafbig said:
simply the most awesome said:
So it worked?
Edit: flash 4ext recovery instead. Make sure u fastboot erase recovery and then flash the recovery. Extract it and flash the .IMG file.
http://forum.xda-developers.com/showthread.php?p=41343637
from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
No the previous thing did not work but I will try the new way you suggested
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse

6045i - bootloader unlocked but TWRP not flashing

Hi all,
I have a 6045i variant of the idol3. I have successfully unlocked the bootloader and have been trying now to flash TWRP. Then I will install a custom ROM and SU to hopefully end the lagfest.
However, no matter which TWRP I try (2.8.7.0 or 3.0.0-1) it isn't sticking. I've followed the appropriate threads here using adb fastboot to flash the recoveries but when I try to get to recovery it goes to the stock version.
I'm running the latest stock firmware: 5.0.2-7SRN-UEN0
Here's the output of the adb session.
Code:
C:\adb>fastboot -i 0x1bbb devices
cc22eea2 fastboot
C:\adb>fastboot -i 0x1bbb oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
(bootloader) Big core max freq:
(bootloader) Small core max freq:
OKAY [ 0.028s]
finished. total time: 0.029s
C:\adb>fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img
target reported max download size of 268435456 bytes
sending 'recovery' (23880 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 2.207s]
finished. total time: 3.014s
C:\adb>fastboot -i 0x1bbb reboot
rebooting...
finished. total time: 0.003s
When I invoke recovery (either thru adb or power on/volume up) it loads into stock 3e recovery.
Any tips to get past this? I've done a fair amount of searching for similar issues here but haven't ran into any help.
thanks,

try this:
if youflash the TWRP recovery then turn off the phone and right go to recovery (volume up+power).
If you can go t oTWRP recovery and after reboot yo uwill get the stock one again, then there is a stratup script which replaces the custom recovery with the stock one, on every startup.
You have then to flash the twrp recovry, right boot into it and using the file manager inside TWRP to find the script and delete it.

mikehd1959 said:
Hi all,
I have a 6045i variant of the idol3. I have successfully unlocked the bootloader and have been trying now to flash TWRP. Then I will install a custom ROM and SU to hopefully end the lagfest.
However, no matter which TWRP I try (2.8.7.0 or 3.0.0-1) it isn't sticking. I've followed the appropriate threads here using adb fastboot to flash the recoveries but when I try to get to recovery it goes to the stock version.
I'm running the latest stock firmware: 5.0.2-7SRN-UEN0
Here's the output of the adb session.
Code:
C:\adb>fastboot -i 0x1bbb devices
cc22eea2 fastboot
C:\adb>fastboot -i 0x1bbb oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
(bootloader) Big core max freq:
(bootloader) Small core max freq:
OKAY [ 0.028s]
finished. total time: 0.029s
C:\adb>fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img
target reported max download size of 268435456 bytes
sending 'recovery' (23880 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 2.207s]
finished. total time: 3.014s
C:\adb>fastboot -i 0x1bbb reboot
rebooting...
finished. total time: 0.003s
When I invoke recovery (either thru adb or power on/volume up) it loads into stock 3e recovery.
Any tips to get past this? I've done a fair amount of searching for similar issues here but haven't ran into any help.
thanks,
Click to expand...
Click to collapse
You can just try like this
Connect to Pc with usb
Open Adb And Fastboot
Enable Debugging on Device
type "adb reboot bootloader"
Then write"fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img"
and then"fastboot -i 0x1bbb boot twrp-3.0.0-1.img"-wait 2s and Automaticily Device will boot to TWRP recovery so you can flash what do you want

Alek Dev said:
You can just try like this
Connect to Pc with usb
Open Adb And Fastboot
Enable Debugging on Device
type "adb reboot bootloader"
Then write"fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img"
and then"fastboot -i 0x1bbb boot twrp-3.0.0-1.img"-wait 2s and Automaticily Device will boot to TWRP recovery so you can flash what do you want
Click to expand...
Click to collapse
Thanks. That's what I just stumbled into as well. I've gotten into TWRP and was able to reboot in TWRP back into TWRP recovery. So now I'm trying reboot to system from TWRP. I'll then reboot to recovery to see if TWRP has stuck.
While in TWRP I used the terminal to find the init scripts. Here's the list:
Code:
init
init.qcom.usb.sh
init.rc
init.recovery.qcom.rc
init.recovery.qcom.usb.rc
When I executed a ls -lh to see timestamps, they were all some default 1969 year. So I didn't muck with anything with init.
Just completed my first boot into the OS. I shut it down fully then restarted with power on + Vol Up and it went straight to TWRP.
So the trick was to do the flash recovery then boot the image as you suggested.
Is this typical for this device? I've never encountered this on other phones (S3 for example).

mikehd1959 said:
Thanks. That's what I just stumbled into as well. I've gotten into TWRP and was able to reboot in TWRP back into TWRP recovery. So now I'm trying reboot to system from TWRP. I'll then reboot to recovery to see if TWRP has stuck.
While in TWRP I used the terminal to find the init scripts. Here's the list:
Code:
init
init.qcom.usb.sh
init.rc
init.recovery.qcom.rc
init.recovery.qcom.usb.rc
When I executed a ls -lh to see timestamps, they were all some default 1969 year. So I didn't muck with anything with init.
Just completed my first boot into the OS. I shut it down fully then restarted with power on + Vol Up and it went straight to TWRP.
So the trick was to do the flash recovery then boot the image as you suggested.
Is this typical for this device? I've never encountered this on other phones (S3 for example).
Click to expand...
Click to collapse
so the trick was been to flash the TWRP recovery and then aumotacilly go to Recovery...and if you want to restart phone...just reboot it .you no need to flash boot

Alek Dev said:
so the trick was been to flash the TWRP recovery and then aumotacilly go to Recovery...and if you want to restart phone...just reboot it .you no need to flash boot
Click to expand...
Click to collapse
Except that didn't work for me. It would consistently go to stock recovery no matter how I tried to exit adb. If I rebooted to recovery in adb the stock recovery would launch. If I plain rebooted to OS and then shut down and restart (power on + Vol Up) it would go to stock recovery. It was only when I did the commands as listed above would it at last go to TWRP and persist across reboots.

mikehd1959 said:
Except that didn't work for me. It would consistently go to stock recovery no matter how I tried to exit adb. If I rebooted to recovery in adb the stock recovery would launch. If I plain rebooted to OS and then shut down and restart (power on + Vol Up) it would go to stock recovery. It was only when I did the commands as listed above would it at last go to TWRP and persist across reboots.
Click to expand...
Click to collapse
So use the commands to go to Twrp..you can try to lock the bootloader and try again to unlock and then flash Twrp..
Edit:So it can be the problem with the system

Alek Dev said:
So use the commands to go to Twrp..you can try to lock the bootloader and try again to unlock and then flash Twrp..
Edit:So it can be the problem with the system
Click to expand...
Click to collapse
No need to do as you describe. It is now working correctly. When I go to recovery, it launches TWRP as expected. Issue closed.

Pixel 3 XL only fastboot but doesn't accept commands

So somehow I seemed to have bricked my Pixel 3 XL. I've bootet into fastboot and ahve enabled OEM unlock beforehand in the dev options. Also the screen tells me "Device state: unlocked" after I ran
Code:
fastboot flashing unlock
.
But now no matter what I do I end up with a black screen. Can't boot into my OS and can't boot into recovery. I also can't flash a factory ROM or temp boot into TWRP. I also can't flash anything.
Code:
fastboot boot twrp-3.2.3-4-crosshatch.img
downloading 'boot.img'...
OKAY [ 0.396s]
booting...
FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)
finished. total time: 0.765s
Code:
fastboot flash recovery twrp-3.2.3-4-crosshatch.img
target reported max download size of 268435456 bytes
sending 'recovery' (65536 KB)...
OKAY [ 0.392s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
finished. total time: 0.758s
Code:
fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.318s]
finished. total time: 0.318s

Do you have the latest sdk platform tools?

jd1639 said:
Do you have the latest sdk platform tools?
Click to expand...
Click to collapse
afaik I don't have them at all. Never needed them for my Fairphone 2. I am running Ubuntu 18.04.

Ignore..

IronDude said:
afaik I don't have them at all. Never needed them for my Fairphone 2. I am running Ubuntu 18.04.
Click to expand...
Click to collapse
I'm not very familiar with Linux. The latest firmware is compressed with a newer compression method which older versions of fastboot don't handle. What do you get if you run the command fastboot --version? The latest is 28.0.1

sliding_billy said:
Have you tried to get into stock recovery from fastboot? I don't see a screen grab of that. Use key combo to get to bootloader, and then select recovery from fastboot to get to the no command screen and power +volume down to get to recovery options.
Also, did you get a prompt that unlocking the BL would results in a factory reset and did you do one?
Click to expand...
Click to collapse
Yes tried all that. When I chood recovery Mode from the menu I get a black screen. A reboot via fastboot into recovery is not possible afaik.
Code:
fastboot --version
fastboot version 1:7.0.0+r33-2
This is the latest version according to Ubuntu.

IronDude said:
Yes tried all that. When I chood recovery Mode from the menu I get a black screen. A reboot via fastboot into recovery is not possible afaik.
Code:
fastboot --version
fastboot version 1:7.0.0+r33-2
This is the latest version according to Ubuntu.
Click to expand...
Click to collapse
All right, looks like Linux is a little different than windows. See if these help, https://developer.android.com/studio/releases/platform-tools.

jd1639 said:
All right, looks like Linux is a little different than windows. See if these help, https://developer.android.com/studio/releases/platform-tools.
Click to expand...
Click to collapse
Same results

IronDude said:
So somehow I seemed to have bricked my Pixel 3 XL. I've bootet into fastboot and ahve enabled OEM unlock beforehand in the dev options. Also the screen tells me "Device state: unlocked" after I ran
Code:
fastboot flashing unlock
.
But now no matter what I do I end up with a black screen. Can't boot into my OS and can't boot into recovery. I also can't flash a factory ROM or temp boot into TWRP. I also can't flash anything.
Code:
fastboot boot twrp-3.2.3-4-crosshatch.img
downloading 'boot.img'...
OKAY [ 0.396s]
booting...
FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)
finished. total time: 0.765s
Code:
fastboot flash recovery twrp-3.2.3-4-crosshatch.img
target reported max download size of 268435456 bytes
sending 'recovery' (65536 KB)...
OKAY [ 0.392s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
finished. total time: 0.758s
Code:
fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.318s]
finished. total time: 0.318s
Click to expand...
Click to collapse
IronDude said:
Yes tried all that. When I chood recovery Mode from the menu I get a black screen. A reboot via fastboot into recovery is not possible afaik.
Code:
fastboot --version
fastboot version 1:7.0.0+r33-2
This is the latest version according to Ubuntu.
Click to expand...
Click to collapse
You are right about recovery>fastboot. That is why I "deleted" my comment. Maybe starting back over might help. Were you running BL unlocked already? Did you have TWRP installed? Had you been using the same computer /cable/port to execute commands before?

IronDude said:
Same results
Click to expand...
Click to collapse
Try flashing the factory image again. Just use the flash all .sh file.

jd1639 said:
Try flashing the factory image again. Just use the flash all .sh file.
Click to expand...
Click to collapse
Doesn't work:
Code:
./flash-all.sh
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html
Code:
fastboot --version
fastboot version 28.0.1-4986621
Installed as /usr/local/sbin/platform-tools/fastboot

Ok the flash all is just broken but it can be forced to do its job simply by deleting the following lines:
Code:
#if ! grep -q partition-exists $(which fastboot); then
# echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
# exit 1
#fi
I didn't delete them but just made them a comment. Then it worked.

IronDude said:
Ok the flash all is just broken but it can be forced to do its job simply by deleting the following lines:
Code:
#if ! grep -q partition-exists $(which fastboot); then
# echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
# exit 1
#fi
I didn't delete them but just made them a comment. Then it worked.
Click to expand...
Click to collapse
Glad it worked out.

sliding_billy said:
Glad it worked out.
Click to expand...
Click to collapse
Me too mate! Was quite a heart attack moment.

IronDude said:
Me too mate! Was quite a heart attack moment.
Click to expand...
Click to collapse
Sounds good, glad you got it working again!