yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] Piehti:
Changelog?

Howdy,

I'm a bit confused.

Right now I'm using TWRP 2.6.3.0-3. There are no credits and I don't even know where and when I got it. Must be pretty old.

Is there a changelog somehwere? I wasn't able to find thebenefits from updating from 3 to 11. Should I?`Or better go with:

"Never change a runnning system!"

Has 11 this new inverted storage feature?

Cheers
[Eee Pad Transformer Android Development] :
You can find all the changes in this threat. Most of them are minor changes. But all mentioned by Sidneyk.

About the inverted storage: read this post of Sidneyk first

http://xdaforums.com/showthread.php?p=49869336
[Eee Pad Transformer Android Development] sidneyk:
.11 is not inverted but use .10 as .11 has one wrong setting for ext card. It may not hurt anything but better not to chance it. I've posted the latest change log provided at the time I started the thread and pretty sure I gave a link to twrp page. I've also posted any changes I've made. The main reason for .10 is better 4.4.2 compatibilty as it's built on it.
[Eee Pad Transformer Android Development] dlumberg:
Edit: this is not the post you are looking for... move along...
[Eee Pad Transformer Android Development] neofreek01:
been using the new twrp .11 , and everything works fine as far as i can tell....but im getting an error i havent seen before...its actually been happening for a while and i thik even on previous versions.

anyway i get the normal cant mount stagin error that i know to ignore its been there forever, but im also getting a "cant mount btmac" error as well.. ive looked everywhere for anyone else having the problem but cant find nything anyone have any ideas
[Eee Pad Transformer Android Development] sidneyk:
I'm pretty sure it falls in the same category as safe to ignore. I just added it in because it was present in the stock recovery fstab. There is nothing getting flashed there with most zips anyway. I think it may have had something to do with Bluetooth but not sure. I'm going to try and get a fresh build out in a few days as there have been a few changes in the recovery source.

Sent from my OmniROM powered TF101.
[Eee Pad Transformer Android Development] sidneyk:
New TWRP-2.6.3.12_tf101 available

OP has been updated with download links to the latest TWRP-2.6.3.12 for the TF101. This update includes various 'under-the-hood' source code changes from the TWRP/Omni teams. See Omni gerrit for recent merges to android_bootable_recovery for details and more info.
[Eee Pad Transformer Android Development] sidneyk:
Are you getting anywhere with that 3.1 kernel? I've tried a few things, a few times and haven't had much luck.
[Eee Pad Transformer Android Development] dlumberg:
I haven't really done much lately with android. I just upgraded my Rezound to the Moto X and the stock rom is almost perfect so I'll probably be looking for something to do in the near future. That being said, I've got omni building right now with my 3.1 source. It failed the first time but I wasn't watching it so we'll see when it gets to the kernel what it's complaining about. I'm guessing that it's probably a toolchain issue seeing as how it used to build fairly easily with RaymanFX's source mostly unmodified. I'll let you know if I get anywhere with it.
[Eee Pad Transformer Android Development] lucidox:
Just upgraded to 2.6.3.12 from a version from a few months back. I immediately noticed it was more responsive when navigating the UI, which I'm assuming is from rebasing on OmniROM. Thanks Sidney for keeping our aging tabllet going!

Quick question. Is there a way to hide/show the trackpad pointer when docked? I tried toggling it with the trackpad key (positioned above the 3 key) but had no luck. Not a big deal, as I can use the trackpad to move it out of the way.
[Eee Pad Transformer Android Development] Piehti:
Mord responsive: check!

Unable to install SU after wipe in some cases: to be concluded?

Gesendet von meinem TF101 mit Tapatalk
[Eee Pad Transformer Android Development] sidneyk:
SuperSU files are included in the recovery ramdisk. If they're not getting installed after twrp asks if you want to then it must be a twrp bug because I haven't changed anything that should affect that. I think the only time it asks is if you format data completely, after having wiped system and are trying to reboot to recovery as suggested by twrp. Some ROMs also include the supersu files, some have you download them separately and instruct you to flash them immediately after flashing the ROM and gapps. I've not had a chance to test it yet to confirm yes or no as I just finished waiting for all my apps to reinstall from a clean wipe. As long as you can still get into recovery, then it really shouldn't matter as you have no os at this point anyway and will be flashing supersu anyway, either as part of your ROM or right after.
[Eee Pad Transformer Android Development] sidneyk:
So I just tested this. In recovery, I wiped everything clean and formatted data. Got the usual message that a reboot may be necessary, so attempted to reboot, at which point twrp alerted me that I didn't appear to be rooted and had no OS installed and offered to reinstall supersu, by design. I swiped to do so and rebooted to recovery and through adb shell, viewed the /cache/recovery/last log where I could see that it failed to install su to /system/bin, but did install su to /system/xbin, verified by it's presence there. I then restored my backup and rebooted. Compared this to my Note 3 which also has no su in /system/bin, but does in /system/xbin. This is just the way it should work. Hopefully this rumor that it isn't working can be put to rest.

Here is the related part of the log:

I:Switching packages (TWRP)
I:Set page: 'installsu'
I:Set page: 'singleaction_page'
chattr: stat /system/xbin/su: No such file or directory
I:/sbin/chattr -i /system/xbin/su process ended with RC=0
I:Copying file /supersu/su to /system/xbin/su
E:Failed to copy su binary to /system/bin
[Eee Pad Transformer Android Development] Piehti:
I dont get it. Is it a bug or a feature. As said TWRP-12 fails to push su after reboot and this leads to Titanium Backup cant get superuser rights, so this cant really be wanted, no? Installing superuser via flashable zip (the upadate, not the usual cwm - be careful here is a wrong link to the old cwm version around the thread) from chainfire then helps.

I Can make you a video how i wipe / flash etc if wanted. Sorry for annoying.. :\

Gesendet von meinem Transformer TF101 mit Tapatalk
[Eee Pad Transformer Android Development] shonkin:
I ran into this as well... did the following:

1. Installed TWRP (from x9 to x12), it asked me about SU install.

2. I said yes, do it.

3. Rebooted -- and TF101 hung.

4. Held down power button and "down" volume, then hit "up" volume to re-enter TWRP.

5. Again installed my ROM (KatKiss 4.4.?) and latest Gapps. (I did a dirty install -- that is, wiped only system and caches, *not* data.)

6. Rebooted.

7. Took a little longer than normal to load up, but did so without further incident.

That's all I have to say about that. ;)
[Eee Pad Transformer Android Development] Piehti:
Think the result might by diffrent if you take another Rom. Ill try myself later when I reinstall OmniRom. As said: Im not sure if I understand this feature / bug.

Gesendet von meinem Transformer TF101 mit Tapatalk
[Eee Pad Transformer Android Development] :
If I understand Sindeyk this is not a bug neither a feature, when used in the tf101. As we all know, in some roms su is already embedded and in some like OMNI, you have to flash it seperately. No more no less.
[Eee Pad Transformer Android Development] zachf714:
That is exactly it, OMNI does not include the su binary and neither does the installer builds for cm. If this is a bug (I dont think it is) it would be because he is not compiling twrp with omni source and omni does not compile the su binary by default therefore I would not expect the recovery to have it.
[Eee Pad Transformer Android Development] Piehti:
My knowledge of compiling ROMs is very limited (zero?). Will have a look at that. Nevermind. Just trying to understand and help!

So ... why is there an option / prompt to patch it? What does it exactly do? What is it there for - and why doesn't it work?

(As some pointed out it has to do with compilition - but why not fix it - what's the point?). I'm not trying to annoying here... :/
[Eee Pad Transformer Android Development] sidneyk:
For me it did install supersu, on an empty system, after prompting me to do so and before reboot and was still there after reboot, before restoring my backup. It has nothing to do with compilation. TWRP includes the supersu files for this very reason, so it can put some version of supersu back if it doesn't detect it. I don't think it installs supersu otherwise, as you have to already be rooted to install TWRP. Understand though, that adb in recovery already has root permissions.
[Eee Pad Transformer Android Development] dlumberg:
So I got the 3.1 kernel building and booting again (http://github.com/dlumberg/kernel_nvidia_tegra branch 3.1). I noticed that the mount point for /boot is on /dev/block/mmcblk0p9 instead of /dev/block/mmcblk0p4 where Tim's kernel flashes. Is this a KK thing or twrp? It looks like Tim's Kernel shouldn't be able to flash seeing as how his updater-script points to /dev/block/mmcblk0p4 (I grabbed his zip to pack my kernel). Either way I still can't get wifi working on 3.1 and it's really unstable. I haven't gotten a decent dmesg in a while so I'm not entirely sure where it's falling over.

Edit: got a dmesg from boot to desktop http://pastebin.com/z56N7ne9
[Eee Pad Transformer Android Development] sidneyk:
Actually, mmcblk0p4 is the staging partition, where boot images are normally flashed. The TWRP kernel exposes /boot and /recovery partitions which are normally not visible to the user on this device. Per raymanFX, they are 'faked' in the kernel. Tim's kernel does not have this by default. The exposed /boot is indeed mmcblk0p9, but it appears empty in TWRP through adb shell. We don't actually have a boot partition.
[Eee Pad Transformer Android Development] zachf714:
P4/p4wifi has a 3.1 kernel so maybe we can pull some from there
[Eee Pad Transformer Android Development] petran_7:
Thanks for the often updates!

This recovery is the best and you are doing great work for our device! :highfive:
[Eee Pad Transformer Android Development] zachf714:
https://github.com/kasperhettinga/android_kernel_samsung_p4
[Eee Pad Transformer Android Development] Piehti:
:)

Do a real wipe / format and try again. Else you might want to consider taking a newer TWRP version, no? ;)
[Eee Pad Transformer Android Development] jrohwer:
That's completely right re. the staging partition. However, I should add that boot images flashed to the staging partition need to be packed as "blobs" (custom binary format which contains the partition info where the actual image will be flashed to upon reboot (the blue line on reboot indicates this processing of the blob). So images can be tagged in blobs to be flashed to boot (LNX) or recovery (SOS) or other partitions, etc. In this new kernels that expose the boot partition directly, however, you need to flash the android boot image directly (not pack it as a blob). Either way, when you flash a blob to mmcblk0p9 (boot partition) or a straight android boot img to mmcblk0p4 (staging) (i.e. the wrong way round) you will get errors and the device won't boot. So while the end effect is the same (getting a new boot image flashed) the process is different!

You won't see anything in /boot with adb shell because it is not mounted. Android boot images are not normally "mounted" at any point in the file system. If you access mmcblk0p9 directly (e.g. dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img) then you'll see it is not empty and boot.img contains your current boot image. In fact that is what TWRP does under the hood when backuping and restoring boot images.
[Eee Pad Transformer Android Development] sidneyk:
Actually, even with a kernel with boot and recovery exposed you still need a blob packed image, whether you call it boot.img, recovery.img, boot.blob, etc. This is an nvidia requirement I believe. I've never flashed an image on tf101 that wasn't blob packed.
[Eee Pad Transformer Android Development] dlumberg:
I went with the dd method, it just took me a while to figure it all out and change it to mmcblk0p9 in my updater-script file. I wasn't sure if it was a bug so I mentioned it here jic. Thanks for the knowledge, I really appreciate it.
[Eee Pad Transformer Android Development] sidneyk:
The flashable zips also use dd for the boot.blob, but push it to staging. I also dd recovery.blob to staging for testing sometimes before I've made a zip package.
[Eee Pad Transformer Android Development] Magissia:
Hello, there's no inverted storage version for the 3.12 TWRP ?
[Eee Pad Transformer Android Development] sidneyk:
Nope, just the one.
[Eee Pad Transformer Android Development] sidneyk:
New build TWRP-2.6.3.13_tf101 available...

OP has been updated with new download links for TWRP-2.6.3.13 for TF101. Various source code changes from Omnirom and now includes a custom theme. Enjoy!
[Eee Pad Transformer Android Development] rjvdhoek:
Thank you. Is it possible to skip the theme? And did you notice the red square in the middel of the screen? Does it have any function?
[Eee Pad Transformer Android Development] sidneyk:
Yes, custom theme is not included in previous versions. Do you have a pic or something? I'm not seeing a red square. Are you using it on a tf101 or a variant?
[Eee Pad Transformer Android Development] TheSSJ:
Hi sidneyk,

first of all, thanks for the well done job with TWRP.

I am flashing a TF101 of a friend (I don't own a tegra tab myself, only rockchip ;) ), which is still on ICS 4.0.3 and wondered if I just can flash the latest TWRP even with this old system on the tab? Or do I have to install OmniROM/KatKiss/etc. first? At the moment TWRP 2.2.1 is flashed (did it with the EasyFlasher SW here in the forum). Also insecure boot and root is enabled.

So, first install new ROM or can I use TWRP without a problem?

Thanks
[Eee Pad Transformer Android Development] sidneyk:
Yes, you can flash this with no problem. I have been back and forth several times to stock ICS to unbrick, reroot, and flash TWRP from within CWM whenever I soft brick my own tf101 trying new ROM builds and such. You can definitely flash newer ROMs after flashing this TWRP, not so sure how it works with older ROMs though, as I haven't tried.
[Eee Pad Transformer Android Development] sidneyk:
If anyone really doesn't want the custom theme, then just unzip the zip package (you can extract the files with something like ES File Explorer right on the device). Then either copy twrp.blob to /sdcard or from a computer, in the directory where twrp.blob is located, at a command prompt or terminal type:

adb push ./twrp.blob /sdcard/twrp.blob

When that is done, at the same terminal or command prompt, type:

adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit

You can also type just these commands in a terminal program from Android instead:

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

After this, just reboot the tablet, allowing Android to fully boot before attempting to go back into recovery. You should see the blue progress bar, same as if you flashed a zip, and the next time you enter recovery you should see the stock theme.

I'm going to try improving the custom theme over time, but think I will keep it attached as a sort of branding. If anyone has any theming skills or ideas, feel free to share. As long as your theme doesn't alter the functionality, I may like it enough to consider using some or all of it. But, if you prefer the drab, grey stock theme, then the above is how to get it back.
[Eee Pad Transformer Android Development] Piehti:
Got a link for a tutorial or something? Id like to create my own skin. Any hints?

Gesendet von meinem Transformer TF101 mit Tapatalk
[Eee Pad Transformer Android Development] garyngkt:
Flashed 2.6.3.13, quite an interesting theme :laugh:
[Eee Pad Transformer Android Development] jrohwer:
Alternatively just delete the /sdcard/TWRP/theme folder. Can be done in Android or in recovery. No need to re-flash the blob.
[Eee Pad Transformer Android Development] sidneyk:
Actually, you are correct, just delete the theme folder if you are not having any other TWRP issues. And delete it anyway even if you do reflash, if trying to get rid of the theme, because without deleting this folder or having wiped data, then the theme would still be there even if you flashed just the twrp.blob. I was in a hurry when I gave the previous response and hadn't thought it through and didn't have time to test it out.
[Eee Pad Transformer Android Development] rjvdhoek:
Never mind, seems to be the mouse cursor :-/
[Eee Pad Transformer Android Development] sidneyk:
Yeah, I see a mouse cursor when I'm docked, but it looks like the normal white arrow cursor.
[Eee Pad Transformer Android Development] rjvdhoek:
Hm...on my tf101 it is a orange/red square... Never mind, it works fine.
[Eee Pad Transformer Android Development] sidneyk:
New TWRP-2.7.0.0 for TF101 released...

OP has been updated with new download links for TWRP-2.7.0.0. This is still an unofficial build, but the version has been officially moved up now in the source code. This build includes the most recent source code changes from Omnirom. Looks and feel remains roughly the same, perhaps a little snappier. Yes, I am currently seeing a little red block touchpad cursor when docked and swiping the touchpad, but doesn't seem to affect any functionality in an adverse way. The TWRP guys might have changed something under the hood there, as it used to be a white arrow cursor when docked.
[Eee Pad Transformer Android Development] Magissia:
Hey, as it's a major version, possible to redo an inverted storage compilation once confirmed "stable" ?

Regards
[Eee Pad Transformer Android Development] sidneyk:
In reality, it's just the developers finally deciding to bump the version number, no more, no less. I already had most of the changes included. As for the inverted storage and recovery options, I may revisit it when I get some extra time, but I won't be testing it, it will be up to any brave souls that desire that to test. It is too much hassle for me to move everything back and forth as much as I'm doing normal rom and recovery builds and flashing things. But, really if the last inverted recovery build is working you wouldn't really be gaining much more than a higher version number. You can still manually tweak kat kiss or whatever you're using to inverted storage. But, yes, I'll revisit it at some point along with the tf101g and sl101 recovery updates. I've just been spending a lot of time trying to get some issues worked out on OmniROM build.
[Eee Pad Transformer Android Development] Magissia:
[Version part] Yes indeed, but common thing is to bump numbers from a certain place for more important updates than others.

The current inverted storage version do work indeed, if there's not that much changes with the current inverted one, don't bother looking at it now.

[Brave people testing] If you are telling that because of my "stable" asking, it was related to the fact it would be a good idea to be sure the normal version is before looking at the inverted storage version, i'm not asking you to test them as you don't seem to use this version personally, it's already a nice thing you accept to look at it when you can.
[Eee Pad Transformer Android Development] sidneyk:
Didn't mean to sound like I was being accusatory or anything. I believe that twrp, at least for our devices, has been stable for quite some time. Each build I do is usually, most of the time, just bringing in the latest source code updates. I'm very rarely making any changes on the device or kernel side. Now I am using a common device tree for both omnirom and recovery, but the recovery parts don't get touched a lot in the device tree. I build twrp with a prebuilt kernel and sometimes rebuild it for a fresh start. I've been building in what has been called the twrp-2.7 branch for quite some time, almost from the start. It's jyst that the developers have just now decided it was far enough along to actually call it version 2.7.0.0.

When I mention brave souls, it's only because the process to get to inverted storage can be daunting and not for anyone who's not prepared to deal with a soft brick if they happen to mess up somewhere. It took me most of a day to get my tab prepared for the switchover and then to do it and another day lost when I decided to switch back. I wasn't able to see my microsd, formatted as ext4, in Android and didn't like that and couldn't figure a way to make it visible. Yes, I'm saying the changes in the source have been fairly minor things that likely wouldn't be a problem between a newer inverted build or the not so old older build. I think I still have the necessary pieces laying around to do another build, with preparation of my sources, but I won't be testing it.

When I get some things worked out with my rom build, then I will take a look at getting you guys and gals another inverted build of twrp.
[Eee Pad Transformer Android Development] zboq:
Is there any chance that You guys installed newest kat kernel ??, because timduru updated it again to fix su problems i think.
[Eee Pad Transformer Android Development] YayYouFixedIt:
I just tried to flash a titanium custom update.zip with a user app, but they dont take. Anyone know why? Would that be a useful feature to have? :)
[Eee Pad Transformer Android Development] MJPollard:
I've never been able to flash any update.zip created by Titanium Backup, not the app/data backup nor the update.zip it creates to reinstall the app after a new ROM flash. Too bad, too, because it would be very useful to do the latter instead of manually installing the .apk after booting the ROM.
[Eee Pad Transformer Android Development] YayYouFixedIt:
ROM Toolbox Pro shows an update.zip creator. Says "coming soon" however. Time will tell. :)
[Eee Pad Transformer Android Development] sidneyk:
Same here. Had high hopes a few times, but always got let down when it failed and it didn't matter what recovery was being used. Maybe they're using an old updater binary or something.
[Eee Pad Transformer Android Development] MassStash:
Maybe our partitioning is older? I do t think so but something to do with outdated device perhaps

~d2spr runnin' Carbon's Latest Nightly;

Expletive Deleted Kernel

cpu0/1: 1.512ghz | 81mhz | sleep 486mhz

ondemand

row

mpdecision: Rom Based

thermald: Kernel Based

Tapatalk4
[Eee Pad Transformer Android Development] garyngkt:
Ytday I flashed this latest 2.6.1.0 TWRP and my KatKiss couldn't boot up after that had to restore nandroid backup
[Eee Pad Transformer Android Development] sidneyk:
Did you flash the recovery and allow the device to reboot normally before trying to go back into recovery?
[Eee Pad Transformer Android Development] sidneyk:
I'll have to make a Titanium zip and look inside it and see what they have going on. I've never done that yet, just got mad that it didn't work like I wanted it to.
[Eee Pad Transformer Android Development] MassStash:
For sure, I've never ever seen a need for that person ally, so more power to ya!

~d2spr runnin' Carbon's Latest Nightly;

Expletive Deleted Kernel

cpu0/1: 1.512ghz | 81mhz | sleep 486mhz

ondemand

row

mpdecision: Rom Based

thermald: Kernel Based

Tapatalk4
[Eee Pad Transformer Android Development] rrjskj:
Quick question does aroma work with this recovery ??
[Eee Pad Transformer Android Development] garyngkt:
Yes I did, after flashed then rebooted as normal but it got stuck at the KatKiss boot animation. Thanks
[Eee Pad Transformer Android Development] sidneyk:
Did you also download the md5 file to the same folder you flashed from to verify a non-corrupt file? If you haven't already, you might try holding power til it rebooted, let it boot normally if it will, then go back into recovery to see where you're at and reflash the recovery, if necessary. I've flashed it a few times with KatKiss without issue.