yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] mb2k:
Ok, I've searched thru this and other threads but couldn't find a good answer. I am using touch recovery and it's working fine, however my problem is that I can't seem to find the backup files on my internal sdcard. There are about 5 recoveries available and I would really like to clear up some space by removing ones I know I don't need. I have a clockworkmod folder in my sdcard directory but ES explorer reports no files in the folder. Thinking the backups were somehow located in another folder, I renamed the clockworkmod folder to clockworkmod1 and sure enough, CWM says no such directory when trying to do a restore. This is really bugging me. It's as though the files are only visible to the CWM restore app.

Any help on this would be appreciated.

Tony
[Eee Pad Transformer Android Development] tsukasa1105:
Need some help

I have tried flashing different recoveries a bunch of different ways and every time I get the same result... an android icon with a red exclamation point in recovery. The tablet *boots* just fine, and has root, and is bootloader unlocked, but for some reason flashing the recovery is giving me issues.

Anyone have any thoughts on this?
[Eee Pad Transformer Android Development] handsomeboy1702:
I'm trying to flash my friend's b80 transformer. when i press vol down + power and then vol up, it loads for a while and gets stuck at the exclamation mark. how do I go from there?

ps: just find out I have the same issue as the guy above. so sorry for this duplicate post :p
[Eee Pad Transformer Android Development] baseballfanz:
Sounds like you're still on stock recovery.

you can use RecoveryInstaller to install an older version of cwm first then update to this.

Look in the app section for RI apk
[Eee Pad Transformer Android Development] handsomeboy1702:
Thanks. Will try. Didn't have so much trouble with my b60 one, lol
[Eee Pad Transformer Android Development] tsukasa1105:
flashing RI apk didn't solve the problem. Any other ideas?
[Eee Pad Transformer Android Development] sidneyk:
Go into ES File Explorer settings and make sure that you've enabled 'Show hidden files'. Roach's older 3.2.0.1 recovery would save backups on the external microSD in /clockworkmod/backups/ or something close. I'm using the Touch Recovery also and am doing a nandroid backup right now and will let you know what I find out.

[EDIT] OK. I just finished a backup from within this Touch recovery. The default location would seem to be /sdcard/clockworkmod/backup/2012-05-05.05.31.19/ in my case. With ES File Explorer, I see within that directory the following files:

cache.ext4.tar

data.ext4.tar

system.ext4.tar

nandroid.md5

I had nothing in there prior to just doing this backup. Hope that helps.
[Eee Pad Transformer Android Development] baseballfanz:
After you installed the RecoveryInstaller apk, did you open it and flash cwm recovery?
[Eee Pad Transformer Android Development] tsukasa1105:
yes, it flashes successfully, reboots, and then i go back into recovery and i still get the android with the warning sign on top of him
[Eee Pad Transformer Android Development] baseballfanz:
That's weird. Maybe try Wolf's method of adb the recovery blob.
[Eee Pad Transformer Android Development] mb2k:
Thanks for the suggestion, but no luck. I verified that ES Exp was set to show all files. Also checked properties for the clockworkmod folder and it showed as empty, yet I know it's being used because when I renamed the folder, CWM was unable to find any backups. This is very confusing.

Tony
[Eee Pad Transformer Android Development] Djay1809:
running Code name Android, and when I flash Clockwork Recovery, and it says successfully installed, but when I try to boot into recovery it freezes on the splash screen. No matter how I reboot it will not work.
[Eee Pad Transformer Android Development] sarreq:
OK, i'm completely stuck here, I'm stuck in recovery (koush 5.5.0.4), when I go to reboot back to the system it reboots back to recovery instead, I tried this fix, but it can't find the tablet as a device. I can't even use USB from recovery to try another recovery image, because USB is missing from this build for some stupid reason.

Disregard, I found out what happens when you press volume-down from the recovery boot option

update: awshum ;D

so, just figuring out how to get that boot menu got me back up, then your adb command fixed the rest. blazoinga!
[Eee Pad Transformer Android Development] :
will the

-no

-no

-no

-yes

-no

be removed :) because cvm is annoying me with that :(
[Eee Pad Transformer Android Development] GameEs:
Hi, I need help. I installed a new recovery - didn't realise it takes updates from internal sd card. My update is on external SD. I've already formated system partition. How do I push it into the internal SD card?

edit. I've connected Transformer to PC.. APX. But I don't know how to adb push that file inside. Can somebody help please?

edit2. I'm able to push file to transformer but I don't see the rom in the recovery.. I did "adb push Megatron.zip /sdcard" but when looking back into recovery, nothing new.
[Eee Pad Transformer Android Development] baseballfanz:
Use ADB in recovery to push files to internal sd
[Eee Pad Transformer Android Development] GameEs:
thanks, I got to this but as I edited my post just a moment ago

"I'm able to push file to transformer but I don't see the rom in the recovery.. I did "adb push Megatron.zip /sdcard" but when looking back into recovery, nothing new."

oh wow, finally.. If I put it in another folder and not into root itself, I see rom. Thank you anyways.
[Eee Pad Transformer Android Development] philseven:
You know koush and his rom manager well lately it leaves something to be desired it's just like the American car builder's you just can't put anything out there and expect people to buy it eventually people will wise up I am sorry i know this not the place, I still have my n1.Rommanager was the first app I purchased. Koush has done so much for the development rooting and rom management it is ridiculous cyanogenmod and koush went hand and hand. Maybe Koush should start steering the ship again. By the way I am still waiting for a refund for your touch recovery that didn't work for the tf101 lol lol. Just my opinion no disrespect intended.
[Eee Pad Transformer Android Development] josteink:
Put an empty file called one_confirm in /sdcard/clockworkmod and it goes away.
[Eee Pad Transformer Android Development] dominicanman912:
Is it possible now to flash from internal AND external memory?
[Eee Pad Transformer Android Development] Thing O Doom:
Only with the RougeXM version as of right now, not with touch sadly, this is why I havn't upgraded yet.
[Eee Pad Transformer Android Development] blackfoot:
@josteink, this didn't work for me, I'm assuming that this file somehow removes the extra irritating 'no's'.

I have a TF101 running this 5.8.1.8 and originally had a clockworkmod folder on both sd card and internal storage, thinking this might be the issue I removed the (external) sd folder, but it still doesn't work.

Any suggestions or tips would be appreciated.

Saw that you received a thanks, so it obviously worked for someone.

TIA
[Eee Pad Transformer Android Development] lukacs.attila:
put a period (.) before one_confirm. So if you're doing this under windows, one_confirm is the extension.

.one_confirm
[Eee Pad Transformer Android Development] blackfoot:
Sadly, this didn't work either, all that happened was the file was hidden. :confused:

Thanks anyway.

Edit: might this be a permissions problem?
[Eee Pad Transformer Android Development] jrohwer:
Try copying the su binary from /system/bin/su to /system/xbin/su if you have not already done so. Some apps need the binary in xbin in order to detect root.
[Eee Pad Transformer Android Development] RaymanFX:
Hmmm, how screwed am I ?

Your command doesn't seem to work here.

I actually have full adb access and know how to push other roms and stuff to the internal storage, so this ain't the problem.

chris@chris-Parallels-Virtual-Platform:~/working_dir$ adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
dd: writing '/dev/block/mmcblk0p3': No space left on device
4097+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.372434 seconds, 5.4MB/s

Doesn't quite do the trick ...

Nothing happens. Even if I reboot, that annoying "ClockworkMod Recovery v5.8.1.8 is awaiting me.
[Eee Pad Transformer Android Development] sidneyk:
If you can get into APX mode and connect to PC, assuming you have the USB and ADB drivers installed and can use nvflash, then you could nvflash Rogue's Recovery and then flash this touch recovery from this thread (the latest posted file with the hack to fix the reboot to recovery loop) within Rogue Recovery, then it should work. I flashed this same file from within Rogue's Recovery and Touch Recovery is working just fine on my TF101. I just had to get used to flashing everything from internal sdcard instead of external microSD card. I've flashed several kernels and ROMs without issue.
[Eee Pad Transformer Android Development] josteink:
Not everyone is a lucky SBKv1 TF101 owner. In fact SBKv1 models probably havent been in sale the last 8 months.
[Eee Pad Transformer Android Development] tronyx:
i installed touch cwm 5.8.1.8. how i make install zip from external sd card? possible this?
[Eee Pad Transformer Android Development] jjdavola:
I'm patiently waiting for this too. :)

FYI Rogue XM Touch seems to do this, but the spacing between items is too small and it appears to be very touch sensitive IMO.
[Eee Pad Transformer Android Development] sidneyk:
But, it does have navigation buttons (which are also touch) at the bottom to alleviate the spacing issue in Rogue XM Touch. Keeps a nice look with a method to navigate AND uses external microSD with the option to also use internal sdcard, it's almost everything we were asking for.

Roach's Touch version is what I've been using and it's nice once you get used to using the internal sdcard and making sure you don't inadvertently wipe the ROM you were intending to flash, but having both options is the best IMO.
[Eee Pad Transformer Android Development] jjdavola:
I agree. The navigation buttons are a nice touch considering the spacing, but what's the point of having touch on the whole screen then? Don't get me wrong I greatly appreciate all the wonderful developers here, but I'd still like the best of both worlds. ;)

BTW I just have MyBackup Pro backup my CWM folder on my internal SD card every couple days to hopefully mitigate the effect of an inadvertent wipe.
[Eee Pad Transformer Android Development] sidneyk:
I discovered with Roach's Touch that it seems that everything that is under /sdcard is also repeated under /data/media and will survive, IIRC, even a factory reset, since it is setup to not touch /data/media. So, I just kept everything usually under /sdcard/Download but could have it in some other folder under /sdcard, too. You would have to manually format things with some method that didn't care about preserving /data/media in order to start out more totally clean. So, as it turns out, it was safer than at first thought. When I first tried Roach's newer versions, I didn't realize that it no longer recognized the external microSD, so that was where I got caught because I just blindly wiped my old ROM while my new ROM was on the inaccessible external card, leaving me having to connect to PC and nvflash a ROM, which I was fortunate enough to have the ability to do.
[Eee Pad Transformer Android Development] jjdavola:
I have no idea why I said MyBackup Pro. :confused: I meant Dropbox Sync. :o

Really? I'm going to check that out. If that is the case, I guess my Dropbox idea is only triplicating my backup (which isn't awful).

Thanks for the info!
[Eee Pad Transformer Android Development] sidneyk:
No problem. And, yes, being over-diligent with backups is never a bad thing, so long as you have the space somewhere. I actually figured the above out because I was actively trying to get back to a clean state to fix a problem with Talk which kept Play Store from working properly and couldn't figure out why some stuff kept coming back when I thought I hadn't restored them yet, including the Talk problem.
[Eee Pad Transformer Android Development] solitude65:
What if my computers don't see the tf101 through the drivers and APX is out because it is a newer model? Anyway to force recovery to see the external microSD card or force an ADB session? Any other ideas?
[Eee Pad Transformer Android Development] sidneyk:
I didn't know the newer models were unable to enter APX mode. I have an older B6O series. But, if you're stuck in Recovery for whatever reason, then as far as I know, you're going to have to be able to get into APX mode or equivalent to either adb push through a cmd terminal or linux terminal or nvflash from Windows and sounds like nvflash may not be for you. There is a guide somewhere in development about getting adb working. That is paramount to moving forward.

[EDIT] Here is the link to the adb setup guide:

http://xdaforums.com/showthread.php?t=1071584
[Eee Pad Transformer Android Development] solitude65:
thanks. I have tried the steps for windows to no avail. I will be trying Linux tonight.
[Eee Pad Transformer Android Development] kwinsett:
Success!

Bingo!!!! Worked like a champ! :p
[Eee Pad Transformer Android Development] sidneyk:
You might give this a look also:

http://xdaforums.com/showthread.php?t=1514942

What is your situation? Are you stuck in Recovery boot loop? Are you able to get into Android (whatever ROM you have installed)? If you are able to get into Android, go to settings, developer options and make sure that USB debugging is checked. If unable to get into Android (Recovery boot loop), then you might try holding power and volume down buttons until device reboots and as soon as you see the white letters at the top (about 3 lines worth) let go of both buttons and allow Linux to cold-boot and see if that will get you to Android.

[EDIT] And maybe look here:

http://xdaforums.com/showpost.php?p=25848800&postcount=344
[Eee Pad Transformer Android Development] solitude65:
Thanks for the advice. I am not technically stuck in a boot loop because I don't have a system installed after performing a full wipe. I tried to ADB into clockwork recovery, but that did not work.

I tried connecting through Linux after installing the drivers. The tablet was not found when i did an lsusb.

Posing the question another way: Is it possible to put a file in internal SD without having a system installed, without access to ADB or APX, with CWM 5.5.0.4?
[Eee Pad Transformer Android Development] sidneyk:
Sorry you're having such luck. I've moved on now to Rogue's Touch Recovery as it allows use of either internal or external card. I don't think there is any way to get something on the internal with cwm 5.5.0.4 without being able to connect to the tab somehow. Essentially, CWM is it's own system, a Recovery system with it's own kernel and software and limited in functionality. I did push a file to mine in recovery, I think, but I was able to get to apx mode with working drivers installed. Did you, when you were connected, try from a terminal "adb devices"? Anyway, if you haven't already seen it you might check this thread. It speaks of using nvflash with B7O+ devices. But, still you're going to have to be able to connect through apx mode. Then you could just nvflash a new nvflashable recovery or ROM or whatever you want. Here is the link:

http://xdaforums.com/showthread.php?p=26639556
[Eee Pad Transformer Android Development] sidneyk:
possible fix for apx mode?

@solitude65 - If you are able to boot into Android at all, go to settings->storage and click on the 3 dots in the upper right corner then go to USB Computer Connection and make sure that Media Device (MTP) is checked. That should fix adb access and possibly apx mode. I was having trouble with adb until I checked this option in Revolver 4.

[EDIT] Sorry I read back and see you don't have a system installed. Can I ask, how are you attempting to get into apx mode and how are you determining that you're not able to?
[Eee Pad Transformer Android Development] movelbit:
hi

in the latest touch cwm advanced > reboot cwm does not work. it reboots the tf101 normaly
[Eee Pad Transformer Android Development] MC153:
I love this!!! I can't believe how great it works!! Thanks!!
[Eee Pad Transformer Android Development] sidneyk:
This option is working in the new Rogue Touch recovery.
[Eee Pad Transformer Android Development] solitude65:
From CWM, I hold the volume up button and power for 10-20 seconds. When I do an lsusb command in linux, the tablet is not listed. I have also tried to use the new tool Wheelie and it returns an error stating that no device was found in APX mode.
[Eee Pad Transformer Android Development] sidneyk:
I just tested my TF101 in apx mode first under Windows and then under Ubuntu Linux. In Windows 7, I was able to nvflash Rogue's newest Touch Recovery successfully. In Ubuntu, when I enter apx mode, lsusb shows the device as "Bus 003 Device 003: ID 0955:7820 NVidia Corp.". When I unplug it, then lsusb does not show that line anymore. I enter apx mode by pressing volume up and power button for approx. 6 seconds or so. In Windows 7, assuming you have the drivers installed, when you enter apx mode and then plug the tablet in you can hear the familiar Windows device found sound. The screen on the Transformer remains black, as if off, until nvflash succeeds and reboots the tablet, then you will see some screen output.

When I am booted into Recovery, 'adb devices' shows me this:

List of devices attached

3806245421f9417 recovery

lsusb output: Bus 003 Device 004: ID 0b05:4e1f ASUSTek Computer, Inc.

I just successfully adb pushed a file while in Recovery to my TF101. You may have to mount partitions and such from the advanced menu in Recovery in order to find familiar spots and you definitely have to pay close attention to the paths you're using, especially if adb isn't in your global path. For instance, the internal sdcard under Rogue with adb is found at /data/media/ and everything in there should be as you see it on the internal sdcard.
[Eee Pad Transformer Android Development] BrothaJINC:
Hey IM on 5.8.3.4 and it's looping recovery... I tried coaching roach and touch but neither stick.... Any help IM trying to install threw recovery as said
[Eee Pad Transformer Android Development] sidneyk:
See here:

http://xdaforums.com/showpost.php?p=23339963&postcount=249
[Eee Pad Transformer Android Development] Cysign:
First nothing happened....so I restarted your tool, turning "@echo on" in the .bat-file.

Script couldn't find my downloaded blob-file...even at the right place...but it went on perfectly.

Thanks for that!
[Eee Pad Transformer Android Development] dodge3003:
NOob-ish requires help desperately on tf101.

Hello guys,

My problem is that for no reason at all, all of a sudden I can not boot in to recovery.

No matter which way I try to boot in to recovery it will not work. Be it the power+volume method, or the booting from the CWM app method, or even using any of the boot to recovery' app methods. All that happens is the tab re booting to the Asus boot screen the small writing comes up in the left hand corner, its says 'booting in to recovery' but it just sticks there and never does anything and I have waited up to half an hour for something to happen.

I then have to reboot via power+volume down and instead of then hitting the volume up I just wait a moment then cold boot in Linux.

I am running CM9 (and its playing up) hence me needing to get in to recovery to change from.

I have just down graded back to Windows7 from Windows8 in case 8 was not good with Asus drivers.

Please help if you can and be gentle with my noobishness.

Anybody gets me through this gets a drink (you having a PayPal account permitting) I reckon that way is cheaper than buying a new tf101, they are not cheap her in the UK,lol.

Thanks in hopeful advance

Dene. ;-)
[Eee Pad Transformer Android Development] sidneyk:
What are the first 3 characters of your serial number? If it is B6O or less, you could grab the nvflash version of Rogue's Recovery and nvflash that, assuming you have working adb drivers setup in Windows. It will flash only a new Recovery and then you can hopefully get back in to Recovery to flash other things. See my post 2 before yours.
[Eee Pad Transformer Android Development] chikimonke:
@ Roach, Any chance you'd be a willing party to take on porting TWRP to our beloved TF101? http://goo.gl/nfaJn
[Eee Pad Transformer Android Development] dodge3003:
I have just read and I think understood your post 2 above mine. Alas! That is my problem, I can not boot in to recovery :-(
[Eee Pad Transformer Android Development] sidneyk:
So, it sounds like that if you cold boot then you can get into Android. If that is correct and you have an nvflashable TF101 (B6O and below and some B7O's) then you could choose power off from Android then enter APX mode, from power off, by holding power and volume up buttons for around 6 seconds or so then plug your TF101 to Win 7 PC. The TF101 screen will be completely dark at this point and will stay dark until nvflash has done it's thing and then reboots your tab. You will see some small white text in the upper left saying it succeeded or something before the reboot happens. In Win 7, if you have your drivers setup correctly you should hear Windows new hardware found sound as soon as you plug the USB from PC to TF101. You can then nvflash Rogue's Recovery, as it has an nvflash version. If that works, then you can flash back the working version of Roach's Recovery or a new ROM or whatever. Even if you have a newer serial number TF101, B7O+, there is a thread with a method for using nvflash on those now, too. But, you have to have adb and usb drivers properly setup in Windows before anything else. In other words, APX mode doesn't require you to be able to boot into Recovery, it is a special mode that allows the nvflash program to download new bits to the proper places to get you fixed up.
[Eee Pad Transformer Android Development] dodge3003:
Thank you! Thank you!

I read your post above and whilst I got the gist of it and did not really understand it but my lord with out that post above I would of never got fixed (part any way) I looked at what you posted and Googled the crap out of it all and came upon this site http://www.tabletroms.com/forums/tr...ment/976-nvflash-unbricking-forever-root.html . This nvlashed my machine and put a 3.1 rom on it. I have just backed up that rom ready for flashing new and better ones.

As I type this I have got stuck in Recovery. Every time I press on 'reboot system' it powers down, then up (as normal) then I here a click coming from inside the back of the machine and it stops booting and jumps back in to recovery.

I was hearing this click before and just told myself it has always been there and I had never noticed it. It almost sounds like the internal sd stopping being read or something.

So, it looks like my problem was always born out of a hardware physical one.

Any ideas or am I fu**ed? lol

If I let it run out of battery will it boot normaly after a re-charge?

Still though, a big thanks to you, I have learned so much and have nearly got my machine back :-)
[Eee Pad Transformer Android Development] sidneyk:
Try the command in the following link. First, get into Recovery, connect USB from TF101 to PC. From a command prompt, type in the command from this post and follow those instructions then come back and try the things below. Here is the link for the boot loop fix:

http://xdaforums.com/showpost.php?p=23339963&postcount=249

OK, if you can get back into recovery then you might try wiping the cache and dalvik cache then do a factory reset, You will lose your data and have to restore a backup or reinstall your apps. Then try to flash the ROM again. When it finishes successfully then choose reboot. First boot may take a few minutes. If you still get a bootloop then you may need to try another ROM or something.