yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] frederuco:
The only time you will have issues is if your CWM boots by default then it wont work. If you run into that issue, there is a quick terminal emulator command you can run to fix the CWM boot loop.
[Eee Pad Transformer Android Development] petran_7:
Guys just a question

Can I flash the flashable zip of this version over my previous? Like any other zip?

You can see in my signature my current recovery version.
[Eee Pad Transformer Android Development] sidneyk:
Yes, it will replace your current recovery.
[Eee Pad Transformer Android Development] petran_7:
Thanks!! I did it!! :D
[Eee Pad Transformer Android Development] wn1ytw:
Thanks!

---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------

I don't believe it took me a week to get back and look at the present waiting for me! And not just the dock SD but the USB ports as well, COOLAMUNDO!
[Eee Pad Transformer Android Development] sidneyk:
Glad you like it.
[Eee Pad Transformer Android Development] sidneyk:
I'm having moderate luck getting recovery to build on OmniROM 4.4 sources. Now the trick is getting it to boot!
[Eee Pad Transformer Android Development] MassStash:
Lol minor detail bro. Awesome news! You're a beast with these builds bro

~S-Off LTEvo; Back on the Always Solid Viper4G Latest;

Expletive Deleted Kernel

cpu0/1: 1.5ghz ¦ 384mhz ¦ sleep: 486mhz max

ondemand

fiops

thermald: dynamic

With tapatalk4
[Eee Pad Transformer Android Development] Clovett:
I've had this transformer TF-101 for some while and have finally decided to try a better rom. I consider myself to be literate at this type of work but it could be my problem is so simple nobody mentions it.

First I FLASHED the TWRP 2.6.3.0-7 file using GOO Manager

That seemed to work then I put it into recovery using the power+down vol then hitting up vol

I get an android with a blue ball then it turns into a dead android with a triangle above it. I am assuming this is the part where I should get a TWRP screen? I tried the menu pick from GOO Manager to boot into recovery with no success.

I've searched quite a bit and I can't really find a way out of this. The unit still boots fine but without being able to get to TWRP I can't load the Kisskat rom correct?

Also I noted that, I didn't buy this new, the tablet has a custom rom already. I thought it was stock.

I checked under superuser and it says that Rom Manager is installed but it isn't. Leads me to believe that the current rom may have been installed using clockwork. Dunno if that matters

UPDATE

I used this method I found previously posted and put my blob file in the sdcard root

su

dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4

It still won't boot to recovery from GOO Manager but it works with the keys. Thanks
[Eee Pad Transformer Android Development] sidneyk:
That was where I was going to refer you. If you flash KatKiss, you won't have to worry because you'll have a 'reboot to recovery' option that works from the power menu (obtained by holding power down til it appears).
[Eee Pad Transformer Android Development] dlumberg:
I'm stuck at getting it to flash... I'm getting a install binary error and something like set_metadata_recursive error.

Did you get it to flash with twrp?

Edit: exact errors

set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/omni-4.4-20131113-tf101-HOMEMADE.zip'
[Eee Pad Transformer Android Development] sidneyk:
For clarity, I have not built the actual Omni 4.4 rom. I have only used the Omni source to build TWRP recovery. This I can flash through the older TWRP, but it does not boot.
[Eee Pad Transformer Android Development] dlumberg:
Ah, interesting. That leads me to believe that it's definitely something with the fstab stuff, maybe it sees the mount points (ie: /dev/block/mmcblk0p1) I know that the mount points for the TF300T and TF700T look way different, although I haven't gone back to see if that's changed over time.

edit: oh wait... nvm, that's the vold mounts (

/devices/platform/sdhci-tegra.0/mmc_host/mmc2 /storage/sdcard1 auto defaults voldmanaged=sdcard1:auto)
[Eee Pad Transformer Android Development] ShevT:
TWRP for Cyanogenmod 11

Update Required TWRP to install Cyanogenmod 11. At the moment, when you install obtain: Error executing binary...
[Eee Pad Transformer Android Development] sidneyk:
At the moment, I seem to have lost the ability to build a working kernel, thus the reason I haven't updated anything lately. Still playing around with OmniROM 4.4 source to build twrp, just something is whack with the kernel or my build system.
[Eee Pad Transformer Android Development] sidneyk:
See this post and follow the instructions there:

http://xdaforums.com/showthread.php?p=46806749
[Eee Pad Transformer Android Development] noobsgs2:
Hello there, im currenty on Android 3.2.1 with Android Revolution HD 2.3 (quite old) and i would like to move to 4.3... can i install this recovery or do i have to flash bootloaders/intermediate updates?
[Eee Pad Transformer Android Development] frederuco:
Nope, just flash this recovery and then 4.3. Be sure to wipe caches, system and data partitions.
[Eee Pad Transformer Android Development] noobsgs2:
Thanks for the fast response, i'm glad it's so simple... just to be sure can you explain me in 2 lines why i remember that there was some bootloader issues around ICS or something similar?
[Eee Pad Transformer Android Development] Taomyn:
For some reason the option to disable the screen timeout won't save. I untick the box and after rebooting the option is still ticked.
[Eee Pad Transformer Android Development] sidneyk:
Must be a TWRP bug. I haven't changed anything regarding that feature.
[Eee Pad Transformer Android Development] Taomyn:
Well I know it worked for my old Galaxy Nexus.
[Eee Pad Transformer Android Development] sidneyk:
Actually, I just tried this on my tf101 and the 'Enable screen timeout' box stayed unchecked through power down and boot into recovery. I then booted up to Android and rebooted to recovery and the box was still unchecked. Maybe try to reflash the recovery package and see if that makes a difference.
[Eee Pad Transformer Android Development] sidneyk:
TWRP 2.6.3.0-Omni

The OP has been updated with download links to TWRP 2.6.3.0-Omni for the TF101. Other builds to follow for the other 2 devices when I find time to work on it. I finally managed to get this thing to build against OmniROM 4.4 sources. I have added USB Mass Storage support and SE Linux support at the kernel level.

What USB Mass Storage means is that now there is a 'Mount USB Storage' button on the Mount page. If you are connected to a Linux box when you push this button, then you will be able to browse and work with your internal storage in Linux just like we could in Windows (assuming your Linux has the proper USB setup and if you can do adb, then it probably does). You have to 'safely remove' it in Linux by ejecting (unmounting) it before you press the 'Unmount USB Storage' button on the tab. I have to play with it some more to see if you are able to mount both external and internal to the Linux computer that way.

Also, SE Linux support has been added to the kernel via a tweaked configuration file. This adds SE Linux support at the kernel level if I understand it properly and is anyway a necessity going forward if I keep current with Android. A preliminary look around shows everything looking good, but please flash and test it out and let me know if anything is broken. You people wouldn't believe the amount of hours I've spent on this the last 2 weeks. Enjoy!
[Eee Pad Transformer Android Development] Lesbinary:
Thank you very much! I only want to say only something about the version notation. As I've been watching in other devices, the notation of the version is 2.6.3.X and that X depends of the compilation for that device (obviously, I only saw the official builds). Then, I think we don't need to have a 2.6.3.0-X because nobody else is working on this recovery (as I know). I don't know if that have been discussed here or it's not good to use that notation in an unofficial build of the recovery.
[Eee Pad Transformer Android Development] sidneyk:
Actually, my reasoning is that the official source has a file that sets the version, which I can change to whatever I please. It still says 2.6.3.0. I've just been appending incremental numbering on the end of that build variable to say that this (2.6.3.0) is the major version and the -x is just my notation to indicate successive builds for our devices.

So far, I'm not changing any of the TWRP source files beyond this one variable change, so it's really the same version of TWRP. I change it when the authors decide it changes. I've seen those builds like 2.6.3.8 and so floating around, even 'official' builds like that for other devices, like my Note 3. I may decide to just start doing that, too, which would have made this one something like 2.6.3.8.

I just thought the other way was actually less confusing and didn't want to lead anyone to believe that the official source was numbered any different than it actually is. It's all really just arbitrary in the long run. I've been able to, so far, limit all of my changes to either the device tree or kernel configuration, once I got these things set up to build properly with whatever Android source base I wanted to use.

That was what kept me busy the past days learning how to point the kernel build at a tool chain that would successfully build the kernel source that works for TWRP. I even tried to use timduru's kernel source, but couldn't get it to build any configuration besides the one he uses for his ROM and standalone kernel.

With 4.4 base, it sounds like selinux is mandatory, at least support in the kernel, so I needed kernel source that would build with some toolchain with this added. With OmniROM sources and, I discovered, even 10.1 after a sync, the kernel stopped building properly and even when the recovery image would build, it had a non-working kernel because the drivers and any modules weren't getting built. I have that fixed for now by using the older 4.4.3 eabi- toolchain for the kernel build.

Sorry so long, I just thought I would use the opportunity to explain a little of what I've been staying up nights doing.
[Eee Pad Transformer Android Development] shonkin:
I installed this just in time to find out Timduru had released ver 28 of KatKiss; that install, using TWRP 2.6.3.0-Omni Unofficial, went just fine. Thanks!!

"I'm tryin' ta think, but nuthin' happens!" - Curly

Nexus 4 * N5Rom 4.4 * Lots of Squinting.

Asus TF101 * KatKiss Rom 4.3 * Lots of Coffee!
[Eee Pad Transformer Android Development] sidneyk:
Me, too!
[Eee Pad Transformer Android Development] deejayviral:
Hy everyboady.

I have a TF101 with 4.0.3 original version and rooted with 1Click Rooted app and i want to install KatKiss-4.3.1_027 or 28 if is stable like 27, but i want to know fist how i install TWRP 2.6.3.0-Omn and make the correct steps for the upgrade.
[Eee Pad Transformer Android Development] cbrox:
Excellent work sidneyk!!!! Just used the mount usb tab in recovery and it mounted my microSD just fine on my computer; Draged & Dropped 028 on it and then flashed it with no issues. This is so sweet! Just like my SIII now. One hell of a job man!!!

Thank You so much!
[Eee Pad Transformer Android Development] sidneyk:
I assume you have a custom recovery installed? If so, download the latest twrp, reboot to recovery, flash twrp, reboot to Android, download KK 28, it seems stable, download latest gapps from same thread, download fsync-on.zip from same thread, backup your user apps and data, if desired, you can reboot to twrp recovery and backup boot, recovery, system, data from there. Then, do factory reset, wipe cache, dalvik cache, system and data. Flash the ROM first, gapps right after, fsync-on right after that, then wipe both caches again, reboot and enjoy.
[Eee Pad Transformer Android Development] Chinaboy5216:
Hi Sidneyk, a noob question. I'm running kk v028 now. What are the advantages of the new Omni twrp version over the original twrp 2.6.3.0 you released? For which I really want to thank you again!!! Just don't want to break something that's working fine :)
[Eee Pad Transformer Android Development] sidneyk:
Just a newer code base and twrp is now integrated in that code, so it makes sense that it will probably work best built there. This brings the recovery up to 4.4 KitKat level so it should mean better compatibility for the future.
[Eee Pad Transformer Android Development] Chinaboy5216:
Thx for the explanation, I'll download and flash :) to stay up to date and hopefully for the release of KatKiss Kit Kat by Timduru
[Eee Pad Transformer Android Development] shonkin:
Did you read the original post here? It has the directions to install.

"I'm tryin' ta think, but nuthin' happens!" - Curly

Nexus 4 * N5Rom 4.4 * Lots of Squinting.

Asus TF101 * KatKiss Rom 4.3 * Lots of Coffee!
[Eee Pad Transformer Android Development] deejayviral:
thx for the help :)
[Eee Pad Transformer Android Development] sidneyk:
Everyone, be careful with the USB storage feature on a Windows machine. From what I read, Windows will see it as empty and offer to format it because Android fakes the vfat file system and since Android isn't running in recovery Windows doesn't recognize it. I haven't checked it out myself, but consider yourselves warned.
[Eee Pad Transformer Android Development] cris-:
Hi,

I've installed the version available here https://dl.dropboxusercontent.com/u/47619656/twrp-2.6.3.0-Omni.zip and tried to install the following ROM

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

(hosted here http://4pda.ru/forum/index.php?showtopic=395547&st=1400#entry24636815).

Unfortunately the installation failed with the following error:

> "assert failed: getprop("ro.product.device") == "tf101" || getprop("ro.build.product") == "tf101"

I've re-installed another version of TWRP (which I've also downloaded from this thread: twrp-2.6.3.0-05) and the installation of the ROM worked without problems.
[Eee Pad Transformer Android Development] sidneyk:
Are you on a tf101?
[Eee Pad Transformer Android Development] cris-:
yes.
[Eee Pad Transformer Android Development] sidneyk:
I just wiped and re flashed KatKiss 28 and gapps without any issue. Maybe a bad download or flash.
[Eee Pad Transformer Android Development] dlumberg:
Is it a tf101g? With the 3g module in it?
[Eee Pad Transformer Android Development] cris-:
No.

I've downloaded and installed it twice.

The KatKiss' updater-script does not seem to have this check:

assert(getprop("ro.product.device") == "tf101" || getprop("ro.build.product") == "tf101");

Instead the rom I've tried to install has got this line into its updater-script.
[Eee Pad Transformer Android Development] sidneyk:
Does the update binary and updater script from the ROM you're trying to install have the exact same names as the KatKiss ones? Even if they do, it's possible the update binary your ROM is using is an older one that TWRP has problems with. You could try changing out the KK update binary with the one in your ROM, repack it and try again. If it works then you know they were using the older binary.
[Eee Pad Transformer Android Development] cris-:
the installation works with a previous non-omni twrp version (2.6.3.0-05)
[Eee Pad Transformer Android Development] sidneyk:
Well, Omni is where the immediate future is since TWRP is integrated in that code base. I'll be posting new builds in a few minutes. I suggest to always download both the flashable zip and the md5 file to the same directory and if you have md5 checking turned on in recovery it will tell you right away if you have a bad file because it won't even let you flash it. You could try checking that md5 checking is the only checking you have enabled, I.e. turn off signatur re verification and such, but only if you trust the files you're flashing.
[Eee Pad Transformer Android Development] sidneyk:
TWRP 2.6.3.9 now posted...

OP has been updated with links to the newest build, TWRP-2.6.3.9 for the TF101, TF101G, and the SL101. Fully up to date with OmniROM 4.4 sources, as of 11-30-2013. I have decided to just use the last digit of the version number to indicate my successive builds. All zips are now signed and md5 sum files provided. Please test and report any issues, especially SL101 and TF101G users as I do not have those devices and am unable to test them myself. Enjoy.
[Eee Pad Transformer Android Development] thelangosta:
I get the very same error trying to flash ShevT's cyanogenmod. I've tried 4 times and no go. Today I said screw it and tried to flash ARHD and it worked. Go figure. KatKiss 028 flashed fine.

Sent from my Transformer TF101
[Eee Pad Transformer Android Development] ShevT:
assert failed...

I met a similar problem when collecting TWRP for my phone (sources for TWRP based on CM11). Solutions and have not found, but to delete the row from the firmware.

The firmware KatKiss this test no.

I'll update today assembly. Check will be disabled
[Eee Pad Transformer Android Development] cris-:
I believe the problem is somehow related to TWRP (at least this very version):

it does not seem able to read /system/build.prop ... /system not mounted?
[Eee Pad Transformer Android Development] sidneyk:
You are correct that /system is not mounted by default. You could mount it before you try to install your ROM and then it would find the /system/build.prop of your currently installed ROM. But, what if you wipe /system before trying to install a ROM like many people do automatically? Then there is no /system/build.prop to read anyway. One of the values is present in the default.prop within the recovery environment, but not both values. That check, if it was checking this file, would still fail because it wouldn't find both values. I haven't changed anything within TWRP itself other than the version string. If TWRP used to work with that check then TWRP's authors have changed something. Either removing that check as the one guy said or checking something that will be definitely there in the recovery environment would be my suggestion. What do build.props really mean from a ROM you're replacing anyway? Leave the onus for ensuring a correct device is used on the user with a warning in your ROM post.
[Eee Pad Transformer Android Development] cris-:
I agree about the props in the system partition.

I thought recoveries have got acces to some default properties ( used to build the recovery itself).

Anyway, thx for you help.
[Eee Pad Transformer Android Development] sidneyk:
I was checking earlier through adb while in recovery and there is default.prop in the root which has some of the same values found in /system/build.prop and this file is related to the recovery environment. The /system folder is, by default, mostly empty unless you mount the /system partition first. I didn't check if mounting the /system partition in one recovery session would hold it through a reboot into another recovery session. If so, then that might explain why it worked at one time, if you happened to have manually mounted /system at some point. But, I believe it probably doesn't stick. I can assure you that everything seems to be working fine with TWRP on a tf101, at least everything that I have tested.

The ROM dev probably just needs to do things differently instead of assuming that the /system partition will be mounted (without first mounting it) and assuming that anything will be there when it is mounted (that it hasn't been wiped). Again, it is probably more fool proof just to let the user assume responsibility for making sure he's flashing a compatible ROM. At any rate, the /system/build.prop is only indicating what device the current installed ROM was built for. It is assumed that it will be installed on a matching device, but there is nothing to actually guarantee that. Some people have installed tf101 ROMs on tf10g and sl101, so in those cases that check would be mostly meaningless. When those folks complained about the ROM the dev would just tell them to make sure you're putting it on a tf101, so why not just tell them that from the start and let the responsibilty be theirs. It makes the updater script simpler and ensures that it works on a wiped system, too.

The most important thing to remember, at least with our devices, is that recovery lives on it's own partition with it's own separate kernel and initial ramdisk and that the /system folder in the recovery environment is not the same as the Android /system partition unless you mount the Android /system partition there. It is just a mount point until then.
[Eee Pad Transformer Android Development] jrohwer:
As far as I know, when running recovery the system properties are *not* loaded from /system/build.prop but from /default.prop (a file that is provided by recovery). That is the reason that you need to run a TF101G specific recovery when trying to install a TF101G rom, and a TF101 specific recovery when installing a TF101 rom. The two /default.prop files differ in the two recoveries (at least they should). If you want to get rid of the check you could just delete the "assert ..." lines from the updater script. However I like them there because they are an important check and prevent you from flashing a rom on an incompatible device. The point is rather to use the correct recovery for your device :)
[Eee Pad Transformer Android Development] sidneyk:
I extracted the 2.6.3.9-tf101g zip this morning and extracted the initrd to look at the default.prop file that was packed with it. All device references are to tf101g. All that assert check is going to say is that the ROM / Recovery (whatever the case) that you are currently running or have installed, was built for a particular device. There is no guarantee, for certain, that either software piece is actually installed on the proper device. But, the point is, there should be nothing wrong with TWRP on tf101g if the tf101g files were flashed. There are no references to tf101, only tf101g. The only other thing that might be an issue would be a product reference (a usb device reference in Linux I believe) i.e., 41EF or something similar may have gotten left in from the tf101 version. I don't believe the assert function is even checking anywhere that deep though. It is only looking in some file, somewhere, for those 2 strings or keys and the value contained in them. If the assert function was looking at the default.prop file, then it would see tf101g for the value for both of those keys. So, obviously, assuming the correct files were flashed, it must not be looking for default.prop, but rather for something else and the only other place I'm aware of is /system/build.prop, which isn't around in recovery without first mounting the /system partition, assuming a ROM is currently installed.
[Eee Pad Transformer Android Development] jrohwer:
Agree 100% :)

Looking back at the original question: the assert failed for "tf101" which means that if the ROM was actually for tf101g, then the updater-script was not correct. I am quite convinced that these properties are read from /default.prop in recovery and don't think the usb device reference or whatever would be checked. If I install a tf101 recovery on my TF101G (which is perfectly possible) and then tried to flash a TF101G ROM, it would also fail the assert. So before first josteink and then you supplied builds for the variant I used to extract the initrd from the recovery, change all tf101 references in default.prop to tf101g, and then repack, and it would be good to go :)
[Eee Pad Transformer Android Development] sidneyk:
Good thing is you don't have to do that anymore because I fixed up a recovery device tree just for the tf101g with all of that done so that it builds right in. I'm definitely not repacking anything. The build system is doing it all now.