Database Develop

Has Flashing wiped my Micro SD??????

First of all thanks to all on the forum for all the useful tips and tweaks.
I finally took the bold step of my first flash two days ago to Dutty's latest Rom.
As he advised I have slowly added programmes and tweaks to make sure there were no bugs. Last night I was playing around with different wallpapers after a day of the phone being stable. Waking up this morning I found a lot of my tweaks for the today screen had reset themselves. Using file explorer i tried to open my storage card (I kept all the cabs i have been using on it) and it wasn't found. I took i out and have tried to open it through my laptop and it keeps asking to 'insert card' i.e it can't see it either. I tried a hard reset on my HD to see if it was anything I had installed and still nothing!
I have most things backed up on my PC and yesterday set up microsoft myphone so hopefully I haven't lost anything...BUT. Has flashing caused this or is it just coincidental that my storage card has gone tits up!
many thanks in advance.
P.S Off topic. has anybody else found that the Virgin advert causes a stuttering effect when scrolling down a page?

Hi Mate,
take a look at this link
http://forum.xda-developers.com/showthread.php?t=506560
Should explain all, it looks like when you upgrade to one of the newer roms not based on the 1.14 it kills the SD card, you could try formatting it again..
Happens quite randomly , so ...
Bloke

Cheers Bloke
Although the cause doesn't seem to be very clear. I flashed my HD without the SD card in. I have a sandisk card. It came with the phone but it was a replacement phone so not exactly bundled per se. (after getting the phone on an upgrade last Dec with Orange actually paying me a fiver for it, I lost it/had it stolen after owning it a month and had to then fork out £160 for it )
Sods law that i haven't been backing up my SD card as the majority of it was music that i have on my laptop anyway.
Thanks once again

I've never lost any info on my SD Card from flashing any roms, and I've flashed a lot. Even when going from 1.14 roms to 1.59 roms. No probs
However I have heard others have had similar problems and unfortunately only remedy was to format card. Once formatted problem shouldn't arise again

So to update:
tried out spare sd. Not a problem although only looked at it rather than file swap etc
Hard reset: still didn't find card
flashed stock 1.14 rom. Had colours go strange on screen whilst first installing but then touch flo started and colours as norm. Put SD card in and it wasn't found. Soft reset with card in and once booted funny colours came back (all kind of negative and opposite original colours, kind of cool but obviously not good). Still not finding card. Took card out and soft reset, all good and colours back to normal.
So, it seems, I will have to format. Bye Bye data!
I tried to look at the card from command prompt on my PC (xp pro) and it still couldn't see it. Muchos corruption me thinks. Not sure how I am going to format it now?
I hope HTC will look into this and release some sort of fix. Unless they know it's a hardware fault on the card reader and realise it will cost a small fortune to fix everybodies HD not to mention the bad publicity.

Okay, maybe not the most common method to do this, but when I had this happen to me, I also couldn't format the card anymore in my PC (Vista). What I did wat put the card in an old Samsung phone I had lying around, and the phone initialised the card for itself. After that it was also readable again on my PC and in my HD.
Since this happened to me I always take out the SD Card if I flash my phone. Just to be on the safe side.

Damaged SD Card

[Q] SD Flashed itself?
OK so, not quite sure what happened with my SD card today but it pretty much flashed itself and gone done broken the format for my apps2sd.
I was heavily using my phone today for gps and what not by driving around from garage sale to garbage sale with my ole lady. anyways, i noticed that my ringtones werent the same at about half way through, but i didnt think anything of it and kept on going. i got home later, still was doing it, so i went to terminal:
su
reboot
rebooted. when it came up it said my card was damaged and cant be used......is there anyway way to restore it or recover information off it?
edit: yes i still have root. no the card isnt readable in windows but my mac ID's it but cant do anythign with it.

Well i really don't know how or when this happened but my phone now says "Damaged SD card" under my notifications and i can't access my card anymore. I have tried pulling it out and putting it back in, resetting my phone, and mounting to my computer but it never reads. I know formatting the card would restore it but i don't want to lose my pictures, music, and files that i had stored on it. I was just wondering if anyone has had this problem and knows how to solve it... Thanks!!

[Q] stock nexus one highly unstable after boot up

my stock nexus one becomes highly unstable after booting up. im running strock 2.2.1, and this issue started apearing recently (after 2.2.1 update). the phone has never had any problems in the past.
whenever i turn the phone on, if i touch it it becomes really laggy and freezes, requiring me to pull the battery. however, if i let it sit for 15-20 minutes and then play with it it works fine, until the next time i shut id down (which can be days). i have performed a factory reset without reinstalling all of my old applications, i have formatted my sd card, and i have checked all the applications that start on boot up, but none of them seam to be the issue (when there was nothing on the phone it still reacted this way)
any suggestions? should i contact htc? this is really annoying.

Before you do, you could try to root and check the logs for anything suspicious (logcat and kmesg). Also you could try to install custom ROM and see if the problem still exists.
If it doesn't help - you should contact HTC.

EErez said:
my stock nexus one becomes highly unstable after booting up. im running strock 2.2.1, and this issue started apearing recently (after 2.2.1 update). the phone has never had any problems in the past.
whenever i turn the phone on, if i touch it it becomes really laggy and freezes, requiring me to pull the battery. however, if i let it sit for 15-20 minutes and then play with it it works fine, until the next time i shut id down (which can be days). i have performed a factory reset without reinstalling all of my old applications, i have formatted my sd card, and i have checked all the applications that start on boot up, but none of them seam to be the issue (when there was nothing on the phone it still reacted this way)
any suggestions? should i contact htc? this is really annoying.
Click to expand...
Click to collapse
Factory reset with formatted card? Has to be something wrong with the phone.

Go to recovery, wipe cache and dalvik cache, and try to boot phone again, often that helps.

tried wiping everything i can through recovery, yet my phone still freezes soon after start up. any chance htc will fix this? i dont want a refurb

Because when system has just booted up, it needs to check SD card and mounts all App2SD applications.
Try to boot your phone without SD and SIM card, see if it solves the issue.

tried removing sim and microsd and all th possible combinations.
it runs great without the microsd, so im guessing that was the issue. ill try another microsd to make sure its not a hardware/software bug related to sds in general but rather an issue with my specific microsd (which isnt the stock one).
thanks for the suggestion. i was very close to sending my phone in to htc (already had a ticket open and a fedex label)

that sounds good perhaps your SD card was corrupted. Connect it to your computer using a card reader, and do a disk check in Windows, see if it can fix any problem. Also try to degragment your SD card.

[Q] Nook color power off loop for cm7 and froyo sd installs

A couple of days ago my dad got my sister and me nook colors. I installed honeycomb which ran off the sd card on both and rooted both. I was tired of not having YouTube flash and many other apps so I tried out froyo and cm7. After about 50 unsuccessful installs I have decided I must have a hardware problem because they will run on my sisters nook.
The problem is that after the install, it boots off the sd card and loads android completely but when it asks to complete with setup wizard or
Default action it freezes up for a second and shuts off. After I boot again it just says "Powering Down."
I don't know if I should try a native install or go return this one. I already restored it completely to factory conditions so they won't be able to tell. I have searched everywhere and cannot find this anywhere else (problem or solution).
I just find it so strange how it works on the other nook color but not mine. Even setting it up on hers and moving it to mine produces the same issue. I probably will return it unless someone can help me but I'm more curious to what the problem is than how to fix it, since I can simply go get a new one.
Any help is appreciated!

****bump****

Thats certainly a new one. I only have one nook so ive never tried them side by side. Ive never been able too successfully boot off an sd card and have it stable. I eventually just decided to go to cm7 internal and never looked back. I wonder if theres something different in the nook in how it reads from the sd card.
are you overclocking the image? or running it stock?
you said you set it up on your sisters nook then move it to yours and you have problems. did you try taking her good, working build and moving that sd card to your nook and seeing if the problems go away. Ive read alot about sd cards and different quality's of cards. maybe theres something up with the sd card you have.

I have problems no matter what. If i put it on hers to setup, it still has the problem. If i set it up on mine, still has the problem. I just tried phiremod v6.1 and it also had the problem (i expected this because it is still cm7). I probably will return it but i wish they would just update these things to android 2.2/2.3 and maybe even full honeycomb when it comes out and save all of us from these issues.
The image is the normal one. I have tried installing directly to the sd, using the "SD CARD TEMPLATE" files that you install and then boot from to install cm7, etc.
They all work on the other nook but mine is being stubborn for some reason.
I am at the airport getting ready to fly home and i might try installing it internally tomorrow. I just don't want to have this problem again and have to spend a bunch of time reinstalling the stock rom to return it.

I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.

john10101 said:
I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.
Click to expand...
Click to collapse
I tried the internal install, but it is doing the same thing. I am recovering the stock image right now. Thanks for the help, but I am just going to take it back and get a new one and not root it or anything and just install it to the sd card.

I have the same problem too.

[Q] Phone freezes randomly / needs hard reboot - 2.3.3 and 2.3.4 custom ROM's

Hi all
Ever since upgrading to 2.3.3 I've been having random freezes that usually end up in needing a battery pull or pressing down on the power button until the phone reboots itself. This is with Darky's 10.1, although I don't think it's related to the "Darky parts" of the ROM itself, but something more to do with the OS.
Also, I've felt that the phone sometimes slows down. It doesn't feel like the original lag on 2.1, but rather feels like something's eating up CPU power. This will happen on ANY application, and even when moving through homescreens on TW Launcher or ADW Launcher.
Another thing of note is that it seems to be the UI or input process that hangs or dies or something. Because whatever's running keeps running I just can't make the phone respond to touch or any of the hard buttons. For example, today I was playing Age of Wind (sweet game, check it out) and after like 10 seconds of the game stuttering, the phone stopped responding, but my ship just kept going forward and the other ships were trying to keep up with me. Sounds and music kept going. And after 30 seconds of "inactivity", the screen went to sleep. As you can see everything's normal except there's no input.
So what I'd like is for ideas on how to fix or figure out what's wrong. I'm somewhat tech-savvy so I wouldn't be scared of using adb or some other debugging tool. So far I've not been able to figure out what's wrong because all the logs start over whenever I reboot the phone.
So, any ideas? Any additional information that would be useful?
Edit and update: I've changed the title because this has already happened on different custom ROM's, including Darky and Criskelo.
I have now tested for 5 days on Criskelo's ROM (based on 2.3.4) and it will happen also. So far what I've noticed both on Darky's and on Criskelo's ROMs:
- The phone will work perfectly for about 4-5 days
- On the 4th day it will start stuttering and lagging. That's when I know it's very close to locking up.
- On the 4th day it will maybe lock up once in a day
- After the 4th day it will start locking up up to three times a day
- The lock-up is at the UI level. Applications will keep running, it will ring if you call it, notification sounds are still alive, the screen will turn off normally after 30 seconds or whatever timeout you set up. But input is totally dead.
- When it locks up, both soft-buttons will light up and stay lit.
Possible causes:
- Something related to USB storage or SD card storage. Someone mentioned that it might be caused by the "fast media scanner". It's possible, because on one of my many tests, instead of reinstalling an OS, I formatted the minisd, the internal sd and phone storage and the phone was fine for 4-5 days and then it started doing screwy stuff again. This reinforces the theory that it's something to do with storage. My guess is the OS itself starts degrading the filesystem or handles or something. And my suspicion is that it's something in the /system/dbdata or /cache partitions, not the sdcard or external sd cards. Impossible to know because I have no idea how to debug using adb and nobody has given any ideas on this.
- I'm starting to suspect the BLN support in the kernel. I have BLN turned off, but I'm not so sure.

Hi,
Sorry don't have any answers, but am having the exact same problems on Darky's 10.1. Except I have a TouchWiz4 Port + Galaxy S II Icons.
Hopefully someone will know of this issue! Its starting to annoy me!!
Cheers,
Sunny

Tell me something, when you installed Darky, did you restore your apps via Titanium Backup? Did you select "Restore apps + data" or just apps?
I'm in the process of reinstalling Darky's from scratch, see if that works. If not I might go back to 9.5 or try Criskelo's ROM.
Thanks

Hi,
Nope I didn't backup or restore any apps. My data is all on my SD card and I just reinstall apps.. I came from DebusROM G1.
Thanks,
Sunny

Maybe a factory reset (do it in recovery) would help?

I actually did a factory reset before installing.
@sundazetoo: Do you have Voodoo lagfix enabled?
Last night, while in the process of reinstalling Darky's ROM, I disabled the lagfix (converting to RSF) and after almost an hour i decided to pull the battery. Then when I rebooted again, it went through the conversion process, finished in 2 minutes (wut!) and an error displayed (it couldn't mount some partition, one that I know is not critical).
So I'm suspecting a filesystem problem.
I already installed and DO NOT have Voodoo's lagfix enabled. I also did a complete wipe and restored my apps without data. So far it seems fine but it's only been a few hours.

@Lunchbox115: I did the factory reset when I installed too.
@ferparedes: Yep voodoo is enabled. I am now running on the stock launcher that came with Darky's 10.1 and it seems to be running a lot smoother. I was running a TW4 port so that may have been my problem!
I will monitor it and let you know how it goes.
Have you tried clearing the data / cache for the launchers you are using? That seems to fix alot of FC issues for apps for me.. I guess no harm in trying anyways?

2 days in after reinstalling.
Voodoo EXT4 lagfix NOT enabled. Phone is pretty snappy and I've haven't had any more freezes. I think it was either a bad EXT4 conversion or the lagfix itself was causing it. Anyways, since the phone is pretty fast I'm leaving it with RFS lagfix only.
One thing of note, though. I'm running stock GB launcher atm, because ADW was giving some problems.
Yesterday ADW Launcher *died* and although the phone was working and responsive, the launcher never came back. The result was that when I pressed the home button nothing happened but a blank screen. The power button worked, though, so I was able to do a clean reboot and switch to Launcher.

Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.

Same again
I get these issues too. I seem to get them RFS and ext4 (I think - mostly its been ext4 though). Often get a delay on the keyboard. Its driving me a bit nuts but I am reluctant to go back to Froyo just for this (I hate having to restore all my user names and passwords).
Silly thing is I cannot recall if I got in when I tried Gingerreal (on Darky 10.1 now).
Would love to see thoughts and theories too..
G

UPDATE
After almost 2 days of totally flawless operation, I reinserted my 16 GB Micro SD card with all of my stuff in there. Among many things:
- Audible audiobooks, along with bookmark and "furthest listened" data
- Music, playlists. All created by TuneSync (which I use to wireless sync music and playlists from my PC's iTunes)
- Dropbox download folder
- Photos and videos taken with the phone
- Some other files not associated with any app
2 hours after doing this, blam, the phone locked up again requiring a reboot. So I removed the Micro SD and when I got home I backed up my photos and videos on the PC, reinserted it in the phone and formated the card. This was last night.
So far the phone's working fine.
My current theory:
The Micro SD card I originally bought for the phone was an 8gig. When I got the 16 gig one, I just copied everything from the 8gig onto a folder on the PC, then copied everything over to the 16 one. This might've broken something.
After going to Gingerbread, it's possible that the way some applications look for their data (for example, Audible) changed but when encountering the same data (that was copied over from a windows folder on the PC) it might've generated errors which in turn put the interface into a deadlock.
My strongest suspect is Audible. After installing Darky 10.1, the app just chugged away remembering all my farthest listened to data, all my audiobooks were visible, etc. After reinstalling (and removing the Micro SD) I had to redownload some, but it still remembered where I was and didn't have to reactivate the device. Now, after formatting the Micro SD, I've had to redownload everything, it didn't remember where I was on each audiobook and I also had to reactivate the device.
If the phone doesn't lock up during the next 4-5 days then I'll conclude that errors on accessing the Micro SD by some app was the cause.

sundazetoo said:
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Click to expand...
Click to collapse
Yeah I actually don't think ADW launcher is causing this particular problem. But in a different problem altogether, it did die and in this case required me to do a reboot, albeit a clean one. But if it gave me this one single problem than I'm inclined to stop using it. I don't want the phone disabled for the 3-5 minutes it takes to boot up if I need it in an emergency (it's a phone first and foremost, after all)

tw4 is an EVIL for SGSi9000 imho... because almost everyone have problems with it !!! so just use another Launchers... LauncherPro, Launcher EX (my favourite) but not TW4 )))

I tried to fix with a reinstall of stock jvp and then went to F1 v8 jvp rkm but I also formated ext_sd card as suggested here (and deleted audible application which I was not using.
So far so good but it's only been an hour...
Sent from my GT-I9000 using XDA Premium App

Definitely something related to sd card. Everything is screwy now but less so with the sd card out.
Anyone find any solutions?
I was getting double boot screens and freezes on the dialer. Realized it was the sd when my backup would not load.
Sent from my GT-I9000 using XDA Premium App

Had this happen to me today,
I had the phone boot up and it would get to the lockscreen, then media scan, then it would lock up, only a battery pull would turn it off.
Tried booting without the External SD and it didnt occur, hmmm
Put the microSD card in the card reader on the PC, and performed a scan for errors/fix bad sectors, it didnt find anything but i put it back in and it goes fine now, im sure its the external card.

related info
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...

It did it again with the micro sd card out. So today I reformated the internal SD storage (usb storage) and will see how it goes. If this last attempt fails I will either go back to froyo or try another ROM.
But I do think it has something to do with one of the SD card storage.

gfacer said:
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
Click to expand...
Click to collapse
Should be fine

More things to try
Looked at my rom page (F1 JVP) and noticed that V8, which I have now, had the faster media scanner as does Darky's 10.1-which is not getting updates often now it seems. Well the faster media scanner only lasted 2 days until V9 of the F1 rom when the delevoper removed it. My guess it that it was causing issues.
Leads me to wonder if that might be causing the corruption in the first place or at least a contributing factor.
Also read some threads at google about similar issues across a whole wave of devices and one person there mentioned H2testw utility to test the sectors of your SD card. It sounds like cheap ebay sd card and larger SD cards my have more issues (mine is a 32gb). It is best to format and then test with h2testw but I decided to run just on the empty parts of the card and decide from there.
G