Database Info

[Q] Asus Transformer & CWM

I rooted my Asus Transformer TF101-B1, but I can't get into Recovery. I know rooting was successful because I get the # prompt in ADB shell and can run root-only apps like Titanium Backup. I've tried every method for getting into CWM/Recovery that I've been able to turn up on XDA and Google, including:
* Running "adb reboot recovery"
* Holding Power + Vol down during boot, then pressing Vol up within 5 seconds of the device powering on.
* Selecting "reboot into recovery" from the ROM Manager app.
Nothing works, it just does a normal boot every time. I even did a factory reset to try and get into the stock recovery (a suggestion I found on another thread here), but that didn't work, either (and my device still appears to be rooted).
I'm hoping someone out there can provide more insight/advice, as I'm pretty well out of options.
Device info:
Android version: 3.0.1
Kernel: 2.6.36.3-00003-g8038d35, android 'at' Mercury #1
Build: HRI66.US_epad-8.2.3.9-20110423
(all stock)

ok, I managed to get into CWM and now my question is, "where can I get the latest version of CWM?" I've seen several posts that just say, "head over to the CWM thread and download the newest version", but they don't give links and I didn't find much searching the forums.
Sorry for being such a n00b...

Im also having a similar problem though my transformer wont do anything after i choose to boot into recovery.

kfarstrider said:
ok, I managed to get into CWM and now my question is, "where can I get the latest version of CWM?" I've seen several posts that just say, "head over to the CWM thread and download the newest version", but they don't give links and I didn't find much searching the forums.
Sorry for being such a n00b...
Click to expand...
Click to collapse
How did you get into recovery? No matter what I do it just boots normally. adb doesn't see the tablet anymore either..and I already rooted it so adb *was* working.

ferparedes said:
How did you get into recovery? No matter what I do it just boots normally. adb doesn't see the tablet anymore either..and I already rooted it so adb *was* working.
Click to expand...
Click to collapse
For real. I rooted succesfully. Currently trying to flash a rom, but I don't know how to get into CWM.

Same issue here. Can someone write how they got into CWM?

I used RazorClaw to root my Transformer, yet when I try to reboot into recovery, it gives me the Android with the Caution symbol in the middle. It looks like I cannot get into ClockWorkMod, either.
On www (dot) clockworkmod (dot) com, it does not list the Asus Transformer as being supported with a version of CWM. Rom Manager shows the same thing, so I am forced to select the Xoom or Nook Color.
What are the steps to get from Root to CWM Recovery?
Thanks!

Ok so I'm at the same part of the problem everyone else is in this thread.
I've done the following steps:
Installed Java SDK
Installed Andriod SDK
Rooted via Razorclaw
device is recognized when i do "adb devices" in command shell
install ROM Manager by Clockwork Mod from App store
tried to boot into recovery while connected to PC using Vol Down + Power Button and I get Android Man with Caution with nothing going further. if I unplug the cable from the PC I can't seem to get into Boot Recovery. I've asked for help in asus-transformer on Freenode.net with no help what so ever. From what I can tell my model is a B50
Any help would be appreciated from what I can peice together on the forums the install order would be
Root
CWM on App Market
CWM Recovery by roach
Nandriod
install ROM
Correct me if I'm wrong.
---------- Post added at 08:18 AM ---------- Previous post was at 07:49 AM ----------
Edit: Problem solved, I read somewhere that you needed to enable USB Debugging on the tablet which is correct. But you should not do it until the correct time I enabled it from the start which is wrong

jlscarpa said:
I used RazorClaw to root my Transformer, yet when I try to reboot into recovery, it gives me the Android with the Caution symbol in the middle. It looks like I cannot get into ClockWorkMod, either.
On www (dot) clockworkmod (dot) com, it does not list the Asus Transformer as being supported with a version of CWM. Rom Manager shows the same thing, so I am forced to select the Xoom or Nook Color.
What are the steps to get from Root to CWM Recovery?
Thanks!
Click to expand...
Click to collapse
Exactly what I get!

No Such Luck
[/COLOR]Edit: Problem solved, I read somewhere that you needed to enable USB Debugging on the tablet which is correct. But you should not do it until the correct time I enabled it from the start which is wrong[/QUOTE]
I don't get it. I've been having the same problem as you. So I turned off usb debugging and still had no success getting into recovery in spite of a successful root. Advice anyone?

TommyGunn
If anyone ever received a solution, I'd love to hear it, I'm having the same problem...

Have the same Problem need help.

[Q] Stuck on every ROM

Hi !
I´ve got a serious problem with my device (TF101).:crying:
When I had default ROM by Asus (4.0.3), system sometimes rebooting about twice down per day. But system always booted and worked "fine".
After time a made root (one click root), next I made install recovery-clockwork-touch-5.8.1.8-tf101-repack. Then I made full wipe and flashed ROM. I tried Revolver, Revolution CM10 .. Every rom install is good, but after few hours system frozen.
When I made restart stay stuck on boot logo on every times, helps only full wipe. but after is happend over and over..
Does anybody know what to do?
Thank you so much for your time !
Sorry about my english
Tom

Maybe try an other kernel (kat kernel work fine for me...)
Envoyé depuis mon Galaxy Nexus avec Tapatalk

If you want to know "why" it happens, try "adb logcat" while your device is connected and booting forever. It'll show what's going on.
TWRP is the recommended recovery nowadays it seems, you can install it from Goo Manager (link in my sig).

Thank you guys
[ADB logcat] How can I do that? I must install logcat apk into device, turn on debug mod and next ?
Thank you for your answer.

galvanizer said:
Thank you guys
[ADB logcat] How can I do that? I must install logcat apk into device, turn on debug mod and next ?
Thank you for your answer.
Click to expand...
Click to collapse
You need to connect your tablet via USB to your computer and have USB debugging enabled in Settings - Dev Options.
Install the universal naked drivers for the TF101 to get the ADB device recognized.
Then get the adb.exe file from the Android SDK.
In a command prompt on your PC run the command "adb logcat" from the folder with the adb.exe file in it.

galvanizer said:
After time a made root (one click root), next I made install recovery-clockwork-touch-5.8.1.8-tf101-repack. Then I made full wipe and flashed ROM. I tried Revolver ICS, Revolution ICS CM10 JellyBean .. Every rom install is good, but after few hours system frozen.
When I made restart stay stuck on boot logo on every times, helps only full wipe. but after is happend over and over..
Tom
Click to expand...
Click to collapse
Hi Tom,
Looking at your post, I am curious how you went from CM10 back to ICS. Did you restore a Nandroid or just simply flash an ICS ROM straight away? The thing is, you can't go from JellyBean back to ICS as the partition layouts are different.
Here is my thinking. Use Easyflasher from the Development section and flash back to stock ICS. You can find the stock firmwares here. You can even flash a custom recovery through EasyFlasher as well.
I think that you need a "Truely" clean restart as I am betting something got cross flashed somewhere.

Okey, I´ll flash stock ROM
but one simply question > i downloaded naked driver > connect with PC (debug mod is on) > in device manager uninstall every befere install drivers > and I update new drivers to ASUS android device and asus MTP device, right?
Must I see new storage disk in My compter(Transformer) or not ? Because I cant see nothing.
Thanks all of you !

No. You download the Naked Drivers and put them somewhere. Then boot your Tablet into APX mode (Power + Volume Up at same time). In APX mode your screen will not turn on nor will it be "seen" as a storage/MTP device. Plug into PC and it should download the drivers itself (if Win7 machine). If not then go into Device Manager and find the APX with the yellow ! next to it. Hit Install Drivers from location and point it to the Naked Drivers you downloaded. From there you should be good to go in EasyFlasher.
Take care though, EasyFlasher will wipe your internal SD.

Same with the ADB driver. It will not be the MTP device, it will be another device in the device tree.

Damn, really in time Thanks:good:
Okey, I switched to APX mode, install manualy naked drivers successfully. After that I start easyFlasher (downloaded custom rom into asusupdate folder).
Next I flashed STOCK .. program progress bar is in 10% and showing "Extract files, please wait" for 10 minutes.. Is normally?
I dont think so .. what now?
Thanks!

galvanizer said:
Damn, really in time Thanks:good:
Okey, I switched to APX mode, install manualy naked drivers successfully. After that I start easyFlasher (downloaded custom rom into asusupdate folder).
Next I flashed STOCK .. program progress bar is in 10% and showing "Extract files, please wait" for 10 minutes.. Is normally?
I dont think so .. what now?
Thanks!
Click to expand...
Click to collapse
It is normal. Took me about 15 mins for it to fully run it's actions.
Not sure about putting a custom ROM in the asusupdate folder though as I think it has to be stock to work correctly. Not sure if you use SBK1 or SBK2. It kind of depends on your device. The EasyFlasher OP tells what the difference is.

Woody said:
It is normal. Took me about 15 mins for it to fully run it's actions.
Not sure about putting a custom ROM in the asusupdate folder though as I think it has to be stock to work correctly. Not sure if you use SBK1 or SBK2. It kind of depends on your device. The EasyFlasher OP tells what the difference is.
Click to expand...
Click to collapse
Good, im waiting (btw still 10% progress) .. I use SBK2 (on my box of transformer is serial number B80KA ******) I decide is SBK2, right?
For now, I thank you so much !

I do this operation on my notebook (win7) behind me. A i dont see alert with commander rewrite all I press ALL. Next alert was about is in my device in APX mode > OK > finally shows some progress!
Edit:
Yes !! It works ! I have stock rom now !
So main reason why I flash another ROM was than original rom by asus does about 2 restart per day I want to try another rom but, how can i do that? I dont want be in exactly case like now.
Thanks!

Welcome back my friend.
Ok, all you have to do in EasyFlasher is see the box in the upper left corner? It will say recovery. Click the dropdown to pick the recovery that you want (I use TWRP). Hit it and Start. Once it is done, you can reboot just to be safe. Once that pulls up, shut the tablet down. Then use the finger combo to reboot into recovery (Power + Volume Down, see writing in upper left and then hit Volume Up and release Power). It will boot into which ever recovery you chose to flash in EasyFlasher.
The TWPR in Easy is outdated (but still works). Once I go where I needed to go, I installed Goomanager from the market and updated my recovery to most current version.
Good luck and now you know how to get out of a real bad situation. Happy Flashing.

Thanks,
but bad situation is back now, I do what you writed before (your post was sending) I install Rogue and i want start device its again stuck on boot logo :-/ So i switched to APX mode and flash TWRP and wipe all..
Why stuck on boot logo again ?

If you're trying to install 4.2 you need a compatible recovery. You can install the latest TWRP from GooManager (TWRP link in my sig), then 4.2 roms should work without problems.
Edit: I think you need at least TWRP 2.3.2.x

Lethe6 said:
If you're trying to install 4.2 you need a compatible recovery. You can install TWRP for GooManager (TWRP link in my sig), then 4.2 roms should work without problems.
Click to expand...
Click to collapse
Yes, but i have stock ROM by ASUS now again stuck on boot logo animation

Oh sorry I thought you flashed another rom. You can install logcat live on your device or use "adb logcat" to see what's going on.
Which boot logo? The first one with Asus "innovation" stuff or the one after that with the small text gone?
---------- Post added at 04:49 PM ---------- Previous post was at 04:47 PM ----------
Also did you reinstall any apps at all before you flashed your recovery? Maybe it's an app causing it.

Lethe6 said:
Oh sorry I thought you flashed another rom. You can install logcat live on your device or use "adb logcat" to see what's going on.
Which boot logo? The first one with Asus "innovation" stuff or the one after that with the small text gone?
---------- Post added at 04:49 PM ---------- Previous post was at 04:47 PM ----------
Also did you reinstall any apps at all before you flashed your recovery? Maybe it's an app causing it.
Click to expand...
Click to collapse
Now my transformer runs thanks god 6 minutes up time, i have clean stock rom without app.
But problem is that after while tablet freeze and restarts and stuck on boot logo ASUS animation with running circle over and over.

frederuco said:
You need to connect your tablet via USB to your computer and have USB debugging enabled in Settings - Dev Options.
Install the universal naked drivers for the TF101 to get the ADB device recognized.
Then get the adb.exe file from the Android SDK.
In a command prompt on your PC run the command "adb logcat" from the folder with the adb.exe file in it.
Click to expand...
Click to collapse
Sorry, but where I get adb.exe file? On storage in android?
edit: Stupid question, I tried this http://forum.xda-developers.com/showthread.php?t=1071584

[Q] [HELP NEEDED] Asus TF101 Stuck on splash screen ADB doesn't work!

Right, I searched on numerous pages on these wonderful forums, but couldn't quite find what I was looking for. So I'll try my luck here. I'll describe my problem.
My TF101 was rooted using the CWM recovery. After doing more research I found out I shouldn't be doing this. But, unfortunately the damage has already been done. After several succesful ROM installations I wasn't quite happy with, I tried one last CM10 install. That's when it all went to ****. My TF101 has been stuck on the Eee Pad splash screen for nearly 2 months now.
Normally when going into the recovery mode I can simply select install from SD card and install a new rom. Now it can't seem to mount and displays E:Can't mount \SD card or whatever.
Further on, I tried using the ADB tools to manually restore system files. Without luck. After which I tried to install the naked USB drivers using http://forum.xda-developers.com/showthread.php?t=1426502. Without luck as well. I simply ran out of ideas.
The thing is, in Device manager I do see a device called Android. But, for some reason I can't seem to install any drivers for it. I guesse this would be the first step towards getting it back to work? Or perhaps I should just get it fixed at the computer store?
Any sugestions would be more than welcome!

Easy Flasher will get you back to stock as long as you can access APX. You will lose all data however.

1st mistake read forum before you do something, coz you would have learnt abt CWM issues, anyway thatsvan old story
You got Two options, find an flash able twrp.zip and flash it using current recovery if its still working otherwise as the other guy says easyflasher
To use easy flash you need
Easy flash software from forum
Universal naked driver installed
Asus firmware and PATIENCE
Follow the steps given in the forum and you should get back a tablet running stock rom, then if you want then use easy flash to root your device again but this time use TWRP recovery.....
Sent from my Transformer TF101 using xda app-developers app

Right, so far I've done everything I could find. I have installed the naked ADB files and thus was able to make a connection through USB. However, I wasn't able to push any files onto the tablet through ADB commands.
I entered the (what I assumed to be) APX mode and tried to use EasyFlasher. It seemed to have worked, because a DOS screen asked me whether or not I wanted to overwrite several files. After ending the procedure I rebooted my tablet. And guesse what: CWM is still there and the tab is still stuck on the Splash screen. Also the internal SD still can't be mounted.
What am I doing wrong. I'm slowly but surely going mad here....

hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...

Lethe6 said:
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Click to expand...
Click to collapse
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....

AlbertGJBos said:
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
Click to expand...
Click to collapse
I'll just sum up what I've been doing so far, because it still ain't working for me....
1) Put the TF101 in APX mode using POWER + VOLUME UP
2) Started up EasyFlasher 0.8.3 and selected "Flash Asus stock zip / Unbrick"
3) When prompted "file ..\temp\META-INF\MANIFEST.MF" already exists I selected "A(u)to rename all"
4) And then starts doing it's thing
5) Stuck at creating and formatting 15 partitions with several three letter codes.
I've ran the program three times now, but without luck. Any sugestions?~
[EDIT]Alright, managed to get it to work! Ended the tasks in through task manager about 4 times, but the 5th time was a charm. Exactly work as said. All thanks to EasyFlasher![/EDIT]

[Q] only booting into recovery after updates/more please help

Hi all I've been an idiot and am hoping I haven't done any permanent damage to my unlocked/rooted tf300 so before I continued doing anymore I wanted to make a post here asking for any help possible.
I hadn't updated to the 4.2.1 build yet and finally decided to bite the bullet an hour or two ago since I wanted to try out the newest version of cromi. I was using the patched 2.4 twrp and initially updated to the 10.6.1.8 update using fastboot, then decided I might as well do the 10.6.1.15.3 using the fastboot again and finally updated to the 2.5 twrp using fastboot. As the jb updates were happening I would get the message that the tablet wasn't rooted and to install SuperSU, and because I'm a dumb creature of habit both times I just instinctively swiped to install, only realizing what I had done after the fact.
After all of this I was still able to at least turn on my tablet and get to the home screen, but unable to do a factory reset in recovery (the log would say "unable to" on every task, but the final message would still say successful?) or have any options to install a rom within it. I had also noticed that I wasn't rooted anymore. I used motochopper and was rooted again for the time being and used a couple apps that required root just to make sure that was the case. At this point I rebooted the tablet and holding down the power button/volume down, I think this is the point where my tablet would just boot straight into recovery, unable to boot into anything except recovery since even if I hold down the power button/volume down.
I've tried to do a factory reset and get the same response as earlier and I get a "failed" message when I try to do a data format. I know there will be at least a couple glaring red flags within this message to anybody who knows much more than I do, but I'm hoping this isn't the end of my tablet and would greatly appreciate any assistance provided. If you need any extra information please let me know I'll do the best I can with providing whatever would be useful, thank you in advance for your time and help.

did you install the 4.2 recovery version?

if you have TF300T (not TG or TL), you need to flash openrecovery-twrp-2.5.0.0-tf300t-4.2.blob which you can download from the TWRP official website.
On 10.6.1.15.3, to enter fastboot mode, you need to reboot your tablet and hold volume down button until you see 3 icons (RCK, Android logo, and Wipe). At this point, release the volume down, but do not select any option and do not press volume up. Without doing anything, you are now in fastboot mode.
Do the usual thing you did... connect your tablet to PC via your USB cable, run cmd.exe and change your path to where you have fastboot and the "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" file. Type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
wait until you see a blue progress bar on your tablet. When that completes without error, type:
fastboot reboot
Enter TWRP recovery, Wipe dalvik and cache, try flashing the official ASUS 10.6.1.15.3 stock ROM again. Do not swipe to install SuperSU to root at this point. Just tap "Do not install." If installation goes well, reboot, and re-flash "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob", as installing the official stock ROM may have overwritten your TWRP recovery.
To root, use motochopper like you did. Or alternatively, flash a custom 10.6.1.15.3 stock-compatible kernel and let TWRP install SuperSU (Swipe to install) when prompted before you reboot system. You will get a SuperSU installer app on your launcher. Run that app and choose "Play" or "install from recovery" option. I can confirm that both method works without apparent issues. Choosing Play would be easier and faster than having to go to recovery to flash SuperSU binaries.
I hope this works for you.

matt95 said:
did you install the 4.2 recovery version?
Click to expand...
Click to collapse
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.

peerpressure said:
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.
Click to expand...
Click to collapse
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time

matt95 said:
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time
Click to expand...
Click to collapse
That's too bad I'm leaving for a month and was hoping to be able to use it while I was gone, oh well nobody to blame but myself looks like I'll be without a tablet for a while. Thank you guys for your time and help I really appreciate it, hopefully the fix will come at some point soon in the near future.

I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?

peerpressure said:
I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?
Click to expand...
Click to collapse
probably this will be fixed, i don't know why but we are working onto it... i won't sell it just for few dollars.... it's not worth it

One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.

c0ded said:
One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.
Click to expand...
Click to collapse
Thank you so much for the response, would there be a way to go about getting the 4.2 version onto my tablet though if it only boots into recovery, even when you hold down the power button/volume down? When I plug the tablet into my computer it isn't able to be recognized (I'm assuming just because it only gets to the recovery screen).

Try running "fastboot devices" on your computer while in the bootloader. Does it show anything?
Correct me if I'm wrong, but I remember reading somewhere the when in the bootloader, fastboot automatically launches on 4.2.
---------- Post added at 08:48 PM ---------- Previous post was at 08:31 PM ----------
It IS possible to flash recovery while you're in recovery. Here's how (from tobdaryl; twrp can be gotten from here: techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob):
adb push openrecovery-twrp-2.4.4.0-tf300t-4.2.blob /sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
adb shell
su
dd if=/sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob of=/dev/block/mmcblk0p4
adb reboot
An then to flash stock (once again, from tobdaryl; roms can be gotten from here: forum.xda-developers.com/showthread.php?t=1697227):
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
adb reboot

Oh, well it hasn't been letting me go into the bootloader on the tablet, just boots into recovery regardless, but for what it's worth the options/commands still show up as shown in the attachment. I don't know if that's something they do anyways though.

What about "adb devices"?

c0ded said:
What about "adb devices"?
Click to expand...
Click to collapse
The list of devices attached doesn't show any it looks like it can't find it

Have you tried flashing 4.2 within TWRP?

How would I be able to go about doing that? (sorry for the inexperience and delays in response, have to wait five minutes between posts)

Download the 4.2 rom (http://www.androidfilehost.com/?fid=22926241640219416), extract it, and put the extracted zip file on to a MicroSD card. Boot into TWRP and install it from the external MicroSD (I don't know how to go about that since I don't have TWRP).
Also, you shouldn't be waiting 5 minutes between each response. You are over 10 posts.
---------- Post added at 09:12 PM ---------- Previous post was at 09:06 PM ----------
Oops. I just read the statement carefully and realized that you have to be verified by a moderator, not have over 10 posts.

I tried it out but sadly it looks like the external microsd is unable to mount so I can't pull anything off of it
edit: It gives me the option to mount a system when the ext. microsd is in but not when it is out, I don't know if that is of any help? Every other option isn't possible though.

What type of MicroSD card are you using?

A sandisk 32gb class 4 microsdhc, it's the same one I had been using with the tablet previously before this all happened

[Q] Stuck in CWM v5.8.2.0 with no ROM. ADB/APX working

I inherited this tablet, so my familiarity is growing. I have an Android phone, and have installed ROMs before, so when I rebooted into CWM and wiped the device, I expected to be able to copy over my various .zips to flash without issue.
I was wrong.
I can boot into CWM (it had that on it when I got it). I can boot it into ADB mode (ADB sees the device as well) or APX mode (Windows) now that I have all those drivers. However, I can't seem to mount the device on my desktop in order to copy over a kernel/ROM and proceed.
I see there are many similar threads, but I have found no steps that have led me to the right direction so far.
I apologize for the regulars here who are tired of seeing these types of questions.
At the moment I am trying to find if it's SBK1 or 2 so I can use EasyFlasher, as I've seen others suggest.
Edit 1: Well EasyFlasher doesn't seem to have worked (with either option). Even after flashing it reboots me into CWM 5.8.2.0.
Edit 2: Aha! http://forum.xda-developers.com/showthread.php?t=1601942 - That may be helpful.
Does the TF101 normally allow you to access the SDCard contents from recovery? If not, I'm not sure how I'm going to push any .zip over to the device to flash...

So I tried pushing Rogue XM Recovery 1.5 using ADB, and that worked. But if I flash, reboot (PWR+DWN), then press VOL-UP for recovery it takes me right back to CWM 5.8.2.0.
This is frustrating.

Try NVFlash if your serial is B6O or earlier
http://www.xdafileserver.nl/index.php?dir=Asus%2FAsus+Transformer+%28TF101%29%2FSTOCK+ROMS%2FICS+.27
When you manage to get to the stage of flashing a new recovery, flash TWRP, not CWM

*Detection* said:
Try NVFlash if your serial is B6O or earlier
http://www.xdafileserver.nl/index.php?dir=Asus%2FAsus+Transformer+%28TF101%29%2FSTOCK+ROMS%2FICS+.27
When you manage to get to the stage of flashing a new recovery, flash TWRP, not CWM
Click to expand...
Click to collapse
My S/N is BC0, which looks to be SBK2 / can't use NVFlash. Ah well. Thanks for the response.

Either Peri or Easyflasher are going to be your best bet, I dont see why Easyflasher wouldn't work unless you weren't in the correct mode, not on my pc right now but I'd have another go, make sure USB Debugging is enabled on the tablet
Sent from my Windows Phone using Board Express
EDIT - Make sure you're running everything as Admin on the PC too (Right click > run as admin)

If you flashed a new recovery via ADB, be sure to do a normal reboot afterward to finish the flash. If you do an "adb reboot recovery" or use vol down and power immediately, it will not finish flashing the new recovery.

Have you tried cold reboot ?
Envoyé depuis mon XT925
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
Check this message. About my issues with this recovery. http://forum.xda-developers.com/showthread.php?p=41778131
Envoyé depuis mon XT925

I am embarrassed to say that my problems were all due to it being a TF201, Transformer Prime, not a TF101. It's amazing I did not brick the thing. Like I said, I inherited it, so I had no documentation, box, anything to go off of, thus my confusion.
That said, both processes helped me learn a lot, so in that respect, I thank you.

Lockedown said:
I am embarrassed to say that my problems were all due to it being a TF201, Transformer Prime, not a TF101. It's amazing I did not brick the thing. Like I said, I inherited it, so I had no documentation, box, anything to go off of, thus my confusion.
That said, both processes helped me learn a lot, so in that respect, I thank you.
Click to expand...
Click to collapse
Can't help you don't have tf200
Envoyé depuis ma TF101G-B80 with Revolution HD 4.0 (3.6g release) by Mike _1986

stephane.papin said:
Can't help you don't have tf200
Envoyé depuis ma TF101G-B80 with Revolution HD 4.0 (3.6g release) by Mike _1986
Click to expand...
Click to collapse
Sorry, to be clear I figured out my problems with my TF201 in the other forum. The thread can die now

wow, very lucky you didn't brick, good news you got it sorted
TF101 - Brown plastic back
TF201 - Silver aluminium back