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

[Q] TF700 Unrecoverable bootloader error 0x00000008

signature Mismatch Unrecoverable bootloader error 0x00000008
unlocked & rooted.
had TWRP TeamWin installed
tried to install a new Rom & got the above error
wiped data & now only the following shows.
signature Mismatch
Unrecoverable bootloader error 0x00000008
is this unit dead & not fixable?
I bought from Amazon so maybe returnable? if not fixable, had for a week now.

If you can't get into fastboot or recovery then it is hardbricked.
le rustle face

Keion said:
If you can't get into fastboot or recovery then it is hardbricked.
le rustle face
Click to expand...
Click to collapse
have never used fastboot icon but it dont boot that far for the icons to show anymore.
but no recovery as it can't continue far enough for TWRP TeamWin splash screen to show up
as i guess the bootloader needs to work to get past this stage.
as far as I read there are no fixes for bad bootloader. but this was posted in feb & march of 2012 so I was hoping for new info & maybe a fix.

this is most probably the reason why asus voids your warranty when you unlock. I dont trust any other recovery than ClockWorkMod.

Maybe toggle signature verification to disabled? Or if your able to still go into recovery, sideload the latest firmware from asus site and flash it from recovery?
..........
Sorry just read the above comment... Hopefully someone here can help you out. Good luck to you!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

atc3030 said:
Gtalk Me before you send it. I think I had the same problem and if so i can fix it for you. Gtalk: [email protected]
Click to expand...
Click to collapse
try contacting this guy and see if he can help.
for what its worth I flashed with twrp and had no issues.

lafester said:
try contacting this guy and see if he can help.
for what its worth I flashed with twrp and had no issues.
Click to expand...
Click to collapse
Would have been nice to have a backup bootloader, holding down buttons to switch to & repair
if asus can repair im sure there is a way.
I am not able to get into recovery any longer.
seems like the clockworkmod has an option to disable signature option, but I can't even get to twrp
I made a big mistake & did this flashing AOKP 4.1.1 with twrp I think it wiped the twrp recovery app & messed up the bootloader now.
im sure there is a repair for fixing the bootloader as if it is sent to asus they can repair it for like $50 ;(
Any steps to take to help repair this would be great

NeoGodSpeed said:
Would have been nice to have a backup bootloader, holding down buttons to switch to & repair
if asus can repair im sure there is a way.
I am not able to get into recovery any longer.
seems like the clockworkmod has an option to disable signature option, but I can't even get to twrp
I made a big mistake & did this flashing AOKP 4.1.1 with twrp I think it wiped the twrp recovery app & messed up the bootloader now.
im sure there is a repair for fixing the bootloader as if it is sent to asus they can repair it for like $50 ;(
Any steps to take to help repair this would be great
Click to expand...
Click to collapse
your issue was with the pre alpha AOSP rom, not with the TWRP recovery. TWRP recovery also allows no signature checking.

okantomi said:
your issue was with the pre alpha AOSP rom, not with the TWRP recovery. TWRP recovery also allows no signature checking.
Click to expand...
Click to collapse
cool, nice to know.
seems there must be a way to do something as if you hold the right vol button + power it connects to PC & shows in windows 7 Device Manager
but not the same as if the system was booted in to android as it shows the internal & sdcard. this dont show the interal or sdcard but shows it's connected. wonder if asus connects to the port where the charging cable or dock go's to repair bad bootloaders.
tried adb.exe devices but it dont show anything connected still. even tried the asus android bootloader interface 4.0.0.5 driver.

NeoGodSpeed said:
cool, nice to know.
seems there must be a way to do something as if you hold the right vol button + power it connects to PC & shows in windows 7 Device Manager
but not the same as if the system was booted in to android as it shows the internal & sdcard. this dont show the interal or sdcard but shows it's connected. wonder if asus connects to the port where the charging cable or dock go's to repair bad bootloaders.
tried adb.exe devices but it dont show anything connected still. even tried the asus android bootloader interface 4.0.0.5 driver.
Click to expand...
Click to collapse
I'm really sorry this happened to you, but you probably knew you were venturing into very untested ground.
Are you posting in the Pre alpha AOSP thread? That might be more productive for you. It seems there have been at least 3 hardbricks from flashing that rom.

polish_pat said:
this is most probably the reason why asus voids your warranty when you unlock. I dont trust any other recovery than ClockWorkMod.
Click to expand...
Click to collapse
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
NeoGodSpeed said:
Would have been nice to have a backup bootloader, holding down buttons to switch to & repair
if asus can repair im sure there is a way.
I am not able to get into recovery any longer.
seems like the clockworkmod has an option to disable signature option, but I can't even get to twrp
I made a big mistake & did this flashing AOKP 4.1.1 with twrp I think it wiped the twrp recovery app & messed up the bootloader now.
im sure there is a repair for fixing the bootloader as if it is sent to asus they can repair it for like $50 ;(
Any steps to take to help repair this would be great
Click to expand...
Click to collapse
Accessing the bootloader on phones is done at a much lower level, not sure about tablets. JTAGing is usually the way bootloader is restored when hard bricked (a serial connection). I have been googling just to see what is out there... but pretty limited info on bootloader recovery/overwrite for any of the asus tablets.
NeoGodSpeed said:
cool, nice to know.
seems there must be a way to do something as if you hold the right vol button + power it connects to PC & shows in windows 7 Device Manager
but not the same as if the system was booted in to android as it shows the internal & sdcard. this dont show the interal or sdcard but shows it's connected. wonder if asus connects to the port where the charging cable or dock go's to repair bad bootloaders.
tried adb.exe devices but it dont show anything connected still. even tried the asus android bootloader interface 4.0.0.5 driver.
Click to expand...
Click to collapse
Keep digging. The fact that your PC can see the device is a start. Does win7 load the device drivers?

Poser said:
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
Accessing the bootloader on phones is done at a much lower level, not sure about tablets. JTAGing is usually the way bootloader is restored when hard bricked (a serial connection). I have been googling just to see what is out there... but pretty limited info on bootloader recovery/overwrite for any of the asus tablets.
Keep digging. The fact that your PC can see the device is a start. Does win7 load the device drivers?
Click to expand...
Click to collapse
Im not bashing anyone or any product, was my fault, no one elses. I have been modding for 20 years & should have known better & done more research into what I was doing here. We are warned all over these forums that everything we do is a risk. you dont blame anyone but your self.
JTAGing would be the way to repair, I agree, I just haven't found anything for the transformers yet. been looking, but nothing out there that someone has connected & got to work. just talk about jtag & transformer. there are some arm7 jtag programmers im sure some software could be made, but I think we are far from knowing how to talk to the bootloader in a low level, im sure some are trying to reverse engineer to get to the boot loader.
yes, windows loads the drivers when you hold the right vol button + power. you hear it connecting if windows 7 has speakers on. the drivers do have to be installed for this to work, I think the device is called APX in device manager.
I have posted in the other forum about this, but like I said above, not a products fault.
I would like to thank everyone for there input.

Poser said:
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
Accessing the bootloader on phones is done at a much lower level, not sure about tablets. JTAGing is usually the way bootloader is restored when hard bricked (a serial connection). I have been googling just to see what is out there... but pretty limited info on bootloader recovery/overwrite for any of the asus tablets.
Keep digging. The fact that your PC can see the device is a start. Does win7 load the device drivers?
Click to expand...
Click to collapse
The Volume Up + Power button combination allows you to put the device in APX mode but it's still useless without a working NVflash solution.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

thanks for the info Pretoriano80
I will keep researching for Jtag & bootloader recovery & waiting for nvflash to be ported to the transformer series Doesn't even seem JTAG would even be needed just a port of nvflash, jtag would be a marketing thing most likely after reseaching other tablets that have unlocked bootloader, they just use nvflash if im correct in my finding here. as if it can be fixed down the road then no worries anyone would have as it could be fixed if a JTAG or nvflash portedwas made, bought & was plug & play install not taking apart tablet, just plug into docking station port & plug usb cable to computer install drivers & JTAG software GUI interface software made for windows 32bit & 64bit plus Linux support also or just nvflash ported. im sure there are people already looking into this.
I sent back the unit to Amazon will get another unit late thursday.
I think I will only root this unit, until I understand & research more on Android devices like I should have from the start my mistake, No one else, as this was my fault & no one else.
everyone should know everything is at risk, if the bootloader is unlocked. my new replacement will only be rooted, till I see a must have for a unlocked bootloader. rooted seems to be a must have. but not a unlocked bootloader at this stage of the transformer. maybe at some point down the road, it would be a must have, but time will tell.
:fingers-crossed: Let me know if any of you are looking into JTAG & or nvflash for the tranformer, im sure nvflash is the way to go & not jtag

Poser said:
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
Click to expand...
Click to collapse
Is there a version of cwm yet? Although it has some really great features, I still don't quite trust twrp after causing all of those soft bricks after recovering by not properly restoring /boot
Sent from my Nexus 7 using xda premium

Thread cleaned. Take the fighting out to the parking lot boys....

I think i might have bricked.....

My infinity. I was foolishly in a hurry to make sure I was going to be able to receive the JB update and downloaded the build.prop that was posted last week in the ota thread. I'm so retarded that I forgot that build.prop was for .26 and not 30. So I copied it into system/ and rebooted.
Now all it does is sit at the 1st asus screen and nothing else.
I'm rooted and not unlocked. Iv'e tried factory resetting, hard reset, and nothing works. So it looks like I got an expensive paper weight now.
Any recommendations? If so it would be really awesome.

e?
adb push the correct file? might have to root again first.
i know its tempting but wiping data when you can't boot is never a good idea.

I DID THE SAME THING!!! in fact I think he linked me to it :/ lol
any help PLEASE!!

lafester said:
adb push the correct file? might have to root again first.
i know its tempting but wiping data when you can't boot is never a good idea.
Click to expand...
Click to collapse
I'm in the process of downloading the .30 update from asus's website then i'm going to go from there.
darkreaper476 said:
I DID THE SAME THING!!! in fact I think he linked me to it :/ lol
any help PLEASE!!
Click to expand...
Click to collapse
Sucks don't it! I hope we can recover it.

Im new to the asus' is there any way we can adb into these things via stock recovery mode? any way to get that build.prob fixed? I can take it back but I DONT WANNA.. lol
and what would be the correct build.prop to use? I still have my modified one on the system renamed but.......

Ok, Iv'e tried the "adb devices" from the command prompt and i can't get get my computer to recognize the infinity. Iv'e downloaded android sdk and got it up and running but no dice. I don't know what else to do
If anybody has any advice or any suggestions that me and darkreaper476 can do, i will love you forever. :nohomo:

Nevermind...

I can get to where it says:
reboot system now
wipe data/factory reset
wipe cache partition
But i can't get my computer to recognize the tablet.

This might be a stupid question but I'll ask it anyway. Have you installed the proper drivers for ADB to recognize the TF700?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Biohazard0289 said:
This might be a stupid question but I'll ask it anyway. Have you installed the proper drivers for ADB to recognize the TF700?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
would ADB have recognized it recovery mode? Even it it does the ab doesnt give you enough time to work... 10 seconds before it attempts to reboot. what good is adb if the device isnt in an adb friendly mode? IDK... I'm sick of trying to fix these stupid little issues.. I just returned it, sure I lost some photos and files (I HATE INTERNAL STORAGE) but F it... That why I bought the warranty...
thanks anyway

Something similar to me happened when I was restoring what I thought was my original backup of the build.prop file. Now I get stuck on the Asus screen. Reseting cache, delvik, user data, etc doesn't help.
Does anyone have instructions on how to setup ADB, TF700 drivers, and how to take any firmware and flash it that method, in a simple set of instructions that doesn't require a nuclear physics degree?
I would rather not have to RMA this thing and wait a month or more to get a new one ...

1stx2 said:
I can get to where it says:
reboot system now
wipe data/factory reset
wipe cache partition
But i can't get my computer to recognize the tablet.
Click to expand...
Click to collapse
You don't need adb to recover your device, just follow my How-To guide from the General forum and you should be good but you need an external MicroSd card to do it.

Pretoriano80 said:
You don't need adb to recover your device, just follow my How-To guide from the General forum and you should be good but you need an external MicroSd card to do it.
Click to expand...
Click to collapse
This assumes that I'm able to get to the recovery. I was able to at one point, but now it won't. In other words, if I hold Pwr+VDown, wait till the text, and then release Pwr+Vdown, and then press VUp, it says booting recovery image, signature blah blah, shows an android guy with his chest open and a red exclamation mark. That screen shows for a few minutes, after which I get a reboot and its back to the Asus logo. Is recovery hosed now? If so, now what the hell do I do? Is it bricked for good?

spinaldex said:
This assumes that I'm able to get to the recovery. I was able to at one point, but now it won't. In other words, if I hold Pwr+VDown, wait till the text, and then release Pwr+Vdown, and then press VUp, it says booting recovery image, signature blah blah, shows an android guy with his chest open and a red exclamation mark. That screen shows for a few minutes, after which I get a reboot and its back to the Asus logo. Is recovery hosed now? If so, now what the hell do I do? Is it bricked for good?
Click to expand...
Click to collapse
That's the stock recovery, what happens if you press Power button once while you are at the "dead android" screen?
Edit: in your case Restore with Stock recovery should do the trick.

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] 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