Database Develop

[Q] MicroSD works intermittantly

Hi all
Have a Telecom NZ Milestone a853, was running froyomod (about a month old) fine until yesterday when some of my sdcard files ended up in the lost.dir, then more and more, i grabbed what i could via card reader into my pc and put back into phone to format.
Once booted i got the notification that teh sdcard was damaged or unknown format, when i try and format it flashes up on the screen that sdcard is removed. If i leave it for a while i can format on the phone and even copy files at some ungodly slow rate (usb1.1??). And all is fine til i reboot and it misbehaves the same way again.
I have tried 2 cards a class 6 8gb and bought a new class 10 16gb yesterday. both cards are fine in windows and run as fast as the card will allow.
I have tried flashing back to 2.1 with rsdlite which appeared to work however the card needed formatting but there was enough time to copy open recovery across, take a nandroid backup of the phone and flash to 2.2. 2.2 showed a sd card issue but it formatted fine and i copied across the hono 2.3 nandroid image.
2.3 was fine for about 10 minutes and since then it has been back to square 1, sd card sometimes appears but needs formatting and then the transfer rate is slow and the data is temporary.
Firstly had anyone else had the same issue? did you manage to fix it and how?
Nextly where can i find a TNZ XT sbf for my phone cos it looks like im gonna have to flash it back to stock to return under warranty even though i can probably get them to repair it with the custom rom as we have in NZ a consumer guarantees act which trumps all silly manufacturer opt outs, it will still be less hassle to take it back stock.
thanks in advance guys.

+1 for a clean XT nandroid/*.sbf I forgot to backup before I flashed...

azzaj said:
Hi all
Have a Telecom NZ Milestone a853, was running froyomod (about a month old) fine until yesterday when some of my sdcard files ended up in the lost.dir, then more and more, i grabbed what i could via card reader into my pc and put back into phone to format.
Once booted i got the notification that teh sdcard was damaged or unknown format, when i try and format it flashes up on the screen that sdcard is removed. If i leave it for a while i can format on the phone and even copy files at some ungodly slow rate (usb1.1??). And all is fine til i reboot and it misbehaves the same way again.
I have tried 2 cards a class 6 8gb and bought a new class 10 16gb yesterday. both cards are fine in windows and run as fast as the card will allow.
I have tried flashing back to 2.1 with rsdlite which appeared to work however the card needed formatting but there was enough time to copy open recovery across, take a nandroid backup of the phone and flash to 2.2. 2.2 showed a sd card issue but it formatted fine and i copied across the hono 2.3 nandroid image.
2.3 was fine for about 10 minutes and since then it has been back to square 1, sd card sometimes appears but needs formatting and then the transfer rate is slow and the data is temporary.
Firstly had anyone else had the same issue? did you manage to fix it and how?
Nextly where can i find a TNZ XT sbf for my phone cos it looks like im gonna have to flash it back to stock to return under warranty even though i can probably get them to repair it with the custom rom as we have in NZ a consumer guarantees act which trumps all silly manufacturer opt outs, it will still be less hassle to take it back stock.
thanks in advance guys.
Click to expand...
Click to collapse
I had this issue with my first milestone. It still works (handed down to an employee) but i had to switch the sdcard.
I dont know if you have the same issue...but i would try another card.
Sent from my Milestone using Tapatalk

I had the same issue with my milestone microsd. I ended up fixing it by formating the card via laptop instead of the phone. Don't do a quick format, do a full format instead.
Hope that fixes the issue.

[Q] Nexus One Randomly Rebooting

For the past few weeks, my phone has been randomly rebooting. I would say about 20 times a day. I cant nail down a pattern. Sometimes its while im using it, sometimes its while its idol. Here is what Ive tried so far:
Reinstalled Rom (different versions)
Reinstalled DT A2SD
Whiped Everything (dalvik, SD, and everything else).
Formatted SD card with Amon_RA's recovery.
New Battery
I've tried running a logcat, but this doesn't tell me anything. It just stops when it reboots.
The only thing I havent tried is purchasing a new SD card. I want to see if I have any other options before I do that. I feel like there is something i'm missing. Ive read something about formatting the SD card in windows, instead of in the phone. Are there any other things I can do to troubleshoot? Log's I can check?
Phone Details:
Nexus One
Amon_RA Recovery
CM7 Nightlies
16GB Class 10 SD
DT A2SD
EXT3 SD partition for apps & Dalvik
Thanks for any help that can be provided

It's a known hardware issue.
You have to send your device back to HTC for repair.

I've seen a few claims that similar problems are actually caused by a bad SIM. I've no idea how accurate this is, but it's easy enough to test...?

.257 update

Hi XDA
Anyone else having problems with waterproof notification popups and SD card that gets unmountet all the time after
updating to .257?
i need to reboot my phone multiple times a day to get the sd card to work as when it gets unmounted it doesent mount again
even if i manually take the card out and slide it back in only after a reboot.?
Regards

Hello, i've disabled the popup and no problem with this.
I've a black screen and need to reboot one time in two day with .257.
I've try 3 time to unmount/mount SD card and no problem.
Is the mounting option have a problem before updating ?

No i had no problems before the update but i will test it further this weekend before i factory reset as i have alot of data

[Q] Does my N1 have a RAM defect?

Up until a few weeks ago, my N1 worked fine. Rooted, CM7.
Then I got lots of FCs and decided to re-flash CM7.
It worked fine for a week or so until last night. It was fine before I fell asleep but dead next morning.
I can VOL.DN + POWER on and switch between FASTBOOT and BOOTLOADER/HBOOT
I can boot into ClockworkMod recovery.
Booting CM7 presents coloured X; then a blank screen (it may be off) and sometimes I get softkeys lit or flash once. Usually N1 vibrates slightly every 5 seconds or so. Only way out of this is to remove battery.
I have a very recent backup. but it or any of it's img files have MD5 errors.
So, either this image is bad, or perhaps I have a RAM error that also prevents phone booting?
Is there a log file I could look at (I can connect using adb)?
Is there a way to test RAM? Is there a PASSDIAG.ZIP or PASSDIAG.NBH image I could try?
I also tried re-flashing CM7 - no change.
Any other ideas?

Did you try to use another SD card to use in your device? It could be a SD card failure and is easier to fix than a RAM failure. I also remember reading in other threads that a SIM failure could make reboots and freezes in these devices
I had a similar problem in my Nexus One with the original ROM, but in my case I think that the failure was in some corrupted file in the system partition.

Doubt SD card nor SIM is issue
Same defect when SD card and/or SIM removed (except I can not attempt a restore with SD card removed).
So I don't think either is at fault.
SD card mounts fine when USB connected to a linux laptop under FASTBOOT (I think I did this) or RECOVERY.

Mine have a like problem, i only do a full wipe and start without SD and it worked

[Q] Galaxy S (GT-I9000) SDCard Problem

Hello,
I've owned a Samsung Galaxy S for about 2 years and it recently started to give me problems. Before having the problems I'm going to describe I never rooted or flashed this phone.
It started a few months ago when I restarted my phone, it went to the initial screen with the "Galaxy S / GT-I9000" white text and instead of going to the next screen it just went black and returned to the same screen. I was afraid it would endlessly loop like this, but it didn't. After around 5 minutes it was able to start the phone like usual (I did nothing that could have fixed it, I just kept watching it while it looped and suddenly it didn't loop). After that, with the phone turned on, everything worked just fine.
This problem didn't go away, everytime I restarted my phone it would just sit there looping for what seemed to be a random amount of time (from 4-5 minutes to about an hour) until it was able to turn on. So I decided to try to fix this problem.
I don't know much about smartphones so my first idea was to try and reset the phone to factory settings (In Settings->Privacy if I recall correctly). I did this a few days ago and I guess it didn't help much, since when it restarted after the reset it kept trying to boot for more than an hour before I just removed the battery and came online looking for solutions.
The first solution I encoutered (on this forums) was this one: http://forum.xda-developers.com/showthread.php?t=2247484
I followed it and flashed the Semaphore .tar file in my phone. After that, booting in recovery mode would lead me to the CWM Recovery v6.0.1 menu where I was supposed to Partition the SD Card (That's what I understood from that thread).but the problem was that i couldnt even mount the /sdcard folder. (Nor the /data and /emmc folders). At this time I was only following the instructions and didn't really understand much of what was happening so I skipped to the next step, Install the firmware (I9000XXJVU_I9000OXAJVU_OXA.zip).
So this time I placed the pit file and the 3 other files that were inside the .zip I mentioned above in Odin and flashed my phone. This proccess went OK and after the phone rebooted it seemed to be installing something and gave me an error: "Failed to mount /sdcard (File exists)" (I actually found a picture in this forum with the exact same screen.
Now I was totally lost and "without" a phone, and it was actually really late and I needed to sleep. So I tried to repeat the previous steps, I returned to CWM but it still couldn't mount the /sdcard so I couldnt format or partition it. I cleared the cache and tried to install the firmware again. This time, surprisingly, it worked! After the flash the phone rebooted and was able to boot into android in the first try.
I used the phone for about a day thinking all the problems were gone but they weren't. The following day I rebooted the phone and found myself back in the boot loop. It went eventually turned on after around 15 mins but I realized I was back at the starting point.
So this time I tried another solution, since I thought the problem was in the sdcard i used SDFormatter (in Windows) and, with the phone USB connected to my laptop, I formatted the internal sd_card (I found this solution in another topic, also in this forums). After this I turned the phone off and when I tried to boot it I was back to the loop, I didn't feel like waiting so I just went back to the first solution (this time with the internal sdcard formated) and it made a difference, this time I was able to mount the /sdcard in the CWM recovery menu and was also able to partition it (according to the instructions from the solution I posted). When the partition was done I tried to flash the firmware and it worked perfectly, It booted and I was able to use it, but it wasn't detecting the internal storage, it only had the system storage (In Settings->SD card...). I found this really weird and was about to reboot the phone when it simply crashed and rebooted (It happened when i tried to turn on Wi-fi). Obviously I ended up on the boot loop again.
So now I've returned to the CWM Recovery and I can't mount /sdcard, /data and /emmc. I tried to flash the firmware I was using but now I get the same error I was getting before and trying it again doesn't seem to work (I guess I was really lucky before). I've checked the log and this is what happens when i try to mount those folders (I don't know much about Android so I don't know if this is useful):
W:failed to mount /dev/block/mmvblk0p1 (No such file or directory)
Error mounting /sdcard!
W:failed to mount /dev/block/mmvblk0p2 (No such file or directory)
Error mounting /data!
W:failed to mount /dev/block/mmvblk1p1 (No such file or directory)
Error mounting /emmc!
I've been searching for another people with similar problems and it has led me to believe that the internal sdcard is dead, but I don't know. If it was dead it probably wouldnt boot at all but in my case it just takes a while (sometimes a "long while") to boot, I can't confirm if it boots now since I can't even install the new firmware. The solution I found for these people was to use an external sdcard and divide it into 2 partitions etc, I can try to do that but first I wanted to know if there is another way to come back from this problem? Is the internal sdcard the problem?
Thanks for reading
TL;DR: Phone used to be stuck at boot loop before turning on (took from 5 minutes to 1 hour), I tried to fix it, Formated internal sdcard using SDFormatter, seemed to be working fine but phone crashed and was back on boot loop, now I am on CWM Recovery and can't mount /sdcard,/data,/emmc. I don't know what is the problem.
EDIT: I just turned my phone off and started it again in recovery mode and surprise! now I can mount the /sdcard, I dont know why this happens. One moment I am in CWM Recovery and can't mount it, I turn it off and back on and now I can.

shams94 said:
I turn it off and back on and now I can.
Click to expand...
Click to collapse
basically, your internal SD card may need some re soldering, and only professional technicians can do it or internal SD card may be failing look here about embedded SD card
Check this out! Links to useful Guides and " Banned " Documentaries ​

Thanks for the reply!
I followed the links on your signature and followed some guides to partition my external sdcard and use it to run the phone and it worked! I got my Galaxy S back, atleast for now (even upgraded from 2.3.6 to 4.0.3).
If anyone finds this and has the same problem my solution was this post. It even has a video showing some of the steps.
Again, thanks for your reply, without it i probably wouldn't have found the solution