Database Info

Bricked ZM609 (xybaord) READ THIS

ok so here is a quick question,
i have not had a locked device that has fastboot before
but here is the scenario and the question
i copied my recover, as well as a few other imgs with this command
dd if=/dev/block/mmcblk1p12 of=/sdcard/recovery.img
and for ****s and giggles i decided that iwould see if it would let me flash the img back.
so with device in fastboot mode
i entered
fastboot flash recovery recovery.img
and it flashed....
so i guess my question is... would it flash a custom recovery???
heres the read out
Code:
C:\Users\zach\Desktop\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (9216 KB)...
OKAY [ 0.454s]
writing 'recovery'...
OKAY [ 1.677s]
finished. total time: 2.132s
C:\Users\zach\Desktop\platform-tools>reboot
'reboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\zach\Desktop\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.007s
C:\Users\zach\Desktop\platform-tools>

if any one has brick their xyboard 4g 8.2
please contact me
for more proof of concept i have two mz609
on the one that i flashed recovery it loads and will preform resets and wipe cache, which is ECXATLY what the mz609 tab that is stock + root does and on the stock one i have not fastbooted any recovery,
so this leads me to believe that we can in fact flash imgs, at least stock imgs that is
well if anyone has bricked there ZM609-32
here are some imgs that may or may not work to fastboot img
and before i get flamed with "its a locked bootloader blah blah blah"
if u look at the above code u will see that i successfully fastboot flashed the recovery and the stock recovery still loads, and works with all intensive purposes
i have not however flashed the system.img or the boot.img
but if you have already bricked your tablet,,,whats the worse that could happen right...
if you do use this please report back here and let me know the outcome, and dont just say it didnt work, i want the cmd copied so that i can read where it fails
https://dl.dropbox.com/0/view/n5rll0c7lk7b0ap/my roms/xybaord dump/MZ609_fastboot_images.zip

Sounds interesting

Never mind.....

Unrecoverable bootloader error but not Bricked!

So I unlocked my tf300t and flashed cwm to recovery.
Everything seemed to go fine.
When I would go into cwm it was not able to mount or access any other part of my tab. I figured ok erase/format the recovery partition and try TWRP. So I booted to the bootloader, using fastboot I erased recovery but now whenever I go to flash a new recovery my bootloader either freezes or I get an Unrecoverable bootloader error 0x00000000 (not sure if thats the right amount of zeros but there are no other digits in the error code.) I can access fastboot and adb but it doesn't seem like I can flash using fastboot and I just don't feel comfortable trying with adb. Also I can access fastboot only from the bootloader screen and adb only after I boot into my current rom (stock 4.2.1)
I guess my questions are this:
How can I format my recovery or flash a new recovery?
Were the mount issues I originally encountered going to be solved with a new recovery?
Please help!

Have you tried installing stock rom (from Asus support page) using Fastboot? It should also put stock recovery in your tablet.
Not sure if it is going to work, but it's worth trying though.

1st this is not for the dev section. You should ask questions in the Q&A section.
Go to Asus and dl the latest Stock. Unzipp it 2 times. You should have a blob file now in the extracted folder. put this blob in your fastboot folder.
Open cmd and type:
fastboot -i 0x0B05 flash staging blob
let it run. It seems that nothing is happening for about 5 Minutes. The whole thing can take up to 20 Minutes, so just stay calm and wait till its finished.
Now you should be back to full Stock with Stock recovery.

mikaole said:
1st this is not for the dev section. You should ask questions in the Q&A section.
Go to Asus and dl the latest Stock. Unzipp it 2 times. You should have a blob file now in the extracted folder. put this blob in your fastboot folder.
Open cmd and type:
fastboot -i 0x0B05 flash staging blob
let it run. It seems that nothing is happening for about 5 Minutes. The whole thing can take up to 20 Minutes, so just stay calm and wait till its finished.
Now you should be back to full Stock with Stock recovery.
Click to expand...
Click to collapse
I had this problem too. But on 4.2.1 you can push file blob, and then it's can't run because stock recovery dead.

Were you able to fix the stock recovery issue?

cdguider said:
Were you able to fix the stock recovery issue?
Click to expand...
Click to collapse
Thant i would like to know aswell
Pls

No, I was not. I also have the unrecoverable bootloader error but I have a working device. I downloaded the latest firmware, followed the steps through fastboot and the same thing keeps happening where as soon as you try to enter a command through fastboot the green box stops flashing over rck and even though the cmd prompt window tells you something is going on nothing happens on the tablet end. It freezes. hard reboot and you end up back with a normal working device, no changes and a corrupt bootloader.

lomoski said:
No, I was not. I also have the unrecoverable bootloader error but I have a working device. I downloaded the latest firmware, followed the steps through fastboot and the same thing keeps happening where as soon as you try to enter a command through fastboot the green box stops flashing over rck and even though the cmd prompt window tells you something is going on nothing happens on the tablet end. It freezes. hard reboot and you end up back with a normal working device, no changes and a corrupt bootloader.
Click to expand...
Click to collapse
I have same issue.. has anybody managed to get a fix for this?

I've same problem, how can i fix it?
i've a working device but without recovery mod! I can't flash anything via fastboot because it freezes, i always have "Unrecoverable bootloader error" when press RCK.
Can somebody help me?
Thanks in advance

mister363 said:
I've same problem, how can i fix it?
i've a working device but without recovery mod! I can't flash anything via fastboot because it freezes, i always have "Unrecoverable bootloader error" when press RCK.
Can somebody help me?
Thanks in advance
Click to expand...
Click to collapse
I was having this problem earlier - a new bootloader came out when they went to 4.2, but most of the instructions online don't reflect this. You need an updated recovery image, which usually has the name recovery-jb.img instead of recovery.img. When you're searching make sure the instructions mention 4.2 and jelly bean.
However, I've only managed to get one step further - have now get into clockworkmod recovery, but as with the OP I then couldn't mount anything inside CWM. I tried another instruction set which involved unzipping the ROM and using adb to push over the .blob. This hasn't worked and I have now got a pretty much bricked device - it either bootloops on the asus splash screen, or loads into CWM.
I've found that even when youre in CWM you can type "adb reboot-bootloader" into the terminal, which forces the RCK/android/wipe data page and fastbook to appear. I've also tried to download the latest stock firmware from ASUS, unzipped it to get the stock .blob out and into my fastboot directory, then run "fastboot -i 0x0B05 flash staging blob" in the terminal, as per mikaole's suggestion. This takes a while to push over the 80mb .blob, but after it says it's staged it says "done" then nothing happens and it's still bricked. hmm.

No one's figured this out? I tried flashing the blob file and my system won't boot at all

My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster

IT WORKS!!!
Buster99 said:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
Thank you very much. It works beautifully.

Buster99 said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Now i' m busy because of my Job. But next week i want try your method.
I hope it work for my device!
Inviato dal mio GT-I9100 con Tapatalk 2

Buster99 said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Did your tablet seem to freeze after flashing via fastboot? When I push blob, the console shows that it wrote, but then fastboot on the tablet freezes & I have to manually reboot, putting me right back to the drawing board.
Sent from my HTC One using xda app-developers app

Until now my device freezes. Fastboot seem to work but nothing happens. :banghead:
Inviato dal mio GT-I9100 con Tapatalk 2

P05TMAN said:
Did your tablet seem to freeze after flashing via fastboot? When I push blob, the console shows that it wrote, but then fastboot on the tablet freezes & I have to manually reboot, putting me right back to the drawing board.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
nope. do you use the original cable on usb 2.0 and connected to your pc not a usb hub? should work. if not try a diffrent pc - sometimes usb chipsets make problems.

Buster99 said:
nope. do you use the original cable on usb 2.0 and connected to your pc not a usb hub? should work. if not try a diffrent pc - sometimes usb chipsets make problems.
Click to expand...
Click to collapse
I get invalid argument to all of the erase attempts and the minute I try to push the blob the flashing green icon in fastboot mode on the tablet stops. The command windows says the flash went fine but the tablet is unresponsive and must be reset. Infact any fastboot command that pushed something to the tablet causes it to look up ( indicated by the green flashing RCK icon freezing on whatever phase of green it had at the time)
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.975s]
sending 'system' (800935 KB)...
OKAY [134.565s]
writing 'system'...
OKAY [ 2.040s]
finished. total time: 138.583s
I think its time to bin this doorstop and break something new

d3fiant said:
I get invalid argument to all of the erase attempts and the minute I try to push the blob the flashing green icon in fastboot mode on the tablet stops. The command windows says the flash went fine but the tablet is unresponsive and must be reset. Infact any fastboot command that pushed something to the tablet causes it to look up ( indicated by the green flashing RCK icon freezing on whatever phase of green it had at the time)
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.975s]
sending 'system' (800935 KB)...
OKAY [134.565s]
writing 'system'...
OKAY [ 2.040s]
finished. total time: 138.583s
I think its time to bin this doorstop and break something new
Click to expand...
Click to collapse
Mine does this same thing.....think it's done for?
Sent from my HTC One using xda app-developers app

Buster99, your instructions saved my device. I missed erasing /misc even though you put it in the directions and my tablet's back! I owe you.

[Q] Cannot Reboot Recovery

I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB Download protocol
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000).
I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated.
As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms.

ffalzone23 said:
I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB Download protocol
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000).
I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated.
As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms.
Click to expand...
Click to collapse
I don't know if this method will work on CM. You can give it a shot and report back.
1. Download the Asus firmware from Asus website and extract it once because there is anotherr zip in it.
2. Copy the second zip file to your root directory on your internal sd and reboot
3. If it works, you should see the notification on the lower right corner and click on it. You just follow the instruction to put your device back to the factory bootloader.
Before you use this method, you need to move all your stuff to your computer as a back up because it will wipe everything that you have on your device..
There is another method that you could try if it does not work.. Good luck..:fingers-crossed:

I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification
What is this other method you speak of....
This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time.
On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones?

ffalzone23 said:
I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification
What is this other method you speak of....
This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time.
On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones?
Click to expand...
Click to collapse
Did you unzip it once? You need to have a different firmware version than the one on your system... I will find the other method and link for you..

Thanks Man. I appreciate the help!

ffalzone23 said:
Thanks Man. I appreciate the help!
Click to expand...
Click to collapse
I am still looking for the link. I forgot what it is called... I will post the link here when I find it..

LetMeKnow, Thanks for the update.
Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one!

ffalzone23 said:
LetMeKnow, Thanks for the update.
Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one!
Click to expand...
Click to collapse
By reading your post again, let me summarize it here. You know how to use fastboot, can't boot to your custom recovery (TWRP), want to flash stock recovery to fix your problem, and have try a few methods to put the stock back but it did not work. You still can get to your bootloader menu. Can you try to use this command to see if you can access to your custom recovery: fastboot boot-recovery
Good luck and get back to you on the link...

this is what came up in command prompt....
C:\android-sdk\platform-tools>fastboot boot-recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable

I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there.
C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img
sending 'recovery' (7746 KB)...
OKAY [ 3.606s]
writing 'recovery'...
OKAY [ 2.414s]
finished. total time: 6.022s
C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.548s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s

ffalzone23 said:
I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there.
C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img
sending 'recovery' (7746 KB)...
OKAY [ 3.606s]
writing 'recovery'...
OKAY [ 2.414s]
finished. total time: 6.022s
C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.548s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
Click to expand...
Click to collapse
I have not seen that before, so I don't know what to say...
When I did fastboot TWRP recovery, I used blob file instead of img file. Do you want to download the blob file and try again?
Edit: What version of TWRP did you fastboot? V2.6.3.0 is larger than our partition on the tf700. Therefore, you can not use it..

The .IMG was cwm recovery. I tried that after trying twrp most recent version. 2.6.3.1 I think.
Sent from my XT926 using xda app-developers app

On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.

ffalzone23 said:
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
Click to expand...
Click to collapse
If fastboot doesn't work for you but you have a rooted Android, you can try installing a recovery using the dd method:
Code:
cd wherever/you/downloaded/twrp
su
dd if=openrecovery-twrp-2.6.3.1-tf700t.blob of=/dev/block/mmcblk0p4
then reboot - the bootloader should flash your new recovery with a blue progress bar and reboot again. On the second reboot, hold down volume-down to get to the bootloader menu and try entering RCK again.

ffalzone23 said:
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
Click to expand...
Click to collapse
You can try _that method. He always have good advices and know what he is talking about.....:good:
Good luck....

_that. What screen do I have my tablet on when I run the dd command prompt ?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

ffalzone23 said:
_that. What screen do I have my tablet on when I run the dd command prompt ?
Click to expand...
Click to collapse
You mean the expected output? Something similar to:
Code:
15836+1 records in
15836+1 records out
8108136 bytes (8.1 MB) copied, 0.152395 s, 53.2 MB/s
(the above is from my PC - the TF700 is slower)
Or do you mean where you enter those commands? Either via your PC in an adb shell (in this case you must first transfer the file to the TF700 with adb push or other means), or directly on your tablet with a terminal app under Android (I recommend the one from jackpal, search the Play Store)

I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal.

ffalzone23 said:
I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal.
Click to expand...
Click to collapse
What is the response when you use power and volume down buttons?

It takes me into fastboot or boot loader screen w the rck, android cold boot, and wipe data icons

HELP unrecoverble bootloader error

After trying to flash TWRM img from flashify I get an "unrecoverable bootloader error 0x00000000" I have tried to flash CWM by the same method, with no avail, PLEASE HELP. I can acess CM11 though,and root is still good. the only thing not working is recover

kansasboy001 said:
After trying to flash TWRM img from flashify I get an "unrecoverable bootloader error 0x00000000" I have tried to flash CWM by the same method, with no avail, PLEASE HELP. I can acess CM11 though,and root is still good. the only thing not working is recover
Click to expand...
Click to collapse
I'm sorry I don't have time to post links right now but try to download and install flashboot. If you get that far, you can then download almost any recovery solution and see if you can flash it. I believe the command will be:
Code:
Fastboot -i 0x0B05 flash recovery <file location>
Please read up a bit before you try this. It should flash just the recovery so it shouldn't intefer with the OS or root. Please use caution and read, read, read on the topics (fastboot, TWRP, CWM.)
-Tony

This is the ONLY solution for this problem, worked great for me.
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse

[Q] [SOLVED] Cannot Flash Recovery/Root

Hey all,
I bought a Factor Refurbished TF700t with the intention of getting CROM-i flashed on it. I was able to get it unlocked with no issue, however, whenever I try to flash twrp to it, I get this.
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6948 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
and sometimes this
PS E:\Program Files (x86)\Minimal ADB and Fastboot> fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.009s
I am running the naked USB drivers, usb debugging is enabled and rooting with motochopper does not work. I also downgraded to the 10.6.1.14.8 build. It should be noted that I was on 10.6.1.14.10 build when I did the unlocking, but that didn't seem to effect anything. Lastly, fastboot does see the device as I get this output:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot devices
015d2d43004bfc01 fastboot
My fear is this may be an issue with the factory referb I got, but hopfully that's not the case! If anyone can help me, it would be greatly appreciated!
Edit: Solved! The answer was to do it in Linux. Grab a distro of Mint and get to it! =D

Highsight said:
Hey all,
I bought a Factor Refurbished TF700t with the intention of getting CROM-i flashed on it. I was able to get it unlocked with no issue, however, whenever I try to flash twrp to it, I get this.
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6948 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
and sometimes this
PS E:\Program Files (x86)\Minimal ADB and Fastboot> fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.009s
I am running the naked USB drivers, usb debugging is enabled and rooting with motochopper does not work. I also downgraded to the 10.6.1.14.8 build. It should be noted that I was on 10.6.1.14.10 build when I did the unlocking, but that didn't seem to effect anything. Lastly, fastboot does see the device as I get this output:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot devices
015d2d43004bfc01 fastboot
My fear is this may be an issue with the factory referb I got, but hopfully that's not the case! If anyone can help me, it would be greatly appreciated!
Click to expand...
Click to collapse
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:

LetMeKnow said:
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:
Click to expand...
Click to collapse
Yeah - and also: which TWRP version are you trying to flash?

LetMeKnow said:
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:
Click to expand...
Click to collapse
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
berndblb said:
Yeah - and also: which TWRP version are you trying to flash?
Click to expand...
Click to collapse
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.

Highsight said:
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.
Click to expand...
Click to collapse
Try a different USB port...
Try to wait to plug your device into your PC until your tablet is already in fastboot...
Let me know if this helps... Thx lj

lj50036 said:
Try a different USB port...
Try to wait to plug your device into your PC until your tablet is already in fastboot...
Let me know if this helps... Thx lj
Click to expand...
Click to collapse
Still no luck. I've been at this for a couple days now. I've tried different cords (one from my dad who also has a TF700 and also my old TF100 cords) and different USB ports, same result for all of them. I read somewhere about USB 3.0 possibly causing problems, is this true? I tried my USB 2.0 ports, but the result seemed the same.

Try "fastboot flash staging twrp.blob", maybe this works better. If not, it can't break anything.

_that said:
Try "fastboot flash staging twrp.blob", maybe this works better. If not, it can't break anything.
Click to expand...
Click to collapse
Same result:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot flash staging twrp.blob
sending 'staging' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.007s

OK, then I can only think of "try a different operating system (Linux)" or "try a different computer".

Highsight said:
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
Click to expand...
Click to collapse
So your file is good..
Highsight said:
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.
Click to expand...
Click to collapse
I just flashed twrp v2.7 yesterday and went fast and done.. So the v2.7 is working on the tf700. I think that this might be causing the problem.
Copy your fastboot folder and put it here c:\platform_tools> fastboot -i 0x0B05 flash recovery twrp.blob. I think that android is a unix/linux base so they don't like special characters which means no "space".
Please try that and report back for other users have the same issue, thanks..

LetMeKnow said:
So your file is good..
I just flashed twrp v2.7 yesterday and went fast and done.. So the v2.7 is working on the tf700. I think that this might be causing the problem.
Copy your fastboot folder and put it here c:\platform_tools> fastboot -i 0x0B05 flash recovery twrp.blob. I think that android is a unix/linux base so they don't like special characters which means no "space".
Please try that and report back for other users have the same issue, thanks..
Click to expand...
Click to collapse
Same results...
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.018s
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
C:\platform-tools>
I'm going to try sterilizing my drivers and installing the naked ones again.

I just have to ask.. Your bootloader is unlocked yes ???

Highsight said:
Same results...
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.018s
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
C:\platform-tools>
I'm going to try sterilizing my drivers and installing the naked ones again.
Click to expand...
Click to collapse
I am sorry for a stupid question but do you see "the device is unlocked" in the upper left corner?
Update: Oops, I am slower than you, @lj50036.

lj50036 said:
I just have to ask.. Your bootloader is unlocked yes ???
Click to expand...
Click to collapse
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"

LetMeKnow said:
I am sorry for a stupid question but do you see "the device is unlocked" in the upper left corner?
Click to expand...
Click to collapse
Beat you too It.. @LetMeKnow
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Highsight said:
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"
Click to expand...
Click to collapse
Yes I agree with @_that.... New OS 'Linux' Thats what I would try...

lj50036 said:
Beat you too It.. @LetMeKnow
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Yes I agree with @_that.... New OS 'Linux' Thats what I would try...
Click to expand...
Click to collapse
Lemme see what I can do about setting up a dual-boot for my computer and trying on that. To be honest I'm not great with Linux, especially when it comes to drivers, but I'll see what I can do...

Highsight said:
Lemme see what I can do about setting up a dual-boot for my computer and trying on that. To be honest I'm not great with Linux, especially when it comes to drivers, but I'll see what I can do...
Click to expand...
Click to collapse
O there are no drivers....:good: At least not for your android devices...
I would recommend Mint 16... Here is a link
Mint Download Page
Go for cinnamon desktop....
Shoot me a email if you need any help at all... There is an option to shoot me an email on my user page.....

lj50036 said:
O there are no driver....:good:
I would recommend Mint 16... Here is a link
Mint Download Page
Click to expand...
Click to collapse
Well that's pretty sweet. I assume a live USB will do?

Highsight said:
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"
Click to expand...
Click to collapse
Everything is looking good and you said that your device is communicating with the fastboot command "fastboot devices" with a return of your device serial number. I don't know why that it refuses to write to your recovery partition. Maybe there are some bad blocks in your partition but you just reinstall the stock firmware. I am sorry that I don't have a clue what is going on...

Highsight said:
Well that's pretty sweet. I assume a live USB will do?
Click to expand...
Click to collapse
It will but I would install it native to a hard drive, as we are talking about a 400 dollar tablet.. Your call :fingers-crossed: