[Q] Stuck on the animated boot screen (spinning wheel) - Asus Transformer TF700

Hi guys
I recently tried putting a CM10 on my tf700t 4.2.1
I read all the guides, dangers and info I could before starting.
I had numerous issues with adb and all the command prompt programs not recognising my device was connected.
Anyway, I unlocked it using the ASUS tool from their website, that was fine.
I then followed the instructions on getting the recovery image on. I got TWRP on finally.
I then placed the CM zip folder on the storage, booted in recovery and flashed it on.
It installed successfully but now it doesn't get back the boot up screen of the spinning light wheel.
ANy help would be appreciated, I can still boot to the recovery menu, should I wipe it all or?
Thanks in advance!

Sounds as if you may have the wrong bootloader or the wrong bootloader/recovery combination. Check which bootloader is required for CM and what you are running now. Also, versions matter. So check the compatibility of the TWRP version you are running.
Do not wipe anything unless you know what you are doing!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

Related

HELP! Soft-Bricked TF300T

ACK! I just got my TF300 this evening, and did this method to root it. Nothing is even installed on the tab yet, it's just out of the box. I'm bricked. Stuck on the screen that says "Eee Pad", with no status bar, nothing. Tried to boot into recovery, and get the dead android with the red triangle/white exclamation point on him.
Can anyone help me unbrick my tab, please?
flash cmw via fastboot. once you've got cmw up and running boot into it and adb push c:\stockrom.zip /sdcard and then just flash it.
Sent from my ASUS Transformer Pad TF300T
atomicblue said:
flash cmw via fastboot. once you've got cmw up and running boot into it and adb push c:\stockrom.zip /sdcard and then just flash it.
Sent from my ASUS Transformer Pad TF300T
Click to expand...
Click to collapse
Awesome, thank you much. Two questionsI apologize if they are n00b questions)
1. I have adb.I know fastboot is different (at least, I think it is). How do I install fastboot?
2.Where do I get the stockrom.zip from, or is it already present on the internal sd?
Thank you for the answer and your patience!
I ended up taking the tab back, and they exchanged it for another one. Now, I have a totally new problem, however, so I made a post for it. Thank you tho!

Not able to reboot into recovery or auto-install ROM's

I had unlocked my TF700T and installed CM10, but it has never had the capability to reboot into recovery when enabled in the developer options -- selecting that when rebooting simply makes the ASUS logo come up several times, then it boots normal without going into recovery.
A related issue is when I download a CM10.1 update and tell it to upgrade, it reboots but doesn't install the new version from recovery.
I'm assuming something isn't unlocked or enabled somehow... but on the ASUS boot screen it does say "device is unlocked".
Nerva said:
I had unlocked my TF700T and installed CM10, but it has never had the capability to reboot into recovery when enabled in the developer options -- selecting that when rebooting simply makes the ASUS logo come up several times, then it boots normal without going into recovery.
A related issue is when I download a CM10.1 update and tell it to upgrade, it reboots but doesn't install the new version from recovery.
I'm assuming something isn't unlocked or enabled somehow... but on the ASUS boot screen it does say "device is unlocked".
Click to expand...
Click to collapse
I assume you can still access the recovery per the button-press method?
Yes, that's the only way I can access it.
Nerva said:
Yes, that's the only way I can access it.
Click to expand...
Click to collapse
The button press method is the proper way to flash anything. If you unlock you BETTER know how to flash in recovery. Also, GooManager will not flash firmware on the TF700, you must do it manually from recovery, thus why the upgrade is failing.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Yes I certainly can and do flash all sorts of stuff from recovery -- first CM, now TWRP. But on my Epic 4G I just use CM Updater to download the latest ROM, then it asks me if I want to install, I say yes, and it reboots and installs it for me. But on my TF700T it isn't happening -- when I answer "yes" it just reboots without installing the new ROM.
Is it NORMAL with the TF700T to be unable to boot into recovery by using the power menu??
Is there something I don't have configured properly or didn't install something properly?
Nerva said:
Is it NORMAL with the TF700T to be unable to boot into recovery by using the power menu??
Click to expand...
Click to collapse
Yes (with the stock ROM).
Sorry, I should have been clear: I meant "with any version of CM?"
I use goo manager just to reboot into recovery, than flash manually. If I had to do the button boot recovery I wouldn't flash anything anymore.
Always sweaty hands when I see those three icons.
Sent from my HTC One X using xda app-developers app
Interesting. Rebooting to recovery with Goo Manager doesn't work for me either -- it just flashes the ASUS logo several times and then boots normally.
Seems like my recovery isn't setup properly -- any suggestions on how I can fix it?
Nerva said:
Interesting. Rebooting to recovery with Goo Manager doesn't work for me either -- it just flashes the ASUS logo several times and then boots normally.
Seems like my recovery isn't setup properly -- any suggestions on how I can fix it?
Click to expand...
Click to collapse
Sorry I can't help you fix it. But getting into recovery is as simple as typing this at the terminal if you have busybox installed or use the rebooter widget from ROM Toolbox or the market app. They all do the same thing.
Code:
reboot recovery

Can't access recovery or fastboot

I searched forums extensively but was unable to find a solution to this problem I recently encountered:
I recently flashed CWM Recovery and rooted my TF700 on android 4.0.3. Since I was not receiving any notifications for an OTA jellybean update I flashed it myself as per these instructions (apparently I'm not allowed to post URL as a new user, but the thread I read was entitled [GUIDE] How to manually update/restore firmware (Tf700, TF300, TF101, possibly TF201) and was located on transformerforums.com. The firmware update was successful, however I lost root access in the process. I attempted to reinstall root, however quickly discovered that CWM Recovery was no longer accessible by holding down power and vol down as it usually is; instead, I am taken to a bootloader screen with three options: RCK, ANDROID, WIPE. I can no longer access fastboot or my recovery ... can anyone shed some light on what I may do to gain access to recovery or fastboot again?
Thanks in advance!
fatalinsanity said:
I searched forums extensively but was unable to find a solution to this problem I recently encountered:
I recently flashed CWM Recovery and rooted my TF700 on android 4.0.3. Since I was not receiving any notifications for an OTA jellybean update I flashed it myself as per these instructions (apparently I'm not allowed to post URL as a new user, but the thread I read was entitled [GUIDE] How to manually update/restore firmware (Tf700, TF300, TF101, possibly TF201) and was located on transformerforums.com. The firmware update was successful, however I lost root access in the process. I attempted to reinstall root, however quickly discovered that CWM Recovery was no longer accessible by holding down power and vol down as it usually is; instead, I am taken to a bootloader screen with three options: RCK, ANDROID, WIPE. I can no longer access fastboot or my recovery ... can anyone shed some light on what I may do to gain access to recovery or fastboot again?
Thanks in advance!
Click to expand...
Click to collapse
That is my thread . You flashed stock correct? Then that means you wiped out root and CWM. You are able to access the boot loader with 3 icons? Look up in the corner, it will say when at the screen with 3 icons that fastboot is running. It is also suggested to use TWRP as CWM can cause TF700s to brick when on 4.2.1.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
That is my thread . You flashed stock correct? Then that means you wiped out root and CWM. You are able to access the boot loader with 3 icons? Look up in the corner, it will say when at the screen with 3 icons that fastboot is running. It is also suggested to use TWRP as CWM can cause TF700s to brick when on 4.2.1.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I noticed that it said fastboot was running, however my attempt to flash CWM again was unsuccessful. I will try TWRP tonight, thanks for the tip!
fatalinsanity said:
I noticed that it said fastboot was running, however my attempt to flash CWM again was unsuccessful. I will try TWRP tonight, thanks for the tip!
Click to expand...
Click to collapse
^ sorry i forgot; yes I flashed stock jellybean
Just tried to flash TWRP and got the same hangup as when I tried to flash CWM: command window says waiting on device and they never hook up. I noticed when I plug in my tablet instead of the typical low beep and then a high beep indicating a device is connected, i get three sad, low beeps, does that mean my ADB bootloader drivers are the problem? When I disconnect it makes the typical high beep and low beep.
fatalinsanity said:
^ sorry i forgot; yes I flashed stock jellybean
Just tried to flash TWRP and got the same hangup as when I tried to flash CWM: command window says waiting on device and they never hook up. I noticed when I plug in my tablet instead of the typical low beep and then a high beep indicating a device is connected, i get three sad, low beeps, does that mean my ADB bootloader drivers are the problem? When I disconnect it makes the typical high beep and low beep.
Click to expand...
Click to collapse
To make this simple,boot into the stock ROM, root it using motochopper. You are unlocked correct, Once rooted, download GooManager from Play Store, click top right 3 dots, and select "Install Openscript Recovery". Make sure GooManager has Root Rights' first. Then try booting into recovery after it restart.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Many thanks Tylor, worked perfectly! I now once again have root and have TWRP installed and functioning. Wish I had heard of Motochopper before, very nice tool.

Error loading recovery - trying to install CROMI

I unlocked my stock TF700T using the Asus Unlock Tool with 10.6.1.14.8 installed. It does say the device is unlocked in the upper left hand corner during boot. I then installed Goomanager and installed TWRP 2.5.0.0 as directed. It gave a very small splash screen indicating successful installation. Then when I execute the boot into recovery, it appears to try to install an update and then fails with the Red Exclamation "Error" android.
I've tried repeating the steps to no avail. I was able to wipe data so I think that my stock recovery is still in place. I also tried to install ADB Tool as an alternative way to install TWRP, but my Infinity would not unzip the package correctly and I couldn't install it. Can anyone help me get TWRP in place and boot into recovery so I can flash the CROMI ROM? Thanks.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
I was able to use the ADB Tool on my computer to flash the TWRP recovery onto the TF700. Thanks to all those who looked at this, but I'm on my way again to flashing a ROM. Guess I needed to give myself another hour to figure it out.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Petschska said:
I unlocked my stock TF700T using the Asus Unlock Tool with 10.6.1.14.8 installed. It does say the device is unlocked in the upper left hand corner during boot. I then installed Goomanager and installed TWRP 2.5.0.0 as directed. It gave a very small splash screen indicating successful installation. Then when I execute the boot into recovery, it appears to try to install an update and then fails with the Red Exclamation "Error" android.
I've tried repeating the steps to no avail. I was able to wipe data so I think that my stock recovery is still in place. I also tried to install ADB Tool as an alternative way to install TWRP, but my Infinity would not unzip the package correctly and I couldn't install it. Can anyone help me get TWRP in place and boot into recovery so I can flash the CROMI ROM? Thanks.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
You have to root your tab before you can use Goomanager to install TWRP.
Use the motochopper tool to root: http://forum.xda-developers.com/showthread.php?t=2258633
Run Goo again and give it root access. Now you will be able to install TWRP.

[Q] tf300t

Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Stravor said:
Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
noahvt said:
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
Click to expand...
Click to collapse
"Bricked" seems to be oftenly abused around here. Having ADB access and being able to boot into CWM, isn't there anything I can do to enable fastboot, force a bootloader downgrade or something?
Thanks!
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
noahvt said:
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Stravor said:
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Click to expand...
Click to collapse
"ricked" may be abused, but I don't understand your situation very well, much less how you extricated yourself from it. If you're in a boot loop, you cannot complete the booting process (much like a tab with bootloader, recovery, but no OS installed). Without it, you have no access to ADB. Which in turn doesn't allow you to issue ADB commands. If additionally, you have no access to fastboot because volume down+power, and/or reset+volume down, does nothing (bootloader with icons absent), you cannot issue fastboot commands. Without the two, and the uselessness of APX mode, I'm not sure why that's not characteristic of a soft brick.
I have a mainboard that shows nothing but the initial Asus logo (not the one with boot animation, i.e., spinning dots) and "the device is unlocked." If I use either fastboot or ADB from PC, it returns with "waiting for device..." You were in the same boat, were you not? Looks like part of the firmware is still there (I assume if you replace the nand with a brand new, blank one, nothing would show up on display) , but the bootloader is messed up. If you'd succeeded in resurrecting your tab, then how do I rectify it, if you care to enlighten? Thank you in advance.

Categories

Resources