[Transformer TF300T Q&A, Help & Troubleshooting] TheArkive:
I made a really stupid mistake...

The Good Part:

...I flashed my bootloader/blob via fastboot with the latest update from ASUS (TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip), and at that point no problems. Messed around with the thread that mentioned CWM (regular and JB). Found that I couldn't access the SD Cards with CWM JB, so I tried flashing TWRP.

The Bad Part:

I read everything closely, ..... except the darn file name on the TWRP site, so I ended up flashing the TF300TG by accident, instead of the TF300T recovery.

Here's the sum of what I have left:

- no fastboot (Power + VOL DOWN won't work)

- I read about APX mode (Power + VOL UP???) but no dice there if that is supposed to work

- after i realized I lost fastboot I think I panicked and managed to erase the current firmware, so no OS currently on the device

- I think that I may have killed busybox on the device, and any chance of fully using ADB the normal way to restore ROOT/anything else

- I can get into TWRP recovery

- I can use the ADB connection, but none of the commands that would normally use busybox actually work

- under NORMAL circumstances I can't access the internal memory (/SDCard/ mount) nor can I access the external memory

- I CAN select the option to mount SYSTEM, but the contents of SYSTEM are actually my external SD Card (so I can put files on my device)

Through my hours of googling (and searching XDA) i found a thread for another device that mentioned fixing the mount points. I can't seem to find that thread, but again it was for another device, so the commands would probably be different for all the mount points anyways.

So in a nutshell:

- I can use the basic linux commands (like LS and CD), on ADB and in TWRP command line mode, but no mount or push/pull commands

- I can mount "SYSTEM" from TWRP GUI but the contents of SYSTEM are actually my external SD Card, so I can put files on the device

- I can still use TWRP to CHMOD stuff

--->>> Remaining mounts that seem in tact: (all entries are folders unless specified / anything not specified such as ROOT or SDCARD exists but is blank)

- / contains

/default.prop and several other files

- /DEV/

/block

/bus

/graphics

/input

/log

/ts

/snd

/socket

- /ETC/

/fstab (file)

/mke2fs.conf (file)

/mtab (file)

/recovery.fstab (file)

- /LICENSE/

/openaes

- /PROC/

...... lots of folders with numbers for file name

- /RES/

/fonts

/images

- /SBIN/

...lots of files... starting with [, [[, adbd, adjtimex, arp, ash, awk, base64.....

- /SUPERSU/ ... (i tried install from zip with superuser and SuperSU, and TWRP keeps offering to install SU every time I restart)

/99SuperSUDaemon (file)

/install-recovery.sh (file)

/su (file)

/Superuser.apk (file)

- /SYS/

/block

/bus

/class

/dev

/devices

/firmware

/fs

/kernel

/module

/power

/tf_driver

- /SYSTEM/

/bin (but it is empty, when I actually mount SYSTEM, it is then replaced with the contents of my external SD Card)

- /TMP/

/recovery.log (file) ... I think this was an attempt to use TWRP command button to "Copy Log to SD"

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

I know recovering from this is a major long shot, but the good news is, I have all the data backed up, so nothing is actually lost. Granted I have brick, but it's a brick that I can actually play with, and ADB still partially works. I was wondering about manually installing busybox, fixing mount points, etc, so that I could get back to a state of flashing the proper recovery and/or reflashing the bootloader to an older version.

Of course I'm noob enough to not know exactly where to start, with manually reviving busybox, fixing mount points, and using all this to actually push a bootloader or recovery without fastboot ... and I'm hoping desperately that someone will take a little pity (at least enough to see me squirm???)

I'll appreciate any advice at all to help me recover from my stupidity. I know this is a major long shot. Of course, I'm not above paying ASUS a pretty penny to fix it either, but I'd rather learn and better myself before I shell out money.

I've read a few things about letting the battery completely run out when trying to fix some cases of BRICK ... and supposedly that may get you fastboot back, but I'm holding off on that for the time being while it seems that I may still have a shot since I don't exactly have a 100% brick. My device won't stay on, I can shut it off... (i also read that device staying on all the time = brick??)