Develop Bugs

Tab 3 10.1 help with 64gb micro sd

OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app

you MIGHT have better luck if you format the SD card in some other file system. Other than that I'm not sure
You could buy an 8 gig one and swap it too

DopeShow said:
OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app
Click to expand...
Click to collapse
Have you tried both recoveries? CWM and TWRP if neither work you may have to format to fat32.
Sent from my GT-I9505 using XDA Premium 4 mobile app

Yes I've tried every recovery out there and with cwm it does this count down from 10 that says connecting then after it gets to 1 it says aborted because it cannot mount the micro SD and yes its formated to fat32 and I've tried exfat and every other format nothing works, and in my first post when I said I couldn't root from the micro SD I mean by going into cwm and loading zip file from there it does the same thing and says it can't connect, that's why everytime I root my device this way I have to borrow a 32gb micro SD and everything works fine
Sent from my GT-P5210 using xda app-developers app

Same problem with my 64g card. MY 16g works great. Cant seem to get the 64g formatted in either my phone or the Tab3. I can sometimes get the Tab3 to recognize the card and it will show the files on the memory card but once I go into recovery there is nothing there.

My 64gb card is recognized while the device is in regular running mode like I can go into settings and then storage and see the card there and how much space is used and free the Only time the card doesn't work right is when I'm in recovery mode because for some reason in recovery mode the system says it can't mount it and that is my whole problem, I need a way to fix it so my 64gb card can be mounted and used while in recovery mode.
Sent from my GT-P5210 using xda app-developers app

It's either a recovery issue or a driver/kernel/bootloader issue, a case that the Tab 3 10.1 development is far from being active.
It looks like it can't allocate space that exceeds 32GiB.
Also wrong thread.

Trying formating your SD card on the computer to fat32 or extfat .
Sent from my GT-I9505 using XDA Premium 4 mobile app

I've already done that and the card works fine example in the device it only stops working in cwm recovery saying it can't be mounted
Sent from my GT-P5210 using XDA Premium ANDROID Developer's App

Thread cleaned of off topic posting and unnecessary non-related junk.
(yes, we can do this)
Any more silly ridiculous junk posted, and this thread will be closed permanently.
If the OP wants to keep this in open forums, we cannot prevent this and welcome the debate, as it seems fitting.
Cheers
MD

My thoughts...
Running the tab in normal mode allows the 64gb card to be read. However, if you start in CWM or TWRP recovery, you are no longer in the "normal" mode and the tab does not recognize the 64gb card. In recovery mode, it is possible that the memory allocations are limited where as in normal mode, 64gb is OK.
In this case, for rooting, maybe you should load the root file on internal memory and not the memory card. I use 4gb cards and neither CWM or TWRP could work with them. I think the issue is in the recovery programs and not the Tab, save for memory limitations set by the base firmware.
Again, JMHO and I may be way out in left field here.

TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.

GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
yes ive tried multiple recovery's and they all do the same thing and cannot read the 64gb micro sd and yes I have my sd formatted to fat32 and I am on windows on my laptop but I can format the micro sd to ext3 or 4 but my question is, if I do that and its formatted to ext3 will I still be able to access my tablets drive space through my laptop like I can now with it being on fat32, because if I cant then that would be pointless for me to do because then I wouldn't be able to add and take things off my sd while its in my tablet., also I said in my first post that this problem doesn't happen using a smaller micro sd like 32 or smaller it only happens with the 64gb, so it has to do with the size some how

GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
also IDK if you know this but there isn't many recovery's out there for the galaxy tab 3 10.1 the only one I use is bindroid_cwm_p5210_santos10wifi and even with this recovery it has a slight lag to it when using it.

[Q] Disable USB Mass Storage detection in recent firmwares

Title says it all. Is there any way to disable this? I'm using StickMount on a rooted FTV and every time it restarts for any reason the USB detection dialog pops up asking if you want to format the USB storage (my drive is NTFS so the native USB storage support can't read it, hence it wants to reformat it).
Obviously this makes me rather nervous... I just want to disable the dialog (or whatever it would take to stop it from popping up - I don't want or need the horribly limited built in support).

I use a hub to get around this issue, but it works to my advantage: I can relocate FTV apps to the FAT32 USB. Or you can make a small FAT32 partition in your USB and the rest is NTFS to make FTV happy.

cd2022 said:
I use a hub to get around this issue, but it works to my advantage: I can relocate FTV apps to the FAT32 USB. Or you can make a small FAT32 partition in your USB and the rest is NTFS to make FTV happy.
Click to expand...
Click to collapse
Really strange things happen here.
When I put my 64gb sandisk stick into fireTV and let him format it, there will be right problems with FolderMount. For example FolderMount can not create a folder on the exStorage. So I decide to format it with hp storage format tool to a FAT32 64gb stick.
No the pop-up comes again but stickmount and FolderMount work fine again.
Is there no way to disable this stupid dialog?
Greetings by I_did_it_just_tmrrow
EDIT: MySolution
I format my stick into 2 partitions.
First you need to create one (small or big partition, like you need it) in fat32.
The rest into none or raw, but just not fat32.
Then put into you AFTV and let him create his ****.
Then back into a linux based lapto/pc and start gparted or your fav partition tool.
Make the rest to an secend fat32 partition.
Put into it again and mount stickmount the hole stick.
You should get sda1 & sda2.
One is controlled by your aftv, the secend is yours.
Now you can use apps like FolderMount and make mounts like puttin data/media/obb -> to your own (mostly it is sda2) stick partition. Works nice in my case.

Flashing new ROM on a shared internal storage SM-P605 - Solved

I looked everywhere before I tried this today and found very little info so I thought I'd post my successful dirty flash of LineageOS.
I've been using Unofficial LineageOS on my Note 10.1 (2014) LTE (SM-P605) for a little while now and it has rejuvenated my tablet. Recently I integrated the SD Card (64GB) to internal storage (16GB) and now storage is listed as 73.15GB. However updating LineageOS became a problem in TWRP 3.0 as TWRP doesn't see the 'downloads' folder etc... because the SD Card is no longer external storage and TWRP can't read it, doesn't see it as storage at all actually.
But I solved this by putting the OS and vendor images on a USB drive and used an OTG adapter which TWRP can use. ADB and Fastboot work fine, by the way, with the SD Card as internal storage. As I understand it the ROM, system, vendor, radio, bootloader partitions etc... are still on the 'real' internal storage so my updates have gone smoothly AND I save storage space by not putting the ROM's etc on my device. I run a rooted device so I can set the kernel to permissive and that way the SD Card is recognized on boot as shared storage. Sometimes on reboot it isn't recognized and I have to take the card out and reinsert it to get LineageOS to read it correctly. The only error if that happens seems to be dropbox and photos apps crash at first as they must check the missing area for files at boot. But they work correctly once the card is reinserted.
YMMV
Linuxmon
In my system settings 'storage' is listed now as:
Internal shared storage - 9.93GB used of 14.68GB,
Sandisk SD Card - 14.51GB used of 58.48GB.
For a total of 73.15GB
Running Lineage 14.1-20170422-Unofficial-lte03lte
with latest radio, vendor, bootloader and gapps (Bean, mini).
As a side note; back up your internal storage encryption key on another device so you can decrypt your SD Card later if needed. Just sayin'
https://android.stackexchange.com/questions/145443/how-to-decrypt-adopted-storage

Linuxmon said:
I looked everywhere before I tried this today and found very little info so I thought I'd post my successful dirty flash of LineageOS.
I've been using Unofficial LineageOS on my Note 10.1 (2014) LTE (SM-P605) for a little while now and it has rejuvenated my tablet. Recently I integrated the SD Card (64GB) to internal storage (16GB) and now storage is listed as 73.15GB. However updating LineageOS became a problem in TWRP 3.0 as TWRP doesn't see the 'downloads' folder etc... because the SD Card is no longer external storage and TWRP can't read it, doesn't see it as storage at all actually.
But I solved this by putting the OS and vendor images on a USB drive and used an OTG adapter which TWRP can use. ADB and Fastboot work fine, by the way, with the SD Card as internal storage. As I understand it the ROM, system, vendor, radio, bootloader partitions etc... are still on the 'real' internal storage so my updates have gone smoothly AND I save storage space by not putting the ROM's etc on my device. I run a rooted device so I can set the kernel to permissive and that way the SD Card is recognized on boot as shared storage. Sometimes on reboot it isn't recognized and I have to take the card out and reinsert it to get LineageOS to read it correctly. The only error if that happens seems to be dropbox and photos apps crash at first as they must check the missing area for files at boot. But they work correctly once the card is reinserted.
YMMV
Linuxmon
In my system settings 'storage' is listed now as:
Internal shared storage - 9.93GB used of 14.68GB,
Sandisk SD Card - 14.51GB used of 58.48GB.
For a total of 73.15GB
Running Lineage 14.1-20170422-Unofficial-lte03lte
with latest radio, vendor, bootloader and gapps (Bean, mini).
As a side note; back up your internal storage encryption key on another device so you can decrypt your SD Card later if needed. Just sayin'
https://android.stackexchange.com/questions/145443/how-to-decrypt-adopted-storage
Click to expand...
Click to collapse
I just recently bought a demo mode 605 model and can't seem to get booted into twrp. It puts me at the yellow triangle. Do you have any tips, please.
Sent from my SM-P605V using Tapatalk

I have a problem with my pixel 2 xl and can't figure out why

My issue is connecting to an usb-c flash drive. My usb-c flash drive is Samsung 128gb. It works half of the time. What I mean is it works when I am home and not at work.
Right now work.
I plug my flash drive in to my pixel 2 xl.
ES file manager comes up
Show my usb drive with capacity then disappear
I got notification bar and pick transfer file
My flashdrive show up and disappear again
I have also tried ptp, midi, charge, and supply power. Same thing happens, show and disappear
I enable developer options.
I tried both enable and disable usb debugger
I tried selecting usb configuration from mtm to ptp.
I have an applocker app. I disable it and enable it.
I disable and enable smart lock
Google tech asked me to use their usb adapter. It works when I am home.
When I am home, I have no issue. my usb flash drive works fine.
I hope this is not similar to that star trek card game that Capt Kirk invented, Fizzbin. It aian't tuesday.
does anyone have any idea I can try?
Maybe I missed something.
maybe I enable something I shouldn't have
I am able to connect to a computer fine.
If I left the usb connected and restart, I get "still rejecting Samsung USB drive. Don't remove."

Hmm... are you saying your PHONE recognizes the OTG drive at home but not at work? Are you rooted and have tried StickMount? Sounds more like a drive going bad or a formatting issue and its just working half the time. How is your drive formatted btw? FAT32? You probably already know Android doesn't support NTFS. Also for the record, ES File Explorer is a serious P.O.S. Do yourself a favor and get Solid Explorer. It goes on sale around Xmas time and is worth every penny.

I do have solid explorer. I need to change the default to Solid. I used my phone to format my flash drive. Everyday at work is the same. Doesn’t work before 4:xx pm and works after that. Today I tried a 256 gb with an adapter and it was working (4:4x). After that i put in my samsung 128gb usb-c and it works. Both doesn’t work in the morning or before 4:xxpm.
My phone is not rooted.

Cyc323 said:
I do have solid explorer. I need to change the default to Solid. I used my phone to format my flash drive. Everyday at work is the same. Doesn’t work before 4:xx pm and works after that. Today I tried a 256 gb with an adapter and it was working (4:4x). After that i put in my samsung 128gb usb-c and it works. Both doesn’t work in the morning or before 4:xxpm.
My phone is not rooted.
Click to expand...
Click to collapse
I asked how the drive was formatted, meaning what file system it was formatted to? You said you used your phone to format the drive, but the question still stands... Is it formatted with FAT32, exFAT , Ext3 / Ext 4? Whatever it is, use a PC to reformat it to a different one of these supported file formats. Try exFAT first. The whole "time" thing has no bearing on this whatsoever. It is either a hardware issue with the Samsung or a formatting issue with the drive. Note: please use the "Reply" button so I get notified when you respond.

v12xke said:
I asked how the drive was formatted, meaning what file system it was formatted to? You said you used your phone to format the drive, but the question still stands... Is it formatted with FAT32, exFAT , Ext3 / Ext 4? Whatever it is, use a PC to reformat it to a different one of these supported file formats. Try exFAT first. The whole "time" thing has no bearing on this whatsoever. It is either a hardware issue with the Samsung or a formatting issue with the drive. Note: please use the "Reply" button so I get notified when you respond.
Click to expand...
Click to collapse
I am sorry for not responding back sooner.
I tried to format my usb to exfat, but my phone said it doesn't support that and need to reformat it. It reformated my flash drive to fat32

yeah I have a 256GB Sandisk Dual M3.0 OTG drive and my Pixel 2 XL always format the drive to FAT32 and can't support FILES larger than 4GB.
Are there kernels out there that support exFat for the Pixel 2 XL???

Question Connecting SSD drive

I have a SSD I format it in NTFS and plug it into the phone, it tells me that there is an issue with the drive.
So I format it with phone. Then plug it back into PC and it says it formatted it to Fat32, this makes it impossible to move any video to it.
My main idea was to use it for backup of pictures and video.

eracet said:
I have a SSD I format it in NTFS and plug it into the phone, it tells me that there is an issue with the drive.
So I format it with phone. Then plug it back into PC and it says it formatted it to Fat32, this makes it impossible to move any video to it.
My main idea was to use it for backup of pictures and video.
Click to expand...
Click to collapse
You done it in a wrong way. Sadly, Android devices don’t support NTFS format by default, you have to do it manually. Depends on whether your phone is rooted or not, it has different ways. Without root, use Total Commander to do it, with root, you get more choices. I didn't do it for a long time so can't tell just by memory. You can Google it and there should have a lot information you can get from the web for how to enable NTFS format in Android.

I am rooted, but have not seen a way to do it. Most say Total Commander or Paragon. Searched around web. Some of the threads are super old. And having issues finding ways to do it with Rooted device.
There is no Magisk modules anymore. Will keep looking.

format your ssd as exfat. works for both the computer and phone, and supports files over 4gb

mercenaryhmster said:
format your ssd as exfat. works for both the computer and phone, and supports files over 4gb
Click to expand...
Click to collapse
That doesn't work.
From what I read , it seems Pixel 6 Pro does not support those formats. and you have to do work arounds to get it done.
Still working on those

Correct, Pixels never support ExFAT natively. There "may" be others way to use it on Pixels now, but I'm satisfied now that after all these years of having Pixel phones I bought the full Paragon deal: exFAT/NTFS for USB by Paragon Software. It's not ideal, but it works, and paying for the full deal gets me both ExFAT and NTFS (among other things that I probably don't care about).
I still use X-Plore File Manager to access the external storage through Paragon's app.

exFAT is natively supported on Android 13, at least for Pixel devices. I have a USB NVME drive that's formatted as exFAT and my Pixel 6 Pro running the latest Android 13 beta recognises it natively with full read/write access.
Some more details: https://blog.esper.io/android-dessert-bites-27-exfat-on-pixel-532176849/

craigacgomez said:
exFAT is natively supported on Android 13, at least for Pixel devices. I have a USB NVME drive that's formatted as exFAT and my Pixel 6 Pro running the latest Android 13 beta recognises it natively with full read/write access.
Some more details: https://blog.esper.io/android-dessert-bites-27-exfat-on-pixel-532176849/
Click to expand...
Click to collapse
Oh yeah! Thanks for that reminder. I'm so looking forward to that native capability.

roirraW edor ehT said:
Correct, Pixels never support ExFAT natively. There "may" be others way to use it on Pixels now, but I'm satisfied now that after all these years of having Pixel phones I bought the full Paragon deal: exFAT/NTFS for USB by Paragon Software. It's not ideal, but it works, and paying for the full deal gets me both ExFAT and NTFS (among other things that I probably don't care about).
I still use X-Plore File Manager to access the external storage through Paragon's app.
Click to expand...
Click to collapse
Did that program and it mounted it, but accessing is an issue. Not sure if I am doing it right,
For some reason it keeps asking to use total commander

eracet said:
Did that program and it mounted it, but accessing is an issue. Not sure if I am doing it right,
For some reason it keeps asking to use total commander
Click to expand...
Click to collapse
I know it suggests Total Commander, but there's an option somewhere in there where I could get Paragon's access listed in X-Plore File Manager, which I prefer.
It's possible I didn't have to do anything special in the Paragon app - it's not too often I have to use it. It might have been just using X-Plore File Manager's ability to customize what mounted "drives" it listed, and adding Paragon from the list of available drives - after I already mounted the actual drive through the Paragon app.

I've partitioned my external SSD to 3, and only 1 is exFAT. The rest are NTFS.
In stock android 13 it is only able to read the exFAT partition.
To my surprise I noticed that in AncientOS (12L), it can read all in file manager. Don't know why though! didn't bother to read the features.

use exFAT supposed now with android 13 .