Database Info

[Q] Request for assistance with bricked tf300t

Reading through different forums I have read problems similar to mine but nothing exactly the same. I followed each fix anyway but I have not been successful.
The last thing I remember I did before the brick, I flashed CWM touch then CyanogenMod 9. I am unsure what occurred but I tried to flash back to my JB backup and the problem started.
Now my tablet comes on and just hangs on the Asus splash screen. If I turn the tablet off, it automatically comes back on.
I have tried to turn the tablet off and boot into recovery but it just boots back up to the splash screen and hangs; I have no option to go into recovery, android or fastboot.
I can get into what I think may be USB mode by pressing power and volume up through a couple of cycles; my computer detects a device but I cannot load drivers.
I have downloaded the Android USBPCdrivers but each time I try to navigate to the folder to install the device manager fails.
If anyone has any thoughts I would appreciate any assistance, thanks for your time!
UPDATE TO ORIGINAL POST
I as able to finally get my computer to recognize the tf300t in device manager by wiping all the usb drivers and installing "Universal Naked Driver 0.7" posted by 1wayjonny from XDA's website http://forum.xda-developers.com/show....php?t=1766220, not sure if it matters my computer "sees it" as a ASUS transformer prime rather than tf300t.
Now I am reviewing an ASUS unbrick called Wheelie http://forum.xda-developers.com/show....php?t=1687285, I believe this is geared towards the tf101. Anyone have any thoughts based on my status at this point? Thanks

If you are on JB stock, there is no way to flash a booting Cyanogen 9 ot 10 Rom.
Only Hydro JB is running!!!! And JB Stock.
1st of all you have to download a special Recovery. I highly recommend TWRP. You have to dl the JB version!!!!!
Flash it through fastboot. Then flash the Stock JB via TWRP recovery
Then flash TWRP again via fastboot.
Than flash The Hydro JB rom
Then reboot
Then go back to recovery
Then flash the latest Hydro update and reboot
You are like me stuck on the f...... new JB Bootloader and Kernel. All other roms are for the ICS Bootloader and Kernel, so no way of getting them running until the Cyanogen devs finding a solution.

Fastboot not an option
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?

mfsmith said:
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?
Click to expand...
Click to collapse
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.

krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)

喔喔兒 said:
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)
Click to expand...
Click to collapse
Waiting for nvflash won't do you any good since you needed to have it BEFORE bricking your tablet. If your tablet is already bricked, APX/nvflash will not help you.

krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
He could still try sending it for RMA. Mine got repaired for free for some reason.

An unusual Asus TF300T brick
Yeah, I'm having problems with my TF300T, too. I had CWM installed, but when I tried to flash a new ROM, I bricked it. No problem, I had figured it out before. But when I was in the bootloader, I inadvertantly erased instead of selecting the USB. Now, All I get when I try to boot up is the white ASUS screen with;
The Device is Unlocked
Android cardhu-user bootloader <2.0 e> released by "ww_epad-9.4.3.26-20120416" A03
Checking for android ota recovery
Booting recovery kernel image
My computer sees the tablet. The Device Manager shows: Asus Transformer Prime APX Interface
But it only shows up when I reset. As soon as I try to boot the tablet, it no longer sees it. I can't access the bootloader and Fastboot doesn't do anything except "waiting for device".
SO! If anyone can give me some help, I'd appreciate it. It's a puzzle for ya, anyway.
Thanx

As your last resort, this worked for me
Link to my thread---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, feel free to ask anything.

[Q] My tf700 itc Bricked help

Hello encountered problem that occurs in my TF700 into a brick.
When the issue first picture with the ASUS logo in the top right corner says::
The Device is Unlocked.
When you try to go to recovery mod it produces here
Android cardhu-user bootloader <2.10. e> released by "WW_epad-9.4.5.26-20120720" A03
Checking for android ota recovery
Booting recovery kernel amage
* and everything in it got stuck

Have u tryed downloading the stock update from asus and install from microSD
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Do you have an SD card in that might have an update on it? If so, try removing the micro SD and see if you can boot.

tbtaf said:
Do you have an SD card in that might have an update on it? If so, try removing the micro SD and see if you can boot.
Click to expand...
Click to collapse
Eap i have but did not work:crying::crying:

I haven't tried a usb jig myself, but my friends said it worked as sort of a repair/clear. like a windows CD in a pc and choosing repair windows. only the jig does it automatically. they cost like 10 bucks. my friends said it did something and they were able to get into recovery to full wipe and reinstall rom.
try a jig, it has worked for others soft bricked.

tbtaf said:
Do you have an SD card in that might have an update on it? If so, try removing the micro SD and see if you can boot.
Click to expand...
Click to collapse
entwicklun said:
I haven't tried a usb jig myself, but my friends said it worked as sort of a repair/clear. like a windows CD in a pc and choosing repair windows. only the jig does it automatically. they cost like 10 bucks. my friends said it did something and they were able to get into recovery to full wipe and reinstall rom.
try a jig, it has worked for others soft bricked.
Click to expand...
Click to collapse
but where is it
I asked for help and answer a specific question

entwicklun said:
I haven't tried a usb jig myself, but my friends said it worked as sort of a repair/clear. like a windows CD in a pc and choosing repair windows. only the jig does it automatically. they cost like 10 bucks. my friends said it did something and they were able to get into recovery to full wipe and reinstall rom.
try a jig, it has worked for others soft bricked.
Click to expand...
Click to collapse
How u gonna used the USB jig without the USB on it???? C'mon now

dough30i said:
How u gonna used the USB jig without the USB on it???? C'mon now
Click to expand...
Click to collapse
USB Jig that I have for my Samsung phone is for micro usb port. I thought it only worked with Samsung devices.

I have a jig too, for my SGS2 -- I have never heard a report that it worked for other devices.

MartyHulskemper said:
I have a jig too, for my SGS2 -- I have never heard a report that it worked for other devices.
Click to expand...
Click to collapse
That's what I'm Saying, the infinity doesn't have a micro USB port only hdmi so unless some one cleverly found a way to unbrick the infinity sheit let me know I'll be the first to try anything to get out of brick...
ANYTHING...

Having exactly the same issue. I issued a rma but it looks like Asus has denied it. Only method I have found is the NVflash method (vol up + pwr) , but it is not up to date with the tf700 otherwise it will make things worse. So now I'm just waiting on an update :-[. Let me know if you find a working method please.

saph27 said:
Having exactly the same issue. I issued a rma but it looks like Asus has denied it. Only method I have found is the NVflash method (vol up + pwr) , but it is not up to date with the tf700 otherwise it will make things worse. So now I'm just waiting on an update :-[. Let me know if you find a working method please.
Click to expand...
Click to collapse
Even if we will have nvlash someday you will need to have working fastboot mode on your device,if not nvflash would be useless to you.

How did you flash recovery?
Did you do anything other then boot it up after flashing?
Can you connect using adb or fastboot?

lafester said:
How did you flash recovery?
Did you do anything other then boot it up after flashing?
Can you connect using adb or fastboot?
Click to expand...
Click to collapse
No I can not sound when you POWER VOL DOWN VOL UP I get the message that is written in nachade theme.
Ave you POWER VOL UP my computer to see it in ATC mode ostaetsya black screen and no movement:crying:
I will try to contact the service сenter

israodin said:
No I can not sound when you POWER VOL DOWN VOL UP I get the message that is written in nachade theme.
Ave you POWER VOL UP my computer to see it in ATC mode ostaetsya black screen and no movement:crying:
I will try to contact the service сenter
Click to expand...
Click to collapse
To go in fastboot mode you need to press just Volume Down + Power and wait untild you see the 3 icons.Use Volume Down to navigate to the USB icon (fastboot) and Volume Up to confirm selection.

Pretoriano80 said:
To go in fastboot mode you need to press just Volume Down + Power and wait untild you see the 3 icons.Use Volume Down to navigate to the USB icon (fastboot) and Volume Up to confirm selection.
Click to expand...
Click to collapse
Eap i know but I try to do I get
The Device is Unlocked .
Android cardhu-user bootloader <2.10. e> released by "WW_epad-9.4.5.26-20120720" A03
Checking for android ota recovery
Booting recovery kernel image

The problem is that it just wont leave the very first boot screen. Unless there is a way to fix it in APX mode that does not require already being set up through the device (which is possible see this) and knowing the secure boot key there is no way to access recovery or fastboot. Until we know the Secure Boot Key I have a bad feeling its not fixable. And god knows how long it will take them to release that. I do not understand how releasing this information to the public could impact their company, or why even have them in the first place. I paid for the device, I should be able to access every part or it.

saph27 said:
The problem is that it just wont leave the very first boot screen. Unless there is a way to fix it in APX mode that does not require already being set up through the device (which is possible see this) and knowing the secure boot key there is no way to access recovery or fastboot. Until we know the Secure Boot Key I have a bad feeling its not fixable. And god knows how long it will take them to release that. I do not understand how releasing this information to the public could impact their company, or why even have them in the first place. I paid for the device, I should be able to access every part or it.
Click to expand...
Click to collapse
Agree on 100
but as yet to solve this problem .... I now put him into tsenter service waiting for an answer

After sending in my device with this same issue I got a reply saying they needed to replace my motherboard for $177.00 + Labor at $65.00 ($242 total). Does not make since to me. You would think they would have a way to fix it without charging me for a new motherboard. What do you guys think?

Hello encountered problem that occurs in my TF700 into a brick.
When the issue first picture with the ASUS logo in the top right corner says::
The Device is Unlocked.
When you try to go to recovery mod it produces here
Android cardhu-user bootloader <2.10. e> released by "WW_epad-9.4.5.26-20120720" A03
Checking for android ota recovery
Booting recovery kernel amage
* and everything in it got stuck
Hi all,
I gave her a tablet for service center
They said that since mashines Ulocked
then there are no guarantees and they have no right to engage in such restoration devices
may at this time have someone new ideas as restore

[Q] Infinity with corrupted bootloader, bricked?

Till this morning my Infinity I was on CleanROM Inheritance 3.4.7 with TWRP 2.5.0.0 Recovery, this worked fine. However I wanted to switch to CROMi-Xenogenesis 4.4.1 so I flashed 10.6.1.14.4 WW Bootloader and TWRP 2.5, as said in the OP. Unfortunately after the flash my device is dead, maybee bricked? I can't power on my tablet, with power on - volume down I can't get into recovery anymore.
I can't remember exactly what I saw after the flash. There should be an blue bar but I can't remember I have seen it. I saw this bar before when I flashed another ROM. The tabled had enough battery power, 90 or 95%.
When I put the tablet to my laptop I saw the word APX under other devices. Windows and Windows update doenst't seem to have the drivers present, luckily i found modified Universal naked driver at this blog. So now I have APX, but no fastboot.
When I read this thread, there is not much hope for me. Or is there a way to boot in fastboot modus? Any suggestions?

musicfreak said:
Till this morning my Infinity I was on CleanROM Inheritance 3.4.7 with TWRP 2.5.0.0 Recovery, this worked fine. However I wanted to switch to CROMi-Xenogenesis 4.4.1 so I flashed 10.6.1.14.4 WW Bootloader and TWRP 2.5, as said in the OP. Unfortunately after the flash my device is dead, maybee bricked? I can't power on my tablet, with power on - volume down I can't get into recovery anymore.
I can't remember exactly what I saw after the flash. There should be an blue bar but I can't remember I have seen it. I saw this bar before when I flashed another ROM. The tabled had enough battery power, 90 or 95%.
When I put the tablet to my laptop I saw the word APX under other devices. Windows and Windows update doenst't seem to have the drivers present, luckily i found modified Universal naked driver at this blog. So now I have APX, but no fastboot.
When I read this thread, there is not much hope for me. Or is there a way to boot in fastboot modus? Any suggestions?
Click to expand...
Click to collapse
I would figure the tablet is on somehow if APX is noticing it. Have you tried holding down the power button until it vibrates to force shut it down then hold the power and volume down to get back into the boot loader?
Just wanting to make sure because APX is useless unless you have you NVFLASH blobs.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Tylorw1 said:
I would figure the tablet is on somehow if APX is noticing it. Have you tried holding down the power button until it vibrates to force shut it down then hold the power and volume down to get back into the boot loader?
Just wanting to make sure because APX is useless unless you have you NVFLASH blobs.
Click to expand...
Click to collapse
I thought I couldn't make my Transformer to power down. I hold the power button till it vibrates as you suggests. When I press volume down - power button nothing happens, the screen remains blank...

Maybee Nvflash is an option for me?
If I read http://rootzwiki.com/topic/35086-gu...rs-guide-unbrickrecoverdowngradeupgrade-tf201 correctly you can flash Nvflash in APX mode.

musicfreak said:
Maybee Nvflash is an option for me?
If I read http://rootzwiki.com/topic/35086-gu...rs-guide-unbrickrecoverdowngradeupgrade-tf201 correctly you can flash Nvflash in APX mode.
Click to expand...
Click to collapse
For this procedure, you must have obtained a blob.bin file by installing the hacked bootloader while you were still on a 9.4.5.26 or older bootloader.
If you don't have this file, and you don't know your tablet's unique SBK (Secure Boot Key), which nobody outside Asus knows, then you can't use nvflash.

Ah, so Nvflash is no option...
I contacted Asus support today by mail. First they came with the option of reinstalling the operating system for about 75 euro. Is that realistic? Or is an motherboard swap necessary? In that case the cost are about 160 till 200 euro. Quit a lot of mony. Then Ebay seems a better alternative...

musicfreak said:
Ah, so Nvflash is no option...
I contacted Asus support today by mail. First they came with the option of reinstalling the operating system for about 75 euro. Is that realistic? Or is an motherboard swap necessary? In that case the cost are about 160 till 200 euro. Quit a lot of mony. Then Ebay seems a better alternative...
Click to expand...
Click to collapse
If you can't get into recovery and you're using the correct side of the volume rocker (left!) and it really, really doesn't react to holding the power button for eternity - then you're probably bricked
The question is why? And how?
This hardly ever happens on the CleanRoms...
Did you reboot into system after flashing the bootloader and before flashing CromiX?
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

I don't know what happened after I flashed the 10.6.1.14.4 WW Bootloader and TWRP 2.5 recovery. After a while the tablet didn't react anymore...
In a Dutch forum I get the suggestion to check Easyflasher (http://www.youtube.com/watch?v=BxNmK6uXfFE&list=PLudvvIZ2s2oHbCK2Gb8aZHIoPpABzwthA). But om http://forum.xda-developers.com/showthread.php?t=1688012 I read WARNING: IF YOU USE THIS ON YOUR TF201/TF300/TF700 YOU WILL BRICK IT so this will be of no use I think.

I wouldn't use this -- it has been reported earlier to brick.
Have you tried to get into the bootloader -- that's what Tylor rightfully suggested, but I find your reply ambiguous -- press and hold down the left volume button ("volume down") and while you do so, keep the power button pressed until you feel it vibrate. Release the power button, and when/if you see some icons, release the volume button.
You're based in Amersfoort -- do you visit Utrecht with any regularity? (I live in Hoorn, but work shifts in the UMC Utrecht so might take a look at it for you.)

berndblb said:
The question is why? And how?
This hardly ever happens on the CleanRoms...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I strongly suspect the Recovery, I also had issues attempting to flash a later version of Clean
Rom. It took a day of flashing to get the tab back to health. Along the same lines I have also had issues flashing my T'bolt and also my DNA. For the time being I am refraining from changes on the tab and DNA.
I have used both CWM and TWRP

MartyHulskemper said:
Have you tried to get into the bootloader -- that's what Tylor rightfully suggested, but I find your reply ambiguous -- press and hold down the left volume button ("volume down") and while you do so, keep the power button pressed until you feel it vibrate. Release the power button, and when/if you see some icons, release the volume button.
Click to expand...
Click to collapse
I've done this, but I see no Icons.... For me it's hard to see if my tablet is on or off. But when I hold the power button for a long time it vibrates so I assume it's off then.
You're based in Amersfoort -- do you visit Utrecht with any regularity? (I live in Hoorn, but work shifts in the UMC Utrecht so might take a look at it for you.)
Click to expand...
Click to collapse
What a great offer! Sometimes I visit Utrecht, and the UMC so this would be nice. When I'm planning to visit Utrecht I will give you a sign.

OK, so I went over and despite musicfreak having good ideas along the way, we haven't been able to revive his 700, and I'm not feeling too optimistic it can be done. However, I don't want to pass up the opportunity for _that to show off his immense skill once more (feel the pressure? ) and help musicfreak out.
In short:
- unit doesn't actually boot into the bootloader at all, apparently. Screen stays black, no white lettering anywhere. Not a single one. Dead as a dodo.
- only APX mode is available, by booting with VOL_UP pressed-- nothing else works (screen is oof, so I cannot tell if anything else is loading; Windows detects only APX device connected). No fastboot.
- the procedure for reflashing stock doesn't work at all, obviously, because there was a custom recovery (TWRP) -- still, grasping every little straw, we tried -- everything -- but the screen stays black.
My own 700 is detected properly in fastboot mode, so it seems unlikely we have a cabling and/or USB port and/or OS error (tried both WinXP 32-bit and 7 64-bit).
After the usual hassle of getting the drivers in place -- musicfreak's saving the day of installing the patched drivers (I though the patch had gone mainline by now) -- we haven't been able to get any further.
Is there a command we can get to the device in APX mode to detect what is causing this?
Is this recoverable? RMA?
Thanks for the help and insights, guys and girls.

MartyHulskemper said:
- unit doesn't actually boot into the bootloader at all, apparently. Screen stays black, no white lettering anywhere. Not a single one. Dead as a dodo.
Click to expand...
Click to collapse
Dead/broken/missing bootloader (or broken eMMC), or dead screen.
MartyHulskemper said:
- only APX mode is available, by booting with VOL_UP pressed-- nothing else works (screen is oof, so I cannot tell if anything else is loading; Windows detects only APX device connected). No fastboot.
Click to expand...
Click to collapse
If you tried to enable fastboot mode blindly and the PC didn't detect it, then we can rule out "dead screen".
MartyHulskemper said:
Is there a command we can get to the device in APX mode to detect what is causing this?
Click to expand...
Click to collapse
The only way to do anything in APX mode is NVFlash. Without the SBK (aka "unobtainium") or the "wheelie" tool and the matching blob, that mode is useless, as far as I know.

_that said:
Dead/broken/missing bootloader (or broken eMMC), or dead screen.
If you tried to enable fastboot mode blindly and the PC didn't detect it, then we can rule out "dead screen".
The only way to do anything in APX mode is NVFlash. Without the SBK (aka "unobtainium") or the "wheelie" tool and the matching blob, that mode is useless, as far as I know.
Click to expand...
Click to collapse
Yup, the two options you call out here were in my head, too. I got over to musicfreaks' thinking that the bootloader was actually working, but it soon turned out to be dead. Since the only mode Windows can detect is APX and neither adb nor fastboot give any reaction or meaningful reply, I guess musicfreak's 700 is deceased.
@OP: given the fact that even our guru knows not how to save your 700, it comes down to either salvaging the parts and selling them on their own, or selling the broken unit and dock together subtracting the repair cost.
Anyone having specific ideas which is better? (I'd veer towards selling it in whole, which at least makes sure you're not going to get stuck with loose parts...)

Yes, there seems no hope for my TF700 anymore....
I also think that selling the whole set (tablet and dock) is the best choice.

Unfortunately looks like a brick to me. Without nvflash the only option is to send it off to Asus if you want it fixed. Otherwise sell it for parts (Screen, digitiser, case etc)

I will, ýesterday I've put my Infinity on sale, see this at on Tweakers.net (in Dutch). Anyone interested here?
One thing comes to my mind: why can't the SBK be generated? Can't it be extracted somehow from the processor?
@MartyHulskemper: Have we tried to flash the stock rom from MicroSD card? I'm not sure.

musicfreak said:
I will, ýesterday I've put my Infinity on sale, see this at on Tweakers.net (in Dutch). Anyone interested here?
One thing comes to my mind: why can't the SBK be generated? Can't it be extracted somehow from the processor?
@MartyHulskemper: Have we tried to flash the stock rom from MicroSD card? I'm not sure.
Click to expand...
Click to collapse
Nope. If it were unencrypted, we could've tackled it ages ago and use it to unlock the bootloader without ASUS knowing. I have no doubt that the processor serial number or some other identifier does figure into the process, but we do not know the rest of the algorithm used.
As to your specific question: there is no use in trying to flash anything from the microSD card since we couldn't get into the bootloader at all, and therefore have never even seen a recovery of whatever description or denomination.
As I said when I was at your place: I was udner the impression you at least had the bootloader and fastboot access. Although it's probably hard working even then, it would not be without hope. Not having a bootloader, and not having Nvflash at hand, well... I fear it is without hope.

It has been a while since I post the last update to this thread.
In short: I sent my tablet tot Asus, they charge me 310 euro. After an email discussion with them without notice they sent the tablet back to me. I asked the shop where I bought it for repair, and now I nead some information for my email to them.
All this goed wrong when I flashed CROMi-Xenogenesis 4.7.0. Is flashing this ROM more risky then flasting CleanROM Inheritance 3.4.7? If so, why?
I hope somebody can explain this to me.

musicfreak said:
It has been a while since I post the last update to this thread.
In short: I sent my tablet tot Asus, they charge me 310 euro. After an email discussion with them without notice they sent the tablet back to me. I asked the shop where I bought it for repair, and now I nead some information for my email to them.
All this goed wrong when I flashed CROMi-Xenogenesis 4.7.0. Is flashing this ROM more risky then flasting CleanROM Inheritance 3.4.7? If so, why?
I hope somebody can explain this to me.
Click to expand...
Click to collapse
No it is no more risky than flashing any ROM. Flashing a ROM is not very risky cos even if you brick you will be soft bricked and usually that is recoverable. Your issue may have been related to the bootloader and recovery flash. Did you interrupt it - it should have rebooted on its own after the blue bar went to full?

[Q] I accidentally everything (TWRP)

Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?

JunoZXV said:
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
Click to expand...
Click to collapse
Im having exactly the same problem, did you find a solution to this?

So far no results yet. I tried hitting the reset button on the side but all that did was lead me back to the boot screen. I read something about undoing the the hard boot using a series of override programs. But the problem is the documentation is so cluttered that I can't fathom the instructions (I'll try it again just in case.)

Bump update: So I called Asus and it turns out it's gonna cost 288$ to get the thing fixed by them. So I'm not doing that. I'm looking into other ways of recovery. I've got other multiple options I'm exploring at the moment. Like looking for a recycling program or a way to use the technology in a new way.

UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this

JunoZXV said:
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
Click to expand...
Click to collapse
Unfortunately if you can only get to APX mode and you don't have nvflash specific blobs for your device you are hard bricked...

Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.

JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
Sorry it really doesn't look good, Maybe i can corrected but the device will fallback to APX mode if the bootloader is corrupted, without a bootloader you cant install/fix a recovery and without NvFlash blobs you cant fix the bootloader. Your two options are buy a new motherboard and replace it yourself or send it in for repair with Asus

JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
As JTR says I'm pretty sure you can't fix this without replacing the hardware now. I don't think your friend really understands what APX mode is. YOu can't access the bootloader nor recovery. Without NVflash backup blobs you can't recover anything, there is no way to get your TWRP backups back on to the device and even if you could you have no working bootloader......

[Q] Bricked TF700

Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.

Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately ROM Manager does not work with the TF700 and you are not the first one to find out the hard way...
If you cannot find a way to boot into the bootloader to have fastboot, there's nothing you can do anymore without the NVflash blobs.
Did you try holding Vol - and then pressing the reset button in that little pinhole on the side of the tablet?
If you have ADB drivers installed on your PC you could try if you can establish an ADB connection at any point. If you did, you could issue the command: "adb reboot bootloader", which would enable you to flash a recovery and/or bootloader. This probably won't work since you need to be in the recovery or have Android booted for ADB to work, but worth a try anyway...
Admittedly these are very thin straws - but what have you got to loose?
Also: Just a few days ago a user here was stuck on a bootloop to recovery and couldn't get out of it. He left it alone overnight and all the sudden the bootloop sorted itself out... I have no explanation for it and it is unlikely to happen in your case, but you never know...
Good luck!

Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.

Quentin2 said:
Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.
Click to expand...
Click to collapse
For the TF700 the nvflash blobs are device specific - sorry.

Damn. That was the only answer I didn't want to read
Thanks a lot. So chances are gone, only RMA could help... I will ask friendly at Asus what costs they will charge...
q2.

Update:
Reply is here.
They only want to exchange mainboard. They of course know (and it seems that this is the only thing they know) that my bootloader was unlocked, therefore this is no case of guarantee for them. I know, I wrote to them that I just want to know how much they wanna charge me to fix this issue.
But: they don't want to tell me how much. They say they do not even know which revision and what hardware is inside my tablet, not even from my serial number. And I must first send them my tablet and they will charge me 95 Euro to check what's going on. And then they will tell me how much it will cost (and according to other threads I saw prices of over 400 Euro for a mainboard change - the TF701 successor model cost 450 Euro new in store)...
I somehow feel the need to reply that if they would've put only half the energy the put into logging who has unlocked the bootloader into the fact of making APX usable as a emergency recovery (as obviously not even Asus is able to generate a working blob for my device), they would have higher customer satisfactory statistics. I still just cannot believe a today's device lacks of all recovery options after a bootloader fails for some reason - as well as I cannot understand why Koush did not display a warning in ROM manager if problems are known to the community with this specific device (I mean the problem did not arise last week and ROM manager had tenths of updates since then).
I know that in the end all was my fault. And all flashing is done on our own risk. I will have to deal with it.
Phew...

Unlucky. It should be be stickied here somewhere that ROM Manager bricks the TF700 but then there is no guarantee it would be read. It is well known on this forum but that doesn't help people that don't visit frequently.
You can replace the mainboard yourself fairly easily. Watch the you tube vids on how to do it,. That is what I would do if I was in your position.

berndblb said:
For the TF700 the nvflash blobs are device specific - sorry.
Click to expand...
Click to collapse
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app

zeddock said:
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash

Any Solution?
Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately I'm stuck in same boat I tried to wipe out settings completely and clockwork mode was stuck and I was able to wipe recovery with TWRP or so I thought tried to reboot into recovery got stalled and now stuck on asus screen. I'm not opposed to buying a new motherboard but I find it very hard to believe that no one has come up with a solution to flashing the mainboard with the original firmware. I'm tempted to ask asus but I know the bill will be more then the tablet. Did you find an easier solution or do I just have to swap out the mainboard?

sbdags said:
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash
Click to expand...
Click to collapse
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock

zeddock said:
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock
Click to expand...
Click to collapse
That's correct. You have to flash a modified bootloader and recovery. Done correctly this is not risky at all. But if there is a single line in the instructions you are not sure you understand, you are not quite ready.
There are quite a few tutorials on flashing in fastboot on this forum. Read them.
But generating your nvflash blobs you have to do without a safety net. It's worth it though! I have become much more adventurous with my tablet since I have the blobs squared away...

berndblb said:
Done correctly this is not risky at all.
Click to expand...
Click to collapse
How do you define risk?
Flashing a bootloader (without having nvflash access) is always risky by my definition, it *can* permabrick your tablet if something goes wrong at the wrong moment. But it's the best we have.