yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] sidneyk:
Just a reminder, each of these builds was built with it's own device tree. All three now are using the same kernel source tree.

I run each recovery build separate, against Omnirom 4.4 sources, then blob pack the resultant image, then zip it up with it's corresponding updater binary and script, customized for each device, then sign the 3 zips with dsixda's kitchen.

I then generate the 3 md5 files and upload all for you to use. No repacking of initrd, delivered just as it's built. Each SHOULD be right for the device built for, with all identifiers pointing to the correct device.

Of course, I can only test the tf101 version because I don't own or have access to the other 2 devices.

I try to keep this all up to date and run new builds when I see there have been changes in the source code, particularly the twrp sources.

Yes, it takes time and effort, sometimes more than others, but I enjoy doing it and hope that everyone enjoys the results. Most of the credit belongs to Team Win, all I'm doing, mostly, is just manipulating configs to get the thing to build.
[Eee Pad Transformer Android Development] MassStash:
And we all appreciate it more than can be out into words my friend!

~Jflteusc runnin' latest Carbon Nightly

Latest KToonsez Kernel 2.1;189;480

Pegasusq

Row

Thermald:

Mpdecision:
[Eee Pad Transformer Android Development] sidneyk:
[MENTION=3753391]jrohwer[/MENTION], I may have got this topic confused with another thread where the user was using tf101g recovery and having same issue with assert failing with tf101g ROM. If so, sorry.
[Eee Pad Transformer Android Development] jrohwer:
Yes seeing that now as well :) Indeed in the CM10.1 thread was getting the assert fail even when flashing a tf101g rom with a tf101g recovery. Also he mentions that it was working fine with your build 2.6.3.0-5 but failed with 2.6.3.9. I'm still on 2.6.3.0-6 myself (have not found reason or time to upgrade) but have never had any issues with flashing tf101g roms. In the other thread [MENTION=3594812]ShevT[/MENTION] (who builds the latest CM roms) was also mentioning this. Could there be a problem with assert checking in your latest TWRP Omirom builds? Does it work ok for your tf101?
[Eee Pad Transformer Android Development] ShevT:
In the last assembly I disabled checking (to determine the problem.) With the last set tvrp wonderful.
[Eee Pad Transformer Android Development] sidneyk:
I was looking through the Omnirom sources while at work yesterday. The assert function comes from edify which is part of recovery, but getprop comes from toolbox which is part of the Android built in shell commands. Maybe something is different in 4.4 in general or Omnirom has changed something, I couldn't determine for sure. I know changes have been made here and there to get Mac builds working. I haven't tried anything with assert on my tab yet, but in terminal on my 4.3 phone getprop gives a big long list of various props. I don't know if it just grabs every file ending in .prop or just specific files it knows about. I did Google the issue and lots of people have had the issue on various devices with the solution generally being to just remove the assert line. So I don't believe the issue is with twrp but something with the toolbox functions.
[Eee Pad Transformer Android Development] sidneyk:
Good to hear.
[Eee Pad Transformer Android Development] jacobsensei:
Does this have anything to do with your recovery?

Is it fixed in your latest version?

Thanks for all your work...

the ONE
[Eee Pad Transformer Android Development] sidneyk:
Well, yes, I enabled USB Mass Storage in the kernel and in TWRP and explained how it works a few posts back. It isn't broken, as such, just Windows won't be able to recognize the USB Storage and may offer to reformat it for you. It is up to you to know that you don't want that to happen and to say no to prevent it. This is the stated reason from TeamWin as to why they do not enable it by default. It's because it is a faked vfat file system via fuse, per their explanation, thus the reason Windows can't recognize it from recovery. It was never broken, just a Windows limitation with reading Linux type filesystems. You can see the USB Storage just fine when connected to an appropriately configured Linux system.
[Eee Pad Transformer Android Development] radcpuman:
I have rooted my TF101 (s/n BC0...). I have root and CWM recovery is installed. I cannot figure out how to replace CWM recovery with this version of TWRP. The root method I used was http://xdaforums.com/showthread.php?t=1689193 which installed Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8).

I've tried installing Goo and doing the script install, but it wont' download the file TWRP file. Just not sure what to do.

Thanks in advance!
[Eee Pad Transformer Android Development] frederuco:
Just flash the zip from the OP in CWM and reboot to Android. So long as you don't have a recovery boot loop it will work.
[Eee Pad Transformer Android Development] radcpuman:
Thank you!
[Eee Pad Transformer Android Development] postmortem.:
I assume it is same way to update TWRP? I have 2.5.0.0 from PERI-0.42.
[Eee Pad Transformer Android Development] frederuco:
Yes!
[Eee Pad Transformer Android Development] just lou:
Anyone have a link for v 07 or 06? The latest version 9 just keeps freezing on me when I try to flash anything.
[Eee Pad Transformer Android Development] sidneyk:
Just back up to the parent directory in the link, they're all there, but I didn't have any issue flashing roms with version 9.
[Eee Pad Transformer Android Development] just lou:
OK. Thanks. ....The recovery keeps freezing on me, and I have to force reboot by holding the power button. I never had a recovery problem until installing version 9.

Edit: Just to clarify, it doesn't freeze during the actual flashing process. It freezes within about 10 seconds of me booting into recovery. I don't have to be doing anything.
[Eee Pad Transformer Android Development] sidneyk:
Maybe a bad recovery flash or file or maybe time to deep clean the gremlins and start afresh. I haven't had any issues with that version. I do have an nvflash or 2 back to stock in the past week or so when a build of Omnirom I tried flashing went haywire with a data wiping boot loop. Also, check that your updater-script isn't doing some assert that bombs. There are some reports of assert getting screwed up in recent Android version.
[Eee Pad Transformer Android Development] just lou:
OK.. I'll try to troubleshoot before I go back.
[Eee Pad Transformer Android Development] ShevT:
Problems and suggestions

Yesterday lost all my data. :)

1) Before flashing make a backup of the data only. Check the backup did not. It is not created.

If you create: boot, system, data, then everything is fine.

2) If you perform a wipe system, the firmware will not install. Have to restart TWRP.

3) The contents of internal card is not copied to the external. Folders are created. (I lost more and contents of internal memory) :p

Suggestions: [MENTION=4342873]sidneyk[/MENTION] Make please button "Recovery" on the "Reboot Menu"

My TF101G begins life with a clean slate ;)
[Eee Pad Transformer Android Development] sidneyk:
I tried, but it doesn't work, just tries to reboot system. Hence, the reason it is left out. Just use the power down button in the reboot menu and use the physical buttons to get back to recovery.
[Eee Pad Transformer Android Development] gls9:
Is a backup of /data/media/0 (=sdcard0) included in this version of TWRP when backup DATA ?

(see also http://xdaforums.com/showpost.php?p=48818502&postcount=447 )
[Eee Pad Transformer Android Development] sidneyk:
I am assuming so. I only have a single user setup on my tf101 and have made backups of /boot, /system, /data and restored everything to the same state as far as I could tell. I wasn't really looking for anything in that context then, but everything seemed to be just as it was before it was wiped clean. I believe the backups may be tar archives and may be viewable through a linux archive manager or something, though I haven't tried.
[Eee Pad Transformer Android Development] gls9:
I have also only a single user setup.

The file in data.ext4.win is the file data.ext4. After renaming this file to data.rar it is possible to show the contents.

Now i can see that /data/media/* is NOT included in the backup, which is the internal SDcard. This is also the case with CWM backup.

So this is probable a feature. I used TWRP 2.3.2.3 but expect the same in 2.6.*.*

It think this is the same as the issue from ShevT: 3) The contents of internal card is not copied to the external. Folders are created. (I lost more and contents of internal memory)

So I learned: never do format DATA if you want to retain the internal sdcard (sdcard0) because it is NOT included in a nandroid backup.
[Eee Pad Transformer Android Development] alberteske:
you are right but you refer to media only. it is a good practice to format data oncein a while
[Eee Pad Transformer Android Development] sidneyk:
Ok, as I think about this, if you want to preserve /data/media, then you can wipe /data and TWRP will not touch /data/media and uses rm -r or similar to wipe everything else in /data. But, if you format /data then ALL of /data is not only wiped away, but a whole new file system is laid down in its place.

So, don't wipe internal storage or format /data if you plan on keeping the sdcard contents. You will have to back this up separately.
[Eee Pad Transformer Android Development] gls9:
My mistake was that I thought everything was in the DATA backup, which is not the case.
[Eee Pad Transformer Android Development] Westi01:
[MENTION=4342873]sidneyk[/MENTION] could you reupload the newest Version? Dropbox blocked it due to high traffic load.
[Eee Pad Transformer Android Development] *Detection*:
signed_twrp-2.6.3.9_tf101.zip
[Eee Pad Transformer Android Development] sidneyk:
When I get back home.
[Eee Pad Transformer Android Development] frederuco:
Here is another mirror for the TF101 version: https://dl.dropboxusercontent.com/u/34321735/signed_twrp-2.6.3.9_tf101.zip

*Detection* and I got new links up for ya boss!
[Eee Pad Transformer Android Development] Westi01:
wow, nice! Thanks guys! I got a problem with updating to TWRP. I am currently on 3.1.0.1 CWM and after flashing it and rebooting it starts CWM again instead of TWRP or Android System. :( Any Ideas how to get out of there?
[Eee Pad Transformer Android Development] frederuco:
[RECOVERY][TF101][TF101G][SL101] TWRP 2.6.3.9 Unofficial [2013-11-30]

Can you boot to your ROM?

If so, run the following in terminal emulator:

su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

Reboot normally. It should boot to Android by default. Once this is done, try updating TWRP in CWM and it should work.

If you cannot get to a ROM, use ADB shell whilst in CWM and run the code. It may give SU by default in CWM.
[Eee Pad Transformer Android Development] Westi01:
No unfortunately I cannot boot to a ROM and ADB isn't working in CWM either :(
[Eee Pad Transformer Android Development] frederuco:
Is it a bad cable that is causing issues with your ADB? If so, you will need to get a cable or get it booting.

You can try using APX mode and EasyFlasher. I have a re packed version with TWRP 2.6.3.0 here: https://www.dropbox.com/s/8iq8hh16ll0ku3l/EasyFlasher-0.8.3b-STABLE_TWRP2.6.3.0.zip

I had my cable stop working for MTP/PTP/ADB/APX however it still works for charging with the wall wart. New cable fixed it up straight away.
[Eee Pad Transformer Android Development] Westi01:
Thanks, I select TWRP 2.2.1 for 2.6.3.0?

Edit: WORKED! :) Thanks a million! :)
[Eee Pad Transformer Android Development] frederuco:
[RECOVERY][TF101][TF101G][SL101] TWRP 2.6.3.9 Unofficial [2013-11-30]

Yes, it will install the newer version.

I couldn't figure out how to edit the dropdown text.
[Eee Pad Transformer Android Development] sidneyk:
New download links for TF101 version

OP has been updated with new download links for the TF101 version of TWRP 2.6.3.9.
[Eee Pad Transformer Android Development] shanegru:
can i use this twrp on ics stock? im using twrp 2.2.1.4 on ics... or does this require kitkat rom? i onse installed a custom recovery.. and it seemed my file structure was changed.. couldnt get to my zip files..so was it a driver problem? or wrong version of recovery? im on ics.. dont want to upgrade to newer android.. cuz stock and flash works too good.. what do you guys think?
[Eee Pad Transformer Android Development] sidneyk:
If you already have ICS stock and intend to keep it, then there is really no reason to even mess with this if you have a working recovery. This TWRP recovery will allow you to flash newer Android versions than ICS, but shouldn't get in the way if you flash an older ICS firmware. The recovery environment is separate from the Android environment, living on it's own partition. It uses some mount points to reach the parts of the storage needed for an Android system so that it can read and write to those areas, but otherwise is completely separate. TWRP or any recovery, when flashing a ROM, is only doing whatever formatting, writing, etc that the ROM's updater-script tells it to.
[Eee Pad Transformer Android Development] sidneyk:
New build for TF101

OP has been updated with new download links for TWRP-2.6.3.10 for TF101. It is now built on OmniROM 4.4.2 sources, right along with the ROM I'm building. No major changes other than any changes that may have occurred in the TWRP sources, just building against different sources with a different device tree. I'm still using a prebuilt kernel for recovery for now.
[Eee Pad Transformer Android Development] Magissia:
Do you know how the recovery will act if using KatKiss inverted storage location? (it mount external storage as sdcard0 and internal as sdcard1)

Regards
[Eee Pad Transformer Android Development] sidneyk:
Recovery mounts storage the old way.
[Eee Pad Transformer Android Development] Magissia:
So we're basically breaking any tools that put stuff to flash queue for Team win recovery partition? Since the mount points won't be the same, path to archives to flash will be invalid, correct?

Regards
[Eee Pad Transformer Android Development] sidneyk:
Yes. You would need to use the same fstab mount points, at least. I don't know if TWRP looks for anything other than what it is given by the recovery fstab. In short, you would need a customized TWRP. If someone supplies me with the appropriate fstab files then I could try a build for you. Does this hold through a wipe since no recovery currently uses those mount points? Sounds more like something that Would need to be setup again every time you wipe things.
[Eee Pad Transformer Android Development] Magissia:
Hello, I planned to use Tim 's work with inverted mount points, for best results I guess you both should contact each other as he would have more technical detail than me.

I copied for you Tim' s post about it from KatKiss 4.3 thread. Maybe you could get a closer look.

Regards
[Eee Pad Transformer Android Development] sidneyk:
OK, sounds like a special inverted storage TWRP may be possible, and even have it include a kernel with the changes so that it persists between recovery and android systems. You would still need the special kernel for android because, most likely, the changes are made in files that live in its ramdisk. That way, then factory resets may work OK because the special recovery already knows where /data really is and won't mistakenly wipe the wrong place. Again, this is just my initial assessment from reading what you sent. I'll take a look at that inverted kernel and see what changes are there and what changes would be necessary for TWRP. It may take me a bit, so don't hold your breath or anything, my wife has my computer tied up right now. Of course, I would need others, like you, to test it if I build it to confirm it works.

Sent from my TF101 running OmniROM 4.4.2.
[Eee Pad Transformer Android Development] Magissia:
Don't worry, i'm not in a hurry, patience is important when you want things done correctly.

Thanks for your time.

Regards
[Eee Pad Transformer Android Development] timduru:
It only has changes in fstab,

/dev/block/mmcblk0p1 /system ext4 ro wait

/dev/block/mmcblk0p2 /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait

/dev/block/mmcblk0p7 /storage/sdcard1 ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=footer

/dev/block/mmcblk1p1 /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=footer

basically just mount microsd as /data and internal as microsd
[Eee Pad Transformer Android Development] sidneyk:
Recovery uses it's own fstab so I'd probably have to change both to make sure. I just don't know yet if TWRP code is doing anything internally to override it all. I'll give it a shot when I get time. So, no changes in any of the init.*.rc files?
[Eee Pad Transformer Android Development] timduru:
Yes you would most likely need to to that in the recovery fstab.

Nothing else changed in the .rc, variables are pointed to path and not to partitions, so inverting partitions is enough.

From there it depends if TWRP tries to auto-detect things or not, but I doubt it. I think it's most likely just using the recovery fstab to mount things "blindly"
[Eee Pad Transformer Android Development] sidneyk:
That's my thinking at this point. Will give it a try. Thanks for the input.
[Eee Pad Transformer Android Development] sidneyk:
New Inverted Storage version for testing...

OK, for you folks wanting an inverted storage capable version of TWRP, here is my first attempt at it. I'm not personally using inverted storage so I cannot test this myself. It assumes that you have already made the inverted storage conversion or that you will be using inverted storage after you flash this. Please test and let me know if this works. If it doesn't, I may need to do an actual rebuild.

twrp_2.6.3.10-INVERTED-TF101.zip

http://xdaforums.com/devdb/project/dl/?id=3078

twrp_2.6.3.10-INVERTED-TF101.zip.md5

http://xdaforums.com/devdb/project/dl/?id=3077

WARNING: ONLY FOR TF101 WITH INVERTED STORAGE!!!
[Eee Pad Transformer Android Development] sidneyk:
So, has anyone tested the inverted storage version yet? If so, how did it go?
[Eee Pad Transformer Android Development] Modesis:
hi all, i need this last version on TWRP in .img format for flashing it with tubuntu installer, can i convert the blob file? if so, how? thx all
[Eee Pad Transformer Android Development] sidneyk:
If you have the blobpack/blobunpack tools then yes it can be converted. You'd just have to extract the zip file in some directory. From that directory, and assuming that blobunpack is in your path, you'd type: blobunpack ./twrp.blob

that will give you a twrp.blob.LNX file. You can rename this to recovery.img, it is the same thing with a different name. But I suggest not using the inverted version for the moment as I don't hink it is right. I was trying to test it the other day and haven't succeeded yet. I think I missed one small detail that needs to be changed and it may even need to be rebuilt. I will let you all know when I get a successful test. But, the above directions also apply to the normal twrp.zip.
[Eee Pad Transformer Android Development] sidneyk:
I'm testing an inverted storage twrp I just built and flashed, it needs some tweaking but seems to work. DO NOT flash the previous inverted twrp version I posted, it doesn't work. If I'm satisfied with the results I will post a good one here in the thread. I'm also testing this with a new inverted storage build of OmniROM and so far so good with a couple caveats.
[Eee Pad Transformer Android Development] sidneyk:
Anyone interested in a working TWRP for inverted storage (along with an inverted storage version of OmniROM), please see this post:

http://xdaforums.com/showpost.php?p=49478678&postcount=165
[Eee Pad Transformer Android Development] sidneyk:
New build TWRP-2.6.3.11-TF101 available....

OP has been updated with new links for TWRP-2.6.3.11 for the TF101. No changes from me, just whatever changes have occurred in the OmniROM sources since the last build was posted. Still looks and feels the same, just newer.
[Eee Pad Transformer Android Development] pippoparecchio:
Is the tf101g support discontinued?

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Eee Pad Transformer Android Development] sidneyk:
No, there are still links for TF101G version. I haven't had the chance to do newer builds for it yet because I need to convert device trees over for it again to use with OmniROM sources, but the version posted should still work fine for TF101G. Same thing for the SL101. When I have some time, I will try to get the device trees for those devices converted over so we can get some newer builds for them and maybe even get some ROM builds that will work for them. Keep your fingers crossed. Now I get a new recovery build every time I rebuild OmniROM for the TF101, so it's pretty easy to just zip it up and post a new link.
[Eee Pad Transformer Android Development] lollazzo:
I have the rogue recovery. I want to flash TWRP. What is the procedure?
[Eee Pad Transformer Android Development] alberteske:
it is written in first post: just flash it as any rom or kernel :good: and reboot.
[Eee Pad Transformer Android Development] sidneyk:
Like he said, but make sure you put the zip where rogue can find it. I don't remember for sure, but I think rogue only sees internal or maybe vice-versa.
[Eee Pad Transformer Android Development] kevria:
I am trying to upgrade from TWRP 2.3.2.3 to 2.6.3.11 and verified the md5 sum using AFV but I keep getting "md5 does not match" when I try to install 2.6.3.11 from within 2.3.2.3
[Eee Pad Transformer Android Development] sidneyk:
Did you download the md5 file to the same directory as twrp? If so it means one or both of your files are bad. Try to download again and always reboot to android after flashing twrp and reboot to recovery after to see if it took. You can use a terminal in android to verify the md5sum of both files from the directory they are in, type : md5sum <filename>, replacing <filename> with the appropriate info.
[Eee Pad Transformer Android Development] kevria:
Both are in the same file and the md5 sum contained in the .md5 file matches the md5 sum calculated for the .zip.

I just tried redownloading both again and it still failed the md5 check in twrp recovery.

also verified the .zip with md5sum
[Eee Pad Transformer Android Development] sidneyk:
Since you verified the file is good then just delete the md5 file and flash the new twrp. Then there won't be anything to check and it should flash unless your current twrp is broken for some reason.
[Eee Pad Transformer Android Development] kevria:
Done and worked, thanks.
[Eee Pad Transformer Android Development] mickfo:
I use the twrp 2.6.3.11 and the backup don't save /system/media...
[Eee Pad Transformer Android Development] sidneyk:
I was aware that /data/media was not backed up, but didn't know that /system/media wasn't. I'll have to look into it. Was it backed before on any other version?
[Eee Pad Transformer Android Development] mickfo:
I do a backup with the 2.6.3.9 (previous version not sure) but /system/media was saved
[Eee Pad Transformer Android Development] gls9:
It was also in the backup of 2.3.2.3
[Eee Pad Transformer Android Development] AzureusPT:
I tried flashing 2.6.3.11 twice yesterday without luck. I was on TWRP 2.6+ (don't remember the exact version) and once flashed 2.6.3.11 and done a full reboot, I couldn't enter recovery again. The TF101 got stuck just before loading recovery, in the screen where you push vol up to enter recovery. I see the text "entering recovery" or "loading recovery" just before I push vol up, but there it stays.

Any idea why does it get stuck there? Does it take longer to load than previous versions?

EDIT: Nevermind, I flashed it using dd and now it loads without problem.