yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] Buddlespit:
no, I mean ext4 works wonderful in recovery. But when I boot up the rom, I can't even mount the sdcard, let alone browse it.
[Sprint Samsung Galaxy S III] Skunk Ape1:
Gotcha...
[Sprint Samsung Galaxy S III] Dees_Troy:
You can set up an init.d script or use something like gscript to "manually" mount the sdcard. The biggest problem is permissions on ext4 can cause some issues. CM10 did a good job. After using init.d the ROM would fuse the ext4 into an emulated file system at /external_sd which worked around the permissions.
[Sprint Samsung Galaxy S III] EndlessDissent:
I beg to differ. I'm definitely having permissions problems on CM10. When my phone boots, the permissions for my SD card are blank, and the card reads as empty. If I fix the permissions and move anything to the card, the file moves fine and remains there for the rest of my session, but once I reboot, everything goes back - blank permissions and empty card. USB Storage Mode also no longer starts; the spinner never stops spinning, and it just sits on that screen forever. I'm using Linux (Crunchbang specifically), so everything should work perfectly with ext4 - at least, that's what I expect from an OS based on Linux. Why should CM need to use FUSE to work around permissions? Why would that be a problem if Android natively supports ext4 and even uses it for the internal storage? Why aren't there any permissions problems with the internal storage, then?

As it pertains to this recovery, one thing I noticed is that if I move things from my computer to my phone while it's in the recovery's UMS mode (which works beautifully under Linux with an ext4 card), the file transfers fine, but again, CM reads the card as empty. If I then use CM to copy files to the card (as above, this appears to work fine) and then reboot into recovery, the file that I had previously moved using UMS in recovery will still be on the card, but everything from CM will be gone.

Sorry for being so off-topic for the thread, but since you mentioned the way CM handles ext4 cards, I figured you could provide some insight. Do you have any idea why CM derps so hard with ext4 SD cards? It makes no sense to me since ext4 should be natively and universally supported by an operating system based on Linux, especially since Android uses ext4 for the internal storage. On Linux - on a PC, anyway - plugging in an ext4-formatted drive of any kind works perfectly with no modifications. Why wouldn't it be the same in Android? I don't want to be stuck with any Windows anything, including FAT32. I don't want to use a legacy filesystem when there are plenty of full-featured, modern filesystems available. All I want is for Android to support ext4 (maybe even Btrfs in the future?) like any other Linux OS would.

Uh... Sorry for the rant there. This is just very frustrating for me. I just can't make sense of why a Linux-based OS would have any problems with ext4.
[Sprint Samsung Galaxy S III] Skunk Ape1:
It's not just cm that has trouble with this. Every touchwiz rom had the same issues, including the stock rom.
[Sprint Samsung Galaxy S III] EndlessDissent:
Well, my point included the TW ROMs as well. Any Android ROM, regardless of who's making it, should be able to handle ext4-formatted SD cards. If support for ext4 is there (it is if the internal storage uses ext4, and it does), then there shouldn't be any problems.

I like that TWRP supports ext4 perfectly, but that shouldn't even be a concern with a Linux-based OS. Ext4 support should just be expected in Android.

Maybe I'm expecting too much, but in the Linux PC world, if you build a kernel with ext4 support, all ext4 drives work fine. Why wouldn't it work like that for Android?
[Sprint Samsung Galaxy S III] Buddlespit:
Could you do me a favor when you're next in your rom, and type in terminal:

cat /proc/filesystems

and if you see "ext4" somewhere in the list, you might just have a mounting problem, like we appear to have.

BTW, Skunk? I'm sick, so I didn't put that much effort into figuring out how to mount the sdcard w/ ext4 in Wicked. I'll look into it more today, ok?
[Sprint Samsung Galaxy S III] EndlessDissent:
Yeah, it's in there.

u0_a38@android:/ $ cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
nodev ecryptfs
nodev nfs
nodev nfs4
nodev cifs
nodev fuse
fuseblk
nodev fusectl

If it weren't there, the internal storage wouldn't mount, either.

I checked /etc/vold.fstab, but there is no parameter for the filesystem. I guess it's just supposed to auto-detect it. I have no idea why ext4 would **** it up.
[Sprint Samsung Galaxy S III] Dees_Troy:
The ROMS don't automatically mount sdcard formatted to ext4 but you can manually mount it via terminal emulator or adb. mkdir test && mount -t ext4 /dev/block/mmcblk1p1 /test

You can automate with init.d so that it mounts during boot.
[Sprint Samsung Galaxy S III] Buddlespit:
Ya, Skunkape was working on that yesterday via PM. I got sick over the weekend and really didn't feel like tearing apart my otterbox to pull the sdcard out. Still sick, still don't want to pull the sdcard...:silly:
[Sprint Samsung Galaxy S III] EndlessDissent:
Thanks. I was thinking of doing something like that. Is there any way to edit /etc/vold.fstab so it gets mounted correctly on boot? I'm guessing no, but that's the only place I can think of that may affect how the card mounts. It's still annoying that workarounds are necessary just to use a real filesystem.

Anyway, I'll quit derailing the thread and bring the non-TWRP talk elsewhere. Thanks for your patience.

Edit: In case anyone wants to try mounting via Terminal Emulator, I wasn't able to create a /test directory, or any other root directory for that matter, so I mounted it at /storage/sdcard1, and it works perfectly.
[Sprint Samsung Galaxy S III] Master K:
New Version

The main TWRP site shows the current version as 2.3.2.0 but there does not seem to be one for our phone. Any idea when that will be available.

The change log says it is updated for 4.2

Thanks!
[Sprint Samsung Galaxy S III] Dees_Troy:
If anyone wants a build with exFAT support but no USB storage and wants 2.3.2.3 then you can flash this manually:

http://techerrata.com/dees_troy/d2spr-exfat.img

Put it in /sdcard and then run this via adb shell or terminal emulator:

dd if=/sdcard/d2spr-exfat.img of=/dev/block/mmcblk0p18
[Sprint Samsung Galaxy S III] Anon9mouz:
Is 2.3.1.0 safe to flash new cm 10.1 4.2.1 or should I wait??

__________________________________________________
[Sprint Samsung Galaxy S III] Upstreammiami:
Can anyone make a flashable zip file?

Samsung Galaxy S III
[Sprint Samsung Galaxy S III] Naddict:
Flashable 2.3.2.3 TWRP

Here ye all go!!! Flash away
[Sprint Samsung Galaxy S III] Buddlespit:
There's no need. Copy the .img file to the root of your sdcard (internal) and c&p

dd if=/sdcard/d2spr-exfat.img of=/dev/block/mmcblk0p18

via adb shell.

Easy-Peasy!
[Sprint Samsung Galaxy S III] Upstreammiami:
Yayyyyyy

Samsung Galaxy S III
[Sprint Samsung Galaxy S III] Dees_Troy:
No, either flash the exfat build or wait until tomorrow's 2.3.3.0 release.
[Sprint Samsung Galaxy S III] Anon9mouz:
I'll wait but what's funny is someone said they used the cm updater doing nightlies and flash over cm10 with cm10.1 and he didn't have problems strange but yeah I'll wait no problem. Are u done updating the sprint gnex recovery??

__________________________________________________
[Sprint Samsung Galaxy S III] 5FOOTER:
Dees first time using this recovery you gonna post on how to update? I'm sure you will. A lot of us came from the touchy epic touch with a lot of flashing issues.
[Sprint Samsung Galaxy S III] Upstreammiami:
Will the update stop cm10.1 from moving files to 0

Samsung Galaxy S III
[Sprint Samsung Galaxy S III] Anon9mouz:
I believe what it does is make it to where there's not multiple 0 folders every time u flash a rom

__________________________________________________
[Sprint Samsung Galaxy S III] Dees_Troy:
The SGS3 line is much simpler. Just flash with goomanager.
[Sprint Samsung Galaxy S III] Skunk Ape1:
You little weasel. I made one soon as I got home from work... You beat me to it. LOL...:good:
[Sprint Samsung Galaxy S III] EvgeniX:
no 2.3.3 update? :confused:
[Sprint Samsung Galaxy S III] Upstreammiami:
Chill out dude he said it will come today

Samsung Galaxy S III
[Sprint Samsung Galaxy S III] Anon9mouz:
New recovery on goo

__________________________________________________
[Sprint Samsung Galaxy S III] Dees_Troy:
Updated!
[Sprint Samsung Galaxy S III] Naddict:
Flashable TWRP 2.3.3.0

here you go!

flashable new release...
[Sprint Samsung Galaxy S III] Buddlespit:
Does 2.3.3.0 not have exfat support?
[Sprint Samsung Galaxy S III] Skunk Ape1:
No... that would be 2.3.2.3 posted one page back.
[Sprint Samsung Galaxy S III] Buddlespit:
Ya. I also made that clear in your AC thread too.
[Sprint Samsung Galaxy S III] Skunk Ape1:
If anyone wants a tar version to flash in Odin. Just let me know which version you need.
[Sprint Samsung Galaxy S III] Upstreammiami:
What does Exfat do?

Samsung Galaxy S III
[Sprint Samsung Galaxy S III] teh roxxorz:
.....Google my son.

ExFat
[Sprint Samsung Galaxy S III] Dees_Troy:
I think I finally got Odin flashable tars made correctly in my build script so the 2.3.3.0 tar in this folder should work. I didn't make one for the 2.3.2.3 with exFAT support though.
[Sprint Samsung Galaxy S III] Skunk Ape1:
I'll take care of 2.3.2.3 with exfat after dinner.

Here's TWRP 2.3.2.3 with exfat support. Flashable in Odin or Mobile Odin.

TWRP-recovery-2.3.2.3skunk.tar.md5 - DOWNLOAD HERE
[Sprint Samsung Galaxy S III] vMAC:
Thank you, Thank you.

P.S. When I first tried this via Terminal Emulator I was getting a permission error with writing to /dev/block/mmcblk0p18. Tried changing permissions of that file, still had same issue. ADB however worked perfectly, so if you have any trouble, try that.
[Sprint Samsung Galaxy S III] Skunk Ape1:
Exfat is a proprietary microsoft file system. It overcomes many of fat32 file system limitations such as it can handle file sizes in excess of 4gb. Many HD movies are larger than 4gb in size. The problem is that most recoveries don't read sdcards formatted in exfat. So if you have your sdcard formatted in fat32 so you can access it in recovery, you can't have files larger than 4gb in size. So you basically have to choose does your sdcard get seen in recovery or do you want large file support.

With TWRP 2.3.2.3 with exfat support you can have both.
[Sprint Samsung Galaxy S III] Anon9mouz:
Questions is why would u wanna see files larger than 4gb in recovery no rom is that big and ur not flashing movies just curious as to why its even needed??

__________________________________________________
[Sprint Samsung Galaxy S III] styles420:
Let's say you want to be able to see the sd card in recovery to flash rom's from it, while also being able to store larger files such as movies for those much more frequent times that you aren't in recovery... can't do it. You have to choose - if you want to store larger files, then you have to give up the recovery's sd card access. So the point is not to have access to large files from recovery, but to be able to have both features instead of having to choose one or the other
[Sprint Samsung Galaxy S III] Skunk Ape1:
EDIT: Already answered above.... too slow with the send button again.
[Sprint Samsung Galaxy S III] reverepats:
Hmm that makes sense. Cause I need ver really understood what the point of having it either.
[Sprint Samsung Galaxy S III] styles420:
Part of it may just be familiarity with older phones, where the sd card was the only place to store roms... it would be useful to have access to the sd card if the rom boot loops and the file you need to flash isn't already on the phone, but that isn't the only option (adb push works for transferring to either storage location with some custom recoveries, for example).

So depending on what is broken, the ability to move the external sd card to a computer could end up being the only way to fix it without losing user data to the Odin process...

But I can't think of anything other than movies that are likely to exceed 4gb, and those movies can be converted to a smaller format without any perceivable loss of quality (even on a larger screen)
[Sprint Samsung Galaxy S III] vMAC:
Or to put it simply. You don't need two sdcards, one for recovery (think backups, and installing ROMs) and then another to watch movies in the ROM.
[Sprint Samsung Galaxy S III] timezone12:
Wouldn't it be easier just to get a otg usb cable and use a 64 gig thumbdrive or even a mini hard drive?
[Sprint Samsung Galaxy S III] Skunk Ape1:
No it's easier to have a recovery that reads exfat like Twrp2.3.2.3. :D
[Sprint Samsung Galaxy S III] monstaX:
Once we have 2.3.3.0 does that mean when we flash CM10.1 Roms it won't create the '0' folder and move all my files to it?
[Sprint Samsung Galaxy S III] EndlessDissent:
The '0' folder is part of Android 4.2. You can't flash CM10.1 without creating it. The problem was that when one would perform a factory reset and flash 10.1 again, it would create another '0' folder inside the first '0' folder. That's the problem that 2.3.2.0 (and by extension 2.3.3.0) fixes.
[Sprint Samsung Galaxy S III] Skunk Ape1:
Here's a Odin flashable TWRP2.3.3.0 tar file for you guys to enjoy.

TWRP-recovery-2.3.3.0skunk.tar.md5 - DOWNLOAD HERE
[Sprint Samsung Galaxy S III] Anon9mouz:
Never mind but will I have all the same features as 2.3.3.0??

__________________________________________________
[Sprint Samsung Galaxy S III] Slimegod:
Where in Odin do I put this?
[Sprint Samsung Galaxy S III] Skunk Ape1:
Pda in desktop Odin and recovery in mobile Odin.

---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------

It is 2.3.3.0.
[Sprint Samsung Galaxy S III] Visionikz03:
anyone having problems mounting the usb storage? Niether card (internal nor external) will show up on my computer... didn't have the problem til i updated to the newest version...
[Sprint Samsung Galaxy S III] vMAC:
Then you must have upgraded to the TWRP with exFat support.

If you want exFat you will lose USB support, and vice versa.
[Sprint Samsung Galaxy S III] jklong03:
Seems I remember asking about this in another recovery thread and never really got an answer.

Is there any way to set the phones lower level clock? In other words, even though I have set twrp settings for my time zone, if I let the recovery set the backup name itself, the date/timestamp is way off from the actual date/time I create the recovery.

Not a big deal really as naming my backup before I create it is one of my favorite features of twrp and I always use today's date as part of the backup name anyway. Just seems like somewhere we should be able to reset the phone's "internal" clock ourselves.

Also, I have always been suspicious of the clear Dalvik function, as it completes almost instantly, whereas clear cache takes long enough that you can tell it's really clearing it. Just my paranoia or is the Dalvik cache really that small to begin with?

BTW, I am running the Goodness v6.0.2 ROM.
[Sprint Samsung Galaxy S III] evoandroidevo:
Would there be any reason that my time it off by 30 years ??? In recovery its 1980 and 5 hours off O.o any way to fix this

Seems that the guy above me has the same trouble lol

Sent From My AOKP Galaxy S III From Sprint
[Sprint Samsung Galaxy S III] vMAC:
This is a known bug, and no there is no way to fix it, that is why TWRP has the name your backup feature.
[Sprint Samsung Galaxy S III] evoandroidevo:
Okay well looks like I will have to get use to naming my backups :D

Sent From My AOKP Galaxy S III From Sprint
[Sprint Samsung Galaxy S III] Skunk Ape1:
Btw... CWM can't date it right either.
[Sprint Samsung Galaxy S III] evoandroidevo:
Yea I noticed that since i backed up stock with cwm as that's what what was put on here from rooting

So is this like a problem with the phone or just something missing in recovery?

Sent From My AOKP Galaxy S III From Sprint
[Sprint Samsung Galaxy S III] Dees_Troy:
It's a problem with all of the USA SGS3 devices & it cannot be fixed without breaking your ability to use Internet at least.
[Sprint Samsung Galaxy S III] styles420:
Is the date always off by the same amount?
[Sprint Samsung Galaxy S III] styles420:
I don't know if the offset will be the same for everyone - even if it is random, it does at least seem to remain the same between reboots. I set my TWRP time zone to UTC -4 with an offset of 15 minutes, and the display time matches my local time (which is actually UTC -7).

If everyone else can get the correct time with the same (technically incorrect) settings, then perhaps an adjustment can be made in the TWRP source so that we can set the correct time zone in order to get the correct time...
[Sprint Samsung Galaxy S III] Skunk Ape1:
Just not important for me since most people like to rename the backup with something more than a date. With twrp, the name can be chosen before the back up is named.
[Sprint Samsung Galaxy S III] styles420:
A good point, but if it is as simple as hard-coding a base offset to correct the difference, then those of us who like a time-stamped backup can enjoy the convenience of not having to enter it manually (which avoids the possibility of an unfortunate typo). And those with OCD might be able to sleep a little better, lol :p

Maybe I'll be able to take a crack at it this weekend - I've been meaning to learn the nuances of compiling source for android, so if it's as simple as my hypothesis then it could be a good starting point (while messing with the recovery is a little risky, I'm not a programming noob... and I have Odin at the ready, lol)
[Sprint Samsung Galaxy S III] reverepats:
Hey guys. This may sound totally ridiculous, but at the same time. I can't figure out WTH happened/happening here. Some inside or feedback would be so much appreciated. So a long story (in a short version I hope lol) I flashed another rom this morning to check out a particular mod. Somewhere in the confusion, it appeared that I mistakenly wipe the internal memory from TWRP. Don't remember doing that, but whatever. So I went back and forth all day between CM, TPR, and goodness. Now.....

In TWRP if I make as if I'm going to Install something from the internal memory, it shows up nothing. Completely wiped. If I boot into CM and use root explorer I can see all my old contents in the Internal memory. If I happen to boot back into Touchwiz it shows a fresh start in my Internal memory. I know I'm all over the place here, but it seems like my memory was compromised in some freaky way. I'm usually pretty good with Android lol. But I have no idea WTF is going here haha. Has anyone had anything happen like this?

I mean, it's so hard for me too explain what's going on, cause I don't really know where this all happened. Only thing I can say for sure, is after I fresh flashed the Goodness rom, I got thrown in a boot loop for some reason, booted back into TWRP and noticed this. I even loaded CWM then went back to TWRP. Any insight regarding my strange occurrence would be awesome. Thank you

EDIT... Ok, I I reloaded CWM and it does show that my internal memory is wiped. But in CM with Root explorer, I can see all my old content in my internal memory. So frikken weird. I'm so confused. Never seen this before lol. Maybe I should ditch this backup of CM and start out fresh I guess. But I still wanna find out WTF happened. It's gonna irritate the he'll out of me lol. Thanks for sitting thru my rant fellas. Be safe out there tonight, Please!

Jon
[Sprint Samsung Galaxy S III] Skunk Ape1:
The only thing I can think of, you may have hit the format data button in twrp instead of wipe data/factory reset. That will wipe your internal memory.
[Sprint Samsung Galaxy S III] reverepats:
Yeah I know. I had to have hit something. So now, if I head into the Gallery I can see 2 folders for Downloads. Which one is my internal memory. But if I go into root explorer, the folder is empty hahaha. I don't get it. Mind you, I'm back on the people's rom. No more CM. Maybe I should manually wipe the internal memory myself. Should I do it thru TWRP or with in Android? Thanks a lot bro.
[Sprint Samsung Galaxy S III] Skunk Ape1:
Just use a root explorer and delete the files and folders you don't want. No real need to wipe...
[Sprint Samsung Galaxy S III] therenegadenail:
hello all, i basically have a few quickies i hope someone can help me with, pretty much im running cwm and want to switch over to twrp pretty much for the single file backups because i dont trust myself with the blogs folder i may or may not accidentally delete

so i only have two back ups i want to keep, and i know twrp and cmw aren't capable with each other, is there a way i can flash twrp, back up, flash cwm, load my back up, flash twrp and make my other back up etc

any way to do this?
[Sprint Samsung Galaxy S III] Buddlespit:
In cwm, flash a backup, reboot system, flash twrp, reboot recovery, make backup, flash cwm, flash a backup, reboot system, flash twrp, reboot recovery, make backup, etc et all...
[Sprint Samsung Galaxy S III] swiggs98:
TWRP Backup Folder Question

When I backup TWRP to an external SDcard, it stores the backup to the following location:

/extSdCard/TWRP/BACKUPS/

"auto generated folder name"

/"backup name"

What is the importance of this "auto generated folder name?" Where did this name come from? The folder name is different than the one on my wife's S3. If I put files in another folder in BACKUPS other than this one, TWRP does not see the backups.
[Sprint Samsung Galaxy S III] Dees_Troy:
That's the serial number of the device. It's not recommended to restore a backup from a different device, but you can do what you please of course.
[Sprint Samsung Galaxy S III] swiggs98:
That makes sense. I mostly just wanted to understand this. I do, however, take a NANDROID of a fresh stock Sprint ROM I made from one device to another (mine & my wife's) with the exact same model and hardware version when I need to update PRLs, profile, or anything else that requires a TW ROM. I know I could download another TW ROM, but this was just easy. I have done this a few times now and it seems to work fine.

If I am playing with fire doing this, I will stop doing it (just let me know). I just didn't see any reason not to given my very narrow purpose.

BTW... thanks for the reply.
[Sprint Samsung Galaxy S III] runwitme:
Quick question .. so to do a nand is just using the backup correct? .. im just on the stock rom on my gs3 that is just rooted . Was just wondering because i did a back up and its 2gb . Thats a lot for a nand . Is the stock jb rom that big?
[Sprint Samsung Galaxy S III] Evilone69tmg:
Yes. I did a backup of my stock rom after rooting and the size of it is 1.32gb.
[Sprint Samsung Galaxy S III] Notorious:
I didnt even make a stock backup :p first 10min I got the phone I was on Aokp :p
[Sprint Samsung Galaxy S III] Evilone69tmg:
LOL. It took me 2 days then was bored with stock. Not sure why I even still got that backup. Going to delete it now. :laugh:
[Sprint Samsung Galaxy S III] NYCHitman1:
My phone wasn't even activated before it was rooted and ROM'd. Slapped AOKP on it as well, but moved to greener pastures shortly after.
[Sprint Samsung Galaxy S III] sleekgreek:
works good
[Sprint Samsung Galaxy S III] xblackvalorx:
Latest version isn't picking up my internal storage right at all
[Sprint Samsung Galaxy S III] Jamin13:
Check if you have a 0 folder somewhere in the internal storage.
[Sprint Samsung Galaxy S III] xblackvalorx:
I do indeed but it won't delete. What do I do?
[Sprint Samsung Galaxy S III] reverepats:
Last resort for me was copying the original stuff from my Internal, then formatting. You flashed a 4.2 ROM correct? It's cause by the new multi user feature in there. Head to the CM thread and go back to Thursday or Friday posts. Someone post a link to root wiki that's spoke about it. It's F up, so I won't do that again.