[Asus Transformer TF700] MiM81:
Hey guys...

I think I'm in serious problems with my tf700... :(

I run (ran...) Chromi-X on internal with f2fs-formatted /data and the modified twrp from the xda f2fs thread.

I didn't do anything special and used the pad in this configuration for a few days (some time ago I used Zombi-X for a while... I often switched between ROMs and never had any problems with my pad).

Though I had to unbrick my device some weeks ago for another reason, so I know how to unbrick it with the wheelie method.

Here is what I did:

During the day I noticed the dock battery to be empty and the pad battery being ~ 45%. I didn't care about that, because I used the pad very long before and never had battery drain problems.

After a few hours when I was back at home my pad was shut down. I wondered if this might be caused by a somehow fully drained battery during the time I have been away.

So I pressed power button, the pad vibrated twice and the boot menu with the 4 green penguin appeared.

After the first line of the preinit script nothing else appeared for minutes, so I turned the pad off again and then turned it on while pressing volume down.

When I tried to enter rck, the 4 black penguin appeared, but instead of starting recovery there is just a line that reads "a n d r o i d _" blinking for minutes.

I tried the above steps for several times without success.

So I turned the pad off again, plugged it into my pc, then turned it on pressing volume down and started a linux terminal, typing "adb devices". The device is recognized as usual.

So I tried to reflash twrp recovery using adb. Doesn't complete sending data or doesn't send data at all, I don't know...

EDIT: I mean fastboot, not adb.

fastboot -i 0x0B05 flash recovery twrp.blob

Ok, last chance... I turned the pad off again and then started it using power and volume up to start apx mode.

Then I bootstrapped (successfully) with wheelie and entered nvflash mode:

~/adb $ sudo ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x15d456d7e34180c
[=] RCM Version: 0x30001

[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

But when I try to nvflash my unlock-token.img it doesn't finish sending it or doesn't send it at all... no error message, nor in terminal nor on pad, just nothing...

sudo ./nvflash -r --download 7 unlock-token.img
Nvflash v1.13.87205 started
[resume mode]
sending file: unlock-token.img

After waiting for many many minutes I opened another terminal, typing "adb devices". Device is no longer present.

(I have to mention that I don't know if this is normal or not while in apx mode, just writing down everything what I did)

So I pressed power button to shutdown the pad.

Immediately the other terminal window (running NVflash) told me:

\ 131072/8388608 bytes sentdata send failed NvError 0x8
command failure: partition download failed

Wow... 131 kb out of 8390?

How long can (should) it take to send the unlock-token.img?

I don't know what to do now...

Should I press the tiny reset hole? :/

Or should I wait for ...hours... to send the unlock-token.img?

greets,

MiM81