Database Info

[Q] [solved] Won't boot - No ADB, no CWM/, no "wipe data", no nvflash (c20 serial)

[Q] [solved] Won't boot - No ADB, no CWM/, no "wipe data", no nvflash (c20 serial)
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
After lots of searching and reading, I found a few help threads that offered suggestions for those unable to boot, but they all require adb. My understanding based on the adb tutorial is that it requries configuration within the Android OS, and for the device to be running, which mine does not. And from what I've read, the c20 serial number isn't compatible with nvflash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
edit: to clarify, I never setup ADB, which makes me think that solutions like this won't work: http://forum.xda-developers.com/showthread.php?p=25636698#post25636698

Hello cfbauer,
Did you try this driver pack? after 1st remove all you transformer drivers?
http://forum.xda-developers.com/showthread.php?t=1514942
If you install this, then you can check with adb if there is communication possible with your transformer. if you connect it, is there any life on your pc when you start your TF?
or volume + and power to put tablet in apx mode and see if then the apx driver installs. If it does then try the brks rootkit v7.1 to see if you can install cwm with this tool....maybe your refurbished TF is an old B40 to 70).
unless this is what you already did......
dont forget to disable spashtop and asys sync on your pc.......

Well I managed to get ADB setup, I think. I'm new to this, but when I attempt to boot into recovery, and do "adb devices" I get "0123456789ABCDEF offline".
I'm a little hesitant to try nlheiz's suggestion of brks rootkit v7.1 as it says it's for a serial number that's older than my device is. nlheiz, can you confirm this is safe? Or can someone else suggest an alternate method of getting my 2 week old Transformer to a useful state? I definitely appreciate the help.
-Chris
edit: I just read this
The only thing that differs between SBK1 tablets and SBK2 tablets is the use of NVFlash. SBK2 cannot use NVFlash, so if you end up botching both your recovery and your ROM, and cannot boot into either, then you are SCREWED, so I would suggest reading everything before attempting to mod your device if you are an SBK2 owner.
Click to expand...
Click to collapse
There is no emoticon to convey how sad I am right now
edit2: I'm looking at trying this guide: http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html since it appears to be able to fix the issue I'm having.
edit3:attempting the guide posted in edit2 is giving me a "error:device offline" on step 6 when I try the adb push command
edit4: I can't seem to download brk Universal Rootkit 7.1 as neither download link is working

Does anyone have a suggestion? I'd appreciate it. Or is my device totally dead and I'm just screwed?

Try NvFlash anyway, It can't hurt. Does ADB work at all?

Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Thanks for your response. I get "0123456789ABCDEF offline" when I type adb devices when I boot into recovery mode, which isn't actually recovery mode since the system it hangs when I try to boot into recovery mode.

cfbauer said:
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
Click to expand...
Click to collapse
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?

baseballfanz said:
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?
Click to expand...
Click to collapse
OMG it worked! I'm back baby! So exited. Thanks for your help! I suppose this means my Transformer is an SBK1. Nice.
To answer your questions if you're curious, I used RecoveryInstaller. It was CWM, but an older version, my mistake. I ran into the random reboots issue, but the version of CWM recoveryInstaller used wasn't compatible with Aroma, which was required to install a custom kernel.
I don't remember the exact text on screen when I try to load into recovery, but I believe it was something like "booting into recovery mode."
And yes, I did try a different usb port for adb, it didn't work. Thanks for the suggestion though!

Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Worked! Thanks for the heads up!

By the way, you don't need Aroma to install a custom kernel with AOKP. Since I utterly refuse to flash touch recovery (no ext-sd support) I can't use aroma. The classic way is to go grab the .zip of the kernel (I recommend Testymehics or Guevor's test kernels) out of development. Clear cache, then flash as if you were flashing a rom, no aroma required.

[Q] Trying to Root.

I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!

Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?

arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.

sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?

arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?

sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.

arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.

I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.

sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).

arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.

sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.

Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS

unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance

1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.

Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.

Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx

D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.

arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?

D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.

arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me

[Q] TF300TG Boot/Recovery Problem

OK - some help please? I've replaced/unlocked bootloaders and installed cwm/twrp/custom roms and recovery on a dozen android phones and tablets recently - but the TF300TG has beaten me ....
I have recently:
1. Unlocked bootloader on 4.1.1 device using Asus Unlocker v7 (OK - so there goes any warranty )
2. Upgraded to Android v4.2.1
3. Installed JB TWRP - android remains accessible and functional but cannot access partitions from TWRP
4. Replaced TWRP with CWM (recovery-jb) - no improvement
5. Returned to TWRP. However on reboot, the system immediately boots TWRP instead of full android. I am unable to access either Android proper or Fastboot.????
EDIT: I should also add here that I suspect it was some idiot's(umm - that'll be me) foolish Wipe within the TWRP at step 5 above that caused this disaster - and that this removed more than just data. RTFM Richard!!
Not bad for a 4 day old tablet eh? Since I can no longer access fastboot, my guess is that I may need to rebuild the partitions (or at least the partition table) via ADB Sideload. Make any sense? If so, a little guidance really would be appreciated!
TIA,
Richard

Bump?
riclin54 said:
OK - some help please? I've replaced/unlocked bootloaders and installed cwm/twrp/custom roms and recovery on a dozen android phones and tablets recently - but the TF300TG has beaten me ....
I have recently:
1. Unlocked bootloader on 4.1.1 device using Asus Unlocker v7 (OK - so there goes any warranty )
2. Upgraded to Android v4.2.1
3. Installed JB TWRP - android remains accessible and functional but cannot access partitions from TWRP
4. Replaced TWRP with CWM (recovery-jb) - no improvement
5. Returned to TWRP. However on reboot, the system immediately boots TWRP instead of full android. I am unable to access either Android proper or Fastboot.????
EDIT: I should also add here that I suspect it was some idiot's(umm - that'll be me) foolish Wipe within the TWRP at step 5 above that caused this disaster - and that this removed more than just data. RTFM Richard!!
Not bad for a 4 day old tablet eh? Since I can no longer access fastboot, my guess is that I may need to rebuild the partitions (or at least the partition table) via ADB Sideload. Make any sense? If so, a little guidance really would be appreciated!
TIA,
Richard
Click to expand...
Click to collapse

No-one able to help here??
Would really appreciate some guidance before I blow the tablet away completely!
riclin54 said:
Bump?
Click to expand...
Click to collapse

riclin54 said:
Would really appreciate some guidance before I blow the tablet away completely!
Click to expand...
Click to collapse
Once booted in TWRP go to the Reboot menu and "Power Off" then boot into fastboot (it should NOT skip straight into TWRP unless your volume rocker is busted). Once you've got fastboot back ensure you do get the right TWRP!
f69m said:
First of all go to the bootloader screen by holding power and vol-down.
Double-check the Asus version of your bootloader at the top of the bootloader screen and pick the right TWRP version for it:
For Asus v10.4.*: any TWRP *-jb.blob
For Asus v10.6.1.8.*: only TWRP 2.4.4.0-4.2.blob
For Asus v10.6.1.15.*: any TWRP *-4.2.blob
Hope this is clear enough!
Click to expand...
Click to collapse

Thanks for your suggestion Rhian. However I've not yet sorted this. Perhaps a little more info from me will help you help me
The device is running 'Android cardhu-user bootloader <1.0.0 e> released by "WW_epad-10.6.2.3-20130402" A03'. It was unlocked with Asus Unlock_v7 whilst still running ICS and has had Superuser-3.2-RC3-arm-signed.zip installed.
Currently, on initial power up, the device boots straight into TWRP v2.5.0.0 Recovery. I can execute TWRP commands - however there seems to be an issue with access to partitions. Although I can mount the System partition - Cache & Data as well as Micro SDcard and SD-Ext are unmountable (neither can I see block devices in /dev that relate to these). I am however able to access a shell via adb. Further, both volume toggles appear to be operating as they should.
Rebooting from TWRP alerts that "Root permissions appear to be lost". I have attempted to reinstall Superuser but this has not resolved the matter.
"adb reboot boot-loader" will reboot the device into fastboot mode with the boot screen noting "Key driver not found .. Booting OS" and the version info above. From here, I have attempted to use adb to replace TWRP 2.5.0.0 with version 2.4.4.0. Although the adb commands complete without error, the new recovery is not written and the existing 2.5.0.0 remains in place.
From the Fastboot screen on the device, it can be forced to boot Android where everything seems to operate normally and with all partitions and filesystems appearing to be accessible.
All this suggests to me that there is either a problem with the bootloader itself, or less probably, that there is an issue with one or more of the partitions which is interfering with the boot process. There is however a better than even chance that I'm wrong.
I'm considering reformating and replacing the partitions one by one - however this seems rather extreme and in any case, I've not been able to locate an ASUS source of the partitions images yet.
Doing my head in here Rhian - any suggestions?
Thanks,
Richard
Rhian said:
Once booted in TWRP go to the Reboot menu and "Power Off" then boot into fastboot (it should NOT skip straight into TWRP unless your volume rocker is busted). Once you've got fastboot back ensure you do get the right TWRP!
Click to expand...
Click to collapse

Recovery issue
Hi, i have the latest 10.6.1.15.3 rom. I've installed twrp 5.0.0, 4.2 recovery. Now, i can enter to recovery, but if i want to make something, do nothing. It seems, twrp don't see the sd card. Any idea?
Thanks

Possibly bricked trying to update to CM11

A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!

Quevvy said:
A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!
Click to expand...
Click to collapse
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.

cmendonc2 said:
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.
Click to expand...
Click to collapse
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…

Quevvy said:
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…
Click to expand...
Click to collapse
No, you need nvflash backups to use APX mode. Since you can't get to the recovery menu, I can't think of any other solutions....?

Same here
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.

boggessb said:
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.
Click to expand...
Click to collapse
You would have to open it and replace the motherboard with a new one like this:
http://forum.xda-developers.com/showthread.php?t=2368372
With a new part like this:
http://www.ebay.com/itm/like/390706401658?lpid=82

[Q] TF700 bricked...?

Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!

Fastboot
pippolino123 said:
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Click to expand...
Click to collapse
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??

lj50036 said:
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
Click to expand...
Click to collapse
unfortunately not... I don't see the three icons it is stuck with the ASUS logo

nvflash
pippolino123 said:
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
Click to expand...
Click to collapse
Do you have your Blob files from enabling nvflash??

lj50036 said:
Do you have your Blob files from enabling nvflash??
Click to expand...
Click to collapse
sorry don't understand what you mean. Can you please clarify. ..?

nvflash
pippolino123 said:
sorry don't understand what you mean. Can you please clarify. ..?
Click to expand...
Click to collapse
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/

lj50036 said:
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
Click to expand...
Click to collapse
yes, I think you are right... didn't know about the nvflash stuff. Thanks either way for your help!

Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app

lj50036 said:
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure I will... thanks again and happy holidays

So since I feel like I have a complex problem that I can't seem to search for, I'm piggy backing this thread. It's been a year since I rooted this tablet, and I went on deployment with it. Worst ROM ever, couldn't get YouTube, WiFi was sketchy at best so I came back and it even had the OTA updater to update to a newer version, well that wouldn't load at all.
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen. So when I tried to update to this new ROM, I kept getting download faults, so I figured I was stuck with this crap ROM because basically I quit trying. Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik (I didn't save anything to this tablet, nothing to lose)
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?

First the good news:
The page with the three icons is the bootloader menu which means you should have fastboot access to your tablet from your computer.
You can use fastboot to flash a new recovery (TWRP) and once that is installed you can flash the new rom.
So this can be fixed relatively easy, but you have to do some reading before attempting it. Done correctly this is a safe procedure. Done without understanding what you are doing could leave you with a hard brick - right now you're probably just soft bricked.
s14owner95 said:
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen.
Click to expand...
Click to collapse
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik.
Click to expand...
Click to collapse
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
Click to expand...
Click to collapse
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have to unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.

berndblb said:
First the good news:
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Click to expand...
Click to collapse
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
berndblb said:
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Click to expand...
Click to collapse
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
berndblb said:
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
Click to expand...
Click to collapse
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery

Hope this worked

s14owner95 said:
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Click to expand...
Click to collapse
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???

berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?

s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
Click to expand...
Click to collapse
Mmmhh, your tablet may need a little deeper cleaning. Check out buster99's post (#12). His method has helped dozens recover from worse than you have right now.
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
His instructions are for the TF300. naturally you want to flash the blob for the TF700. That would get you back to a healthy stock system. Then you can again flash TWRP and through it a custom rom.
Good luck!
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
Click to expand...
Click to collapse
Are you saying the twrp flash went ok?
You don't flash the rom in fastboot. You boot back into recovery, choose "Install" and select the CROMi-X zip you downloaded.
But before you do that I would seriously suggest you format your data partition. That means you have to have the downlaoded rom zip on your external card (otherwise you will erase it with the format).
So boot into TWRP, choose Wipe > Advanced > Format data
Then go back to TWRP Home, choose Install and navigate to the CromiX zip. Make sure the box "verify zip signature" is checked and flash the rom.
Do this only if you have a working recovery!!! Do not attempt with your busted one!!
You can only access the tablet in MTP (as an external drive) if your system is working. It's not - yet.

OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.

s14owner95 said:
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
Click to expand...
Click to collapse
To use ADB you have to be in your recovery or the Android system needs to run.
If you have a working recovery back - why do you want to mess with ADB unless you are familiar with it? You are treading on thin ice doing stuff without really understanding what you are doing! What's the rush?

The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it

s14owner95 said:
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
Click to expand...
Click to collapse
Your drivers are working. You need different sets of drivers for different modes: fastboot drivers, adb drivers, mtp drivers.
Your tablet shows up as a bootloader interface because it is in fastboot mode - ergo the fastboot drivers are working.
You HAVE to get a working recovery onto the tablet. It will NOT work without a recovery. To push a rom zip to the tablet is useless - the only thing working on your tablet is fastboot mode.
If the recovery flash fails, try buster99's method. That should clean all the crud off your partitions.
But you need to have the Asus firmware blob file for this! You cannot do this with any rom zip!!
Edit: You did push the correct recovery this time, did you?