Database Info

recover options for bricked TF700 Please Help!!!

I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.

xdatester11 said:
I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.
Click to expand...
Click to collapse
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Pretoriano80 said:
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.

xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
AFAIK the nvflash method doesn't work for TF700 and is possible that you really bricked your device... The only solutionn i can see is to flash a recovery in fastboot mod and flash the Asus stock from there,but if you can't even boot in fastboot then i don't see any other way to recover the device.

xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.

xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
attachment

NVFlash works with the TF700??? That's news to me!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
Sorry mate,but according to this --> http://androidroot.mobi/2012/07/15/nvflash-for-tegra3-transformer-prime/ <-- i don't think you will be able to use nvflash for recovery and it clearly states that you need to get fastboot working in order to use that method. (to get in fastboot mode press Volume down + Power and release the buttons when the message about having 5 second to press Volume Up shows...if this work you will get to a menu with the "USB icon" wich means boot in fastboot mode).
P.S : Can you tell us why you had to mess with nvflash?That is the most advanced way to recover/backup the Transformer 101/201 series and you have really high chances to brick your device for good.
EDIT: I don't think someone here will be able to make a backup for you with nvflash...it will only lead to more bricks.
EDIT 2: Can you please tell us the name of the app that bricked your device so we can avoid other people bricking their device?

The app was transformer reboot recovery I think.
I only used nvflash because it was the only option left as the tab wouldn't work with adb or fastboot.
I guess I'll keep it as a paper weight.

xdatester11 said:
The app was transformer reboot recovery I think.
Click to expand...
Click to collapse
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.

henbone11 said:
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.
Click to expand...
Click to collapse
Yes,i also used that app with no issue,but one of the developers behind TWRP advised to not use it at all,because if for some reason your recovery gets corrupted (that app send a custom command to boot into recovery) the device will boot loop trying to get in recovery and without nvflash we don't have many options to recover from that.
"
KEEP AWAY from that app for the moment,just stick with the old good " Volume Down + Power and then Volume UP " method to get into recovery.

Same issues here as well
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.

shasan2 said:
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.
Click to expand...
Click to collapse
1The first step is to get your recovery back and working...here's a how-to:
1) Download the recovery from here
2) Follow the instruction on how to flash the recovery in fastboot mode
If the flash went good and you can get in recovery mode follow this steps:
1)Download the 9.4.5.26 firmware from Asus site (the SKU for your region)
2)Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3)Put the extracted zip to a MicroSD card
4)Insert the MicroSD card in your tablet and boot into recovery
5)Install the zip from recovery and restard when done
If all goes well your tablet will be again up and running

Ray of Teamwin
:good::good::good:Thanks a million, seeing the team win screen relieved me. The only problem is i cant boot into recovery (teamwin screen is visible)through the wipe data mode, wherein everything is wiped and it reboots automatically. I cant seem to force the table into recovery without this is there any fastboot command which i can use to force the tablet into recovery.

Need Stock Boot, Recovery, System img
Still no luck with the recovery mode. Every time i wipe the device it automatically reboots. I was wondering if i could get hold of stock recovery, boot and system .img files so that i can push them or flash them through fastboot.
i tried using the blob pack and unpack but i cant seem to get around the blob header thing.
Anyone to spare me stock .img files

End of Infinity
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available

shasan2 said:
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available
Click to expand...
Click to collapse
There's a thread (I can't find it again) that talks about this "Reboot into Recovery" app and how it might be bricking TF700T's. This guy wrote in, because he could not get to the recovery menu at all any more and could not do the "PWR+VOL-DOWN" combo. Nothing would happen. Maybe this was the thread, I don't know.
An XDA Mod in another thread said the app *might* be bricking them, but was waiting for confirmation before posting that it does.
I wish to confirm that IT DOES BRICK TF700T's! IT DOES!!!
And there is NOT A DAMN THING you can do! Your PC will not even recognize that the device is connected! You cannot get to the little icons to pick USB Mode, or whatever it's called.
This is the free app, not the other pay one in the Market. I don't know about that one, but this one is called, "Reboot into Recovery" and if you can somehow find that thread if I don't and just copy my post there, I would really appreciate it! I just want to warn people, ya know?
Also, using ANY of the "ROM Managers", whether it's CWM's, or GooMgr's, will take away all ability to get to a recovery menu at boot, at all! The device will still work and everything and boot to your Home Screen and everything. It won't be bricked like the app listed above does to it, but it will take away your recovery menu altogether and the PWR+VOLDOWN thing won't work any more either.
You can Unlock the TF700T, you can Root it. But you cannot use ANY ROM Mgr and you cannot use that Reboot into Recovery app.
But the app I listed above WILL BRICK YOUR DEVICE BEYOND ANY RECOVERY METHOD!
Please pass this on, I am confirming the experience. It doesn't matter if others say it worked for them. It is bricking them at random and even one of the guys who reviewed the app (diff guy than the one who posted here) said it bricked his. It is happening! It is not the user messing up! I did do it right!
Thanks!

I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No offense, but I think a huge problem in forums, is that people don't read carefully.
1) I think you are referring to the paid app. Read what I said about that.
2) You're saying what you're saying, in a thread started by a guy who had a running device and who didn't after using the app.
3) I said that it bricks them AT RANDOM.
4) Another problem with forums, is that whenever someone has a problem, A LOT of users want to post responses that ignore the users' experience and they want to act like the problem doesn't "really" exist. If multiple people are posting the same problem, then IT DOES EXIST. It just doesn't exist for YOU! But something working for you, does not mean it works for everybody and it does not mean there is a problem with their device, nor that they did something wrong.
5) And yet another problem with forums, is that when someone like me points things like this out, many users will respond by jumping on me, instead of those who try to make the guy feel like he's hallucinating and who, instead of trying to help him out, or just keep their mouths shut if they have nothing helpful to offer, think the right thing to do is to argue with the person having the problem.
These forums are for help and information. If someone has neither to offer the person, or at least warn others, then why are they responding at all? And why would anyone defend someone doing that?! It's ridiculous! But that's what typically happens, especially in XDA doe some reason (lots of snobs here, who like to prove they are, by doing as I just described).
The bottom line is, you do not run the app I talked about and even if you did, that does not take away from the experience that some have had and the best thing, is to avoid the app, because there's a risk involved and there is no recovery from it. I decided to warn people. You decided to tell us that we're hallucinating and that people should use the app. You did not carefully read what I wrote, or you would have checked the Market to see what the name of the app that does not have a pay version is. The one I am talking about does not.
I will tell you this. I am posting this from my laptop, because I had to return my Tablet and have a replacement shipped and now I have to spend a few days getting it all set up again the way I had it.
Avoid the ROM Mgr apps on the TF700T. And avoid the free app called "Reboot into Recovery". A user told me about it for my device, who had seen it used successfully. However, if you look at the reviews in the Market, you'll see that one of them says it bricked his *WORKING* *FINE* tablet and this thread right here has told you about two more. So just believe it and don't criticize, huh?
Okay Mods, feel free to jump on me again, just like last time.

I agree with many of your points, Zeuszoos, and thanks for pointing that out, but I believe there are many senior members at XDA willing to help if they have knowledge/abilities to do so, that's been my experience so far and hopefully it can be yours too. Of course, a little SEARCH won't hurt before posting one's problem, as you reasonably mentioned yourself
"reboot to recovery" has been in my apps STICKY thread in the sections "apps to avoid" (RED) for quite some time now after first reports of bricking users' devices started popping up and I believe it has helped some users who did a little reading before clicking...

Potentially F'ed TF300T

I was wiping my tab getting ready to sell it to my cousin. I was in recovery TWRP 2.22 I think. I walked away when my 4 yr son got a hold of it. I came back to see he wiped everything meaning the system. So tried to recover from my nandroid back up but it was gone with everything on my internal SD. I tried mounting the tab to my PC to transfer the old ROM back on but it wouldn't see it with any drivers I've tried. I also tried putting it on my microSD that was in there and it's also not being seen by TWRP 2.22.
I tried to fastboot flash the OEM JB ROM on it when all else failed in TWRP recovery. That didn't work. I tried flashing a CWM recovery to see if it would work better than the old TWRP I had. But after flashing that, my tab won't boot to fastboot and goes in a constant boot loop lol. SMFH at this madness. When the until turns on, it shows the device is unlocked. If I hold the vol down, it will say it's going to recovery then restarts every time no matter what. All I want to do is see if this is even remotely possible to recover from. If not this joint is going on Feebay to game some cash back. So if anyone has any good idea's. I'm open to whatever. What's he worst that can happen. My tab becomes an even bigger bricked unit lol.

Anybody know what options I got? I've read through many threads and none seem to have the answer I'm looking for.

So you extracted the blob file from the Asus official firmaware and flash system blob in fastboot? And that failed?
Sent from my Galaxy Nexus using xda premium

larryv1979 said:
So you extracted the blob file from the Asus official firmaware and flash system blob in fastboot? And that failed?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah I tried that about 40 times. On 3 PCs with the Asus transformer pad usb drivers on all. I could fastboot TWRP latest recovery then it caused my tab to go into a endless boot loop. I can't get into fastboot mode no more.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Does it get recognized by the PC? Check Device Manager and see if its recognized. If it is and it has an alert (meaning it needs troubleshooting) right click the device update driver and when it asks you select the option where you search manually through a list of drivers. In there try looking for android ADB driver should be one of the first, install it and try again.

It shows up as Asus ADB Interface. But as soon as I attempt to get the to get back to fastboot or even recovery it reboots. So I think the system is dead because nothing I've read seems to be related or can help this system out.

Don't know if this will help, but have you tried the hard reset button?

Where's that? I know that's a potentially a [email protected] question but I didn't realize there was a hard reset button.

JayWheelz said:
Where's that? I know that's a potentially a [email protected] question but I didn't realize there was a hard reset button.
Click to expand...
Click to collapse
AFAIK its the small hole under the microsd slot.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

I tried that hard reset button and it doesn't help. But I managed to put the tablet in a state where it's recognized by my PC looking for a APX driver. Then I found a Asus APXusb driver but still don't know what I can do from here. After installing the driver. I still can't fastboot or adb to the device. So again I think this tab is a brick.

[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] Bricked TF300T (APX mode only, no nvflash) – any hope?

I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.

I think to only solution is to replace the main board OR buy a new tablet :'(
Sent from my ASUS Transformer Pad TF300T

jay-roc said:
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
Click to expand...
Click to collapse
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
For future reference here is the way I see the recovery and rom matching issue.
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob

tobdaryl said:
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
Click to expand...
Click to collapse
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.

jay-roc said:
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
Click to expand...
Click to collapse
I'm sorry, I hoped the guide would give you a chance of recovery.

I definitely appreciate the help, and the guide's a great resource.
tobdaryl said:
I'm sorry, I hoped the guide would give you a chance of recovery.
Click to expand...
Click to collapse

jay-roc said:
I definitely appreciate the help, and the guide's a great resource.
Click to expand...
Click to collapse
You are welcome!
I had wished for better results.
Good Luck!

noahvt said:
I think to only solution is to replace the main board OR buy a new tablet :'(
Click to expand...
Click to collapse
Is there any tips for buying mainboard? Should it be exactly the same as in my tablet (I mean the same region and, therefore, version of ROM installed), maybe serials.
I have a bricked TF300T, and the only way I have to resurrect it - MB replacement. So, please, ANY info will be useful. Thanks in advance.

try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster

Buster99 said:
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Click to expand...
Click to collapse
I'm so damn appreciated! Thank you so much)) I'd add this way to get to fastboot - adb reboot fastboot - just from faulty CWM. Other way it didn't worked.

I got mine working this way
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!

ozkrtech said:
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
Click to expand...
Click to collapse
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty

martyzzz said:
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
Click to expand...
Click to collapse
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+

ozkrtech said:
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
Click to expand...
Click to collapse
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers

martyzzz said:
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
Click to expand...
Click to collapse
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.

is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app

ozkrtech said:
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
Click to expand...
Click to collapse
When i press vol down+power i get the asus boot screen for a minute or 2, the tab switches off and on again to the same boot screen.
I cant boot into recovery
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
Buster99 said:
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
I dont have fastboot in any way.
I can only power on the device with volume up + power to enter APX mode, than only my pc sees a USB device.
I tried a lot of differtent drivers but for nome of them i can ADB of Fastboot to the device.
It would help if someone that has managed to unbrick through APX mode posted the right driver for a TF300T
Cheers

have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app

Buster99 said:
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)

martyzzz said:
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
Click to expand...
Click to collapse
don't just point at the folder
manually select the driver for the device from android-sdk\extras\google\usb_driver
gl

[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.