yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] mdcarter67:
I don't see the Note 3 list as a supported device on the TeamWin site. How do i download it?
[T-Mobile Samsung Galaxy Note 3] deeznutz1977:
Its not up yet sorry i have a uncompleted/ not the way they want test version
[T-Mobile Samsung Galaxy Note 3] bp328i:
So are saying you have a custom recovery on your phone? That would mean the bootloader is not locked, which is great news!
[T-Mobile Samsung Galaxy Note 3] bigbiff:
OK Guys it's up!
[T-Mobile Samsung Galaxy Note 3] bigbiff:
That's correct. ATT remains to be seen.
[T-Mobile Samsung Galaxy Note 3] deeznutz1977:
yup rooted and twrp.. so no lock
[T-Mobile Samsung Galaxy Note 3] bp328i:
let the fun begin!!!!!
[T-Mobile Samsung Galaxy Note 3] Diablohtr:
Backup and restore functioning correctly?

I know international CWM was having issues?
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Let us know. Please pull /tmp/recovery.log if you have issues and paste it at http://paste.tinyw.in.
[T-Mobile Samsung Galaxy Note 3] paul89:
Omg this is so exciting, I was worried for minute there...
[T-Mobile Samsung Galaxy Note 3] deeznutz1977:
Bigbiff should i flash the one in the op.\

\ or is the one from irc ok
[T-Mobile Samsung Galaxy Note 3] bigbiff:
It's the same build afaik.
[T-Mobile Samsung Galaxy Note 3] BACARDILIMON:
ok so before this i did cwm recovery. how do i get twrp on it
[T-Mobile Samsung Galaxy Note 3] Diablohtr:
Just follow the instructions, it will overwrite CWM
[T-Mobile Samsung Galaxy Note 3] combatmedic870:
Thanks for the quick recovery!!
[T-Mobile Samsung Galaxy Note 3] Steve Lazarus:
Yeah, I'll root the new one on Tues, but that's about it for now.... Might even wait on that, at least until I get all my stuff settled in over in Vegas. Might start throwing red flags if I have to call T-Mob again so soon with issues....lol :p
[T-Mobile Samsung Galaxy Note 3] janjannsen99:
So I have 2.6.3.1 installed now and general consensus would be to hold off for now on flashing any more recoveries right?

Also does anyone have the stock recovery .zip or tar file?
[T-Mobile Samsung Galaxy Note 3] glensta:
You might want to wait until you get to Vegas to root your phone. Just a thought. This phone is a beast and even stock it's really nice to play with
[T-Mobile Samsung Galaxy Note 3] DataHawg:
I agree that it isn't a great idea to try to restore stuff with TM onto a new phone. Especially if the Android version is different. We had problems restoring Nandroids with CWM on the Epic 4g Touch (Sprint GS2) after new custom kernels were built without the emmc brick bug. The only thing that worked for us was to do a full wipe in recovery, flash the bare rom that you were wanting to restore, let the phone boot and skip the setup stuff, then boot back to recovery and run restore from CWM. That fixed the problem and I always did it that way after that. If anyone really needs to restore a backup because something got borked give it a try.
[T-Mobile Samsung Galaxy Note 3] turilo:
Well not sure if you guys know yet, but seems even some apps from the play store will cause a bootloop
[T-Mobile Samsung Galaxy Note 3] Pandemoniumone:
Do you know which ones exactly at this point? We should get a list going...
[T-Mobile Samsung Galaxy Note 3] turilo:
So far not sure it's like you have to do one at a time and reboot just to check :/
[T-Mobile Samsung Galaxy Note 3] chrisa887:
http://xdaforums.com/showthread.php?t=2465764
[T-Mobile Samsung Galaxy Note 3] BACARDILIMON:
That is what I am on and if it works stay with it

NOTE 3
[T-Mobile Samsung Galaxy Note 3] janjannsen99:
Ok so where's the recovery. That's the entire firmware.
[T-Mobile Samsung Galaxy Note 3] chrisa887:
im sorry i thought you wanted the firmware lol dont think there is a stock recovery. maybe if you unroot it by odining back to the stock firmware the stock recovery might be back on it. at least it would make sense anyways lol
[T-Mobile Samsung Galaxy Note 3] janjannsen99:
Maybe I can download that and find the recovery within the file. I have a 2nd note 3 I will test on....just don't like the idea of bricking anything. In my whole flashing life I haven't bricked one and I really wouldn't be able to live with my self bricking the best phone ever released lol. Thanks for that anyways it's a start. It has to be in there somewhere right?

I'll be ready when mskip releases his toolkit....makes things safe and painless.

---------- Post added at 12:26 AM ---------- Previous post was at 12:25 AM ----------

Well I haven't used it for ANYTHING yet as fearing the bad consequence.
[T-Mobile Samsung Galaxy Note 3] Warrior1975:
I think I have the stock recovery image, not 100%. I had to reinstall windows last night, it may have been on that computer. I'll check tonight when I get home.

sgh-TWEAKED-889©
[T-Mobile Samsung Galaxy Note 3] Steve Lazarus:
Correct, once you Odin back to stock, you still have a recovery, you can

Update from ADB

Update from EXT Storage

Wipe Data/Factory reset

Wipe cache partition

Apply update from cache
[T-Mobile Samsung Galaxy Note 3] HughesNet:
Not very helpful if that is all you have. I haven't seen this.
[T-Mobile Samsung Galaxy Note 3] turilo:
Well be like all other minions and test for yourself
[T-Mobile Samsung Galaxy Note 3] HughesNet:
There is nothing to go on to test any thing. Just a vague note that maybe some unnamed apps on the play store cause boot loops. Useless except to spread paranoia.
[T-Mobile Samsung Galaxy Note 3] turilo:
Install a bunch of apps then reboot your device and let us know. Now don't reply unless you have something proper to say, instead of trolling the thread. Thanks
[T-Mobile Samsung Galaxy Note 3] HughesNet:
I have over 100 installed with no issues. You want to talk about not posting unless you have something to say? That is my problem with your post. Serves no purpose as you are spreading a rumor you have not even verified without even an app name. Your post can serve no purpose but to scare people needlessly. Now be a hypocrite and reply to this.
[T-Mobile Samsung Galaxy Note 3] vagelis:
Correct me if I'm wrong, but I think 2.6.3.2 is unable to select the external storage.
[T-Mobile Samsung Galaxy Note 3] Mike B.:
Not quite true. I routinely use a Note 3 with a 128GB microSDX formatted as exFat with full read/write access (including from TWRP2.8.6.0), as well as a spare Note 3 with a 64GB card also formatted as exFAT. Obviously, you need a kernel that supports exFAT (not all do) but there's no intrinsic hardware incompatibility. I have no experience with (or funding for!) 200GB cards and can't comment on those.
[T-Mobile Samsung Galaxy Note 3] Apo11on:
I've researched the issue extensively back in the day, have read plenty of articles and forum threads, in addition to trying several cards, formatted into exFAT and other formats myself. You're the first person ever I hear from, saying this... Regardless of what you've been able to do - it doesnt work for me, and all other people I've heard from, and never has. Including this 200GB card in question. Therefore, we need a recovery solution, which supports 200GB cards, formatted into FAT32.

As far as being able to afford 200GB card - very soon they're gonna be dirt cheap thanks to Microdia
[T-Mobile Samsung Galaxy Note 3] Mike B.:
Oh I too have seen lots of things online, including articles and forum threads, not all of which are necessarily accurate! ;)

Apparently you're satisfy with your current FAT32 compromise so there's no point pursuing the matter. I merely wanted to point out that >= 64GB cards can be successfully formatted as exFAT for use on a N900T, at least when proper firmware and software support (I use leanKernel-hlte-3.17 on the KK phone) is provided.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
My stock Note 3 recognizes exFat cards, but the 64GB and greater take too long to mount (about a minute) so I stick with 32GB, which mount instantly.

Frank
[T-Mobile Samsung Galaxy Note 3] Apo11on:
Mike & Frank: your experience is not common. For vast majority of the people exFAT doesnt work for sdcards, larger than 32GB. Reports about it are all over XDA and internet. You may have some odd, unusual rom/kernel/hardware configuration, where it works, but I think correcting me, saying "it's not true" and "it works" is counter productive, because it might mislead the developer, who may think all I have to do is reformat the card with different file system and the problems will go away, which is not the case. I'm glad it works for you, but it doesnt for the majority of the people. That's not a speculation, but an established fact based on solid research and that's what matters. TWRP needs to be fixed to support large capacity sdcards, formatted into FAT32 because everyone, besides rare exceptions like yourselves, is using FAT32 with 64GB or larger cards.

[MENTION=4698029]Mike[/MENTION]: did you register that 2nd nick "954wrecker" to follow you around and thank your main handle for every post, even in cases where it's most inappropriate and makes no sense, just to boost your Thanks count? :laugh:
[T-Mobile Samsung Galaxy Note 3] Mike B.:
This is getting plain silly. I'm sorry to hear you have SD Card problems, but you should stick to facts. The example link you provided earlier to back up your claims of incompatibility is completely unrelated to the Note 3, or even Samsung devices in general, casting some doubt on the validity of your "research". I would encourage you to try and establish a civilized exchange of ideas and suggestions with those of us who successfully use exFAT, but it appears that you are not interested.

On a more personal note, I would like to point out that having concurrent multiple identities is against XDA rules and that my Thanks count is simply due to the members who are kind enough to thank me for various posts that they apparently found useful. I see that your own thanks-to-posts ratio is quite a bit lower, but that really matters very little on here, except perhaps for having a slight impact on general credibility. That said, let's stay away from such trivial issues, please.
[T-Mobile Samsung Galaxy Note 3] Mike B.:
Let's cut to the chase in order to help members get to the facts:

The link you provided, labeled "this one", in your post #1980 refers to the

Xiaomi Mi Pad

, a specific device that has no bearing on Note 3 matters, Samsung devices, or even Android in general.

The people at

Samsung

, who presumably know a little bit about the Note 3, tell us that MicroSD Cards 64GB and larger can and should be formatted as exFAT as you can see

THERE

(check under "what format should you put microSD Cards into?").

You are correct about one point: you joined XDA before I did, but there's a possibility that I might have a bit more experience with both the Internet and Android, even though this is not germane to the matter at hand.

I'm sure [MENTION=2638973]bigbiff[/MENTION] will seek your advice to improve the TWRP recovery if he so chooses.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
OK, I guess sdcardfs must be a fuse mounted thing. I assumed you had some alternative fs in use, not fat32.

Please do the following (I don't care about your previous technical discussion btw) in TWRP:

mount -t vfat /dev/block/mmcblk1p1 /sdcard

dmesg > /tmp/dmesg.txt

adb pull /tmp/dmesg.txt

Post dmesg.txt here.
[T-Mobile Samsung Galaxy Note 3] Mike B.:
[MENTION=2638973]bigbiff[/MENTION]:

If it helps, here are relevant(?) portions of the output from the 'mount' command from within a TWRP 2.8.6.0 (hltetmo) recovery that allows full read/write access to a 128GB SD Card formatted as exFAT on a SM-N900T (tmo Note 3). Another N900T with the same recovery performs equally well with a 64GB exFAT card.

/dev/block/mmcblk0p25 on /data type ext4 (rw,seclabel,relatime,data=ordered)

/dev/block/mmcblk0p25 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)

/dev/block/mmcblk0p24 on /cache type ext4 (rw,seclabel,relatime,data=ordered)

/dev/block/mmcblk1p1 on /external_sd type exfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro)

/dev/block/mmcblk0p23 on /system type ext4 (rw,seclabel,relatime,data=ordered)

For reference, here's the similar 'mount' output from within a rooted TouchWiz 4.4.2 ROM on the same device, still allowing full rw access.

/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0

/dev/block/vold/179:65 /mnt/media_rw/extSdCard exfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 0 0

/dev/fuse /storage/extSdCard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

In both cases, the kernel is LeanKernel 3.17 for hltetmo. If you need more (dmesg?), just ask and I'll try later on today. ;)
[T-Mobile Samsung Galaxy Note 3] Apo11on:
I tried to generate and collect dmesg several times, but there is nothing in this kernel log file about this mount attempt. I believe it's because the mount command above fails with the following output:

mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: Invalid argument

Also, sdcard folder does exist, so mkdir sdcard fails. Attaching dmesg anyway - maybe you'll see something I missed. I appreciate your time looking into this. Soon 200GB cards will be more common and a lot more people will discover this issue.
[T-Mobile Samsung Galaxy Note 3] Mike B.:
Since the recovery already mounts something as /sdcard (the internal emulated SD Card, 29.1GiB on mmcblk0) as expected on our devices, a better test command for a vfat physical partition at mmcblk1p1 (already recognized as SDXC 183GiB in your dmesg) would be:

mount -t vfat /dev/block/mmcblk1p1 /sdcard1​

or

mount -t vfat /dev/block/mmcblk1p1 /extSdCard​

( try or simply ignore )
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
[MENTION=1192060]Apo11on[/MENTION]:

You are in a Note 3 forum and it appears to me that you are discussing problems with some other device; perhaps that is why your confusion about device capabilities.

Frank
[T-Mobile Samsung Galaxy Note 3] Apo11on:
You seem to be confused. I have T-Mobile Note 3 hltetmo and this thread is about TWRP recovery for this phone. I am discussing TWRP for hltetmo issue, and there are no other devices involved. External sdcard is one of the partitions, TWRP supports and is supposed to be able to mount.

---------- Post added at 02:23 PM ---------- Previous post was at 02:09 PM ----------

I tried creating both folders you suggested (not that the name matters) and both mount attempts failed with the exact same "Invalid argument" message. Syntax probably wrong, something with the flags or vfat simply not supported
[T-Mobile Samsung Galaxy Note 3] toastido:
FWIW I've used my exfat formatted 128gb SD with TWRP without issue since at least October of last year when I got the card. Both stock and lean kernels.

Just another data point for the Note 3.
[T-Mobile Samsung Galaxy Note 3] Apo11on:
Any ideas? Would appreciate some suggestions - I'm out of ideas and need to get this to work. Don't have enough space on internal sdcard to be able to do in recovery what I normally do.
[T-Mobile Samsung Galaxy Note 3] Mike B.:
Make sure to try with the current LeanKernel (3.17 for KitKat). Your logs show that the card itself

is

properly recognized (183GiB) but not the partition on it. Since your extensive signature says you have a P900, a device that has the same basic SDXC capabilities, you could also try the 200GB in that. Why you can't even access a 128GB exFAT partition is puzzling, but even if you want to use FAT32, reformatting the 200GB card

in the device

itself is worth a try.

EDIT:

Have you tried the latest TWRP 2.8.7.0 (twrp-2.8.7.0-hltetmo-4.4.zip) released a short while ago? I see nothing obvious in there that would relate to your SD Card issue, but it can't hurt to update.
[T-Mobile Samsung Galaxy Note 3] Apo11on:
Problem solved

I finally fixed the issue. I've examined the partitioning of the card using a good partition manager app and found out there was some unallocated space in the size of 7.9Mb in the beginning of the sdcard. Also, the FAT32 partition was created as logical, not primary partition on the card. Logical partitions by definition cannot be located at the beginning of the hardware space on a disk/sdcard - that's why there was unallocated space in the beginning of sdcard. After converting that FAT32 partition to primary, the partition manager app let me resize it to full size of the sdcard, eliminating that unallocated space. As soon as I did that TWRP started recognizing the sdcard with no issues.

I think there are 2 lessons to be learned here, one for me and one for bigbiff:

- I need to make sure to properly format sdcards before use

- TWRP code needs to be modified, to account for cases, where file system on sdcard represents logical partition instead of primary, which means the actual size of the partition on the sdcard does not equal the size of the sdcard. TWRP needs to handle cases, where first physical block of the sdcard does not equal first block of the partition with file system.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
We can scan for all the partitions on the device and know what they are. That's why we need recovery.fstab
[T-Mobile Samsung Galaxy Note 3] Mike B.:
This is great news but I'll add one last unrequested comment for future reference: Now that we understand what the problem was, it seems that your woes might have been completely eliminated had you simply (re)formatted the card

in the phone

(exFAT or FAT32) as opposed to relying on the factory format or external utilities (even the SD Association's own SDFormatter). I know it shouldn't be required in theory, but it often is.

In any case, congratulations! ;)
[T-Mobile Samsung Galaxy Note 3] Apo11on:
Is there an action item for me here? Do you need me to send something over?

---------- Post added at 11:24 AM ---------- Previous post was at 11:04 AM ----------

I already said the card came pre-formatted in exFAT and did not work in my phone out-of-the-box, as expected. So, I had no choice but to format it outside the phone into another file system. When formatting the card in the phone, the native android partitioning utility doesn't give you a choice of file system - it always formats into exFAT. So, your suggestion to format it into FAT32 in the phone is not feasible, and formatting it back to exFAT doesnt make sense because the card already came pre-formatted into exFAT and didn't work. Also, you're overlooking one very important detail: I didnt discover that TWRP cannot see the card until some time after I started using it, and I already filled it up with all my files and data. That 200GB card is almost full, and fomatting wipes it, so I'd have to back it up and restore it for each format attempt - that's transferring nearly 400GB of data to/from PC over USB connection....That is quite an undertaking, takes a LONG time, so before you suggest for me to routinely try formatting in all kinds of places and file systems - take into account it's not a 5 minute breezy job - each such attempt requires backing up/restoring 400GB of data, which is quite a project.
[T-Mobile Samsung Galaxy Note 3] Mike B.:
I though we were done, but I guess not...

I can now confirm that a SanDIsk 200GB SDXC formatted as exFAT works just fine with TWRP 2.8.6.0 and KK 4.4.2 on a N900T. A contact of mine was kind enough to temporarily test a card he uses in some lab equipment. It was formatted as several ext4 partitions, so he let his N900T reformat it (exFAT) and it worked instantly with read/write access under both his 4.4.2 ROM (rooted stock) and TWRP 2.8.6.0.

Perhaps the root of your woes was the assumption that because the factory format was supposed to be exFAT, letting your phone reformat it as exFAT would be pointless. In retrospect it's clear that checking for full compatibility before filling up the card would have been preferable, and that following the common advice to always first format in the target device might have saved lots of headaches, but the mistakes we make can be great opportunities for learning... ;)

There is no clear indication that TWRP was somehow at fault or needs to be modified. Even if TWRP could be made to recognize unusual partitioning schemes, it would be pointless if a system boot can't. I hope we can now return to discussing germane TWRP matters... ;)
[T-Mobile Samsung Galaxy Note 3] Apo11on:
I will address each one of the above quotes one at a time.

1. I thought "we" were done too, and yet after I reported the problem was resolved you felt the need to post your comments "in retrospect", which contained incorrect assumptions I'm about to clarify *once again* for you, and were downright condescending. First, when I say "we" - it's not the same "we" you mean - I mean bigbiff & myself, because *we* were working on this issue long before you interfered. Your continued interference was unwarranted, unwelcome and still is. So for us (this time when I say us I mean you and I) to be "done" you need to stop something you should not have started in the first place.

2. What you continue to fail to understand is that when I say "the card didn't work" it means the phone did not see it, at all. Therefore, your suggestion to format it in the phone (into exFAT or whatever) makes no sense - you cannot format something that doesn't exist. The phone did not detect the presence of sdcard in any way, shape or form. Therefore, the only choice I had is to format it externally, outside the phone. And as I stated already many many times before - based on a solid research, hands on previous experience and testimonies from many other large sdcard users, exFAT is the wrong choice for file system on cards, larger than 32GB and FAT32 is the right choice. I believed it then and I know now for fact that FAT32 works fine.

3. Your statement that there is no clear indication TWRP is "somehow" at fault and needs to be modified could not be more wrong, and it astounds me how could anyone arrive to that conclusion, when I posted information, which is a clear evidence to the contrary. File system type aside, I just said I tested that when sdcard is formatted with logical partition, thus not occupying the full sdcard space and has empty, unformatted space in the beginning TWRP does not see it. When the same sdcard, using the same file system, has primary partition on it, occupying the full sdcard space (first block of the card matches first block of partition) TWRP sees the card just fine. I also clearly indicated that there is no issue in Android with both formatting styles and whether the partition is logical or primary - Android sees it just fine. Calling a basic logical partition an "unusual partitioning scheme" only demonstrates your inexperience and lack of knowledge in hardware partitioning and in no way represents the truth. In fact, there are *a lot* more logical partitions on hard drives, solid state drives and other types of eMMC memory than primary partitions, because each drive can have only 1 primary partition and unlimited number of logical ones. Since both configurations are common, Android works fine with both and TWRP only sees cards with primary partition and matching HW block IDs - it could not be any more clear the recovery lacks support for sdcard configurations with only logical partition on it. To me, the need to add that support is apparent, because contrary to your unfounded statement, such configuration is not uncommon, but it's the developer's decision of course.