Database Info

{Solved} Semi-brick? Help needed

My transformer tablet is having a hard time getting past the initial splash screen. It i let it just start up it will not go past this screen however if i press vol down + power so that i get a choice to either boot or wipe and select the option to boot it will boot android. I am also unable to access the recovery and reflashing from the cwm app doesn't seem to fix this issue.
Doles anyone have any suggestions? Sadly I have an SBK2 device so i cannot use nvflash, are their any other methods of getting the stock boot/recovery back on? or a way to repair my current boot / cwm recovery?
Thankful I was able to resolve this. This post held the answer i sought. http://forum.xda-developers.com/showpost.php?p=25083176&postcount=13

Broken CWM

I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks

If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".

abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.

if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img

cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.

power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.

There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.

So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA

RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?

Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr

unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.

Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.

[Q] Need Help Unbricking

I just got a transformer pad tf300t, and i am new to android, and just the other day i managed to brick it. i have searched for hours on end for a way to unbrick it, but all the methods i can find don't match my circumstances. So far all i have managed to do it get it into APX mode (i don't know how), and installed a driver so that in Device Manager it says "Asus Transformer Prime APX Interface". Whenever i do volume up+power button, or volume down+power button on boot, it reboots and returns to the boot screen where it stays forever until the battery goes dead. This all happened after i unlocked the boot loader, attempted to install clockworks, and then the battery went dead while using the wipe system data option in the boot menu (or whatever it's called when you do volume down+power button). Any help would be awesome and i would greatly appreciate it.
EDIT: Just sent an email to ASUS about the problem, and of course they weren't any help and just said i might need new hardware (hopefully not true)

Hi, i've met the same problem.
In fact when i tried to update my TF300T to JellyBean, my device didn't want to boot anymore only in Recovery or on Bootloader. So i tried to update the Recovery with the fastboot and install a TWRP recovery with Fastboot in USB and tried to re-install the ROM (CM 10).
But after that, Recovery and Fastboot did'nt work anymore. I've made a video to illustrate the problem (youtu.be/9aSWZrkP_Ec)
This is like that in Loop untill the device has no battery left.
Sorry for my mistakes, i've got an aproximative english
Thanks for any help.

To the OP, if you can some how push a new boot.blob from a ROM and then push a new system blob from the stock firmware, that fixed it for me. I could get into recovery still though so I used fastboot to do this.

[Q] no fastboot no adb wrong drivers?

WHats up guys? My tf300 is still bricked after like 6 months. It started with me flashing the wrong recovery image then a wipe data finished it off. I can get into apx mode and device manager sees it as an apx device with a yellow triangle, or as several different names according to which driver i use. I have tried all the asus ones, the adb, the composite adb, all the ones from the naked driver set. No matter which ones i use fastboot devices returns nothing and adb devices says "list of devices attatched but nothing. Is there something wrong with the way im using fastboot? I just go to the fastboot folder and open a cmd window and it starts like C:\user\fastboot or whatever and im stuck there please help

jerimynal wiley said:
WHats up guys? My tf300 is still bricked after like 6 months. It started with me flashing the wrong recovery image then a wipe data finished it off. I can get into apx mode and device manager sees it as an apx device with a yellow triangle, or as several different names according to which driver i use. I have tried all the asus ones, the adb, the composite adb, all the ones from the naked driver set. No matter which ones i use fastboot devices returns nothing and adb devices says "list of devices attatched but nothing. Is there something wrong with the way im using fastboot? I just go to the fastboot folder and open a cmd window and it starts like C:\user\fastboot or whatever and im stuck there please help
Click to expand...
Click to collapse
Questions: what rom did you have before? Did you wipe data from the Asus menu, and not from inside a custom recovery? When you now try to get into fastboot by holding volume down + power, what happens? No matter what, try Buster99's solution. If the only mode you can get into is APX, and you didn't generate NVflash files, then I'm afraid your motherboard is stuck, the only solution to which is replacing it.

graphdarnell said:
Questions: what rom did you have before? Did you wipe data from the Asus menu, and not from inside a custom recovery? When you now try to get into fastboot by holding volume down + power, what happens? No matter what, try Buster99's solution. If the only mode you can get into is APX, and you didn't generate NVflash files, then I'm afraid your motherboard is stuck, the only solution to which is replacing it.
Click to expand...
Click to collapse
i came from stock jb rom and i flashed an ics cwm recovery img i got into the bootloader screen but it wouldnt go into recovery so for some stupid reason i did a wipe from there, from the asus menu. volume down and power just shuts the screen off for a few seconds then straight back to the asus screen volume up and power will apx mode. the driver i had got from asus pulled up transformer prime apx interface in device manager

jerimynal wiley said:
i came from stock jb rom and i flashed an ics cwm recovery img i got into the bootloader screen but it wouldnt go into recovery so for some stupid reason i did a wipe from there, from the asus menu. volume down and power just shuts the screen off for a few seconds then straight back to the asus screen volume up and power will apx mode. the driver i had got from asus pulled up transformer prime apx interface in device manager
Click to expand...
Click to collapse
Must've been the wrong recovery that screwed up your tab. In my experience, wiping data from the Asus menu while you're on stock rom is not supposed to brick it as described by you. Try this method. It has saved quite a few semi-dead tabs. Good luck, and give thanks to the author if it helps.

graphdarnell said:
Must've been the wrong recovery that screwed up your tab. In my experience, wiping data from the Asus menu while you're on stock rom is not supposed to brick it as described by you. Try this method. It has saved quite a few semi-dead tabs. Good luck, and give thanks to the author if it helps.
Click to expand...
Click to collapse
im sure it was the wrong recovery i dont know why i did it. i had another ics tablet and for some reasone i put both recovery images in the same folder the link u provided is one that i had previously read. I cant even get fastboot to "see" the tablet.

SOLVED:Totally screwed up. All I can get is teamwin screen

So I had updated to the KitKas Lolipop rom. Ran a program that ended up corrupting things.
I had I believe 2.7.0.0 Geas Or whatever TWRP.
Tried some Dalvik/cache clears ect... to resolve, finally wiped system/dalvik/cache in an attempt to keep my data.. no go
Then I was originally able to access with Volume down / power button the Recovery / Android / Wipe Data Selections.
Everytime I would try to boot into Recovery up to and including the point I'm out now, it just sticks at the [Teamwin] Backdrop and those words with no options to proceed into recovery.
I can no longer do the volume up/down with power button to access anything else, it just keeps booting to this [Teamwin] screen with no options. (Just prior to this occuring terminally now as my tablet won't even shut off at all, I did a Wipe Data selection when it was available, now as said, it just boots to teamwin screen / backdrop with no options within at all.
Help!

Had same problem with twrp 2.8.1.0
To reboot long press power button (10s) and hold Vol- to enter fastboot.
Follow Buster99 method to flash stock rom and twrp again.
It should work. When all working again please send a "fdisk -l /dev/block/mmcblk0" output
After all ok should read [DEV][TOOL][BRICKPROOF]TF300 NVFlash release! and [GUIDE] Install NvFlash Flatline (become unbrickable!!).
lazer9 said:
So I had updated to the KitKas Lolipop rom. Ran a program that ended up corrupting things.
I had I believe 2.7.0.0 Geas Or whatever TWRP.
Tried some Dalvik/cache clears ect... to resolve, finally wiped system/dalvik/cache in an attempt to keep my data.. no go
Then I was originally able to access with Volume down / power button the Recovery / Android / Wipe Data Selections.
Everytime I would try to boot into Recovery up to and including the point I'm out now, it just sticks at the [Teamwin] Backdrop and those words with no options to proceed into recovery.
I can no longer do the volume up/down with power button to access anything else, it just keeps booting to this [Teamwin] screen with no options.
Help!
Click to expand...
Click to collapse

Thanks for the reply but that's my problem. No matter what I hold / vol - with 10sec on power button, ect... Have tried all sorts of combos, length of time pressing, ect... it just leads me to same screen with no options.
I think I'm hard bricked as the tablet won't even turn off.

No matter what, this is all I can achieve.

Another nearly to my "last gasp" post. In Adb with TF300T connected via USB whilst sitting on the described teamwin screen I get:

lazer9 said:
Another nearly to my "last gasp" post. In Adb with TF300T connected via USB whilst sitting on the described teamwin screen I get:
Click to expand...
Click to collapse
DId you see my thread over here .....
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495
Let me know if you need any help along the way, in that tread .....
Thx Josh

lj50036 said:
DId you see my thread over here .....
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495
Let me know if you need any help along the way, in that tread .....
Thx Josh
Click to expand...
Click to collapse
As noted in given link above, Josh thankfully and patiently guided me through the process and via his guide given. I encourage all who happen upon this thread to follow his link and I'm guessing based on my dilemma that a resolve can be met to restore your tablet in most cases.
At this point, if desired, a mod can close out this thread as it has been solved!
Thanks again Josh!