Database Info

having fun in recovery... (and messing with Red5)

So, I'm playing with recovery... In particular, I'm working on replacing the stock recovery with CWM Recovery. A good nandroid backup is always the first step to hacking an android device.
I've managed to repack the recovery partition (finally) as unsecure (meaning I can boot into recovery, adb shell into the device, and have root access.) While in here, I'm just noticing something different on the tablet:
It appears that the firmware update from kies has added some odd bloat: the default factory recovery starts by copying several items from a "preload" partition to your /sdcard partition. How nice of Samsung to add even more addition BLOAT to our devices. (I'll be removing that aspect of recovery, I promise.)
Another oddity I'm finding is that, normally with these devices when they are booted normally (and adb is able to connect), the commandline "adb reboot recovery" will reboot the device into recovery mode. That does NOT happen with this tablet (but I'm not sure why.) I have to power down and power back on with the proper volume switch held down.
Okay... time for me to build a copy of CWM Recovery that'll (hopefully) work on this tablet. Wish me luck!
Gary

Thanks in advance! Always glad to hear the interesting finds in a new device.
Sent from my GT-P6210 using Tapatalk

ah, yes... the "new" shared partitions in honeycomb (and ICS.) No longer is there supposed to be dedicated space for /data and /sdcard partitions. They are supposed to use the same space.
Actually, that makes sense. You never have to use something like app2sd, because it's all really the same space. How it gets there, however, is annoying (when trying to reverse engineer a gingerbreak CWM recovery to a honeycomb device.) There is no /sdcard parition on this thing. /sdcard is actually a remap of the /data/media directory. Nice.
My problem is getting CWM Recovery to understand that. pfft.
I wish I could find some source for a CWM recovery partition for another honeycomb tablet. that'd make my life easier, I think.

WARNING: Playing "world of goo" is a major distraction to getting other things accomplished.

have recovery making a nandroid. This would probably be easier if I knew what I was doing. Oh, btw, who wants to test this stuff for me?

garyd9 said:
have recovery making a nandroid. This would probably be easier if I knew what I was doing. Oh, btw, who wants to test this stuff for me?
Click to expand...
Click to collapse
Hey,
I'm also working on it, I'm an dev who ported CWM to the Galaxy Note.
Wait a few hours and you will have CWM

netchip said:
Hey,
I'm also working on it, I'm an dev who ported CWM to the Galaxy Note.
Wait a few hours and you will have CWM
Click to expand...
Click to collapse
I might have just beat you to it. I'll give you a hint, though: honeycomb does some things with partitioning thats very different from previous android versions. CWM tries to take some of that into account, but because of how /data is set up in recovery.fstab, it's not detected that /sdcard should really be /data/media. (I'm rambling.. heh..)
Anyway, pershoot worked this out, so if you pull a specific changeset from his github (https://github.com/pershoot/android...mmit/6dacf061b8476c3e3e2857ca078df95706d62770), and apply it to the CWM in the current cyanogen 7.2, everything should work.
Well, so far everything appears to be working. I've validated the backup works, but haven't verified the restore. I've also modified the code to discourage people from partitioning their sdcards (and it's a bug in CWM that they can choose that option when /sdcard is just a symlink to /data/media)
Anyway, I'll dump the image someplace if anyone wants to mess with it. I honestly have NO idea how to build any kind of package to automate installing it. I've been using "dd" all night long.

On second thought, maybe I'll go to bed... (been awake for over 24 hours)
I'm in the middle of testing the nandroid restores, and there's no way I'll post anything until I'm sure it works. Considering how tired I am, I'll feel better testing this when I'm rested.
One issue I'm REALLY getting annoyed by: For some reason, when I do a "adb reboot recovery", the tablet doesn't reboot into recovery. Even if I'm in a root shell, "reboot recovery" isn't taking me into recovery.
Good night!
Gary

garyd9 said:
On second thought, maybe I'll go to bed... (been awake for over 24 hours)
I'm in the middle of testing the nandroid restores, and there's no way I'll post anything until I'm sure it works. Considering how tired I am, I'll feel better testing this when I'm rested.
One issue I'm REALLY getting annoyed by: For some reason, when I do a "adb reboot recovery", the tablet doesn't reboot into recovery. Even if I'm in a root shell, "reboot recovery" isn't taking me into recovery.
Good night!
Gary
Click to expand...
Click to collapse
I think the kernel is not connected with HC
ICS == almost HC.
There we also don't need the patch

thank you guys so much! great job!

chrisrotolo said:
thank you guys so much! great job!
Click to expand...
Click to collapse
Is on this device the Download mode?
I compile my kernels from source, now I need a tester who don't care about warranty.
I use a module of the SGS2, I've contacted a few people experieced in param.lfs, and they say if the kernel can't mount it it says "logo.jpg not found" and it still boots further.
PM me if you are interested!

posted CWM Recovery.

this is habit forming.
the upcoming version will, in addition to being in a nice update.zip, will also install 'su' so you can root your tab and install recovery all at once.
I am _not_, however, installing the SuperUser application (which is needed as well.) That can easily be done from the market after installing this update file.
All will be documented soon.

I could swore I had an sdcard partition, under it's own or external
Sent from my GT-P6210 using xda premium

For the internal, it's not a real partition. The "/mnt/sdcard" mount is a FUSE link to /data/media. (It's a real parition on the external sdcard if you have one installed.)

I'm working with someone to get copies of the recovery and normal boot kernel partitions from the P6200 (international 3g.) Once I have that, and assuming my blind kernel compiles actually work, we'll have CWM recovery for that tablet as well.
Take care
Gary

I have an international 6200. If you tell me what you need and maybe some help in how to get it, I will dump whatever you want.
Z.

garyd9 said:
I'm working with someone to get copies of the recovery and normal boot kernel partitions from the P6200 (international 3g.) Once I have that, and assuming my blind kernel compiles actually work, we'll have CWM recovery for that tablet as well.
Take care
Gary
Click to expand...
Click to collapse
BTW, have you confirmed that recoveries are incompatible between variants? The 10.1 was "one recovery fits all".

Entropy512 said:
BTW, have you confirmed that recoveries are incompatible between variants? The 10.1 was "one recovery fits all".
Click to expand...
Click to collapse
Currently, they all share the same "recovery" binary (entire /sbin directory, actually), but they need different recovery.fstab files in the initramfs due to different /system (and /data, I think) locations. I'm not at home, so I can't check if it was only 'system' or both.
That one file being different causes them to have a different initramfs, and therefore a different zImage (recovery.img.) I once considered using init.rc to dynamically put a different recovery.fsab into place based on the tablet model at runtime, but how would I be able to determine the tablet model dynamically? default.prop would be useless (as it's also part of the recovery initramfs) and it wouldn't be a good idea for the RECOVERY to rely on the existance of valid data on any other partition. There are ways to take educated guesses based on partition counts and other strange things, but I don't think it's worth the risks.
I do have to admit that I've been having fun messing with this stuff.
Take care
Gary

Ah, that's odd/rare - kind of disappointing.

[Recovery] Rogue XM Touch Recovery v1.5.0-R1 (CWM-based v5.0.2.8) [2012-05-25]

Rogue XM Touch Recovery v1.5.0-R1
(CWM-based Recovery v5.0.2.8)
For the Asus Transformer TF101​
First off, thank you to...
Team Rogue
Koush
CyanogenMod Team
j-r0dd
Solarnz
Roach2010​
All I did slap together all their hard work to make it work on the TF101.​
Sources
Rogue Recovery
The source and more info for Rouge Recovery is available in the Xoom release thread from Team Rogue. I have not made any modifications to it to work with the TF101. You can find that thread here:
http://forum.xda-developers.com/showthread.php?t=1235170
The discussion of the touch release in that thread begins here:
http://forum.xda-developers.com/showthread.php?t=1235170&page=13#123​
Recovery Kernel
I used the kernel from Roach2010's ClockworkMod Recovery 3.2.0.1 release here:
http://forum.xda-developers.com/showthread.php?t=1213723​
Device Tree
Mostly based on AOKP's TF101 device tree, just picked out the parts needed to compile the recovery. Particularly BoardConfig.mk:
https://github.com/rburrow87/android_device_asus_tf101_recoveryonly​
Updates
[2012-05-25] 1.5.0-R1 (5028-based)
Updated to Rogue XM Recovery v1.5.0 which is touch-enabled with the same features as before. See the Xoom release thread for more information on Rogue Recovery:
http://forum.xda-developers.com/showthread.php?t=1235170
Can also finally use the boot to recovery option available in some ROMs thanks to the recovery boot loop fix from Roach2010 from here:
http://forum.xda-developers.com/showthread.php?t=1213723
Workaround for small menu targets
http://forum.xda-developers.com/showpost.php?p=26142147&postcount=151
If I can figure out a way to just make the menu items taller, I'll make an update. Otherwise I'm waiting for Rogue to implement it first.​
[2012-01-14] 1.3.0-R1 (5027-based)
Original release, non-touch​
Info
Mounting as USB storage does not work. (Accessing the tablet or SD card from your computer when plugged in via USB)​
Installation
I tested this the best I could, but use at your own risk. I am not liable for data loss, spontaneous combustion, temporal anomalies, or anything in between.
Just flash the attached zip from CWM.
There's also an nvflash version that has the recovery.img in it and will only flash the recovery if you prefer that method. Or just so you don't have to unpack the blob file if you need the recovery.img.​
Misc:
I did this because I thought it'd be nice to have a newer recovery for our TF101s, but also because I want to learn to do some sort of development even if it's just building for similar devices. I'm still new to using anything like git or using C/Java like this so don't expect miracles right away if bugs come up! I have some experience with other languages, but not in this kind of application.

Thank you, looks nice. Doing a nand backup right now with it.

there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App

Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk

baseballfanz said:
Thank you, looks nice. Doing a nand backup right now with it.
Click to expand...
Click to collapse
Awesome!
will8578 said:
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I saw that post! I've been watching that thread and trying it out when there's an update.
80slovechild said:
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
To do that, you have to extract the zip and then unpack the blob file... but I updated the OP with an extra nvflash version that flashes just the recovery and gives you the recovery.img.

Finally...a relatively current back up for the TF!!
THANK YOU!!
Backing up with 3201, then installing this.
Beautiful work!! Works flawlessly!

Finally! A 5.x.x.x CWM recovery
Does this allow flashing from both internal and external?
On my Galaxy Nexus, they also have a touch softkey mod that has softkeys for up, down, back, and select. Not a big deal but something cool to look into if you get bored.
LTE EX Galaxy Nexus - CM9 AOKP
Asus Transformer - Revolver

Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..

luna_c666 said:
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
Click to expand...
Click to collapse
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.

Worked for me. Way way way better color scheme and it booted quick! Thanks!

wackydroid said:
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Click to expand...
Click to collapse
its definitely not the same as v3.x.... that being said however, simply look at the android_bootable_recovery github to see the differences since v3.x
I think with the latest versions its even possible to use the mount usb with the tablets own MicroSD card where-as in the v3.x tree it wasnt (thanks to v5.x's inclusion of dual mount support, specifically done to support devices with large internal storage)
Still, i have to agree with everyone else, its REALLY nice to finally see a v5.x CWM... using it on my HD2, Evo Shift, and HeroC, it really was a surprising difference from when I was sticking with v3.x

Just awesome!!! Thanks so much!

this needs to be moved to the dev section, but great job!
Sent from my Transformer TF101 using xda premium

Thanks! Installed successfully on two separate rooted B60 TF101's(ARHD 3.2, and Krakd 1.4.2)without any issues. Works great nice job!

New recovery works great!
Just flashed this without any issue. Nice look and feel. Are there more options available under the 'wipe' option, such as ability to wipe only cache or Dalvik cache like the 3.2.0.1 had? I haven't had a chance to look yet and didn't want to chance inadvertently wiping my device. Thanks.
[EDIT] I've now had time to look around and answer my own question. Yes, the other wipe options are there under the wipe menu item. Good to not see that sd card error all the time. So far it seems pretty flawless and better looking, too. I had to reflash my ROM last night and got to put it through it's paces.

Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --

I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.

jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
I also did a back up and restore and my Wifi is fine.
I did not do the advance backup just the regular backup.
Someone else reported this wifi problems using Roach's 3.2.0.1 CWM also.

jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
Hmm, weird, I'm not sure why the recovery would break that unless it's failing to restore something or possibly failed to back something up. I did several backups and restores when I was checking to see if everything worked and never encountered that. Maybe try restoring the one giving your trouble a couple of times to see if it comes back?

hachamacha said:
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
Click to expand...
Click to collapse
Looks like somewhere around CWM 4 is when the switch to tar was made. It has better the speed along with the ability to back up and restore the correct filesystem. Sounds like the progress thing was added somewhere around then as well.
[ Found here: https[colon]//plus.google[dot]com/103583939320326217147/posts/G4VQuCpR25y Sorry, can't make outside links yet. ]
Looking at a kernel zip, it uses dd to put the blob in /dev/block/mmcblk0p4, which is also where the recovery goes... I clearly need to learn more about what's going on here when flashing a kernel or recovery to the same thing and what the function of the blob is.
Looking in the nandroid backuip system tar though, it grabs the /system/lib/modules folder which some kernel zips add to, so the nandroid is backing that up. I'm not sure if nandroid, at least in its current state, is able to back up or restore the kernel itself because of the whole blob thing?
Hmm, perhaps I should make a feature list instead of just saying look at the Xoom release thread!

Help an aging PC hacker upgrade his brain and his TF101

Hi young grasshoppers
I'm an aging PC hacker (down to disassembling viruses with Softice and the works, I'm THAT old!) with a splendid TF101 and I could use an upgrade to my brain and my TF101. I looked for a thorough FAQ to get a clue, but clue I didn't get.
Long story short, one year ago I rooted my TF101 in a rush with success, but didn't have enough time to do the homework and RTFM as I am used to (damn crisis!).
Presently the TF101 has Prime! 1.4 (Android 3.1), Kernel 2.6.36.3-00001-gf377a2b, CWM Recovery 3.1.0.1 Solarnz-R3-230511
My goals are two:
1. trying the new 4.x roms on my TF101;
2. get a clue;
My mental framework comes from PC: mobo holds flashable ROMs and BIOS, hd holds Operating System(s), Apps and Bootloader. As I don't know how the TF101 and Android's structureI'm a little bit lost and I don't want to brick it or upgrading without understanding how to restore it to its present state.
As far as I understood, the TF101 has: Internal SD (holding apps and kernel ? ), external SD aka MicroSD holding media and apps movable to SD, some flashable memory for ROM (?).
As I was cosidering trying Android Revolution HD 3.5.1, I noticed that it requires: CWM v3.2.0.1 and a Super Wipe Full which scared the hell out of me...what is it going to Wipe??? ...and rooting made by RazorClaw
What I would like to understand is:
1. How do I backup the present Kernel and Apps and eventually restore it ? Under CWM 3.1.0.1 I just did a (I believe it's called) Nandroid System Backup that was stored to the MicroSD (external SD) ... what did I just back up ? Kernel,apps,both?
1.1 CWM also offers the Factory Wipe/ Reset function: what does it do? Does it restore the OLD (original as bought) Rom and wipes the Kernelt (and deletes the apps) so that it basically reverts to my original unrooted TF101 as-bought?
1.2 Upgrading the CMW would need: copying the new CWM zip into the external SD card, launcing CWM and using the upgrade procedure?
2. As apparently I need to root throught RazorClaw, I think the present rooting might interfere w/ ARevolution installation. So what would the correct unrootin procedure would be, considered my situation? I'm aware that some apps are able to unroot, but not being sure I'd rather ask.
Finally, I would absolutely love to know if there's a post generally addressing my doubts, giving me an overview of a. what's get modded by rooting b. and where c. and what ROM, Kernel, Bootloaders are in a TF101 or (more generally) in the Android world.
Thanks a lot for your help and for giving me some clues! :laugh:

Ill try to answer your questions as best i can
1.0 Nandroid backs up your rom, apps and appdata not the kernel
1.1 Factory reset wipes apps, data and internal sd it does not change your rom or kernel
1.2 Yup just copy over the new cwm (rouge or twrp are my favorites) and navigate to the file in cwm and hit install
2. If you already on prime you are already rooted so thats not a problem
Rooting just allows you elevated privileges like read/write in the system and things like that. Its like su is essentially sudo
All rooting is is putting the su.sh and busybox.sh into the system using an exploit
You really should not restore a kernel from android 3.1 on anything but 3.1 or your going to have a bad time
Before you update make sure to back up your apps. Titanium Backup is a good choice
Most the roms that are currently active are Jelly bean betas which are a little unstable so i would go with a nice stable ICS rom like megatron or revolver
There is a lot of info in the android general form that you might want to read through but a most development seems to be device specific

elpapacito said:
Hi young grasshoppers
I'm an aging PC hacker (down to disassembling viruses with Softice and the works, I'm THAT old!) with a splendid TF101 and I could use an upgrade to my brain and my TF101. I looked for a thorough FAQ to get a clue, but clue I didn't get.
Long story short, one year ago I rooted my TF101 in a rush with success, but didn't have enough time to do the homework and RTFM as I am used to (damn crisis!).
Presently the TF101 has Prime! 1.4 (Android 3.1), Kernel 2.6.36.3-00001-gf377a2b, CWM Recovery 3.1.0.1 Solarnz-R3-230511
My goals are two:
1. trying the new 4.x roms on my TF101;
2. get a clue;
My mental framework comes from PC: mobo holds flashable ROMs and BIOS, hd holds Operating System(s), Apps and Bootloader. As I don't know how the TF101 and Android's structureI'm a little bit lost and I don't want to brick it or upgrading without understanding how to restore it to its present state.
As far as I understood, the TF101 has: Internal SD (holding apps and kernel ? ), external SD aka MicroSD holding media and apps movable to SD, some flashable memory for ROM (?).
As I was cosidering trying Android Revolution HD 3.5.1, I noticed that it requires: CWM v3.2.0.1 and a Super Wipe Full which scared the hell out of me...what is it going to Wipe??? ...and rooting made by RazorClaw
What I would like to understand is:
1. How do I backup the present Kernel and Apps and eventually restore it ? Under CWM 3.1.0.1 I just did a (I believe it's called) Nandroid System Backup that was stored to the MicroSD (external SD) ... what did I just back up ? Kernel,apps,both?
1.1 CWM also offers the Factory Wipe/ Reset function: what does it do? Does it restore the OLD (original as bought) Rom and wipes the Kernelt (and deletes the apps) so that it basically reverts to my original unrooted TF101 as-bought?
1.2 Upgrading the CMW would need: copying the new CWM zip into the external SD card, launcing CWM and using the upgrade procedure?
2. As apparently I need to root throught RazorClaw, I think the present rooting might interfere w/ ARevolution installation. So what would the correct unrootin procedure would be, considered my situation? I'm aware that some apps are able to unroot, but not being sure I'd rather ask.
Finally, I would absolutely love to know if there's a post generally addressing my doubts, giving me an overview of a. what's get modded by rooting b. and where c. and what ROM, Kernel, Bootloaders are in a TF101 or (more generally) in the Android world.
Thanks a lot for your help and for giving me some clues! :laugh:
Click to expand...
Click to collapse
OK here goes:
You have a custom recovery (CWM) which will allow you to flash whatever you like. There are other versions of recoveries out there CWM, rougue, etc. They all do the similar things, but some have more features than others. The nice part is that you can use one recovery to flash another. My personal preference is for the simpler versions.
1) The nandroid backup backs up system and data, but not the kernel (aka boot.img). This is typical for TFs- I think it's because the kernel is usually flashed through the staging partition and not directly in recovery, like many other android devices. The issue with not having a kernel backup when you restore a backup to "go back" but you have an incompatible kernel. This could happen if you flash a jelly bean rom and then decide to restore a backup to go back to prime (honeycomb). You'll get boot loops and hangs, but you will be able to go back to recovery and flash a compatible kernel.
1.1) Factory wipe will wipe the data partition, which is where all your info is kept. Other roms, this is called userspace. The system partition is untouched, so it will still boot, but you will have to reconfigure wifi, email, bookmarks, etc.
1.2) Essentially, yes. If you can get a CWM flashable version of a recovery, you can flash it in CWM or any other custom recovery. It will be a zip file. Be warned, some versions of recovery don't see or use the external SD card, so be sure your files are somewhere you can get to them. If only I had a $1 for every time someone flashed CWM 5.x and then did a superwipe- it uses the internal SD card and the superwipe erases all the roms and backups they had.
2) You are already rooted because you have Prime 1.4. You can use CWM to flash any rom you like, including stock, as long as you don't overwrite the recovery.
Most android users are obsessed with wiping and super-wiping. It's usually only necessary when going from a custom (a la ASUS) rom to an AOSP rom or vice-versa, and even then it will probably be fine.
---------- Post added at 08:22 PM ---------- Previous post was at 08:13 PM ----------
As far as rooting goes, it's usually an exploit that allows root level access to the file system.
I think technically, all that is needed is the su binary installed in the system folder so that it is persistent and executable. Of course, the system folder on stock roms is usually read only, which makes the exploit necessary. On custom roms, su is usually pre-installed in system/bin or system/xbin.

Follow these steps... download TWRP (its a recovery), download either ICS jelly bean ROM... place both of them in your SD card ( internal and external). Place it both because I don't know what version of CWM you are using... now restart you tablet into recovery ( press both power and volume down buttons together and as soon as tablet turns on press volume up button)... now go to the folder where you placed your recovery (TWRP.ZIP) flash/install it and reboot into recovery... now wipe (factory data, cache wipe, dalvik wipe, system, internal memory)... after these steps install the required kernel and flash the ROM... wipe dalvik cache and cache again and restart... you are good to go...
If you want to back up your old OS.. select backup and recovery option in recovery and do a backup..
Link for twrp
http://forum.xda-developers.com/showthread.php?p=28454456
Link to kernel
http://forum.xda-developers.com/showthread.php?p=29010487
Link to jelly bean ROM
AOSP ROM
http://forum.xda-developers.com/showthread.php?p=28915296
Team eos ROM
http://forum.xda-developers.com/showthread.php?p=28992514
Coming to your questions
Root access..... it gives you administrator access called superuser by which you can remove/modify/change system apps or configurations. Since you already have cwm access i assume you have superuser/root privileges. So don't worry about it... all you need to do is download the latest recovery from above link and install it through recovery. To install choose "install from SD card" and not "update from SD card"
I wouldn't advice you to back up anything because there is no use and sometimes backed apps with data give problems like random restarts/force close etc... if you still want then you can backup from recovery but it won't back up the kernel... it backs up all your system but not kernel.
Your tablet is already rooted because you have recovery access. So don't worry about rooting... if you want to unroot anytime then search for easy flash/nvflash method..
Ask questions if you have more doubts
GOOD LUCK
Sent from my Transformer TF101 using xda app-developers app

udupa82 said:
Follow these steps... [...]. now wipe (factory data, cache wipe, dalvik wipe, system, internal memory)... [...]
If you want to back up your old OS.. select backup and recovery option in recovery and do a backup..
Click to expand...
Click to collapse
First socks, then shoes!

WOW thank guys, many answers and many very detailed options! You rock!
Gee One: oh I see, so Superwise indeed does delete and format, so bye bye to any Titanium Backup on the internal SD.
Brilliant, so I guess I have to move the backup directory to the external (microsd).
Two more fast questions : what's the difference (roughly) between a "custom (a la ASUS)" ROM and an AOSP rom?
And the second one: you state that "You can use CWM to flash any rom you like, including stock, as long as
you don't overwrite the recovery." Oh wow, makes sense..without recovery it's pretty darn difficult to flash anything...but
where does Recovery reside? On the internal SD? I wouldn't like to accidentaly Wipe it out the machine.
Udupa82: wow thanks for the very detailed instructions. For the time being, I guess I'll go with Ice Cream
as I gather that Jelly Beans are still not stable...unfortunately I can't really afford the luxury of having TF101 misbehaving or
behaving weirdly (that's why I staid one year with a stable rom, I already have enough issues to address in work life, so I have
to have the Transformer running and upgraded within the week..so that if problems arises, I still have time to fix it).
Anyhow I succesfully installed CWM v3.2.0.1 - but your detailed indications made me wonder one thing: is it safer to
always place the ROM/other zip packages ALSO in the root of the internal SD (assuming having SU privileges allows me to write
in the root dir of the internal SD) ?
I also gather that restoring an Apps Backup may not be the brightest idea when doing such a jump from a 3.1 to 4.0.3 or higher,
so I guess the Titanium Backup at this point may generate more problems than It would solve.
All: as for the Kernel, I figured by the very few modded kernels (fewer people know how to mess with it properly) I've found
on XDA and by their description that kernels indeed manage the core functions of the machine, which had me wondering if any
of you guys had issues with Kernel 2.6.36.3-00001-gf377a2b in combination with some ICS or Jelly Bean Rom.
Thanks a lot for your precious directions!

elpapacito said:
Gee One: oh I see, so Superwise indeed does delete and format, so bye bye to any Titanium Backup on the internal SD.
Brilliant, so I guess I have to move the backup directory to the external (microsd).
Two more fast questions : what's the difference (roughly) between a "custom (a la ASUS)" ROM and an AOSP rom?
And the second one: you state that "You can use CWM to flash any rom you like, including stock, as long as
you don't overwrite the recovery." Oh wow, makes sense..without recovery it's pretty darn difficult to flash anything...but
where does Recovery reside? On the internal SD? I wouldn't like to accidentaly Wipe it out the machine.
Click to expand...
Click to collapse
The ASUS rom is just the stock firmware that comes with the TF. It has whatever bloatware they ASUS decided to put on there. The AOSP is built from the google code and usually contains little or no bloatware. The AOSP roms are usually cooked up by devs here on XDA. CyanogenMod is a AOSP based rom, for example.
The recovery is located on the SOS partition. I don't think you can erase it by wiping or even super wiping. Wheelie or nvflash (which is the nvidia bootloader) can wipe the partition.

elpapacito said:
WOW thank guys, many answers and many very detailed options! You rock!
Gee One: oh I see, so Superwise indeed does delete and format, so bye bye to any Titanium Backup on the internal SD.
Brilliant, so I guess I have to move the backup directory to the external (microsd).
Two more fast questions : what's the difference (roughly) between a "custom (a la ASUS)" ROM and an AOSP rom?
And the second one: you state that "You can use CWM to flash any rom you like, including stock, as long as
you don't overwrite the recovery." Oh wow, makes sense..without recovery it's pretty darn difficult to flash anything...but
where does Recovery reside? On the internal SD? I wouldn't like to accidentaly Wipe it out the machine.
Udupa82: wow thanks for the very detailed instructions. For the time being, I guess I'll go with Ice Cream
as I gather that Jelly Beans are still not stable...unfortunately I can't really afford the luxury of having TF101 misbehaving or
behaving weirdly (that's why I staid one year with a stable rom, I already have enough issues to address in work life, so I have
to have the Transformer running and upgraded within the week..so that if problems arises, I still have time to fix it).
Anyhow I succesfully installed CWM v3.2.0.1 - but your detailed indications made me wonder one thing: is it safer to
always place the ROM/other zip packages ALSO in the root of the internal SD (assuming having SU privileges allows me to write
in the root dir of the internal SD) ?
I also gather that restoring an Apps Backup may not be the brightest idea when doing such a jump from a 3.1 to 4.0.3 or higher,
so I guess the Titanium Backup at this point may generate more problems than It would solve.
All: as for the Kernel, I figured by the very few modded kernels (fewer people know how to mess with it properly) I've found
on XDA and by their description that kernels indeed manage the core functions of the machine, which had me wondering if any
of you guys had issues with Kernel 2.6.36.3-00001-gf377a2b in combination with some ICS or Jelly Bean Rom.
Thanks a lot for your precious directions!
Click to expand...
Click to collapse
As far as I remember CWM 3.2.0.1 will give you access to external SD card so no need to place the zip file in internal memory... but creating a copy in internal is always better... remember CWM 5.x.x.x version doesn't allow external SD access so never install it...
Do not use restore apps from backup as I always faced problem of force closing. If you still want to then back up any app which is important to you using titanium backup..
Asus stock ROM= its the ROM from Asus with some added softwares from Asus..
AOSP= Android Open Source Project is a OS usually written from scratch using Google's / android's source codes as android is a open software, it comes without any added software(plus point) and more setting/ tweak options(plus point)
There are some good and stable ROMs... but if you don't want much issues then I advice to go for rooted/detoxed stock ROMs because they dont need any custom kernels
Revolver ICS
http://forum.xda-developers.com/showthread.php?p=23000467
Android Revolution HD
http://forum.xda-developers.com/showthread.php?p=17202357
Good luck
Sent from my Transformer TF101 using xda app-developers app

Android Revolution HD
http://forum.xda-developers.com/showthread.php?p=17202357
Good luck
Thanks guys, the upgrade was succesfull! Indeed there's a world of a difference in speed from 3.1 to ARevolution HD..smooth as silk so far Thanks a lot for the help!

[Q] Flash CWM 5 over CWM 6

I currently have CWM 6 installed, but prefer the older version's backup method and file structure (don't like the Blob thing). Can I flash CWM 5 over 6? Thanks!

Youy could, but I dont recommend it. I dont have CWM installed so I cant tell you exactly how, but in the advanced options I am to understand there is an option to disabled the segmented backups, which would eliminate the blobs folder and each backup would then be in its own folder.

apacseven said:
Youy could, but I dont recommend it. I dont have CWM installed so I cant tell you exactly how, but in the advanced options I am to understand there is an option to disabled the segmented backups, which would eliminate the blobs folder and each backup would then be in its own folder.
Click to expand...
Click to collapse
Thanks for your response. I looked at the various menu options and couldn't find that option. Can you be more specific? Thanks!

STraver said:
Thanks for your response. I looked at the various menu options and couldn't find that option. Can you be more specific? Thanks!
Click to expand...
Click to collapse
The best I can do since I dont use CWM myself and dont really feel like installing it just to check (sorry) is quote the person that pointed out to me that it can be disabled. Hope this helps.
Legato Bluesummers said:
You guys realize you can stop making blob backups and go back to normal tar right? Under back up go to advanced settings or whatever its called and choose the other option. Now you won't make back ups in blobs,but now you do them the old way. One folder for the whole back up, about 1-2 GB in size. Blobs are just nice as the backup takes under 5 min. Doing it the old way takes a bit longer.
Click to expand...
Click to collapse
FWIW I use and prefer TWRP (team win recovery project). I switched to it because I was frustrated with the very problem you are having, and gave TWRP a shot and never looked back. I make backups quite frequently and I needed the option of deleting individual backups at will. You can install it with ez recovery. Give it a shot sometime.

apacseven said:
The best I can do since I dont use CWM myself and dont really feel like installing it just to check (sorry) is quote the person that pointed out to me that it can be disabled. Hope this helps.
FWIW I use and prefer TWRP (team win recovery project). I switched to it because I was frustrated with the very problem you are having, and gave TWRP a shot and never looked back. I make backups quite frequently and I needed the option of deleting individual backups at will. You can install it with ez recovery. Give it a shot sometime.
Click to expand...
Click to collapse
Okay thanks. I can't find the option they're talking about. Thanks for your help.

Iirc if you chose backup to external sd card wont it put each backup in its own dated dir inside the clockworkmod dir?
Sent from my CleanRom'd Galaxy SIII

x714x said:
Iirc if you chose backup to external sd card wont it put each backup in its own dated dir inside the clockworkmod dir?
Click to expand...
Click to collapse
Thats what it was doing when I stopped using it, but each folder was only 20mb. The rest of the data was going into the blobs folder.

Recovery Twrp vs CWR

Any advantage over one from the other
Sent from my GT-N8013 using xda app-developers app

I Rio Wonder about that
Sent from my GT-I9100 using xda premium

this will be interesting hearing everyone's imput ... tho its all based on personal preferenceim sure .. i like cwr

I have used both in the past and still prefer CWM....no reason other than its what I learned to use when i was a noob....now Im a noob veteran.

droidstyle said:
I have used both in the past and still prefer CWM....no reason other than its what I learned to use when i was a noob....now Im a noob veteran.
Click to expand...
Click to collapse
I will second this, I like them both, in fact I still use TWRP on my Nook Tablet, but I've been using Koush's stuff for so long, over 3 or 4 phones now, that it just seems natural for me to use CWM.

TWRP for me. Its much faster and has nice features.

I use to be a CWM fan, that was until I started using TWRP on my Rezound. From then on I use TWRP, but I don't mind good ole CWM every once in a while.

TWRP because it's faster and the UI is easier to use simply because the tiles are large.

I like Amon Ra best of all. Oopps...wrong thread LOL!. I use TWRP on my Bionic and CWM on the Galaxy. Like mentioned above, CWM is what I learned on and for some reason it feels like more hands on.

Let me say this. My friend was running CM10 all the way from like september. I tried updating it in CWM but it gave me assert errors. Reflash TWRP on it, and flash latest nightlies no problem. Dirty flash too, just wipe dalvik and cache.

There isn't an objective answer that I can give. I'm biased towards pretty much anything that is alternative to what everyone else is using. Also, I have no data that would indicate one recovery is better than another. So here's my purely subjective answer.
I prefer TWRP over CWMR for several subjective reasons:
Coming from the original Moto Droid on vzw, I ran RZrecovery (a moded version of SPrecovery, which had an OC'd kernel and lots of options as well as charging while in recovery way before I had seen it anywhere else). Basically, I'm not accustomed to CWMR.
I'm not a fan of the differential backups that CWMR defaults to. I know it takes up more space to have an IMG or TAR for each partition I choose, but I'm a crack flasher and go back and forth between TouchWiz and AOSP based roms all the time. I need to be able to keep my backups completely seperate. No blobs. I need a golden master for each ROM I flash. With a 64GB externeal SD card and a 32GB internal card, I rarely run out of space.
I can name backups while booted into TWRP before you create the backup. The whole date being wrong in every recovery thing is indeed annoying.
I like the terminal. I prefer to root, flash, hack, etc etc on my own without help from apps and or pre-built tools (except for dsixda's android kitchen, which is so bloody easy to use it blow my friggin mind). So I don't need or want ROM Manager to do much of anything for me. I even flash TWRP via the terminal. GooManager always runs in the background, and hasn't really ever had the most up to date versions of TWRP, so I ditched it pretty fast. I hate apps that run in the background when I'm not using them.
I like the look and feel of TWRP. Its feels like a teeny version of android with a small but very functional UI. Only thing missing is a terminal emulator that I could use from within TWRP itself. (Choosing a command file to run just isn't the same, but it has come in handy)
I also like having backups go to a folder that is labeled with the device's SN. Seems like a really fantastical feature in the making, like a cloud based storage for TWRP could be somewhere off in the future, where you could backup multiple devices to one online storage space.
Its the only "alternative" in town. I like "alternative" aka not so main stream stuff, which is odd cause I'm not a fan of Alt Rock. More of a Hendrix, Zepplin "classic rock" (aka blues based rock n roll with lots of riffs on the minor pentatonic scale) kind of person.
Um, I don't really have an 8th reason. But I would like an OC'd kernel in TWRP to help speed up backups, but I dunno how viable that is.
Ta,
ALQI

alquimista said:
Um, I don't really have an 8th reason. But I would like an OC'd kernel in TWRP to help speed up backups, but I dunno how viable that is.
Click to expand...
Click to collapse
Tempting, but with backups/flashing/recovery, I think slow and steady wins the race.

I used to use cwm, but with the change to blobs all of my backups stopped working. Even ones I just made.
so I stopped trusting it.
I switched to twrp. The backups are larger I think, but I trust them more.
Sent from my SCH-I535 using xda app-developers app

Haven't had any problems with TWRP, and it was the first I used. So pretty much just became acquainted with it and haven't seen a reason to switch.

I use CRW on my phone and TWP on the Kindle Fire. The best advice I can give is use what ever method the dev tells you to use, if he goes out of his way to mention it there is probably a good reason behind it.
One thing about CRW I wish would get fixed is the file name date being wrong (When it saves a file it gives the file a name based on the date but all current versions save it with an incorrect date (it thinks its 1970 lol) If i dont change it right away I end up with a bunch of mystery backups.
Another thing to remember about the latest CRW's is the blob. To save space during the saving of a backup a file (blob) is created that has any redundant info shared by backups in it. So all the info for your latest backup file isn't all in the file with that backups name some or most of it is in the blob file. So if you want two or three backups from your phone saved to your home computer make sure you take the entire clockworkmod file because if you take just the individual CRW backup file (1970 -blah-blah-blah) you will be missing all the info on the blob. CRW will let you restore with the partial file and that can get ugly fast.

I've always used cwr but I will give twrp a shot, love trying new stuff. And the date issue with cwr is really annoying. I'm sure it could be renamed but I don't want to change anything and get an md5 mismatch.
Sent from my SCH-I535 using xda app-developers app