Database Info

[Q] Toshiba Folio 100: partition-type:recovery error(0x2)

Hello,
i am using my Toshiba Folio as a playground for new ROMs. I have already successfully installed different mods but since the last one, my Folio seems to be broken.
I followed this guide here: http://forum.xda-developers.com/showpost.php?p=31004271&postcount=9 but when i issue the fastboot commands i always get this:
[email protected]:~/Downloads/adt-bundle-linux/sdk/platform-tools> fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 0.001s
[email protected]:~/Downloads/adt-bundle-linux/sdk/platform-tools> fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 0.002s
Click to expand...
Click to collapse
My Folio says:
Failed to process command getvar: partition-type:xxxx error(0x2)
Click to expand...
Click to collapse
where 'xxxx' is the partition i try to access accordingly.
Can anyone help me out or do i have a brick now? I definitly have done something wrong.
Greetings,
Alex

problem
hello good, I have the same problem as you, could you fix it?

Just popped here to say how I managed to get arround this:
fastboot -u -S 0 flash linux boot.img
and it worked.
My understanding is that 'fastboot' changed and has new capability of getting 'partition-type' from device.
Folio doesn't seem to understand that command, so it's either -u or -S 0 that makes it work.
Cheers my friends!

I had the same problem!! The working parameters is "-S 0"

Tried everything // getting failed // found a way
I spent the whole day to understand how to make this work...
I did the factory reset via Settings in Android menu, I connected the tablet to PC and the only thing I could do using fastboot was "reboot".
I forgot all "erase" functions and I tried "fastboot boot <filename.img>" and it worked!
Then you follow http://forum.xda-developers.com/showpost.php?p=31004271&postcount=9
Just try this if anything else fails.

[Script][Linux/Windows_7/8][TF700T][Firmware][Bootloader][Stock_Rom]

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

Cannot access system to turn on developer mode

Hi I have been working all day trying to get my moto G up and running again.
The problem is that when I boot it shows the boot animations then boots to a blank screen with backlight on.
So far I have tried.
1. Going into the bootloader then into recovery by holding up for 10s then tapping power. From here I wiped back to factory settings. Then I tired to wipe cach partition. When I did this it said ERASING... then rebooted a second later.
It went back to the same black screen after I booted.
1. Flashing a new recovery. TWERP. The flashing process seemed to go ok ... .
target max-sparse-size: 256MB
sending 'recovery' (9488 KB)...
OKAY [ 0.318s]
writing 'recovery'...
OKAY [ 0.170s]
finished. total time: 0.488s
but when I checked I was still on stock recovery.
Then I went and used fastboot to erase recovery and tried flashing again and rebooted bootloader with fastboot reboot command. Still on stock recovery.
2. Then I tried sideloading falcon to this device it aborted.
3. I discovered the sideload boot recovery and when I was able to load TWERP into RAM and boot from there I thought I had it made.
I tried sideloading my ROM from here and got Error 7 I am on bootloader 4113 and I need to be on a newer on.
4. Flashed bootloader
First with getvar I was able to confirm I was on 13. I downloaded 41.19 and flashed that
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.099s]
but when I rebooted the bootloader with fastboot reboot, and did getvar again. I saw that I was still on 13.
This is only a short summary of the highlights of what I have tried with this phone today. Can anybody give me and idea how to proceed? I'm stuck fast here.
Then I tried simply booting into TWRP recovery with

And yes I unlocked the bootloader. I also tried flashing a stock ROM from here

I've seen similar reports like yours and no solution. It is supposed to be a hardware error. To confirm this, fastboot boot twrp.img and then run adb shell dmesg > dmesg.txt and post the file, maybe there are any clues in this kernel log.

_that said:
I've seen similar reports like yours and no solution. It is supposed to be a hardware error. To confirm this, fastboot boot twrp.img and then run adb shell dmesg > dmesg.txt and post the file, maybe there are any clues in this kernel log.
Click to expand...
Click to collapse
Sorry. I am not sure exactly how to do this. Would you be so nice as to post command here so that I can cut and paste into command line?

jonawald said:
Sorry. I am not sure exactly how to do this. Would you be so nice as to post command here so that I can cut and paste into command line?
Click to expand...
Click to collapse
You can literally cut and paste the commands from my post (if your twrp image is named "twrp.img"). Between fastboot and adb, wait for TWRP to start up.

_that said:
You can literally cut and paste the commands from my post (if your twrp image is named "twrp.img"). Between fastboot and adb, wait for TWRP to start up.
Click to expand...
Click to collapse
I tried this
adb-mac adb dmesg > dmesg.txt
and this
adb-mac adb shell dmesg > dmesg.txt
I am using a mac as you might guess from the -mac piece. When I try this I get
Android Debug Bridge version 1.0.32
Revision 760a64fe84b7-android
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
etc.

TF700T - Bootloop TWRP after install with official TWRP app

Hi Guys, I need some help.
I tried to flash TWRP 3.1 over a 3.0 using the official TWRP app from the store (With root access) The img file I downloaded using the app is the one specific for the TF700T.
Now my device got stuck in a TWRP bootloop. Initially I got the classic RCK/ANDROID/WHIPE DATA menu, but since I used whipe data it is only cycling through TWRP boot loops. (No more menu)
I can only stop the loop using the volume-up rocker during boot.
I'm trying the adb sideload but I am unable to flash the recovery partition.
adb devices does return the device ID followed by 'recovery' but when flashing the new img file the process only waits for a responding device.
> adb devices (output above)
> adb reboot bootloader
> adb devices (output above)
> fastboot -i 0x0B05 flash recovery twrp31.img (Here is where it fails, the device reboot by itself returning to the bootloop / TWRP is obviously not flashed)
Tx a lot for your help
JS:crying:

Geez - where to start?
You should never use Wipe Data from the bootloader menu if you have a custom recovery installed!
You cannot use fastboot commands while connected in adb.
Two different protocols or tools:
Use adb in recovery or Android, and fastboot when I the bootloader.
And that is where you want to be to fix this.
So you have to use bootit.ko to kick the tablet out of the loop and into the bootloader. Not literally please
Check out the guide below and ask if not clear before you completely brick it...
And then never use an app again to flash a recovery. Ever!
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my Nexus 5X using Tapatalk

Hi
Thanks for your comments on my post. I will have a good look at the info tonight and check if all is clear before I execute the next step.
Kindest regards
JS
PS: I'll be a good boy from now on and keep your advice in the back of my head at all times.

It's not the first time that I see a story like yours. These apps have to be designed for many, many different devices and identify the correct partition to the flash the recovery to for each device. So they either need a large data base of Android devices with the correct partition tables (not likely) or they need to read the partition table off the device - correctly... And that's the weak spot. If you're unlucky it could flash the recovery to the boot partition - good luck getting out of that one.
In your case it flashed it wrong but not super wrong and then you made it worse with that wipe data.
As long as you have adb in recovery this should be fixable. Good luck!
Sent from my Nexus 5X using Tapatalk

Made some progress
Here are the results of my attempt
adb push bootit.ko /
1136 KB/s (27690 bytes in 0.023s)
adb shell insmod /bootit.ko
(No return, so I asume its ok)
GOT OUT OF BOOTLOOP
fastboot devices
015d2bbce63fec14 fastboot
fastboot erase misc
erasing 'misc'...
OKAY [ 0.260s]
finished. total time: 0.261s
fastboot reboot
rebooting...
finished. total time: 0.020s
fastboot -i 0x0B05 flash recovery twrp31.img
< waiting for device >
sending 'recovery' (7218 KB)...
OKAY [ 2.863s]
writing 'recovery'...
OKAY [ 8.069s]
finished. total time: 10.933s
fastboot reboot
rebooting...
finished. total time: 0.021s
TWRP 3.1.0.0 is loaded, when I boot I get the splash screen, but there it loops again. Stop bootloop by using Volume down rocker.
I have used following commands with the new 3.1.0.0
fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.249s]
finished. total time: 1.249s
fastboot -w
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
erasing 'userdata'...
OKAY [ 64.078s]
sending 'userdata' (139133 KB)...
OKAY [ 25.092s]
writing 'userdata'...
OKAY [ 2.166s]
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 96.343s
fastboot -i 0x0B05 flash recovery filename.img
sending 'recovery' (7126 KB)...
OKAY [ 2.029s]
writing 'recovery'...
OKAY [ 7.546s]
finished. total time: 9.590s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
TWRP does start OK, I am able to flash a custom ROM
Thanks a lot for your incredible support. I hope to have your knowledge and understanding on this topic on day
Kindest regards
JS

It's just practice my friend, just practice. And making a lot of stupid mistakes. Like you did.
Glad you're up and running
Sent from my Nexus 5X using Tapatalk

Hi,
I had to erase/format the system and data partition to get access to TWRP. (fastboot -w)
Once that was done, it all went smooth and silky.
Tx again
JS :good:

berndblb said:
Geez - where to start?
You should never use Wipe Data from the bootloader menu if you have a custom recovery installed!
You cannot use fastboot commands while connected in adb.
Two different protocols or tools:
Use adb in recovery or Android, and fastboot when I the bootloader.
And that is where you want to be to fix this.
So you have to use bootit.ko to kick the tablet out of the loop and into the bootloader. Not literally please
Check out the guide below and ask if not clear before you completely brick it...
And then never use an app again to flash a recovery. Ever!
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
Click to expand...
Click to collapse
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!

[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!
Click to expand...
Click to collapse
Hey @[email protected] - how about sharing the script? I'd like to add it to the guide.

[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!
Click to expand...
Click to collapse
Hello can you share your batch file because I have the same problem as you had.

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!