Database Info

sd card

so now that we have a working sd card is there any way to change the save location of the browser and camera to the new working sd card?
Sent from my Xoom using Tapatalk

is there anything special to get the SD slot working? Mine still doesn't seem to be doing anything.

Well, in my opinion, which may be wrong...and probably is.
The new sd mod mounts the actual sd as /sdcard2/.
The problem i see with this is all the apps are looking for /sdcard/.
Now I think the best way to handle it would be to symlink /sdcard/ and /sdcard2/ as one volume.
The problem with that is that the volume manager would probably freak the **** out when you take your sdcard out of the device.
I don't know though, maybe bigrush or whoever got it working has this thought out better than I would have - but I am a software developer, not a kernel developer. That **** hurts my head.
Right now, i don't have an extra SD card worth my time of putting in (biggest extra I have is 8 gigs).
The only point I really see in it at the moment is extra space available from a file manager.
I am not sure if media scanner has to be modified to include the new directory to pic up on pictures, movies, and audio.

06types said:
is there anything special to get the SD slot working? Mine still doesn't seem to be doing anything.
Click to expand...
Click to collapse
Lol root your xoom and flash the new tiamat 1.3.0 kernel

oh, maybe ill just break down and root it... I didn't really see any point until now with the lack of roms out for this so far.

I have already flashed my xoom, with the original one button flash. The new version does not have a way like the original to just one button the kernel. Will I have to re-root everything and go from there or will it sense that I am already rooted and take me to changing the kernel to be able to use the sdcard?

floridatank said:
I have already flashed my xoom, with the original one button flash. The new version does not have a way like the original to just one button the kernel. Will I have to re-root everything and go from there or will it sense that I am already rooted and take me to changing the kernel to be able to use the sdcard?
Click to expand...
Click to collapse
if you use the newest one click method with tiamat 1.3.1 you will be wiping your xoom's data back to stock as well. which means you'll have to setup your xoom again and reinstall all your apps again.
if you want to just flash the newest kernel w/out wiping the data just follow the instructions on this page:
http://forum.xda-developers.com/showthread.php?t=978013

[Q] Why does my SD card keep switching from internal to external

I'm about ready to send my phone back and get a warranty replacement. But I just did a fresh wipe/format of the the sd cards and then reloaded all my rom and kernel. Running ICS using Owain/Harsh combo and I checked the Vold fstab and it has an 8 not a 9. also loaded a gb rom first because that's what the dev thread said to do. New to the forum not new to rom replacement. trying to get braver about asking for help. It sees the external and switches it back and forth every boot and even mid boot. no recognition of the internal hence why I want to just warranty replace the thing. I'm at my end please guys give me some suggestions
thanks anyone who can throw in some ideas.

lifelikedavid said:
I'm about ready to send my phone back and get a warranty replacement. But I just did a fresh wipe/format of the the sd cards and then reloaded all my rom and kernel. Running ICS using Owain/Harsh combo and I checked the Vold fstab and it has an 8 not a 9. also loaded a gb rom first because that's what the dev thread said to do. New to the forum not new to rom replacement. trying to get braver about asking for help. It sees the external and switches it back and forth every boot and even mid boot. no recognition of the internal hence why I want to just warranty replace the thing. I'm at my end please guys give me some suggestions
thanks anyone who can throw in some ideas.
Click to expand...
Click to collapse
what do you mean by they are swtiching? do you mean mounts it as /emmc then /sdcard? i really hope not cause that sounds bad...
make a backup, and flash a gingerbread rom and let it boot fully to check if the problem is still happening, then report back.
also, before you warranty it, try putting back a completely stock rom and see if the problem is still there.

Klathmon said:
what do you mean by they are swtiching? do you mean mounts it as /emmc then /sdcard? i really hope not cause that sounds bad...
make a backup, and flash a gingerbread rom and let it boot fully to check if the problem is still happening, then report back.
also, before you warranty it, try putting back a completely stock rom and see if the problem is still there.
Click to expand...
Click to collapse
well no worries about the making a backup.. i haven't installed much because of the issue, so far the sd card has remained as the external with emmc not being mountable from settings>storage...
flashing gb will report back

repartioning my sd card back to full use.
So my problem was simpler than i thought evidently the format that I did to the internal sd wasn't complete so while in gb I used the erase sd tool and voila I have internal sd memory again the only issue I'm having now is it's like 6gb instead of the 8 it should be because way back when i partitioned my sdcard for sd-ext... hence why i was trying to format in the first place... any help for that.

lifelikedavid said:
So my problem was simpler than i thought evidently the format that I did to the internal sd wasn't complete so while in gb I used the erase sd tool and voila I have internal sd memory again the only issue I'm having now is it's like 6gb instead of the 8 it should be because way back when i partitioned my sdcard for sd-ext... hence why i was trying to format in the first place... any help for that.
Click to expand...
Click to collapse
Is it the internal or external that's smaller than it should be?
Sent from my LG-P999 using Tapatalk 2

Klathmon said:
Is it the internal or external that's smaller than it should be?
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Both.

[Q] Trying to root my Inspire 4g

I am asking this again here, as my previous thread seemed to be hijacked by someone elses question!
I recently decided to root my inspire as i am no longer using it as a phone, so i thought that it would be interesting to do and fun to play around with all of the options available (i recently did the same thing on my Nook Tablet, and that was the single best decision i have made a while!). I started out researching the manual techniques to do it, but i didn't really like the high risk factor there (i really dont want to brick my phone) so i tried Ace Hack Kit. Of course, it has to download the phone from 2.3.5 to be able to work. During this process, it has me hold volume up and power twice, and every time i do that, it flashes up really quick something about holding volume up and volume down and power, but then it skips past that. Anyway, here is where my problem comes in: It says that it should reboot in to hboot, which it does, but that hboot should run a test, then prompt me to continue by pressing volume up, and then should reboot, flashing twice, and that should be the end of it. THe problem is, it does boot in to hboot, but it is just a standard hboot screen asking to recover, load bootloader, etc. When i reboot from there it just boots in to the phone as normal. I have tried 3 different SD cards, all of which work and are recognized by my PC, my other phone and my Nook tablet. I have also inserted a working sim card, just to be sure that wasnt the issue, and i still cant make it work. Does anyone have any experience with his issue, or any idea what i might be doing wrong?

Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell

marsdta said:
Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell
Click to expand...
Click to collapse
OK, as i have stated, i have tried a new SD card (2, actually, with the same results.) as far as an output screen, there is none. Ace Hack Kit goes through the whole downgrade process, my phone gets in to hboot, but it is just a standard hboot screen, and it doesn't downgrade. When my phone restarts, it restarts like i just did a factory reset.

There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?

marsdta said:
There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?
Click to expand...
Click to collapse
by changing the of the boot img do you mean downgrading it? That is what i am trying to do. The kit is supposed to do it automatically. If that is not what you mean, please explain!
As to the output, copy thing, no, there is none of that. I have followed the instructions about 20 times. After starting the downgrade process, the phone restarts and comes up with a red triangle. At that point i am supposed to hold volume up and power, and it goes and reboots and i do the same thing again. At this point, i am told that the phone will boot into hboot and check the boot image. When it is done, i am supposed to hit volume up to confirm, and then the phone will reboot, this time in to the down graded image. That is where my problem comes in. Instead of checking the boot image, it just goes to a standard hboot screen. There are no error messages or warnings, and i have followed the instructions to the letter.
As far as the cards are concerned, the maker of the kit suggested a 2 or 4gb Sandisk series 4 or 6 SDHC card, so i bought 2 of the series 6 4gb, along with the 2 others that i already have. I also have 2 series 4 4gb and 2 series 4 2gb Sandisk cards, as well as an 8gb and 2 4gb PNY cards. All of the cards recognize in my phone and PC, and the older cards also recognize in my Nook (and were used to root and load custom roms on several other devices), i have not loaded the new cards in to any other devices besides my laptop and the phone for fear of corrupting it. So i find it difficult to believe that the cards could be the problem.

I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method

marsdta said:
I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method
Click to expand...
Click to collapse
I appreciate the attempt to help (the reason why i didn't post a direct copy paste was simply as i was in no position at the time to take one, not any reluctance to ultimately do so...) In my recent attempt to provide you with a full copy paste of the process, i was able to figure out what i was doing wrong. For anyone who may have the same or similar issue: format the SD card while it is in the phone from your PC right before starting the process. Thats all it took. Even for a card that was brand new and untouched, or formatted before putting it in the phone, i couldn't get it to work, but it worked doing it that way, and i am now happily rooted and ready to install CM9!

Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.

pazzo02 said:
Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.
Click to expand...
Click to collapse
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.

glevitan said:
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.
Click to expand...
Click to collapse
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?

pazzo02 said:
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?
Click to expand...
Click to collapse
As far as I am concerned the boot partition can not be restored by formatting. SDCARD should always be dismounted properly.

[Q] help i think ive well and truly ****ed it

hiya i wonder if any1 can help!
basically my phone was telling me my sd card had been removed (no big deal i thought, this seems to happen to my phone from time to time since running this ROM (bruce2728's cm10)).
i can usually either remove the sd card and put back in, or the same with the battery to get it working again. but no matter how many times i try it wont work. also when using this ROM (and before this problem) every time that i try to enter storage from the settings menu, settings force closes.
so completely out of ideas i tried doing a wipe and trying again. now u see im fairly new to all this and that seems to get touted as a way to fix some things, so i thought id give it a go.
but now my phone wont get past the white with green HTC logo, its been sat like that for about an hour! and in recovery it just says that it cannot mount sd card!!
i feel im firmly up **** creek. is there any way to fix this? perhaps a way to flash a ROM without using sd card to a phone that wont boot up?
i feel i might need to flash a new bootanimation.img as i changed this from the default in the ROM, could i also do this without an sd card or a phone that wont get past HTC logo?
i hope there is someone out there that can help!
thank you in advance,
Max

I would install ARHD from Mike1986 it seems to help resettle the device running a sense ROM. Make sure you follow his instructions using ext4 and super wipe
Sent from my HTC Sensation using xda app-developers app

if you are S-ON enable smartflash first from 4ext and then flash the rom

rzr86 said:
if you are S-ON enable smartflash first from 4ext and then flash the rom
Click to expand...
Click to collapse
yeah thats what i always do but because i cant access my sd card i cant flash the ROM which is saved on it. it just keeps saying cant mount /sdcard

Max792 said:
yeah thats what i always do but because i cant access my sd card i cant flash the ROM which is saved on it. it just keeps saying cant mount /sdcard
Click to expand...
Click to collapse
The recovery won't pick up the SD card? That is very odd. Do you have any others around to test with?
tapped out from my sexy sensation XE

heavy_metal_man said:
The recovery won't pick up the SD card? That is very odd. Do you have any others around to test with?
tapped out from my sexy sensation XE
Click to expand...
Click to collapse
I'm assuming you've tried pulling the battery, unseating the sd card, reseating it, putting battery back, and going to recovery right?
If that doesn't work I'd suggest trying to read the sd in card in a PC... is it readable there?
All in all you can get to recovery so you arent that bad off, just need to figure out what's up with the SD.

Yes I can view my SD card on both my PC and my tablet :/ but when I boot into 4ext it says problem mounting SD card, may take longer without. Then when 4ext loads I can't manually mount SD or browse for zip file. You think this is more likely a hardware issue with my sensation?
Sent from my Transformer Prime TF201 using XDA Premium HD app

Max792 said:
Yes I can view my SD card on both my PC and my tablet :/ but when I boot into 4ext it says problem mounting SD card, may take longer without. Then when 4ext loads I can't manually mount SD or browse for zip file. You think this is more likely a hardware issue with my sensation?
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
On your PC, copy all your files off your SD card, format your SD card (makes sure the filesystem is set to fat32), and then just put 1 file on it, a ROM, and see if the recovery detects it. If that doesn't work then you can always try using a different SD card.

android1234567 said:
On your PC, copy all your files off your SD card, format your SD card (makes sure the filesystem is set to fat32), and then just put 1 file on it, a ROM, and see if the recovery detects it. If that doesn't work then you can always try using a different SD card.
Click to expand...
Click to collapse
Okay thanks I will try this, but I think its the SD card tray that has gone because I just squeezed it and it was able to mount, however only for a second then 4ext rebooted
Sent from my Transformer Prime TF201 using XDA Premium HD app

Max792 said:
i can usually either remove the sd card and put back in, or the same with the battery to get it working again. but no matter how many times i try it wont work. also when using this ROM (and before this problem) every time that i try to enter storage from the settings menu, settings force closes.
Click to expand...
Click to collapse
This isn't part of your SD card problem. This was a ROM bug that was fixed in the Jan 9th update. Any use of the storage menu from the settings on the late December to Jan 6th builds caused a FC.
So if you are using one of those builds, don't factor in th esettings FC in your diagnosis of the problem.
SD card ejections were also an issue on the Dec 21 - Jan 3rd builds if I recall correctly. I had one day where the SD card would just unmount and refused to remount. It was a problem experienced by only a handful of people and seemed to be very limited. Though if you can't mount in recovery than that's probably not the issue.
Also, you said you could press the SD card into the slot and it mounted for a second...
2 things on that note.
First, your SD card might be the problem. Maybe the contacts are worn out. Take a lcose look at it and make sure it looks okay. No corrosion, etc...
Second, the metal housing around the SD card...that can be mashed in slightly to put more pressure on the card. Take the card out and press the middle of that housing in. It could create enough force to hold the card in more securely. Be VERY careful with this option though.
Also, did you make sure another SD card got the same problem? If another card works, then your card is just f'ed.

Skipjacks said:
This isn't part of your SD card problem. This was a ROM bug that was fixed in the Jan 9th update. Any use of the storage menu from the settings on the late December to Jan 6th builds caused a FC.
So if you are using one of those builds, don't factor in th esettings FC in your diagnosis of the problem.
SD card ejections were also an issue on the Dec 21 - Jan 3rd builds if I recall correctly. I had one day where the SD card would just unmount and refused to remount. It was a problem experienced by only a handful of people and seemed to be very limited. Though if you can't mount in recovery than that's probably not the issue.
Also, you said you could press the SD card into the slot and it mounted for a second...
2 things on that note.
First, your SD card might be the problem. Maybe the contacts are worn out. Take a lcose look at it and make sure it looks okay. No corrosion, etc...
Second, the metal housing around the SD card...that can be mashed in slightly to put more pressure on the card. Take the card out and press the middle of that housing in. It could create enough force to hold the card in more securely. Be VERY careful with this option though.
Also, did you make sure another SD card got the same problem? If another card works, then your card is just f'ed.
Click to expand...
Click to collapse
cheers mate helped a lot. i did actually see that kind of talk in the thread but kind of passed over it because it hadnt affected me... yet!
if it was a ROM bug i feel im totally f'ed as i cant flash a new version due to the inaccessible sd card.
yeah ive been doing this exact mashing you speak of lol, hopefully it will work or i am completely out of ideas :\
cheers everybody for your help tho guys really appreciate it

Max792 said:
cheers mate helped a lot. i did actually see that kind of talk in the thread but kind of passed over it because it hadnt affected me... yet!
if it was a ROM bug i feel im totally f'ed as i cant flash a new version due to the inaccessible sd card.
yeah ive been doing this exact mashing you speak of lol, hopefully it will work or i am completely out of ideas :\
cheers everybody for your help tho guys really appreciate it
Click to expand...
Click to collapse
Find the exact rom you were on and take the boot IMG out of it. Wipe your data and cache and then boot to fastboot. With the boot.IMG
In your adb folder do fastboot boot boot.IMG and see if it boots into the rom.
Tapped out from my sexy nexus 7

SD cards: exFAT Fat32 file sizes

Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.

gsmyth said:
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
Click to expand...
Click to collapse
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32

jujuburi said:
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
This is the first problem I've had with it to be honest, had it or over a year and was using it in my HTC Sensation previously. I'm trying to remember if it was exFAT or FAT32, I remember a ROM (Google Edition S4 ROM) not being compatible with exFAT and checking mine out of curiosity, but just can't recall what it was and never flashed the ROM. I didn't reformat it coming from my Sensation so it hadn't changed in anyway.
Luckily all my photos were backed up to dropbox so nothing lost of too much importance. Need to get a microSD card reader to see if its completely borked or if files can be retrieved.

Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.

Theoriginalgiga said:
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Click to expand...
Click to collapse
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.

gsmyth said:
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
Click to expand...
Click to collapse
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.

Theoriginalgiga said:
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Click to expand...
Click to collapse
Cheers, I had re-downloaded the previous version of the ROM which I was on before hand and made sure to check the md5s but it still wouldn't boot which was annoying, but a full install from scratch may be the way to go. Never had bootloops before and was just worried after I had wiped and started a fresh and it still happened. I think the real lesson is to make sure to backup ANYTHING that is of value to you!
Luckily I had just happened to use the auto backup for photos to dropbox so got off lightly this time!

I have had the EXACT same issue 2 weeks ago.
I bought 2 x 32gig microSD cards (Sandisk)
1 for my phone and 1 for my digital camera.
Recently the 32gig one in my phone just DIED for no reason at all. Lost all my files, music, everything.
I contacted Sandisk, had it repalced. In the meanwhile i purchased a 64gig Samsung one.
I am yet to have an issue with the Samsung 64gig, but only time will tell.
On a plus note, Sandisk sent me a replacement 32gig card very quickly (infact too quick, i purchased the 64gig Samsung one on the idea that the Sandisk replacement was going to take months... in fact it only took 6 days...)
Cheers

How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app

jujuburi said:
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
I always use Fat32 on SD-cards. Why? It works on every Rom, with every kernel, every recovery, on every device, every camera, every computer, all the time.
When not in need of files greater than 4GB Fat32 simply is the way to go, compatibilty-wise.

gsmyth said:
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tried the card in a reader connected to my laptop but nothing. I've emailed Sandisk support so will see what they say.
Sent from my GT-I9505 using xda app-developers app