Database Info

[Q] help, i think i bricked my tablet

hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?

iostu said:
hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?
Click to expand...
Click to collapse
Unless you can go into fastboot (Power + volume down) there isn't much to do but to sign a petition & wait...
XDA member HAZARD17 has been running a petition
Sign NVflash petition for Transformer TF300T, Prime & Infinity!
https://www.change.org/petitions/asus-nvidia-revert-changes-in-jb-bootloader-that-prevent-nvflash

vconceicao said:
Unless you can go into fastboot (Power + volume down) there isn't much to doo but to wait...
Click to expand...
Click to collapse
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:

iostu said:
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:
Click to expand...
Click to collapse
For someone to come up with a solution, Like a NVflash utility for Tf300...

Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).

Hazard17 said:
Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).
Click to expand...
Click to collapse
i can't flash anything :| in adb it sais <waiting for device> i've tried everything and i can't get it to work.. can you pleeeeeease help me ?

ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please

iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
The USB icon is gone. I sugguest downloading the correct firmware and flashing it with fastboot.
fastboot flash system blob
Download the correct system firmware, open the zip, open the zip, extract the blob to the same directory as fast boot.

iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
4.2 bootloader does not have USB icon, just plug in USB..

i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !

iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
Sounds like you're in the same boat as the rest of us...
http://forum.xda-developers.com/showthread.php?t=2179874

iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
OK. The bootloader menu you now are seeing is the new 4.2 version. RCK - Android - Wipe Data(do not use wipe data).
When you get into this menu if you leave everything alone your tablet should auto into fastboot - watch the screen - upper left.
With fastboot flash the latest (proper) JB blob for your unit.
Good Luck!

iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."

hgoldner said:
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."
Click to expand...
Click to collapse
Here is an example of an adb command that does work to flash twrp with slight modification it will flash stock blob as well.
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I don't know where you are getting your information but you need a new source.
No one said type adb fastboot they are two different things and each has a specific structure to follow.
If the op can get either fastboot or adb to work I'll gladly provide the proper commands.

then you have the same problem as me and a bunch of other people. The bootloader freezes on the flash command, even though it will show success and stuff. It never flashes.
I can push files with ADB and on reboot the files on gone. Since we can't flash with fastboot. We have to send it in to asus at this point. I got quoted $87 + shipping.

sorry, i meant to say just fastboot. i didn't write adb fastboot.. i've tried everything you guys said, but with no success my last resort is to send it to asus for re-softing. It costs about $80 + shipping. It doesn't sound like a lot of money, but it's a price to pay for stupidness or noobness i just hope they can repair it or otherwise i'll have a very expensive thing on whch to chop onions
thanks again guys for helping me

[Q] Bricked TF300T - ADB semi ok, no fastboot, some (strange) options left

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??)

Potential Soultion
Quote:
TheArkive said:
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??)
Click to expand...
Click to collapse
Hi there.
Buster99 kind of had the same problem, and he managed to unbrick it.
All credit goes to Buster99.
Here is his post:
http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
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
Hope this helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.

Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster

You guys rock! I'll try that as soon as i get home!!
∫εทт ƒя๑๓ ๓γ αทδя๑ïD

Successfully unbricked!!!
I can't thank you guys enough!
At the moment I'm able to run the stock 4.2.1. TWRP (the right one) is installed, and all seems to be working. When I did a backup of the stock ROM on TWRP it said FAILED up top, but everything else seemed to go ok. There were 2 other error messages too:
Code:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
I know usually the recovery and boot aren't messed with when running a custom recovery, so I didn't really worry about it, but I figured I'd post it here just in case.
Now I'm messing around with a few versions of CyanogenMod. I guess I'll try the "failed" backup if neither version of CM wants to work. Since I have fastboot back I can of course re-load the blob from the 4.2.1 stock update.
Seems like the latest stable CM (10.0.0) doesn't work so well on the 4.2.1 bootloader? Or should it matter? Now I'm trying the nightly (10.2) and it loaded up much quicker than CM 10.0
Thanks again guys!

Quote:
TheArkive said:
Successfully unbricked!!!
I can't thank you guys enough!
At the moment I'm able to run the stock 4.2.1. TWRP (the right one) is installed, and all seems to be working. When I did a backup of the stock ROM on TWRP it said FAILED up top, but everything else seemed to go ok. There were 2 other error messages too:
Code:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
I know usually the recovery and boot aren't messed with when running a custom recovery, so I didn't really worry about it, but I figured I'd post it here just in case.
Now I'm messing around with a few versions of CyanogenMod. I guess I'll try the "failed" backup if neither version of CM wants to work. Since I have fastboot back I can of course re-load the blob from the 4.2.1 stock update.
Seems like the latest stable CM (10.0.0) doesn't work so well on the 4.2.1 bootloader? Or should it matter? Now I'm trying the nightly (10.2) and it loaded up much quicker than CM 10.0
Thanks again guys!
Click to expand...
Click to collapse
Glad to have helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.

Buster99 said:
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
Click to expand...
Click to collapse
Buster,
Looking around you are the master with these tablets. I have a question. I am on CM 10.2 I flashed TWRP 2.6.3.0 In my hast I flashed the TF300TG recovery. My tablet always boots straight to recovery but I can't mount anything. I discovered that I can use ADB commands and have it boot to the bootloader. From there I can select the android operating system and the tablet boots and runs as normal. I then tried to flash the correct recovery the same way through terminal emulator on the tablet. It says that it pushed the recovery fine but no change was made. I then tried booting into fastboot and flashing through the computer. As soon as I hit enter the green flashing box around RCK stops flashing and the computer says it was successful but it just sits there. I have to force the tablet to reboot. Reboots right to recovery with no change and I have to use ADB to get back to the bootloader in order to boot the tablet.
Is there another way to get recovery on the tablet? Do you think I'm going to have to redo the whole thing in order to get it working again? Not sure if it matters but in fastboot it says Key driver not found.. Booting OS

hatdrc said:
Buster,
Looking around you are the master with these tablets. I have a question. I am on CM 10.2 I flashed TWRP 2.6.3.0 In my hast I flashed the TF300TG recovery. My tablet always boots straight to recovery but I can't mount anything. I discovered that I can use ADB commands and have it boot to the bootloader. From there I can select the android operating system and the tablet boots and runs as normal. I then tried to flash the correct recovery the same way through terminal emulator on the tablet. It says that it pushed the recovery fine but no change was made. I then tried booting into fastboot and flashing through the computer. As soon as I hit enter the green flashing box around RCK stops flashing and the computer says it was successful but it just sits there. I have to force the tablet to reboot. Reboots right to recovery with no change and I have to use ADB to get back to the bootloader in order to boot the tablet.
Is there another way to get recovery on the tablet? Do you think I'm going to have to redo the whole thing in order to get it working again? Not sure if it matters but in fastboot it says Key driver not found.. Booting OS
Click to expand...
Click to collapse
try fastboot erase recovery then reflash scannos latest twrp for kitkat from his omnirom thread. (also i think that 2.6.3.0 and above are kitkat recoveries)
this way you are at least sure that your recovery partition is clean.
also I use @scanno omni rom as my daily driver try it. (but bear in mind that without a jb backup you will have to do some work getting jb running again)
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
try fastboot erase recovery then reflash scannos latest twrp for kitkat from his omnirom thread. (also i think that 2.6.3.0 and above are kitkat recoveries)
this way you are at least sure that your recovery partition is clean.
also I use @scanno omni rom as my daily driver try it. (but bear in mind that without a jb backup you will have to do some work getting jb running again)
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I went into fastboot and and erase recovery. Did it. Then I tried to flash recovery and again it locks up. Rebooted and it went straight to CM 10.2 Tried flashing recovery with terminal emulator. Said it was copied. Rebooted went back to CM. Rebooted again to recovery but it went back to CM. Booted to fastboot again and selected RCK. now it says
Booting Recovery kernel image
Booting failed
Unrecoverable bootloader error (0x00000000)
It does boot to CM but now I have no recovery. OmniRom was the one I wanted to flash but at this point I'm thinking im going to have to start from square one. I just don't understand why it doesn't want to flash a recovery
Thank you for your help, you are the man

strange, which recovery did you try to flash just now? what is the output in fastboot when you flash the recovery there?
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
strange, which recovery did you try to flash just now? what is the output in fastboot when you flash the recovery there?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was trying to flash the most current blob from the twrp site. I get the following:
fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.965s]
finished. total time: 1.965s
fastboot -i 0x0b05 flashe recovery twrp.blob
sending 'recovery' (6448 kb)...
OKAY [ 2.561s]
writing 'recovery'...
OKAY [ 2.394s]
finished. total time: 4.955s
When I erase recovery the green flashing box on the tablet keeps flashing. When I try to flash the recovery the box just stops on what ever shade of green it was on when I hit enter. Also after if I do fastboot devices I get:
???????????? fastboot

hatdrc said:
fastboot -i 0x0b05 flashe recovery twrp.blob
Click to expand...
Click to collapse
flashe?
please try scannos version via fastboot.
gl
buster
Sent from my TF300T using XDA Premium 4 mobile app

Buster99 said:
flashe?
please try scannos version via fastboot.
gl
buster
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry, typo. Should have been flash.
So i unzipped the recovery.img file and placed it in my fastboot folder. I get the same results.
fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' (6892 KB)...
OKAY [ 2.445s]
writing 'recovery'...
OKAY [ 2.477s]
finished. total time: 4.922s
The green box stops flashing as soon as I hit enter
Could it be that my recovery partition as gotten messed up, would formatting it help you think. Guess there's only one way to find out.
EDIT: Never mind, can't format a 'basic' filesystem

huh?
fastboot erase recovery
then
fastboot reboot bootloader
then
fastboot flash recovery scannostwrp2.6.3.1
fastboot reboot
then boot into recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
huh?
fastboot erase recovery
then
fastboot reboot bootloader
then
fastboot flash recovery scannostwrp2.6.3.1
fastboot reboot
then boot into recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Still a no go. The only recover on there was a flashable zip file. That's why I was trying to get anything on it so I could flash that. I'm at the end of my knowledge. I've always had Samsung so I got use to odin. Never had to use fastboot. I really appreciate your help. Guess its going to have to run CM10.2 and hope it doesn't have a problem
Sent from my SGH-T999 using Tapatalk

odin is a bastardisation of standards set by google.
please check the tf300 forum. there is a how to for noobs or smth like that with a script that does all. mb you have more luck with that
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
odin is a bastardisation of standards set by google.
please check the tf300 forum. there is a how to for noobs or smth like that with a script that does all. mb you have more luck with that
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will take a look, and I thank you for the time you have spent with me! If all else fails at least its running and usable for now.
Sent from my SGH-T999 using Tapatalk

Buster99 said:
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
Click to expand...
Click to collapse
Hi Buster,
I have a similar problem, but I cant reach the fastboot. I tried to reset and push volume down, connect tablet to PC with volume down pushed, turn off and start the tablet with the volume down pushed, but nothing. My recovery is corrupted, because it doesnt recognize any file in the SD. I tried to type adb reboot bootloader from the pc, but it says "erro: device not found".
Do you have any idea?

Help
this problem looks similiar to mien can you pls read my problem and help me? why no replies? I had a feel that the devs of this site are the best but no one helped me
http://forum.xda-developers.com/showthread.php?t=2755322
+needle wont do anything for me cos mine boots to twrp logo and stay there for ever until battery is drained :/ hellp

It's not the exactly the same problem... For me ADB doesnt work.....
ConsoleFreak said:
this problem looks similiar to mien can you pls read my problem and help me? why no replies? I had a feel that the devs of this site are the best but no one helped me
http://forum.xda-developers.com/showthread.php?t=2755322
Click to expand...
Click to collapse

TF300t constantly booting into recovery

I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?

tjk639 said:
I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?
Click to expand...
Click to collapse
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.

cmendonc2 said:
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.
Click to expand...
Click to collapse
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.

tjk639 said:
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.
Click to expand...
Click to collapse
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"

cmendonc2 said:
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"
Click to expand...
Click to collapse
Where do I find "fastboot devices"?

tjk639 said:
Where do I find "fastboot devices"?
Click to expand...
Click to collapse
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.

cmendonc2 said:
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.
Click to expand...
Click to collapse
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.

tjk639 said:
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.
Click to expand...
Click to collapse
hmm idk. Im guessing you flashed the wrong version of TWRP, which has ended up in a brick for most users, but they had fastboot access and could later recover it using this: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. You dont seem to have either ADB or fastboot, and TWRP is in a non working state. You could try reinstalling your fastboot and ADB drivers with the universal naked drivers, and then retrying ADB reboot bootloader and fastboot.

All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.

tjk639 said:
All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.
Click to expand...
Click to collapse
No problem, glad I could help!

[Q] Unable to boot out of TWRP

I was attempting to install a ROM on my Transformer TF300T and I've apparently done something severe to it.
Right now I have TWRP 2.6.3.0 on it. I've apparently broken the /data, /cache, and internal storage, they're all unable to mount now. I cannot user the PWR and VOL DOWN buttons to get to fastboot anymore, it just ignores the fact that i'm holding those buttons down and only boots into TWRP. I can't choose the ADB Sideload option in TWP, it fails because of the broken partitions. I am able to connect to it in adb from my desktop, and I can push files to it, but I haven't been able to find anything that lets me fix the partitions or fastboot.
I can provide any other info necessary, but I have no idea what further to do with it.

greymonk said:
I was attempting to install a ROM on my Transformer TF300T and I've apparently done something severe to it.
Right now I have TWRP 2.6.3.0 on it. I've apparently broken the /data, /cache, and internal storage, they're all unable to mount now. I cannot user the PWR and VOL DOWN buttons to get to fastboot anymore, it just ignores the fact that i'm holding those buttons down and only boots into TWRP. I can't choose the ADB Sideload option in TWP, it fails because of the broken partitions. I am able to connect to it in adb from my desktop, and I can push files to it, but I haven't been able to find anything that lets me fix the partitions or fastboot.
I can provide any other info necessary, but I have no idea what further to do with it.
Click to expand...
Click to collapse
Try using fastboot as soon as the Tablet boots into the loading screen of TWRP. That worked for some people.

cmendonc2 said:
Try using fastboot as soon as the Tablet boots into the loading screen of TWRP. That worked for some people.
Click to expand...
Click to collapse
I tried this, fastboot doesn't seem to see it.
I also tried pushing an earlier blob of TWRP, 2.5, just to see if the if it would do that much. It doesn't seem to work. It still has 2.6.3.0 installed, even though it looked like it was responding properly.
Code:
C:\android_sdk\sdk\platform-tools>adb shell
~ # ←[6ndd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
12896+1 records in
12896+1 records out
6602856 bytes (6.3MB) copied, 0.091592 seconds, 68.8MB/s
~ # ←[6n
It also has the weird ~ # ←[6n as a prompt in the adb shell.

Type adb reboot bootloader
Sent from my GS3 on Carbon KK using Tapatalk 4

ebildude123 said:
Type adb reboot bootloader
Click to expand...
Click to collapse
That worked. I just need to, presumably, rebuild the /data and /cache partitions, I assume?

Well, I think I've completely killed it now. I think I had originally put the wrong TWRP onto it. I tried pushing the correct one to it with fastboot, and now it will either 1) do an infinite boot loop, or 2) boot to the fastboot screen but 'fastboot devices' does not see it. I can't see what else I can do with it at this point.

greymonk said:
Well, I think I've completely killed it now. I think I had originally put the wrong TWRP onto it. I tried pushing the correct one to it with fastboot, and now it will either 1) do an infinite boot loop, or 2) boot to the fastboot screen but 'fastboot devices' does not see it. I can't see what else I can do with it at this point.
Click to expand...
Click to collapse
Shoot me an email at [email protected] we can continue there... Thx lj

lj50036 said:
Shoot me an email at [email protected] we can continue there... Thx lj
Click to expand...
Click to collapse
Dude, thanks again. I really can't thank you enough for resurrecting this thing. :victory:

Bootloop when starting android or RCK

I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.

Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk

Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.

That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk

Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)

I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?

double post

Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.

Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!

Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385

berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??

berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks

ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!

monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks

ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.

monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks

ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.

monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!

berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.

monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?