I got this Sleep of death problem along with a microSD "card error checking problems",so I tought that replacing the card would solve my problem.So I got rid of the "stock" one and I got a 8Gb SanDisk,4-class.But after that,the Sleep of death was still there,even after chaning 3 ROMs.So,after reading a few threads from other phones I saw that one solution is to format all partitions with a special program,because a simple format wouldn't be enough as data wouldn't be deleted 100% from a simple format resulting in errors etc.As I couldn't find one software to work on Desire,I just used the format option in recovery.So,I did format the /data /system /boot etc partitions for ~5 times.Now,this screen of death problem occurs only once each day(before it was like 3-4 times a day).
Anyone knows a better solution for this problem?
infoschumi said:
I got this Sleep of death problem along with a microSD "card error checking problems",so I tought that replacing the card would solve my problem.So I got rid of the "stock" one and I got a 8Gb SanDisk,4-class.But after that,the Sleep of death was still there,even after chaning 3 ROMs.So,after reading a few threads from other phones I saw that one solution is to format all partitions with a special program,because a simple format wouldn't be enough as data wouldn't be deleted 100% from a simple format resulting in errors etc.As I couldn't find one software to work on Desire,I just used the format option in recovery.So,I did format the /data /system /boot etc partitions for ~5 times.Now,this screen of death problem occurs only once each day(before it was like 3-4 times a day).
Anyone knows a better solution for this problem?
Click to expand...
Click to collapse
i was having those sd card erros checking for problems error. what i did to fix it was connect via disk mount, right click the drive, open properties, then click check disc. tyou pc will run some tests on the sd card. should take a minute or 2. when its done, mine said found issues on card and fixed them. i then reran it to confirm and the 2dn tie it said my card was ifne. had no issues since. but as far as the sleep of death as u put it, ive never heard of this issue. my advice to u is find your service providers RUU and reflash to stock. ive had issues with sim card errors etc and a ruu flash fixed it all. then reroot, re s-off, repartition, and renandroid your stock root rom.worked 4 me. time consuming, but it fixed mt isuses
Another sleep of death post, I see I am not the only one.
Do what LINKSLOVESANDROID said, I was having the same problem 4-6 times a day. After error-checking it reduced to a couple, better than the previous situation!
I always did that error check via disk mount,and only after that my card was recognized again.Still,I changed the microSD,so no more card errors,but Sleep of death is still present.They seem to be 2 totally different problems.
I would like to try with a RUU,but I can't find the one for Orange Romania.It was carrier locked on Orange,but now it's unlocked.Which RUU should I try?
solved!
I was having the sleep of death issue as well, and I was advised to flash a RUU.
However, I didn't. What I did is take the sd card out of the phone, I put it in my mac, ran disk utility, erased all partitions (fat and ext2) and format the whole thing twice (we never know).
Then I flashed LeeDroid's rom (2.3d non a2sd) and now my phone works better than ever before! It's all solved!!!
Did you also have FCs???
I had,but it was because I had CM7 with A2SD,so when the microSD became corrupt,all apps from SD gave FCs.That can be easily solved with LINKSLOVESANDROID solved.
I still wonder if there is a method to "fully" format system,data,boto partitons,or if anyone can tell me which RUU to try.
And I found my answer.
All AOSP gingerbread ROMs had this bug.Looks like they were fixed in Oxygen and CM7
Fixed pmem exhaustion *
* The pmem exhaustion was causing the so called 'black screens'
at random intervals
About two weeks ago my SDcard kept coming up as damaged/corrupted in my e4gt and in my evo 4g so I figured I was sol and formatted it. Now there's nothing saved to it except the normal stuff that's saved when formatted via android. But now I was trying to move a large file to the SD card both rom toolbox and root browser freeze after about 300ish MB and my phone restarts. I tried just straight moving the file, copying it and zipping it and no matter what it locks up and restarts. I tried just redownloading the file onto the SD card directly with the same end result it locks up and restarts. Anyone know what could be causing this?
Sent from my SPH-D710 using xda app-developers app
Maybe you SD card is damaged or corrupted still? If it is trying to write to a corrupted sector that would explain the crashes, and a mere format isn't going to fix corrupted sectors.
As to how to fix our even test for corrupted sectors on a ssd I am at a loss.
Sent from my SPH-D710 using xda app-developers app
Have you tried checking it on your computer with Scandisk? Might find something, though I had a card that was giving me random problems (disappearing apps, phone saying card was damaged) even after Scandisk said it was okay, no problems after using a new card.
Be careful about ever letting Scandisk RESTORE damaged files because you will likely end up with a bunch of useless CHK files (been there...).
so another 64 gig sd card question, though im pretty sure mine is fresh. Got a 64 gig sd card class 10 (forget brand name, will look it up and update the post in a bit) i format it to exfat first, and pop it in my phone (using infamous latest, along with ktoonez kernel) phone immediately says sd card is damaged, try Reformatting it. i browse the sd card on my phone with rom toolbox. folders are corrupt (folders are named something along the lines of µideos~1 (my videos folder) or µusic~1 (my music folder), etc etc). i pop the card back in my computer, reformat, but trying fat32 this time. same result, pop in phone, says its damaged, corrupt folders. try formatting directly with the phone, pop it out to transfer my stuff onto it, pop it back in. same result, says damaged etc.
The thing is, the card works fine computer to computer. No corruption, but as soon as i pop it in the phone, above happens. Ive used the windows default formatting tool. Ive used easus partitioning and formatting tool and i have also used gparted (linux partitioning and formatting tool) all with same results. This doesnt just occur on my phone, this also happens on my friends verizon galaxy note 2 (running clean rom with sabertooth kernel).
So im wondering, is it a faulty card, a kernel problem, a general android problem, or am i doing something wrong with preparing the card with my phone?
Heres the gparted log i generated when i ran its fix and recover feature
Code:
GParted 0.12.1 --enable-libparted-dmraid
Libparted 2.3
Check and repair file system (fat32) on /dev/sdc1 00:00:16 ( SUCCESS )
calibrate /dev/sdc1 00:00:00 ( SUCCESS )
path: /dev/sdc1
start: 63
end: 131,058,269
size: 131,058,207 (62.49 GiB)
check file system on /dev/sdc1 for errors and (if possible) fix them 00:00:02 ( SUCCESS )
dosfsck -a -w -v /dev/sdc1
dosfsck 3.0.14 (23 Jan 2023)
dosfsck 3.0.14, 23 Jan 2023, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkdosfs"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
16384 bytes per cluster
32 reserved sectors
First FAT starts at byte 16384 (sector 32)
2 FATs, 32 bit entries
16384000 bytes per FAT (= 32000 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 32784384 (sector 64032)
4093567 data clusters (67069001728 bytes)
63 sectors/track, 255 heads
0 hidden sectors
131058207 sectors total
Reclaiming unconnected clusters.
Checking free cluster summary.
/dev/sdc1: 0 files, 1/4093567 clusters
grow file system to fill the partition 00:00:14 ( SUCCESS )
using libparted
from what i see, everything looks fine and normal, but maybe im overlooking something, it is 4 in the morn here and ive yet to go to sleep
anyone?
TheAtheistOtaku said:
anyone?
Click to expand...
Click to collapse
bump
another bump. ran surface tests and all came back clean
Exfat makes my phone bootloop.
You never updated to say which brand of card it was. I still haven't had to buy a new 64gb card and am still using 32gb cards. I'd like to know which brands to avoid getting.
Well Samsung says it only officially supports up to 32 gbs, so putting in a 64gb is a gamble. I just ordered a 64 let's see what happens.
Sent from my SGH-M919 using Tapatalk 4
horr1blek1tten said:
Well Samsung says it only officially supports up to 32 gbs, so putting in a 64gb is a gamble. I just ordered a 64 let's see what happens.
Sent from my SGH-M919 using Tapatalk 4
Click to expand...
Click to collapse
A 64gb card in exFAT format will work just fine on a GS4 out of the box. It's when a custom kernel that doesn't support exFAT get use is when it give troubles.
Oh okay cool good thing I'm stock
Sent from my SGH-M919 using Tapatalk 4
so as for branding, the friend i got this from is away for a while so lets assume its generic. theres no noticeable branding on the card so this is likely the case.
Though, i he did mention the brand to me when he gave it to me, i know it starts with an M.
anyone wanna suggest anymore tests i should run on it.
TheAtheistOtaku said:
so as for branding, the friend i got this from is away for a while so lets assume its generic. theres no noticeable branding on the card so this is likely the case.
Though, i he did mention the brand to me when he gave it to me, i know it starts with an M.
anyone wanna suggest anymore tests i should run on it.
Click to expand...
Click to collapse
It might be a fake card I've seen em. I'm sure they have apps on the play store to check the actual capacity. That's probably the problem.
Sent from my SGH-M919 using Tapatalk 4
disregard
horr1blek1tten said:
It might be a fake card I've seen em. I'm sure they have apps on the play store to check the actual capacity. That's probably the problem.
Sent from my SGH-M919 using Tapatalk 4
Click to expand...
Click to collapse
currently running a test on the card in the phone. its about half way done (currently, it wrote 35 gigs @9.5MB/s) so it seems though it may be generic, im one of the lucky few who have a working generic (except for the problem in the op, obviously)
so if this test does come back completely clean, what step should i take next. If tests on both the pc and phone are coming back clean, It should be something with the phone (more then likely the kernel) right?
TheAtheistOtaku said:
currently running a test on the card in the phone. its about half way done (currently, it wrote 35 gigs @9.5MB/s) so it seems though it may be generic, im one of the lucky few who have a working generic (except for the problem in the op, obviously)
so if this test does come back completely clean, what step should i take next. If tests on both the pc and phone are coming back clean, It should be something with the phone (more then likely the kernel) right?
Click to expand...
Click to collapse
Yes, most likely. My 64gb arrives tomorrow I'll run some tests on my stock s4 let's see if that makes a difference.
Sent from my SGH-M919 using Tapatalk 4
baseballfanz said:
A 64gb card in exFAT format will work just fine on a GS4 out of the box. It's when a custom kernel that doesn't support exFAT get use is when it give troubles.
Click to expand...
Click to collapse
Which is why my card is fat32.
Sent from Spaceball One.
I have the same issue
Hi there
Almost a year to the day and im wandering if you ever figured out what the heck caused the: µEDGE, µIDEO, µOMICS, µUSIC and so on. Did you find a cure or fix? All i know is I have a Samsung galaxy S3 gt-19300 and a Samsung galaxy tab 2 7.0 I often swap the 32Gb sd between the 2 and all of a sudden this happens. I reformatted the card (which took soom doing) nothing happened there still there. any help would be appreciated.
tonyheaney said:
Hi there
Almost a year to the day and im wandering if you ever figured out what the heck caused the: µEDGE, µIDEO, µOMICS, µUSIC and so on. Did you find a cure or fix? All i know is I have a Samsung galaxy S3 gt-19300 and a Samsung galaxy tab 2 7.0 I often swap the 32Gb sd between the 2 and all of a sudden this happens. I reformatted the card (which took soom doing) nothing happened there still there. any help would be appreciated.
Click to expand...
Click to collapse
You reformatted but nothing happened? Like, all the data is still there? Mine is doing that now; been using the same 64GB card for almost a year now and just recently it started showing as Generic Hierarchical instead of FAT32... I've used multiple programs in Windows and on the phone itself, and even GParted in Ubuntu; everything says it formats but after I unmount then remount I see that there has been no change... almost as if it's write-protected. I can read all my information, but unlike yours, mine isn't corrupted at all... but I cannot write or make any sort of changes to the contents.
Out of curiosity, if you do a chkdsk /f in Windows, does it mention anything about a dirty bit being set and unable to be removed? I only ask because mine does and no program or app I've used can fix it. Either way, I've tried everything but a low-level format (which I'm going to try in a few days) and haven't been able to find a fix. I'm thinking our cards might just be beyond repair...
mini card
lordcheeto03 said:
You reformatted but nothing happened? Like, all the data is still there? Mine is doing that now; been using the same 64GB card for almost a year now and just recently it started showing as Generic Hierarchical instead of FAT32... I've used multiple programs in Windows and on the phone itself, and even GParted in Ubuntu; everything says it formats but after I unmount then remount I see that there has been no change... almost as if it's write-protected. I can read all my information, but unlike yours, mine isn't corrupted at all... but I cannot write or make any sort of changes to the contents.
Out of curiosity, if you do a chkdsk /f in Windows, does it mention anything about a dirty bit being set and unable to be removed? I only ask because mine does and no program or app I've used can fix it. Either way, I've tried everything but a low-level format (which I'm going to try in a few days) and haven't been able to find a fix. I'm thinking our cards might just be beyond repair...
Click to expand...
Click to collapse
I found a fix (i hope) i had an old phone Vodafone V55 Blue and i formatted it from the phone its self. it worked. before i did this the card was not registering on my S3.
tonyheaney said:
I found a fix (i hope) i had an old phone Vodafone V55 Blue and i formatted it from the phone its self. it worked. before i did this the card was not registering on my S3.
Click to expand...
Click to collapse
My SanDisk 32GB microSD just got hit by this, too. Samsung Note3. Should I try data recovery on it?
Eric
Hi guys, this is my last attempt to figure out this problem that is driving me crazy.
Ive got this Kingelon G9000 with KK on board, and the seller says its fake 16gb. I can get the EBR modified as i wish using EBRTweak, but while the internal memory can be resized as the tweak (say, 4,90gb) the internal phone memory results always 9gb, or 11gb if i choose a smaller EBR size.
So far i know that the preloader file contains the partition table and size, but flashing a different preloader from the same phone with the same os, i got always that fake space in internal phone memory. The REAL size is 8gb.
Is there anything i can see/test/try? I have a decent knowledge of adb and linux related commands, but everything i tried didnt lead me to success.
Any help is appreciated, im willing to donate to the ones who can sort this issue. I can provide files if needed.
Thanks alot.
Hello. I've noticed that somehow my internal storage partition got its capacity reduced. It is a 32Gigs model. Before it was 29ish or so, can't really tell now it shows 23 gigs max?
I've been trying to figure out how it happened. I did updated to Marshmallow prior to shrinking. Do you guys have similar issues or experience and suggestions to share? Thank you.
Proof: http://i.imgur.com/6GhQSsj.png
I do remember reading a thread that talked about internal space being reduced after update to MM...
Can't remember where I saw it....but if I remember correctly it was a duplicate file left behind about 3 gig in size...
Once deleted the device storage returns to normal...
Perhaps someone more familiar with that issue will chime in with a solution for you....g
Hey greg. Thanks for your reply. I've noticed a file/folder when doing a twrp backup. Twrp backup shows "system image" of more than 4 gigs + "system" while data is normally around 1 gig. System and System image do have different size though. I don't know yet if that can be related with what ate my memory.
EDIT: Screenshot of that System Image when backing up: http://i.imgur.com/K1gQXyh.png
I've no idea from where it came and whatnot. All I know is that my internal storage capacity got reduced. Thanks
Figured that the system image is for stock backing up for later use such as taking an OTA update. But still I can't figure our why capacity got down.