Related
I'm pretty sure I have these items in the correct order to "Permaroot" my MT4G and begin using Clockworkmod to load ROMs (and or/also want to be able to back up my default ROM)
My current attempts:
Downloaded and installed: VISIONary, from android.modaco.com, sorry I can't post actual links (VISIONary+, most recent version) was no longer avalible in the market so I had to install it from the URL)
Downloaded and installed "Clockwordmod" from the Market.
Put the phone into USB-Debugging mod, and disabled fast boot.
VISIONary+ question: I setup TEMPROOT, and "Root on Boot", assuming I would than be able to boot into "Recovery mode" via "Clockworkmod"
The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Going back to VISIONary+, I attempt to "Permaroot", the phone's homescreen goes blank and nothing happens. The phone eventually turns itself off but doesn't reboot, subsequently, I must restart it manually, again, I'm not sure if I've achieved anything?
Advice, suggestions? Would be very appreciated.
Questions that might explain what's wrong?
Even in USB-Debugging mode, should I be connected to a PC via USB-Cable during all of this?
Any thoughts on why the PERMAROOT fails, or the "Root on boot" fails to get me to "Recovery mode"?
Last thing, I get a complaint from "Clockworkmod" when loading, that my SD Card must be mounted (which I'm assuming it isn't due to USB-Debugging mode and/or being connected to the PC) So should I get a good charge and disconnect from the PC while attempting all this? Fixed, disconnected USB-Cable, and mounted SD card in settings, this stopped this error
Also, I'm interested in backing up my default ROM ASAP as a safety-net in-case I screw something up. Is this possible via recovery mode in "Clockworkmod"? Links to advice on doing this?
Thanks everyone! Great board!
you should follow this as it worked for me flawlessly
http://forum.xda-developers.com/showthread.php?p=9534017#post9534017
thanks! that post seems to answer a lot of the specifics I might have been missing! Guess I missed it in search! I'll report my results!
I followed it exactly but I still get the Red Exclamation Point. I have rooted my phone s-off and I have superuser and rom manager. I did the Flash Clockwork Recovery but when I reboot into recovery I get Red Exclamation Point then when I click vol up and power the next says " E:Can't open /cashe/recovery/command " What should I do??
[*]The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Click to expand...
Click to collapse
You can NOT flash clockwork without S-OFF and the red triangle is recovery. It is stock recovery if you press volup+power you will see the menu
S is off I rooted my phone using the terminal Emulator and that worked fine
When I press upvol and power I see
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cashe partition
E:Can't open /cashe/recovery/command
This is what my screen shows when I try to go into recovery and again my phone is rooted s-off and I use superuser
Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot
I found out the problem it was so easy but I never would of thought of checking but my wife said maybe my Rom Manager is a bad copy (because I get all my apps from a not so honest site) so I deleted my RM and downloaded the freebie on the market and it worked on the first try.....Now I have Glacier Rom running and I feel like a new man
slhpss said:
Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot
Click to expand...
Click to collapse
+1 on that, When I first flashed it, I was still getting the red triangle, after a quick google search I re flashed it an extra 2 times and it worked flawlessly
Every time I install a new zip, I have to reset the IDME boot to 4000 before I can use the device again in Android. What can I do to prevent this?
I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...
podspi said:
I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...
Click to expand...
Click to collapse
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?
ontwowheels said:
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?
Click to expand...
Click to collapse
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.
furtom said:
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.
Click to expand...
Click to collapse
Thanks....I currently have this and TWRP installed via the KFUtility.
Can also verify I have avoided this by always powering down and not rebooting into recovery. At least with the 4 zips I have flashed.
install clockworkmod touch recovery
twrp never fixed the reboot option.
Sent from my HTC Glacier using xda premium
Fix TWRP boot loop
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.
citizenandroid said:
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.
Click to expand...
Click to collapse
Thank you for this! I've been looking through the forums trying to find something that would work. ADB won't launch for me, something I need to look into, but this worked. Thank! :]
Hi all!
I'm an andoird newbie and I've a big problem with my tab!
I was using the NX Manager by my PC to unlockink my android table and installing CWM.
All was going all right but, while I'm using CWM I was entring in the Format/Mount section to mount "system" but I've click the wrong botton in the wrong line and I've format my system dir.
Now I've my nexus block on the main page, where ther is the "Google" string on black screen.
I thinks there's no problem because I'll can install an new Rom (like cm 10) but, when I connect my device to my PC, the PC don't recognise my tablet! And I can't reboot the tablet or entre in recovery mod! Is block!
What can I do!?
The Rootkit don't go, the NX manager don't go (because I was hoping thet they reboot my tablet in fastboot).
Rox666 said:
Hi all!
I'm an andoird newbie and I've a big problem with my tab!
I was using the NX Manager by my PC to unlockink my android table and installing CWM.
All was going all right but, while I'm using CWM I was entring in the Format/Mount section to mount "system" but I've click the wrong botton in the wrong line and I've format my system dir.
Now I've my nexus block on the main page, where ther is the "Google" string on black screen.
I thinks there's no problem because I'll can install an new Rom (like cm 10) but, when I connect my device to my PC, the PC don't recognise my tablet! And I can't reboot the tablet or entre in recovery mod! Is block!
What can I do!?
The Rootkit don't go, the NX manager don't go (because I was hoping thet they reboot my tablet in fastboot).
Click to expand...
Click to collapse
So what's the issue, you don't have a recovery installed any longer?
RMarkwald said:
So what's the issue, you don't have a recovery installed any longer?
Click to expand...
Click to collapse
No because I've done a mess!
I' ve formatted the "system" folder, and now my tablet is freezed on the startup screen, with the Google logo, and if I try to reboot it/shut it down, the tablet doesn't work. So i'm locked in this situation.
I've downloaded two roms: CM 10 and the orignial google roms.
The very big problem is that:
Windows doesn't recognises my tablet! It says that I've connected an USB MTP but don't open anything! So I can't do aything...Is there any flasher program that can help me?
A good way to reboot it may be to turn off the battery opening the back dock, but i'm not good in hardware-hacking so I wonder in any other solution.
Thanks
Just now I turned it off holding the Powerbutton+Volumeup ( but now doesn't reboot in any way) and Windows recognises it as an APX device
Another edit:
I just rebooted in the bootloader, but when I start the Recovery Mode, the tablet freezes on an "android" icon with a red "error" icon
Thanks
You can either do one of two things:
1. Start over from scratch going back to complete stock. This will erase your internal sd card, so anything there will be gone. Hopefully you have a backup if anything important is there.
LINK: http://forum.xda-developers.com/showthread.php?t=1907796
NOTE: Assuming you unlocked your bootloader already, start reading under the heading Flashing Factory Image, start at Step 3.
2. You can boot into the Bootloader, connect the tablet to your computer, use fastboot to flash a custom recovery, then use adb to push the CM10 zip file to your device, flash it in recovery and reboot.
There's a few steps involved in each, both use fastboot commands, so it's really up to you. I can explain either.
EDIT: The methods I'll describe do not use any sort of toolkit, which is also known as the "manual" way of doing things.
Problem solved!
Ok, I MADE IT!! :victory:
I forced the shutdown pressing PowerButton+Volume UP, then i Rebooted the device pressing PowerButton+Volume DOWN ( Fast Boot).
Then...
First of all I downloaded the Nexus7 Toolkit of XDA Developers,
- I downloaded the flash stock (Google/Nexus) ( Step 9 of the toolkit actions)
- and flashed the device from the Nexus7Toolkit (Step 9 of the toolkit actions again)
Then the device returned in "factory status", including the Bootloader version ( Removing the old Recovery Mode).
Problem Solved! :laugh:
Thank you very much for the instant support.
I was misunderstanding some things about installing the ROMS ( I've tried to Push the factory stock into the tab - Step 13 of the Toolkit) , so I thought I came in trouble, but following step by step the Toolkit commands, I made it.
Thank you so much.
Rox666 said:
Ok, I MADE IT!! :victory:
I forced the shutdown pressing PowerButton+Volume UP, then i Rebooted the device pressing PowerButton+Volume DOWN ( Fast Boot).
Then...
First of all I downloaded the Nexus7 Toolkit of XDA Developers,
- I downloaded the flash stock (Google/Nexus) ( Step 9 of the toolkit actions)
- and flashed the device from the Nexus7Toolkit (Step 9 of the toolkit actions again)
Then the device returned in "factory status", including the Bootloader version ( Removing the old Recovery Mode).
Problem Solved! :laugh:
Thank you very much for the instant support.
I was misunderstanding some things about installing the ROMS ( I've tried to Push the factory stock into the tab - Step 13 of the Toolkit) , so I thought I came in trouble, but following step by step the Toolkit commands, I made it.
Thank you so much.
Click to expand...
Click to collapse
You're welcome, glad I could help!
This is how I unbricked my TF300T that had no rom installed and a wrong bootloader/recovery combination. (4.2 bootloader with TWRP recovery JB version). Hope it helps.:good:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster <----(credits to him) Go to this link ---> http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 because that's the guy that wrote this procedure from above (credits to him) :
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This part was me now -ozkrtech <--- (credits to me)
In addition to that, if you simply can't see your device using the command "adb devices" go check on device manager if you see a device called just "Transformer" with a yellow icon indicating it needs a driver, and manually update driver, select "browse my computer for drivers" and then select let me pick from a list of device drivers on my computer" there you will see a list of like 3 different drivers, one of them says "bootloader" and one of the others says "adb" (i think they self explain) but just in case try with each one of them you can keep on switching drivers until you get your device recognized by the command "adb devices".
You should be asking yourself... whats the right moment to do an "adb devices" command? well my tablet same as -Buster's tablet had the wrong recovery menu flashed (wrong bootloader version) and it just kept booting into the corrupted recovery (in my case TWRP) with the "can't mount anything" and "what's the password" issue. When you get to password screen just hit cancel and try the "adb devices" commando and you'll see it gets recognized with your device serial number.
Once your device gets recognized by "adb devices" command you will proceed to use "adb reboot-bootloader" command and the tablet will reboot into the menu that had 4 options but now have 3 options and its missing the fastboot option (don't panic) in the last bootloader it is auto-fastboot mode when you reach that screen with just 3 options in it now (yeah is the screen with the RCK option) at this point try "fastboot devices" command to see if your device gets recognized same as "adb devices" procedure, it should get recognized with a different serial number (don't know why, maybe that number isn't a serial number), at this time you are SO LUCKY! now you will follow what I posted at the beginning from that other dude ---> (-Buster) or follow his link --- > http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
And you'll have an unbricked tf300t in no time =) (I personally used the stock but newest Asus ROM) 4.2.1 (10.6.1.27.1) and it worked flawlessly.
**NOTE** don't turn off nor reset your device once you have formatted the partitions, no need for that (don't know what happends but it might get really hard bricked) just proceed to flash the stock rom after erasing the partitions.
I'm 100% positive this will work if your device is in same state as ours. (had TWRP for JB) then updated bootloader to version 4.2 and forgot to update twrp to version 4.2 or installed twrp version JB by mistake and lost fastboot and TWRP is asking password.
Hope it helps. Let me know your status and if it worked for you.
So I am in the same boat as I flashed the wrong twrp. My device shows up under adb devices and I can boot into the bootloader using adb reboot-bootloader. However, once there, I can not get the device recognized with fastboot. I have tried messing with the drivers like you suggested but nothing will get it to show up with fastboot. Anybody have advice on where to go from here?
So extra info. The device bootloops into twrp 2.6. The only way I can boot into fastboot mode is with adb reboot-bootloader and I can get into APX. I can also boot directly into my current ROM (Slim beta 3) by selecting android in the bootloader menu. I have tried flashing proper recovery through flashify, which is says was successful, but the wrong twrp never gets overwritten. Rebooting the device will send it back to twrp.
Thanks if anyone can help
Thanks, man! It took a while to find this thread, but this was exactly my problem. The adb driver in windows was the pre-solution to help get back to the fastboot server in the bootloader. Awesome information. Thanks again!
I have tried "adb reboot-bootloader" and then adb devices and fastboot devices and neither will show the tab listed while the tab reaches that screen with just 3 options. I have uninstalled reinstalled drivers, it does show in device manager as Asus Android Composite ADB Interface but when running the command it will not list the tablet. Any suggestions?
Hello!
A few days ago I tried to root my Asus TF300T because before that, I changed the lcd and the touchscreen from FPC-1 to G01 version. So I had to root and update touchscreen's firmware to 02-3011-4820.ekt. I already updated with last firmware from asus.com. First, I installed a TRWP recovery but was useless since the touchscreen doesn't worked. So I tried to rewrite CWM recovery. I reset it and I don't remember exactly if I begun to install or not CWM but when I tried to wipe data (Vol- + Power), the tablet has freezed. After a few minutes I did a hardware reset (pin hole). Since that, the tablet freeze with "Device Unlocked", Asus logo and nVidia. The device was already unlocked. I don't have any backup from it. No fastboot, no adb. Just APX mode. Is it possible to do something with it anymore? I tried BootTools2, extracted bloobs from last version of firmware, tryed to flash them with nvflash and wheelie but vainly. What is the next step? I'm a beginner!
Remember please I cannot go in fastboot recovery menu, only apx. Thank you in advance!
I can not thank you enough!!! my tablet is now working I honestly though it was done for aha THANK YOU!!!
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following the OP's guide I was successfully able to reflash stock firmware and the device runs fine now.
However, upon reflashing said firmware, it became apparent to me (from reading various threads in the development subforum), that I would need to downgrade to an older firmware version to reflash TWRP. So I did that successfully, but now I am having a problem similar, or perhaps identical, to that of Bionicbowtieguy, in that ADB appears to be broken for my tablet. I have tried uninstalling and reinstalling the Asus usb drivers, in addition to reinstalling/updating all of the ADB software. Fastboot still works fine, but as such I'm unable to root using Motochop's rooting kit (I know there are other methods out there), nor am I able to flash a new recovery. I have also tried repeatedly reflashing the older stock in the hopes that ADB would magically start working again to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Kombatant said:
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Click to expand...
Click to collapse
Same here!
Thank you OP for making this a topic even if you didn't come up with it you made it a thread that has saved a few people like myself money and headaches. Literally I just stumbled on this thread 10 minutes after I told my wife is be Tablet shipping Black Friday. Thank you sir.
Thank you.
I did this on a hackintosh running OSX since on Win 8.1 fastboot kept crashing.
March of this year I bricked my tablet during that 1 week period where nobody knew that TWRP was broken + fastboot freezing.
I must have tried everything, Maybe that erase misc was the key factor for success.
I was about to sell this for what I could get or send it to asus, now I can use it again!
How are you guys getting your tablet into fastboot mode? I've tried power on with volume down, the reset hole with volume down, and letting the battery die then recharge, then power on with volume down... Nothing. What am I doing wrong?
Sent from my Galaxy Nexus using Tapatalk
Best thread ever!! You are a life saver !!! thank you!!
leris2 said:
Best thread ever!! You are a life saver !!! thank you!!
Click to expand...
Click to collapse
Indeed. You are a god among men. Thank you so much
This worked! I thought I was out of luck. Thanks a lot.
I accidentally flashed an incomparable version of twrp. It would only boot straight into recovery and I couldn't get into recovery. TWRP kept asking for a password even though I never set one up and it wouldn't mount the internal storage or sd card.
I had to follow the instructions at the bottom to intall the drivers so adb and fastboot to work. After that I followed the instructions at the top.
The only thing different I did was skip the "fastboot erase boot" step. I was afraid that would really brick my device if I screwed up (Does this really erase the bootaloader leaving the device with no bootloader?).
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Fastboot
Bolandk said:
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Click to expand...
Click to collapse
They do not sit at all they will go right to it. You must not have the right combination yet. Keep trying.
Took me awhile to get the link.
norm883
FIXED!
BY GOD, I have no words for how incredible grateful I am right now! You not only saved my TF300T's life but also a lot of money for me and gave me another lesson of Android insight.
Thanks so much for this!
Let me know if I can return the favor somehow!
Regards,
(a very happy) philleicht
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
same problem reboot back to twrp
well i may be stupid because i can't understand why i have tried a couple of commands and i still get the same problem reset volume down still goes back to twrp and ask for a password can someone please explain this in alittle more detail and what commands i also get the waiting for device in my commands is there another way to push these files into this device tf201 please help is there a way to do something in the twrp recovery like terminal command
I was a fool for flashing wrong recovery!
DrPhant0m said:
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
Click to expand...
Click to collapse
I have exactly this! I hope someone knows the answer for this issue. Else the tablet will learn how to fly!
I tried to push the reset button as described earlier but nothing changes. Not able to go into recovery Just stuck at ASUS in the middle NVidia in the bottomright corner en upperleft corner 'this device is unlocked'
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!