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
Related
Hi buddy,
My o3d is a stock (unflashed) one. It can enter fastboot mode mainly by this method. (I have tried different methods, like the wkpark one, but finally I have succeeded with that, and with the wkparks fastboot loader tool. Anyway, I can make my way to that white LG logo fastboot place ) And when I do fastboot devices it returns my serial number. (So I am sure it is in fastboot mode.) But when I want to boot a custom recovery from PC, by the command fastboot boot recovery-clockwork-6.0.1.9-p920.img, the command prompt gives the following messages:
Code:
creating boot image...
creating boot image - 5484544 bytes
downloading 'boot.img'...
OKAY [ 2.770s]
booting...
OKAY [ -0.000s]
finished. total time: 2.790s
Seems alright. But my o3d stays still on that white LG logo. It obviously didnt boot. If I now try fastboot devices again, it gives ??? instead of the serial number:
Code:
???????????? fastboot
I have tried using recovery-clockwork-6.0.1.9-p920.img and recovery-clockwork-touch-6.0.1.9-p920.img downloaded from this page, and also the cm-7.2.0-p920 boot.img downloaded from this page. But all give the same result .
I would like to try the custom recovery, by fastboot boot recovery.img, before really flashing into my o3d, by fastboot flash recovery recovery.img .
Any clues?
Thanks so much!
midnite
I thing that you cant fasboot boot, don't work here. Something is mentioned before in some thread by wkpark.
Sent from my LG-SU760 using xda app-developers app
iodak said:
I thing that you cant fasboot boot, don't work here. Something is mentioned before in some thread by wkpark.
Sent from my LG-SU760 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply.
There are really so less resources talking about fastboot boot over the internet. Could you give me some hints where can I use fastboot boot?
Thanks!!
Re: Sideloading CWM recovery by <fastboot boot> ?
Try doing Fastboot Reboot after
Sent from my LG-P920 using xda app-developers app
JunDavis said:
Try doing Fastboot Reboot after
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply!
I have tried fastboot reboot and fastboot reboot-bootloader after. But the phone screen turns off and stays off.
---
fastboot reboot after fastboot boot recovery.img
Code:
C:\>fastboot devices
0911234567898019 fastboot
C:\>fastboot boot recovery-clockwork-6.0.1.9-p920.img
creating boot image...
creating boot image - 5484544 bytes
downloading 'boot.img'...
OKAY [ 2.740s]
booting...
OKAY [ -0.000s]
finished. total time: 2.740s
C:\>fastboot reboot
rebooting...
finished. total time: 112.290s
C:\>
At the same time, phone screen turns off, and screen remains off.
---
fastboot reboot-bootloader after fastboot boot recovery.img
Code:
C:\>fastboot devices
0911234567898019 fastboot
C:\>fastboot boot recovery-clockwork-6.0.1.9-p920.img
creating boot image...
creating boot image - 5484544 bytes
downloading 'boot.img'...
OKAY [ 2.810s]
booting...
OKAY [ 0.000s]
finished. total time: 2.820s
C:\>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 107.260s
C:\>
At the same time, phone screen turns off, and screen remains off.
---
I also tried only fastboot reboot and fastboot reboot-bootloader, without fastboot boot recovery.img:
Code:
C:\>fastboot devices
0911234567898019 fastboot
C:\>fastboot reboot
rebooting...
finished. total time: 0.010s
C:\>
Phone screen turns off at the same time, and back on to charging screen. It is not really booting into the system.
---
Code:
C:\>fastboot devices
0911234567898019 fastboot
C:\>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
C:\>
Screen turns off, like the first two trials.
---
What do those behaviours mean?
Thanks a lot!!
midnite
Re: Sideloading CWM recovery by <fastboot boot> ?
midnite_ said:
Hi buddy,
My o3d is a stock (unflashed) one. It can enter fastboot mode mainly by this method. (I have tried different methods, like the wkpark one, but finally I have succeeded with that, and with the wkparks fastboot loader tool. Anyway, I can make my way to that white LG logo fastboot place ) And when I do fastboot devices it returns my serial number. (So I am sure it is in fastboot mode.) But when I want to boot a custom recovery from PC, by the command fastboot boot recovery-clockwork-6.0.1.9-p920.img, the command prompt gives the following messages:
Code:
creating boot image...
creating boot image - 5484544 bytes
downloading 'boot.img'...
OKAY [ 2.770s]
booting...
OKAY [ -0.000s]
finished. total time: 2.790s
Seems alright. But my o3d stays still on that white LG logo. It obviously didnt boot. If I now try fastboot devices again, it gives ??? instead of the serial number:
Code:
???????????? fastboot
I have tried using recovery-clockwork-6.0.1.9-p920.img and recovery-clockwork-touch-6.0.1.9-p920.img downloaded from this page, and also the cm-7.2.0-p920 boot.img downloaded from this page. But all give the same result .
I would like to try the custom recovery, by fastboot boot recovery.img, before really flashing into my o3d, by fastboot flash recovery recovery.img .
Any clues?
Thanks so much!
midnite
Click to expand...
Click to collapse
Why all the hastle u can just flash it and when u wanna use stock recovery just flash it using the tool provided in the dark lestat unbricking thread ...Its simple ..btw dont use the latest cwm its kinda slow just use the provided in the dark lestats thread. ... http://forum.xda-developers.com/showthread.php?t=1540163
Sent from my LG-P920 using xda premium
Hello,
I have a lenovo a396(phone) recently.
It acts wired when dealing with fastboot commands, and looks incredible to root(more info at bottom of this post)
And the Lenovo Customer Service stuff says this phone is not able to flash via fastboot and told me I am only able to flash it via recovery <3e>
Is that even possible???
If yes,
how can I even bypass the 3e signature veriation to flash a custom ROM
EDIT: I have a stock update.zip in my hand!
thank you very much for saving me another one week's spare time
dye
FYI:
fastboot erase cache
erasing 'cache'...
FAILED (remote:unknown partition name)
finished. total time: 0.003s
fastboot erase system
erasing 'system'...
FAILED ( remote:unknown partition name)
finished. total time: 0.003s
fastboot boot zImage initramfs.cpio.gz
___FYI___ the zImage and initrd are unmkbootimg from the boot.img via stock updat.zip
creating boot image...
creating boot image - 10975232 bytes
downloading 'boot.img'...
OKAY [ 0.529s]
booting...
OKAY [ 0.197s]
finished. total time: 0.726s
fastboot oem h
...
[PS: after this three dots, hehe, you doomed to wait forever. cuz the process's status turned into D+ ie, waiting for IO]
Lenovo A397
Android 2.3.5
Kernel 3.10.17
Hardware_ver H201
verA397_S162_140528
if more hardware info requested, please post that
Hello, on March 10th I received a new update on my N5. After update, which finished with no problems as usual, my phone was normally working or about two more hours. In that time no new apps were installed. Then it just shut down, and can't be properly turned on.
It always stuck at Google logo and that is all that it does. I'm able to get to the fastboot mode by holding Power+Volume Up+Volume Down buttons, but I can't get into Recovery Mode option to hard reset it. Nothing show up after selecting that option and Power+Volume Up does nothing. Ok, bad luck, time to flash it nice and clean.
Haha, nice try.
I'm not sure if I had USB debugging on or off, but I think off. Obtained ROM from Google + newest platform tools from SDK and followed all possible manual I could get from Internets, results:
Code:
adb devices
List of devices attached
*nothing*
Code:
adb reboot bootloader
error: no devices found
Drivers are newest from Google, reinstalled several times, device is visible in Windows as Android Bootloader Interface and seem working fine. adb just do not see phone.
Code:
fastboot oem unlock
...
OKAY [ 46.402s]
finished. total time: 46.403s - WORKS!
But rest is just no go:
Code:
fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase cache
********Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.217s
Code:
fastboot erase recovery
erasing 'recovery'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.218s
I tried several more commands, like to install twrp, but all with same results.
Code:
fastboot flash recovery twrp.img
sending 'recovery' (14314 KB)...
OKAY [ 0.653s] writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.835s
I also tried "fastboot boot twrp.img" and it worked but didn't helped much. Internal storage is showing size 0 MB an when I try to do anything it ends with wall of red text about how it's unable to find partitions or mount images, first line:
Code:
E:Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
Also when I reboot bootloader, it get stuck and when I get it back with buttons, it is back in its locked state. So my guess is that eMMC went to Silicon Heaven.
Do you guys have any advices? Or is my phone just fancy mirror now?
When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?
audit13 said:
When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?
Click to expand...
Click to collapse
Like i wrote, it get back to locked state.
The emmc chip is defective and cannot be fixed. This is clearly indicated when the bootloader relocks itself at reboot.
Thought so, but wanted confirmation . Thank you.
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!
I unlocked my pixel's bootloader, reset.. etc
but when I fastboot boot twrp.img
this error message appears
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.094s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.388s
help, please!
PS: my phone has no command recovery mode, I don't know if it helps
arahmanaladdin said:
I unlocked my pixel's bootloader, reset.. etc
but when I fastboot boot twrp.img
this error message appears
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.094s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.388s
help, please!
PS: my phone has no command recovery mode, I don't know if it helps
Click to expand...
Click to collapse
Same thing but even I when manage to flash twrp it says: Your device software cant be checked for corruption. Please lock the bootloader. Any ideas?
820p said:
Same thing but even I when manage to flash twrp it says: Your device software cant be checked for corruption. Please lock the bootloader. Any ideas?
Click to expand...
Click to collapse
It will always say that.
---------- Post added at 02:24 PM ---------- Previous post was at 02:12 PM ----------
arahmanaladdin said:
I unlocked my pixel's bootloader, reset.. etc
but when I fastboot boot twrp.img
this error message appears
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.094s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.388s
help, please!
PS: my phone has no command recovery mode, I don't know if it helps
Click to expand...
Click to collapse
Make sure you have the lastest fastboot files. That is too small for a TWRP image. Should be 30 MB. Make sure you didn't get a bad download. Message should say "sending boot.img, not creating boot.img. make sure you typed the commands in correctly.
It was a bad download!! thanks!!
the file was 7kb lol, my bad for not checking