Database Info

[Q] TF101 BB0 full bricked...

Hi,
I have a BB0 eeepad. So, I've tryied to change kernel, After doing that, my eeepad continue rebooting, stucking on the Eeepad first screen (before the asus logo). CWM is not accessible, if I try to power on in apx mode, the tablet does that correctly. I have installed the correct driver using your tutorial (video) but i get the following error:
rcm version 0X4
Command send failed (usb write failed)
If I try to get into CWM, i get the double icon screen, wipe data or android. If i choose wipe, it works, but the tf101 won't boot. If i choose android, the screen show me "cold booting android" and it get freezed...
Could you help me ?
Thank you

Boot into recovery, you have to press Volume UP before the option to 'wipe' or 'cold boot' comes up to get into recovery. I have a feeling you aren't doing that.

Nope, i did it, but in this case, it continues to reboot in loop... (Same as wipe data)

You have a BBO so APX mode is not gonna do anything for you.
So Vol down plus power button till you see words at top left
Immediately push Vol up within 5 sec to get into recovery.
If you wait too long you get the cold boot/wipe data option.
So you're saying even pushing Vol up within the 5 sec don't work?

baseballfanz said:
You have a BBO so APX mode is not gonna do anything for you.
So Vol down plus power button till you see words at top left
Immediately push Vol up within 5 sec to get into recovery.
If you wait too long you get the cold boot/wipe data option.
So you're saying even pushing Vol up within the 5 sec don't work?
Click to expand...
Click to collapse
Yep, Immediately Reboot over and over again...

can you or not acces to cwm? if you can your device is not fully bricked
wich version of cwm recovery do you have?

I have the same issue, I have a B70, I have CWM Version v5.5.0.4, and can access it. I can get in to APX mode, and tried the NVFlash with the hopes I was one of the lucky B70's but got the same message:
rcm version 0X4
Command send failed (usb write failed)
I can get in to the cold boot screen, but I ONLY have the wipe data option, I do not have the Android logo option. Any help would be appreciated with this... I was definitely not trying to hijack this thread, but I really didn't think it was necessary to post a new thread for the same issue.
I get stuck on the Eee Pad startup logo. I can see the tablet in Device Manager as Asus TFP Device, but cannot get ADB serial to recognize it.

If you have no recovery, and you cannot get into your ROM, and you are SBK2..hang it up, you FUBARed your tab..sell it to someone who needs some hardware maybe? Try to RMA it to Asus, who knows- and then go sign the petition to release the SBK2 and this problem would not inconvenience you or Asus any longer when this happens..
Sorry guys

magnumrt562 said:
I have the same issue, I have a B70, I have CWM Version v5.5.0.4, and can access it. I can get in to APX mode, and tried the NVFlash with the hopes I was one of the lucky B70's but got the same message:
rcm version 0X4
Command send failed (usb write failed)
I can get in to the cold boot screen, but I ONLY have the wipe data option, I do not have the Android logo option. Any help would be appreciated with this... I was definitely not trying to hijack this thread, but I really didn't think it was necessary to post a new thread for the same issue.
I get stuck on the Eee Pad startup logo. I can see the tablet in Device Manager as Asus TFP Device, but cannot get ADB serial to recognize it.
Click to expand...
Click to collapse
You need to put working adb. try with a linux livecd or whatever you can, with that version of cwm recovery you will need some commands to be able to acces a microsd card and reflash the device

I'll send to Asus... Let it try...
But no, I've no access to CWM...

Antjac said:
I'll send to Asus... Let it try...
But no, I've no access to CWM...
Click to expand...
Click to collapse
You more than likely voided your warranty by flashing or rooting your device BTW..so good luck getting Asus to cooperate (fooling them)

Unfortunatlly, i've not other choice... (except if NvFlash's team find a solution for B70+)...
Wait and see...

When I try to get adb to recognize the tablet, it runs for a second, then lists attached devices , but no serial #. It does not say no devices or anything... is there any hope I can push a rom?

magnumrt562 said:
When I try to get adb to recognize the tablet, it runs for a second, then lists attached devices , but no serial #. It does not say no devices or anything... is there any hope I can push a rom?
Click to expand...
Click to collapse
That is supposed to happen, you need to execute adb shell to get a shell or adb push file /sdcard/ to push a file to the sdcard

I have the exact same thing, upgraded to ics, all worked ok, rooted, all ok for 2 day then nothing after a reboot, cant nvflash vol+ & power doesnt find any options bar stock if i recover goes to dead android with ! then asus logo and nothing. So it seems the issue is with the upgrade but as most of us rooted we may have a problem, mind you i did the wipe and recovery so it may have erased evidence.

If anyone is selling a TF101 I would love to buy one...
I forgot my TF101 on top of the car and ran it over, still works but the housing and lcd digitizer are dead >.<
Please email or pm me if interested

Well, good news...
As I said, I've sent my TF101 to Asus (to Czech Republic). I said my Tablet was bricked by updating to the ICS rom (That's not wrong in fact...).
So no problem, they flashed my tablet and sent it back. I've received it yesterday, everything is OK

[Q] Can't unbrick. Tried nigh everything.

Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=

If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!

Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!

Yeah, what Mjamocha said...

okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.

okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?

Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.

slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.

Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.

slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.

I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.

slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).

Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?

slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?

How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.

slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?

I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?

I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium

I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?

cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium

[Q] Help with rooted transformer that won't boot up

Hi all,
Been recommed to come here as my transformer seems to be stuck in a bit of a loop. I'm running ICS and rooted a few weeks back with "unlock root" its been telling me for a few days that there's new firmware but I'd not updated as not sure what would happen with being rooted, anyway lent the tablet to a family member who's clicked the update and now I seemed to be stuck with this screen (attached) wont turn off and keeps restarting.
Wondered if anyone can help me out with a soultion. Thanks in advance

Searh bar
http://forum.xda-developers.com/showthread.php?t=1530337
Start reading this thread. All i did was look at your pic and typed the word in the bottom left
Clockworkmod recovery 5.5.04 bootloop
Start reading a bunch or you will own a nice paper weight

DaveG46 said:
Hi all,
Been recommed to come here as my transformer seems to be stuck in a bit of a loop. I'm running ICS and rooted a few weeks back with "unlock root" its been telling me for a few days that there's new firmware but I'd not updated as not sure what would happen with being rooted, anyway lent the tablet to a family member who's clicked the update and now I seemed to be stuck with this screen (attached) wont turn off and keeps restarting.
Wondered if anyone can help me out with a soultion. Thanks in advance
Click to expand...
Click to collapse
Hold the Vol down + Power button.
Wait till you see the options of Cold boot Linux or Wipe data.
Choose Cold boot Linux. It should boot the tablet into the OS.
Now go to play store and download "terminal" (if not already).
Open Terminal
Type in
Code:
su
You should get a # sign meaning you have super user permission
Now type in
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
after that reboot tablet.

Cheers for the reply sandman7793
baseballfanz went with the Vol + power option and the transformer booted back up and seems that its back to factory settings as it's asked me to set up wifi e-mail etc .Would I need to still download terminal?

DaveG46 said:
Cheers for the reply sandman7793
baseballfanz went with the Vol + power option and the transformer booted back up and seems that its back to factory settings as it's asked me to set up wifi e-mail etc .Would I need to still download terminal?
Click to expand...
Click to collapse
If it's booting normally i guess you're fine. If it keep rebooting into recovery then do the steps above with terminal.
To test just press and hold the power button till the tf reboot

Thanks

I'm back, seem that the solution I tried works but only until the battery goes dead or I when I turn off the device, then am back to the same problem. Tried terminal, but don't get the message back when I used it (may have the wrong version). Is there anything else I can try or is,it start reading the link sandman7793 gave? Cheers

TF300 bricked?

So I've searched thru the thread...but I don't know what to search for. Let me explain my problem:
I had Unlocked the device, had TWRP as recovery and was running cleanROM 1.2. So I downloaded cleanROM 2.5 (JB) and put that on my SD card. I also read that I needed TWRP 2.2.2.0 to load it.
So I downloaded and fastbooted TWRP 2.2.2.0 ICS.blob, recovery flashed ok and was able to install cleanROM. Upon reboot, it just bootlooped.
So I figured I needed TWRP 2.2.2.0 JB.blob. I fastboot installed that with no problem but when I rebooted to fastboot mode, I stupidly selected to wipe data from there and now the tablet bootloops with no option for the fastboot. when I try to hold down the power and volume down key the device states "Android cardhu-user bootloader (2.10 e) released by "US_ePad-9.4.3.30-20120604" A03 checking for Android ota revovery" then goes to Booting recovery kernal image.
Did I kill it?

I'm going to assume from your post that you were running ICS bootloader and had never updated to stock JB, if so you were ICS.
I read your post last night but didn't have an answer to your problem so I decided to sleep on it.
If I surmised correctly in my previous statements you had an ICS bootloader and flashed a JB rom, then you flashed a JB recovery while you still had an ICS bootloader. I don't think the data wipe is a factor here. You can't mix and match ICS and JB recoveries and roms the bootloader must match.
I know; how does this help me. We need to establish your situation absolutely if there is any chance of recovery.
I'm still thinking about your situation and your reply will give myself and many others reading your post enough info to consider your options.

I fastboot is not working and you were still on ICS bootloader, try if ADB works.
If yes type this:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
then press enter
Then type this
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and press enter.
Now try if you get fastboot back. If yes fastboot the ICS recovery and then you should be good to go.
1st flash the ICS Stock Rom and then fastboot the ICS recovery again. Now you should be back to normal.
If this doesn´t work dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
unpack it
run WSGFlasher batch
choose 2 as selection and press enter
in the new window choose 1 to fully unbrick and press enter
in the new window choose 1 to Full recovery and press enter
let it run. Needs about 5 to 15 minutes
When everything is done reboot.

tobdaryl said:
I'm going to assume from your post that you were running ICS bootloader and had never updated to stock JB, if so you were ICS.
I read your post last night but didn't have an answer to your problem so I decided to sleep on it.
If I surmised correctly in my previous statements you had an ICS bootloader and flashed a JB rom, then you flashed a JB recovery while you still had an ICS bootloader. I don't think the data wipe is a factor here. You can't mix and match ICS and JB recoveries and roms the bootloader must match.
I know; how does this help me. We need to establish your situation absolutely if there is any chance of recovery.
I'm still thinking about your situation and your reply will give myself and many others reading your post enough info to consider your options.
Click to expand...
Click to collapse
So I'm new to the TF300 as you can probably guess. I flash roms constantly with my S-off Rezound and my prior OG Droid. I'm not new to the game, just new to the TF300t.
I did finally grab the right keywords and found pretty similar posts to what happened to me, and it looks like I bricked it. (though I sure hope not.)
I think you are right that the data wipe isn't the factor. I just thought I needed a JB recovery to flash the JB rom. You know how a certain boot.img will just send your phone into a bootloop, but you flash the correct boot.img, and it'll boot straight into the rom? That was my thinking going into this. (guess I should have taken MORE time to read instead of bullishly charging in...
I also believe you are right in your first statement, I received the tablet with ICS. I rooted it and flashed CleanRom 1.2 immediately, and haven't flashed again. I saw jellybean (Cleanrom 2.5) out and thought, why not? Flashed TWRP 2.2.2.0 ICS and proceeded to install CleanROM 2.5. I did not know I needed to be on a JB bootloader. You are correct in that. BUT....after flashing the TWRP 2.2.2.0 JB recovery, I WAS able to go back into fastboot mode and could switch between Android/USB/Wipe Data... if only I had chosen the USB option.....
I await any help you can offer.
Thanks so much.

mikaole said:
I fastboot is not working and you were still on ICS bootloader, try if ADB works.
If yes type this:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
then press enter
Then type this
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and press enter.
Now try if you get fastboot back. If yes fastboot the ICS recovery and then you should be good to go.
1st flash the ICS Stock Rom and then fastboot the ICS recovery again. Now you should be back to normal.
If this doesn´t work dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
unpack it
run WSGFlasher batch
choose 2 as selection and press enter
in the new window choose 1 to fully unbrick and press enter
in the new window choose 1 to Full recovery and press enter
let it run. Needs about 5 to 15 minutes
When everything is done reboot.
Click to expand...
Click to collapse
Thanks so much, I just returned home from a trip and will try this first thing in the morning.
Though I feel like the bootloop it's stuck in doesn't give me enough time for ADB to work. If ADB doesn't work, I think I'm bjorked.

SO if I read you guys correctly, I would manually have to flash a JB bootloader? It's not something that happens automagically when you flash a ROM? I never flashed a bootloader, just the two recoveries, then once in recovery, the ROM.

Xsoldier2000 said:
So I'm new to the TF300 as you can probably guess. I flash roms constantly with my S-off Rezound and my prior OG Droid. I'm not new to the game, just new to the TF300t.
I did finally grab the right keywords and found pretty similar posts to what happened to me, and it looks like I bricked it. (though I sure hope not.)
I think you are right that the data wipe isn't the factor. I just thought I needed a JB recovery to flash the JB rom. You know how a certain boot.img will just send your phone into a bootloop, but you flash the correct boot.img, and it'll boot straight into the rom? That was my thinking going into this. (guess I should have taken MORE time to read instead of bullishly charging in...
I also believe you are right in your first statement, I received the tablet with ICS. I rooted it and flashed CleanRom 1.2 immediately, and haven't flashed again. I saw jellybean (Cleanrom 2.5) out and thought, why not? Flashed TWRP 2.2.2.0 ICS and proceeded to install CleanROM 2.5. I did not know I needed to be on a JB bootloader. You are correct in that. BUT....after flashing the TWRP 2.2.2.0 JB recovery, I WAS able to go back into fastboot mode and could switch between Android/USB/Wipe Data... if only I had chosen the USB option.....
I await any help you can offer.
Thanks so much.
Click to expand...
Click to collapse
Please see the post directly below mine. mikaole has already provided an excellent path to recover your unit.
Good Luck!

tobdaryl said:
Please see the post directly below mine. mikaole has already provided an excellent path to recover your unit.
Good Luck!
Click to expand...
Click to collapse
Thanks all, but I can't get ADB working on it. It's just a constant reboot - loop.
I guess I need to contact ASUS and try to get it repaired... cheaply, I hope.

Xsoldier2000 said:
Thanks so much, I just returned home from a trip and will try this first thing in the morning.
Though I feel like the bootloop it's stuck in doesn't give me enough time for ADB to work. If ADB doesn't work, I think I'm bjorked.
Click to expand...
Click to collapse
Time for adb; interesting statement. It brings to mind something I have used on another unit with bootloop and on several other units to get boot logs.
I'll try to describe. In terminal you use a command and afterwards if you wish to use the same command you use up arrow and the last command is typed for you and just hit return. I think this also works in windows cmd but can't verify.
Why do we care? Get in terminal and type the first adb command given above and hit return. Now we can send this command twice in one second. Up arrow ( command typed for you ) power on unit, hit return, up arrow hit return, etc. You could verify if there is an adb window of time available by typing adb devices and look at the output. Anything other than devices and blank means there is an adb window.
Sorry; easy to do but hard to describe. Worth a try if you are ready to ship off. This is the only other thing I can think of for your situation.
Good Luck!

tobdaryl said:
Time for adb; interesting statement. It brings to mind something I have used on another unit with bootloop and on several other units to get boot logs.
I'll try to describe. In terminal you use a command and afterwards if you wish to use the same command you use up arrow and the last command is typed for you and just hit return. I think this also works in windows cmd but can't verify.
Why do we care? Get in terminal and type the first adb command given above and hit return. Now we can send this command twice in one second. Up arrow ( command typed for you ) power on unit, hit return, up arrow hit return, etc. You could verify if there is an adb window of time available by typing adb devices and look at the output. Anything other than devices and blank means there is an adb window.
Sorry; easy to do but hard to describe. Worth a try if you are ready to ship off. This is the only other thing I can think of for your situation.
Good Luck!
Click to expand...
Click to collapse
I will def. try that. I have only usually tried the adb once it's in the loop, not from cold start.
I am aware of the command line trick, I've been using Linux for about 7 years, and was surprised to see it in windows.
Great idea to get it running before hand though, enter > up Arrow . enter > up arrow......

Xsoldier2000 said:
I will def. try that. I have only usually tried the adb once it's in the loop, not from cold start.
I am aware of the command line trick, I've been using Linux for about 7 years, and was surprised to see it in windows.
Great idea to get it running before hand though, enter > up Arrow . enter > up arrow......
Click to expand...
Click to collapse
No go. I drained the battery, then plugged it in for like 20 minutes to charge. I got ADB ready with adb devices and began trying.
No devices. for the heck of it I plugged in my phone during the up arrow enter marathon, and adb picked up the phone right away.
Sucks, but thanks so much for all your help. Looking for a refurb or a repair place now.

I'm sorry but I don't know anything else to try.
There is a manual reset on the side below the sdcard.

tobdaryl said:
I'm sorry but I don't know anything else to try.
There is a manual reset on the side below the sdcard.
Click to expand...
Click to collapse
No Worries, I appreciate all your help.

My problem was more or less similar and i managed to fix mine
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
In my case I installed the wrong recovery (TWRP-JB) with the wrong bootloader 4.2 and bricked, I also did the mistake to wipe everything. but after several tries I fixed mine, go to my thread on the link above for details.
Hope it helps.

[Q] Loaded Wrong TWRP on TF300T and can only access APX mode

Hello,
I loaded the wrong version of TWRP on my TF300T. When it rebooted it loaded CM10.1 just fine. I then rebooted a second time in recovery mode and I have been stuck at the ASUS screen with the "device is unlocked" message. I am able to get into APX mode but my research has shown that mode doesn't do me any good if I haven't ran a nvflash backup. I am stuck and I would appreciate some advice or suggestions. I wonder what the factory reset fee would be from ASUS.
Thank you for your responses!

what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD

macgyver40 said:
what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Thanks for the speedy response =)
Version History: Stock 4.1 -> CM 10.1 Nightly 0503 or 0429. I had CWM on it before trying to load openrecovery-twrp-2.5.0.0-tf300t-ICS.blob using the terminal emulator method. I think I should have loaded the JB blob but the warning on the TWRP site said to use that if you ran the offical OTA update, which I never did so I stuck with the ICS. It installed fine, then rebooted into CM 10.1 just fine. I then rebooted from there into recovery and have been stuck at the ASUS screen since.
The Vol + - button keeps me in the ASUS screen. Reset button keeps me in the asus screen. Vol + + puts me in APX mode.
I try running fastboot in APX mode but it hangs stating "waiting for device" so I don't think it'll work in APX mode.
Thanks.
T

Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.

c0ded said:
Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.
Click to expand...
Click to collapse
I bled it last night. I'll try booting it this evening. Thanks!

racet said:
I bled it last night. I'll try booting it this evening. Thanks!
Click to expand...
Click to collapse
No luck. I bled it twice and I'm still stuck at the ASUS logo with "the device is unlocked"
Am I looking at repair here?

If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of eBay and replace it with the one in your tablet. Also, to save other people's tablets from bricks, you may want to look into this petition.

if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD

c0ded said:
If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of
Wow 200$ what a load. To what degree of difficulty are we talking with replacing the mobo? Ifixit makes it look doable, yet at the end he messed up his LCD screen.
Click to expand...
Click to collapse

macgyver40 said:
if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I would def like to try it if you can find it.
T

please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
http://forum.xda-developers.com/showthread.php?t=2041528
found it. Hope this helps you like it helped me out of my broken recovery. once you download and add the files you want its pretty easy. the script in english makes it pretty easy to understand what your doing and hope it works since I know my TWRP was broken I couldn't even sit at the recover,android wipe screen for more then 3 mins without it bootlooping. I put it on that screen while connected to laptop ran the recovery flash and all went well installing TWRP 2.5 which I then recovered my backup and that even restored my 2.4.4 patch TWRP like nothing happened at all. tablet runs great and have made 3 backups that work after all this.
Good luck

macgyver40 said:
please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Please take your time. I have no problem waiting especially if the only solution is to drop 75$ on a replacement mobo.
You could send me the file via email or drop box if it's easier. I was going to use the TWRP 2.5 JB with CM 10.1 nightly. I appreciate all the help!
T

look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD

Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot

macgyver40 said:
look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I tried running through your tread but none of the commands worked on the script. Probably because I can't get fastboot to work. When it tries to load a recovery it just states: "waiting for device" and sits there. =/

c0ded said:
Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot
Click to expand...
Click to collapse
Thanks for the info. I am unable to get fastboot to recognize the device. The only way the PC recognizes it is via APX mode. Download mode just sits there at the ASUS screen and windows doesn't see any devices.

Still no love. Am I bleeding out the battery correctly? I am just running the boot screen until it dies then I try to power it on again.
I popped the back open today to see how difficult it would be to replace the mobo, doesn't look too bad. Just having difficulty finding a good online guide.
Also, just so I have the terminology straight, when the tf300t goes into a "boot loop" does it ever leave the asus screen and go black or does it just hang? Mine never goes black, just sits at the ASUS screen with "the device is unlocked" message. The only time I can get it to leave this screen is when I do a reboot and hold the + sign. then it goes black and APX is detected on windows.
Just wasn't sure if any of that information was useful.
T

One other solution is to unplug the battery for 30 minutes, then plug it back in.

c0ded said:
One other solution is to unplug the battery for 30 minutes, then plug it back in.
Click to expand...
Click to collapse
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)

racet said:
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)
Click to expand...
Click to collapse
Usually, the volume button does not fail. Remember the volume button connects to, but is NOT part of the mother board. If it feels stuck when you push it, that's because you snapped the back cover in wrong. You need to slide it in at the corner where the buttons (volume & power) are, then pop in the rest of it. Take it out and do it again.