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
[Ubuntu-12.04.3 / Asus Transformer Pad TF701F]
Hi all,
my first android device and my first newbie question here:
I successfully connected my Ubuntu desktop with my TF701F tablet via USB (udev, adb, fastboot) and started the root image upload to the tablet with the following output:
Code:
sudo fastboot boot root_tn7.img
downloading 'boot.img'...
OKAY [ 0.868s]
booting...
OKAY [ 0.010s]
finished. total time: 0.878s
After this, the tablet reboots as if everything was alright. No root privilegs for me, though. One of these root checker apps also states that the tablet was not rooted.
What's wrong? Who can help me out, please?
This is for users that would like to upgrade, downgrade from an older, newer bootloader... It will also unbirck a soft bricked 700.. All you need is fastboot installed on your Linux machine and the tablet to be able to boot into fastboot mode......
This will wipe all your data, ALL OF IT.....
This is a very easy script to run from Linux Terminal......Download the zip (MAKE SURE YOU GET THE CORRECT SKU) in the download tab at the top of the page...Extract once...Open a terminal from that directory...Than boot your tablet into fastboot mode (bootloader screen) and type just to verify your PC can see your tablet
Code:
fastboot devices
If you get an output like this your ready to run the script!!!!!
OUTPUT
Code:
[email protected] ~/Asus_tf700t_US_firmware_v10.6.1.14.10 $ fastboot devices
015d2bbce2501405 fastboot
Notice that Im in the directory of the unzipped download folder
Run the Script
Code:
./flash-all.sh
here is my output of the process so everbody is aware of what is going to happen and the amount of time it will take
OUTPUT
Code:
[email protected] ~/Asus_tf700t_US_firmware_v10.6.1.14.10 $ ./flash-all.sh
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 3.008s]
finished. total time: 3.008s
erasing 'recovery'...
OKAY [ 1.998s]
finished. total time: 1.998s
erasing 'boot'...
OKAY [ 0.536s]
finished. total time: 0.536s
erasing 'misc'...
OKAY [ 1.601s]
finished. total time: 1.601s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.953s]
finished. total time: 1.953s
erasing 'system'...
OKAY [ 1.685s]
sending 'system' (800927 KB)...
OKAY [132.489s]
writing 'system'...
OKAY [179.141s]
finished. total time: 313.315s
rebooting...
finished. total time: 0.020s
XDA:DevDB Information
[Script][Linux/Windows_7/8][TF700T][Firmware][Bootloader][Stock_Rom], a Tool/Utility for the Asus Transformer TF700
Contributors
lj50036, sbdags
Version Information
Status: Testing
Created 2014-02-12
Last Updated 2014-02-12
Windows 7/8 Only
sbdags said:
Here is the equivalent windows.bat file. NOTE this only works in Windows 7 or 8 as XP / Vista don't have the timeout command.
Copy to notepad and save as flash-all.bat in the same folder as fastboot.exe and the cwm.img file. Note you will also need a boot.blob from lj50036 to flash system.....
Alternatively unzip the attached to do the same. (Still need the source of boot.blob @lj50036) This will flash cwm 6.0.4.6 which is the latest touch version as of today:
Code:
Echo Press Control-C to quit or any key to continue!
Pause > Nul
fastboot erase system
timeout 5
fastboot erase recovery
timeout 5
fastboot erase boot
timeout 5
fastboot erase misc
timeout 5
fastboot erase cache
timeout 5
fastboot -i 0x0B05 flash system boot.blob
timeout 5
fastboot -i 0x0B05 reboot-bootloader
timeout 20
fastboot -i 0x0B05 flash recovery cwm.img
timeout 5
Echo Done - Press any key to reboot
Pause > Nul
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
Thx sbdags for this Windows version.. For the less fortunate Windows users.... JK
Look at sbdags post for the Flash-All.zip
Reserved
Issues
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot erase system
sleep 5
fastboot erase recovery
sleep 5
fastboot erase boot
sleep 5
fastboot erase misc
sleep 5
fastboot erase cache
sleep 5
fastboot -i 0x0B05 flash system boot.blob
sleep 5
fastboot -i 0x0B05 reboot
Works great, but if I try to add a recovery and make the script look like this
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot erase system
sleep 5
fastboot erase recovery
sleep 5
fastboot erase boot
sleep 5
fastboot erase misc
sleep 5
fastboot erase cache
sleep 5
fastboot -i 0x0B05 flash system boot.blob
sleep 5
fastboot -i 0x0B05 reboot-bootloader
sleep 10
fastboot -i 0x0B05 flash recovery cwm.img
sleep 5
fastboot -i 0x0B05 reboot
I get a infinite reboot..... Can I not do it like that???
Any help with this would be great thx all.....
Try sleep 20 or 30
Just saw you got it fixed
Feedbck
sbdags said:
Try sleep 20 or 30
Click to expand...
Click to collapse
YES!!!! sleep 20 worked like a charm.. A little more testing and I will post with recovery..... LOL... Thx for the help!!!!!
sbdags said:
Try sleep 20 or 30
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Why are you flashing boot.blob to system? Does your boot blob contain system? Don't you mean staging?
Click to expand...
Click to collapse
The boot.blob is really the stock firmware from asus that I renamed boot.blob....The script did not like to run it as just blob, It would hang in flashing.....Should I do something different???
lj50036 said:
YES!!!! sleep 20 worked like a charm.. A little more testing and I will post with recovery..... LOL... Thx for the help!!!!!
Click to expand...
Click to collapse
Tell you what if you do the Linux I'll do the Windows version
Sweet
sbdags said:
Tell you what if you do the Linux I'll do the Windows version
Click to expand...
Click to collapse
That sounds great!!!! Let me know if there is anything I can do.....Thx for your help lj
Here is the equivalent windows.bat file. NOTE this only works in Windows 7 or 8 as XP / Vista don't have the timeout command.
Copy to notepad and save as flash-all.bat in the same folder as fastboot.exe and the cwm.img file. Note you will also need a boot.blob from lj50036 to flash system.....
Alternatively unzip the attached to do the same. (Still need the source of boot.blob @lj50036) This will flash cwm 6.0.4.6 which is the latest touch version as of today:
Code:
Echo Press Control-C to quit or any key to continue!
Pause > Nul
fastboot erase system
timeout 5
fastboot erase recovery
timeout 5
fastboot erase boot
timeout 5
fastboot erase misc
timeout 5
fastboot erase cache
timeout 5
fastboot -i 0x0B05 flash system boot.blob
timeout 5
fastboot -i 0x0B05 reboot-bootloader
timeout 20
fastboot -i 0x0B05 flash recovery cwm.img
timeout 5
Echo Done - Press any key to reboot
Pause > Nul
fastboot -i 0x0B05 reboot
Good evening gentlemen.
fastboot = Vol down + Pwr right?
I can not get into fastboot.
I am trying to recover my soft bricked tf700.
I am currently on TWRP 2.2.1.4 [i know] and can not get anywhere but the recovery screen.
anything I try I get:
E: failed to mount /system, /data, /cache, etc.
Any ideas on why this could be would be greatly appreciated.
C.patrick said:
Good evening gentlemen.
fastboot = Vol down + Pwr right?
I can not get into fastboot.
I am trying to recover my soft bricked tf700.
I am currently on TWRP 2.2.1.4 [i know] and can not get anywhere but the recovery screen.
anything I try I get:
E: failed to mount /system, /data, /cache, etc.
Any ideas on why this could be would be greatly appreciated.
Click to expand...
Click to collapse
Yes thats how you get to fastboot.. I assume you have used fastboot before..In recovery try this in recovery
Code:
adb devices
Let me know the outcome of that... Thx lj
lj50036 said:
Yes thats how you get to fastboot.. I assume you have used fastboot before..In recovery try this in recovery
Code:
adb devices
Let me know the outcome of that... Thx lj
Click to expand...
Click to collapse
Thanks for the reply!
/ # adb devices
got a
E: failed to mount /data (no such file or directory)
when under root
C.patrick said:
Good evening gentlemen.
fastboot = Vol down + Pwr right?
I can not get into fastboot.
I am trying to recover my soft bricked tf700.
I am currently on TWRP 2.2.1.4 [i know] and can not get anywhere but the recovery screen.
anything I try I get:
E: failed to mount /system, /data, /cache, etc.
Any ideas on why this could be would be greatly appreciated.
Click to expand...
Click to collapse
How did you get into this situation? Have you tried to wipe data from the bootloader menu, do a factory reset from Android, or "boot to recovery" from Android before? Any of these together with a non-working recovery (such as yours) are a recipe for a brick.
If you have a current bootloader and an old recovery, the recovery can't access your internal storage, so it cannot reset the "boot to recovery" flag set by one of the above operations.
For a possible fix, read this thread: http://forum.xda-developers.com/showthread.php?t=2437376
Hey there,
do I need an unlocked bootloader for this or is it a way to flash cwm without unlocked bootloaders? I am asking because I got my pad back from rma repair and I'm not able to unlock my bootloader now. But I have contacted the support to register my mac adress. But maybe your script is helpful in my situation?
pestbeule said:
do I need an unlocked bootloader for this
Click to expand...
Click to collapse
Yes.
pestbeule said:
or is it a way to flash cwm without unlocked bootloaders? I am asking because I got my pad back from rma repair and I'm not able to unlock my bootloader now. But I have contacted the support to register my mac adress. But maybe your script is helpful in my situation?
Click to expand...
Click to collapse
Unfortunately there is no way to install recoveries or kernels not signed by Asus with a locked bootloader. Good luck with Asus support, hope your request reaches the right person.
Hi,
Thanks for the great script but I have a novel problem!
I am running Linux Mint 16. I am one of those stupid people that tried to flash a JB rom on my 9.4.5.30 bootloader. :crying:
So I thought this was the perfect tool for me! When I ran ./flash-all.sh here is what I got:
Code:
[email protected] ~/Desktop/Untitled Folder $ ./flash-all.sh
erasing 'system'...
OKAY [ 3.457s]
finished. total time: 3.457s
erasing 'recovery'...
OKAY [ 1.918s]
finished. total time: 1.918s
erasing 'boot'...
OKAY [ 0.495s]
finished. total time: 0.495s
erasing 'misc'...
OKAY [ 0.872s]
finished. total time: 0.872s
erasing 'cache'...
OKAY [ 2.149s]
finished. total time: 2.149s
sending 'system' (800927 KB)...
OKAY [134.175s]
writing 'system'...
FAILED (remote: ()
finished. total time: 134.662s
< waiting for device >
Meanwhile the tf700 in tiny red text says "failed to process command flash:system error(0x170003). In white text above there there are a few lines which I believe were from successful attempts to erase things. There is also a line directly above the scary read text stating "Signature Match".
Not sure where I went wrong. Any ideas?
Thanks for your time!
Feedback
LurkerRWO said:
Hi,
Thanks for the great script but I have a novel problem!
I am running Linux Mint 16. I am one of those stupid people that tried to flash a JB rom on my 9.4.5.30 bootloader. :crying:
So I thought this was the perfect tool for me! When I ran ./flash-all.sh here is what I got:
Code:
[email protected] ~/Desktop/Untitled Folder $ ./flash-all.sh
erasing 'system'...
OKAY [ 3.457s]
finished. total time: 3.457s
erasing 'recovery'...
OKAY [ 1.918s]
finished. total time: 1.918s
erasing 'boot'...
OKAY [ 0.495s]
finished. total time: 0.495s
erasing 'misc'...
OKAY [ 0.872s]
finished. total time: 0.872s
erasing 'cache'...
OKAY [ 2.149s]
finished. total time: 2.149s
sending 'system' (800927 KB)...
OKAY [134.175s]
writing 'system'...
FAILED (remote: ()
finished. total time: 134.662s
< waiting for device >
Meanwhile the tf700 in tiny red text says "failed to process command flash:system error(0x170003). In white text above there there are a few lines which I believe were from successful attempts to erase things. There is also a line directly above the scary read text stating "Signature Match".
Not sure where I went wrong. Any ideas?
Thanks for your time!
Click to expand...
Click to collapse
I may know what is going on.... Take the boot.blob file and move it to your home directory, the same directory that when you open your terminal window its there so an easy check of this is just open terminal and type
Code:
ls
This will give you a list of everything in that directory make sure your boot.blob is there... here is what it looks like on my PC also Mint 16
Code:
[email protected] ~ $ ls
android bin ccache crombix Downloads
[email protected] ~ $
Once you have done that, go to this forum on xda skip the nvflash stuff and start with the fastboot commands... Just enter them one at a time,
make sure you read between the inputs and outputs of the forum, there is good info in there... Let me know if I can help in the process.. Thx lj
http://forum.xda-developers.com/showthread.php?t=2538028
Hi again!
Thanks for the advice, I am in the process of doing what you said but already ran into a hiccup. When I ran 'fastboot -w' I get
Code:
athena torytop # fastboot -w
erasing 'userdata'...
OKAY [ 27.601s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 1.428s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 29.030s
Also, I wasn't able to run fastboot with sudo, it says command not found. So I ran sudo su and then proceeded per your advice minus the sudo commands. I will edit this post when I finish.
Edit: Failed with the same error, and I can't help but wonder if the failure to partition isn't related. This is not my own tablet, a friend gave it to me as it was bricked already, but I was able to get into recovery so took this on as a fun little project. So yeah, I have no clue what he did to brick it, maybe messed with partitions?
LurkerRWO said:
Hi again!
Thanks for the advice, I am in the process of doing what you said but already ran into a hiccup. When I ran 'fastboot -w' I get
Code:
athena torytop # fastboot -w
erasing 'userdata'...
OKAY [ 27.601s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 1.428s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 29.030s
Also, I wasn't able to run fastboot with sudo, it says command not found. So I ran sudo su and then proceeded per your advice minus the sudo commands. I will edit this post when I finish.
Click to expand...
Click to collapse
Skip it
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
I've recently gotten an unknown-manufactured android pad and I want to flash my custom AOSP system into it. I'd just prefer to change the system image of the pad, from Android 9 to Android 10, and when I tried to flash the system image into it, the error pops out like this:
Code:
[email protected] /media/caesar/TLC_0/AOSP/out/target/product/generic fastboot -S 128M flash system system.img
Invalid sparse file format at header magic
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
And now I've got no idea how can I solve this problem, I would appreciate your help. THANKS!