yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] sidneyk:
INVERTED TWRP and INVERTED OMNI BUILD for tf101...

@Magissia and any others that may be interested, below are the links to a new INVERTED storage TWRP-2.7.1.5 and INVERTED storage Omni build for the tf101. I haven't and probably won't be testing these myself, as I'm quite happy with my current setup. But, the adventurous can test, if desired, and let me know how it goes. If I remembered everything correctly, then both pieces should work for tf101 devices that either have been or will be converted to INVERTED storage set up. There is a post or 2 in timduru's KatKiss thread with pretty good instructions on making the conversion. Since a ROM gets built along with recovery I'm posting a link to it also as a bonus, just in case. Please test and let me know if it works or not. DO NOT USE EITHER OF THESE FOR DEVICES THAT HAVE NOT OR ARE NOT INTENDED TO BE CONVERTED TO USE INVERTED DATA STORAGE OR YOU WILL MOST ASSUREDLY LOSE SOME DATA. Enjoy!

As always, I am not responsible for anything that you may decide to do or not do with your device. All risks involved are your own to keep. Did I say that I have NOT tested these? I believe they should work, but the risk is ALL yours.

Filename: signed_twrp-INVERTED-2.7.1.5-tf101.zip

signed_twrp-INVERTED-2.7.1.5-tf101.zip

Filename: signed_twrp-INVERTED-2.7.1.5-tf101.zip.md5

signed_twrp-INVERTED-2.7.1.5-tf101.zip.md5

Filename: signed_INVERTED.omni-4.4.4-20140821-tf101.zip

signed_INVERTED.omni-4.4.4-20140821-tf101.zip

Filename: signed_INVERTED.omni-4.4.4-20140821-tf101.zip.md5

signed_INVERTED.omni-4.4.4-20140821-tf101.zip.md5

[EDIT 8-28-2014] Updated download links for twrp-INVERTED version.
[Eee Pad Transformer Android Development] Magissia:
Will report back as soon as possible

Regards
[Eee Pad Transformer Android Development] sidneyk:
Updated TWRP-INVERTED-TF101 links

In post # 533, I have updated the download links for the twrp-2.7.1.5-INVERTED-tf101 recovery. I discovered 1 place in a custom recovery init.rc I had started using where there was a hard link to the wrong block device for data in an inverted situation and have corrected that and re-uploaded the files. Please redownload twrp-INVERTED from post # 533 if you've been trying to get an inverted situation working but having trouble. The inverted Omnirom I posted looks to be OK. Sorry, for any mishaps.
[Eee Pad Transformer Android Development] oleeo:
md5 file issue

Admittedly, I am new to checking the md5 on files. But I

have

successfully checked other md5's. One other one, to be exact.

I downloaded 'signed_twrp-2.7.1.5_tf101.zip.md5' several times and get the same md5 value calculated with the md5 checker app (I tried two different ones on the TF101). And yet it doesn't match the value on the download screen. I also tested it with the next file down xxxtf101g.md5 and it also didn't match.

I am all ears to where I am making the glitch happen. I didn't see others with this issue on this file, so please be patient or just throw something at me. I promise not to duck.

I am installing this so that I can then install the latest omni 4.4.4 on my newly rooted (in chinese!) and Recovery'd Asus TF101. Time to revitalize the old girl, thanks for any help.

**UPDATE; couldn't figure out how to delete this post. So, the resolution was I dl the .zip file and checked the md5 on it, and all is good. Still no clue what the problem was with the other, but rescuing has been deemed unnecessary. Thank you.
[Eee Pad Transformer Android Development] sidneyk:
To reiterate, the best thing to do is to download both the twrp.zip file and the associated .md5 file to the same directory on your sdcard, say /recoveries. Make sure that md5 checking isn't turned off in your current recovery, then attempt to flash the zip file. If the md5sum of the zip doesn't match what's in the md5 file, then it won't flash, meaning one or both of the files are corrupted somehow. Redownload both and try again. Both files are provided for your benefit and, if used, ensure that the file you are flashing is identical to the file I uploaded. It is rare that you'll have any issue, but possible, either while downloading or moving files around. Glad you got it sorted out.
[Eee Pad Transformer Android Development] Magissia:
Hi, I downloaded your new version with the hard link fix when I wished to report back.

Using your latest inverted I found only minors problem I don't think you should lose time on, like internal data partition mounted correctly but doesn't show as storage on storage list of zip picker (have to manually navigate to root and go to sdcard1) or default brightness too high.

I didn't flashed anything or used backup yet, only looked around and used file manager + mount manager to push packages to system partition.

Regards
[Eee Pad Transformer Android Development] sidneyk:
Do you see in the storage list anything like 'inverted data' or 'inverted sdcard'? I thought I changed display names to something like those.
[Eee Pad Transformer Android Development] Magissia:
In the storage devices list i do see "Inverted storage" (the external sdcard), i don't see the internal /data partition on the storage selection list (but i can access it from /sdcard1 and do file operation like normal), i took screenshots but i don't know where TWRP save them, they are not in the TWRP folder with backups.

Edit : Found them, they are saved in a weird location (/data/media instead of data/media/0) uploading
[Eee Pad Transformer Android Development] sidneyk:
This should be a recovery (INVERTED version) that is to be used after you've already made the conversions necessary for inverted data/storage. You should be seeing on the storage list from install and maybe the mount tab locations also, an entry for 'Inverted Storage' which is mounted at /sdcard1 on device /dev/block/mmcblk0p7 (actual internal storage location, previously /data) and there should also be an entry for 'Inverted Data' which is mounted at /data on device /dev/block/mmcblk1p1 (actual external storage, previously known as /sdcard1, Micro SD, or external_storage, etc.). That's what is in the twrp.fstab for the inverted version. So that now, what used to be your MicroSD card is being used as the /data partition and what used to be your internal storage, i.e /sdcard, /data/media/0, /storage/sdcard0, etc. is being used as the external storage location, i.e. /storage/sdcard1, Micro SD, external_storage, etc. Could you give me a screenshot from recovery also of the Mount tab options? Thanks.
[Eee Pad Transformer Android Development] Magissia:
http://imgur.com/OM5rhp5

http://imgur.com/aKhU7mM

http://imgur.com/55cGto1

Regards
[Eee Pad Transformer Android Development] sidneyk:
OK, so it looks like Inverted Storage (actually internal) is showing up as /sdcard1, the mount point. Is there any time, such as when first going into recovery and looking at the install locations drop down that 'Inverted Storage' does appear? I've seen on the regular twrp that sometimes 'Micro SD' shows up at first but then changes to the mount point name (external_sd) after I've done other things, like mounting, remounting, different functions, etc. Also, the screen shot function in twrp should be saving to /Pictures/Screenshots if /sdcard mounted and /tmp if not mounted. Could be all this inverted stuff has it confused or needs more thinking out in places.
[Eee Pad Transformer Android Development] Magissia:
Nope, the storage list is always the same, with one entry missing, and the mounts list is always this way too, it's not randomly changing or something for me.

Sdcard1 is not mounted by default, I mount it manually each time, system too.

The screens was in that path, but it was inside media and not "0" where the user's files are.

I will check where sdcard is mounted, maybe it's mounted in media instead of 0

Regards
[Eee Pad Transformer Android Development] sidneyk:
I believe it currently is mounted in /data/media.
[Eee Pad Transformer Android Development] Magissia:
Re, checked, yes it is, it also affect backup and restore location, meaning it require moving the backups from/to there to use theses functions.

Regards

Edit : if you're up for another build I'll be happy to test it.
[Eee Pad Transformer Android Development] sidneyk:
I'll look into it. I need to carefully think through some things and make sure I'm not missing something. It may be also that TWRP code has changed how it's checking partitions and determining things. It all gets a little confusing, trying to remember that this is now that and so forth, remembering to reverse my thinking about the storage layout. It also involves swapping out temporarily my normal device tree for the inverted one, but fortunately I saved copies this time. I'll let you know if I post another build. I'm interested also in knowing if, even if you have to manually find the right mounts and mount them and such, will it successfully flash a ROM and leave things arranged as you expected them, with the /data and /sdcard1 actually inverted and usable.
[Eee Pad Transformer Android Development] Magissia:
I know flashing anything with the older version worked, be it an inverted or normal rom, from the inverted recovery. You want to reproduce that if I understand your message correctly, right?

I'm totally available to screw up my system as soon as the backup and restore works :P

Regards
[Eee Pad Transformer Android Development] sidneyk:
I'm not sure I quite follow what you're saying about backup and restore. I can only tell you what I see with the latest regular twrp, built from the same source as the inverted and even using /data/media the same for the /data path. I flashed recovery, rebooted, rebooted back to recovery and made a full backup, /system, /data, /boot, which gets placed, by default, in a subfolder if /TWRP on my external card. I imagine I could have put it wherever I wanted, but chose the default and default naming. I haven't tried restoring it yet as I'm in the middle of backing up other things, but based on past experience, it should restore the /data partition fine, including any /0 folders, which are only used by Android for multi user setup and not by twrp, as far as I know. But I can say the regular twrp backup seemed to work fine. The only differences really are which devices are being used for /data and /sdcard1. Using the file manager in twrp and looking from the root of the file system, if I navigate to /data/media, I see the /0 folder as well as the other emulated paths for internal storage, all looking normal upon inspection. I believe twrp has added intelligence to determine if normal internal sdcard from the ROM perspective is using /data/media or /data/media/0. So, if you have a rom installed and have stuff in /data/media/0 when you backup data in twrp, then it should get restored to same place with a restore. When I changed back to using /data/media instead of /data/media/0, the thought was maybe it would be better for multi user setup. I only have one user so I can't confirm.
[Eee Pad Transformer Android Development] Magissia:
Hello, problem with that is you cannot manage files from there without root, when wiping it should conserve the whole media folder, but backups should be stored on the first user's folder (0/TWRP/randomstring/BACKUP) even when not using the multi user feature, the first user still exist with it's 0 folder on every recent device I had on hands .

Regards
[Eee Pad Transformer Android Development] sidneyk:
That location with normal storage setup would be on my internal sdcard. I always keep twrp backups and Titanium backups on my external storage. Sometimes have to wipe internal storage to get rid of gremlins. I mean if you have a custom recovery then you have root, it's a given.
[Eee Pad Transformer Android Development] Magissia:
It doesn't help ease of use, but I understand your reasons if you don't wish to fix this specific issue.

Thanks anyway.
[Eee Pad Transformer Android Development] sidneyk:
Not saying I won't do anything, just trying to understand exactly what the problems are. When you say backup and restore, I'm assuming you're talking about a nandroid backup and just didn't realize that anyone was storing nandroids in the location you specified. I'll try later with the normal stuff to add a second user and do a backup and restore to see what it does. Just trying to sort things out to make sure I'm not misunderstanding or getting turned around in my thinking. I should say that I've not done anything to change the backup/restore behaviour. In the normal situation I'm thinking that twrp defaults to using the external storage, which of course doesn't have a /data/media anything by default.
[Eee Pad Transformer Android Development] Magissia:
Hi, default path always was TWRP/randomstuff/backup for me, if on internal , in /data/media/0/TWRP and if on external, TWRP folder was in the root of the external media.

I never used TWRP before multi user existed on Android, i was using CWM, so i don't know if it was different before. For the inverted, my guess is it should be on /data/media/0/TWRP/randomstuff/backup too, as TWRP is supposed to think it's the internal memory.

I'm storing them in "internal" data because it is now external with the inverted storage. On previous TWRP inverted version i was also using the fake internal (real external) as storage location.

The only parameter for path of nandroid backups i had was using this page http://i.imgur.com/aKhU7mM.png i never was able to set a path manually. (and had one more entry there for fake external real internal)

PS : Yes, i was talking about nandroid when talking about backup and restore. Sorry for the not-needed added confusion to an already confusing situation ^^'
[Eee Pad Transformer Android Development] sidneyk:
Ok, that helps make it a bit clearer. Mostly, gotta figure out why 'Inverted Storage' isn't showing up where it should. Keep in mind, the point of an Inverted twrp is so that it will recognize things the way you want. That was the reason for attempting to change the display names to show that it was. More work to do on it. I'll Crack open the earlier inverted and see what was different there.
[Eee Pad Transformer Android Development] sidneyk:
inverted twrp

[MENTION=4634775]Magissia[/MENTION] - I'm studying the inverted twrp issues again today and making some minor changes for you to test and will try to post something later, if I get anywhere with it. The upshot is that if I do, it will be version 2.8.0.0, with some new changes made there by the twrp folks. To clarify, did the older 2.6.3.1 inverted seem to work appropriately for the inverted setup or at least like you expected it to?
[Eee Pad Transformer Android Development] Magissia:
inverted 2.6.x worked flawlessly.
[Eee Pad Transformer Android Development] sidneyk:
New INVERTED TWRP and INVERTED Omnirom builds...

Here are some links to a new INVERTED-TWRP-2.8.0.0 and a new INVERTED-OMNIROM, please test and report. I found a couple minor things in comparing with the inverted twrp 2.6.3.x version and also changed it back to using /data/media/0. I also changed a mount point or 2, for example, there is now an /external_sd mount point, which in the inverted versions of recovery/rom is actually pointed to the internal storage, which normally is /data, but in the inverted version is now /external_sd in recovery and /storage/sdcard1 in Android. /data, in the inverted version points to the actual external card, /dev/block/mmcblk1p1, which normally would have been /storage/sdcard1, but will be for /data in recovery, and will hold the same thing as is known as /data/media/0, /sdcard, /storage/sdcard0, etc. The display names of these in the inverted recovery should show as 'Inverted Storage', equivalent to /storage/sdcard1 in Android (actually on internal storage) for the swapped storage location and 'Inverted Data', equivalent to /sdcard, /storage/sdcard0, etc. in Android (actually on external storage, partition 1) for the swapped /data partition. Please report any issues.

Filename: signed_INVERTED-twrp-2.8.0.0-tf101.zip

Link: signed_INVERTED-twrp-2.8.0.0-tf101.zip

Filename: signed_INVERTED-twrp-2.8.0.0-tf101.zip.md5

Link: signed_INVERTED-twrp-2.8.0.0-tf101.zip.md5

Filename: signed_INVERTED-omni-4.4.4-20140912-tf101.zip

Link: signed_INVERTED-omni-4.4.4-20140912-tf101.zip

Filename: signed_INVERTED-omni-4.4.4-20140912-tf101.zip.md5

Link: signed_INVERTED-omni-4.4.4-20140912-tf101.zip.md5
[Eee Pad Transformer Android Development] sidneyk:
New TWRP-2.8.0.0 for TF101 available ...

OP has been updated with new links for TWRP-2.8.0.0 for TF101 and official change log info. See Omni gerrit for recent merges to android_bootable_recovery for more details.
[Eee Pad Transformer Android Development] MassStash:
Awesome! Downloading 2.8 now, Thaaaaannks you so much yet again for continue support on this project man! Is mtp working? it's giving a guy issues building for M8whl

~ TF101 on Timduru's Latest KISS Masterpiece

Currently OC'ed to 1.5, KatKernel
[Eee Pad Transformer Android Development] alberteske:
Thanks a lot sidneyk! :highfive:

working perfectly!
[Eee Pad Transformer Android Development] sidneyk:
I was looking into MTP in recovery and at first, with Windows 7 it wasn't exactly working. Getting the Windows MTP drivers installed was tricky at best, even though MTP was working properly with Android booted. I finally got some piece of MTP drivers to install with recovery booted and was able to see the storages the same as if Android was booted. There could be some bugs that have or are being worked out yet. I'll do another sync and build later to see what we get.
[Eee Pad Transformer Android Development] sidneyk:
Sorry for the duplicate posts above, I thought the first one didn't work.
[Eee Pad Transformer Android Development] sidneyk:
Did a new build with recent recovery merges and in both Linux and Windows I can get MTP working in recovery, but seems I have to be able to connect with adb first. If the device shows up with adb devices, then I can see it as MTP device, otherwise no. It could be that having USB storage also enabled is interfering somehow. I'll test more later.
[Eee Pad Transformer Android Development] MassStash:
Ah wow, that's dope brah!
[Eee Pad Transformer Android Development] Magissia:
Hello, i made backup, restores (both crypted and classic), installing system updates, wiping with your latest inverted version, from post #558. Path were correct and updates successful, it worked flawlessly for me.

Both storages are now correctly shown as it was with the old inverted.

Only feature I didn't tried is f2fs convert/format.

Best regards, Magissia.
[Eee Pad Transformer Android Development] sidneyk:
Would suggest you dont, as we don't have kernel support.
[Eee Pad Transformer Android Development] Magissia:
Didn't plan to for that reason. Thanks for caring ;p

Now patience time to have system update with f2fs to try it. I will recommend the 2.8 inverted version if someone asks as i didn't found problems using it !

Thank you for your time.
[Eee Pad Transformer Android Development] sidneyk:
TWRP-2.8.0.1 for TF101 posted...

OP has been updated with new links for TWRP-2.8.0.1 for TF101. MTP support is working in both Linux and Windows from recovery, assuming you have the necessary drivers and pieces set up and working in each. Made some minor configuration changes. Now you can drag and drop, in Windows or Linux from recovery, just as in Android, while connected to your PC. For now, I have removed separate USB Mass Storage, as it shouldn't be needed now and has been deprecated by Google anyway in favor of MTP. Enjoy!
[Eee Pad Transformer Android Development] MassStash:
Wow bro, you just keep em comin eh? Fantastic work mate, about to flash this beast now!

~ TF101 on Timduru's Latest KISS Masterpiece

Currently OC'ed to 1.5, KatKernel
[Eee Pad Transformer Android Development] MassStash:
Can you check the wipe menu in 2.8.0.1? Think data got misnamed
[Eee Pad Transformer Android Development] sidneyk:
Well, it was an intentional change, but unintentional outcome. I'll revert it in next build soon. Thanks for the catch.
[Eee Pad Transformer Android Development] MassStash:
Ahhhh icic, no problem man. Went to wipe and flash and said, "waaaaaiiittt a second....." lol
[Eee Pad Transformer Android Development] DROITURK182:
I can confirm this also its been renamed to internal storage plus my cursor wouldn't show when I had the tablet on the dock while booted into recovery.
[Eee Pad Transformer Android Development] sidneyk:
I didn't do anything with the cursor but I'll check mine. I've already fixed the other issue and will have a new build up shortly.
[Eee Pad Transformer Android Development] sidneyk:
Cursor working here with dock:
[Eee Pad Transformer Android Development] DROITURK182:
It could of been my dock only having 4% battery left when I booted into the recovery will report when it's charged up and try again.

Sent from my HTC One_M8 Space Banana.
[Eee Pad Transformer Android Development] sidneyk:
Trying to work through some snags and get new Omnirom and TWRP builds out. Hopefully, this pass will succeed!
[Eee Pad Transformer Android Development] MassStash:
Man, I hear ya on snag woa's. Currently working on a bunch for my m8 kernel...

~ TF101 on Timduru's Latest KISS Masterpiece

Currently OC'ed to 1.5, KatKernel
[Eee Pad Transformer Android Development] frederuco:
I have wiped /data and /system with your builds. It behaves exactly the same as previous versions with the SuperUser nag with nothing installed.
[Eee Pad Transformer Android Development] sidneyk:
Is everyone OK with the external microSD mount point being called 'MicroSD'? It can just as easily be called 'sdcard1', if that is preferred. Let me know.
[Eee Pad Transformer Android Development] frederuco:
I think you should call it "Andys_Extra_Room"
[Eee Pad Transformer Android Development] sidneyk:
We could call it Homers-place.
[Eee Pad Transformer Android Development] frederuco:
Now THAT would cornfuse a few users....
[Eee Pad Transformer Android Development] YayYouFixedIt:
i had a couple probs when i flashed with the last Version before this one. The root permission fixer thing. And it did a reboot stuck at Asus screen. Otherwise it did the job. :)
[Eee Pad Transformer Android Development] MassStash:
Flashed katkiss update today with no issues. Microsd seems like a good name to me. Thank you very much yet again

~ TF101 on K900's AOKP

Currently OC'ed to 1.4, KatKernel 70
[Eee Pad Transformer Android Development] zboq:
Nope, I'm using the one that comes with katkiss. But as I sad in another thread, this happened after flashing newest kernel from timduru. Apart from that kernel and rom works fine, no problems with su.
[Eee Pad Transformer Android Development] Magissia:
i think sdcard0 for internal and sdcard1 for micro sd would be good, since that's how they are named in the file system

Regards
[Eee Pad Transformer Android Development] sidneyk:
That was my first thought also. I'll try some things on some test builds and see if we can achieve that. I think I'm beginning to get a grasp on how twrp is working the mounts and we can probably call, at least the external storage, anything we want as long as the proper references are in place. Now keep in mind, the twrp mounts may get to the same places as /storage/sdcard0 and /storage/sdcard1, but is really just remapping these in the recovery environment, as far as I can tell. I believe the real mount work is going on deep in some c code somewhere and I just haven't got that far yet with my limited c abilities.
[Eee Pad Transformer Android Development] rrjskj:
Is there a way to get aroma working on here ?? I tried 2 times with different aroma zips and it acts like it wants to go but then completely stops . Please help ..
[Eee Pad Transformer Android Development] sidneyk:
I was looking into Aroma and trying to gain an understanding of it. If I understand it correctly, it is really just an updated, touch-based, graphical installer package that just replaces the typical updater-script to give a more feature rich environment for installing ROMs or other packages, perhaps even a recovery package??. Give me some time to get my head around it and I'll see what I can learn. Keep a watch here for any developments.