Database Develop

Help G1 is crashing constantly

Hi, I recently flashed my phone to cyanogens 3.6.8.1 all was well until yesterday when the phone screen displayed vertical lines like a grey color, the phone could receive calls but from t mobile customer service and it was booting up tho I couldn't see the screen. Then I took the sim card out and the screen returned to normal but was stuck in the splash screen. I reflashed and sometime the next day it happened again, this time I took out the sim card and it went back to normal
Any ideas

Jonnibravo said:
Hi, I recently flashed my phone to cyanogens 3.6.8.1 all was well until yesterday when the phone screen displayed vertical lines like a grey color, the phone could receive calls but from t mobile customer service and it was booting up tho I couldn't see the screen. Then I took the sim card out and the screen returned to normal but was stuck in the splash screen. I reflashed and sometime the next day it happened again, this time I took out the sim card and it went back to normal
Any ideas
Click to expand...
Click to collapse
Could you post a log of this? Could you also provide some more details about your set-up (a2sd? swap? comcache? spl/recovery?) and how did you get to this point (did you wipe before flash? did you run any back-up apps, what were you doing when it happened?)
Once we have that info we should be able to figure it out.

I started out with th jesus freak rom then I decieded to flash the cyanogens 3.6.8.1, I had trouble with the market because I hadn't wiped first, I did that and all was well for at least 5 days. I created an ext2 partition for apps2sd but I'm not sure if that worked. Then on the Saturday 6 days later I put fotmob on my phone so I could keep an eye on the opening premiership season put the phone in my pocket whilst at the football and 2 hours later the phone screen was dead, nobody could call me tho I know the phone was operating and booting only t mobile manage to get through, I tried a reboot, then took the sim card out and the screen went back to normal but was stuck on the splash screen. I tried fixing file ext but came as error asomething about the super block being unreadable tried manually but didn't work, tried backup still stuck, reflashed worked fine for. 20 hours then it happened again this time I wasn't doing anything with the phone no programs other than the usual running in the background, this time I removed the sim card and the phone went back to normal again for about 4 hours then it happened again this time removing the sim didn't work.straight away but eventually it came good again.
Its now 11 15 and its running fine again. I have noticed that I now only have one ringtone (dream theme) and one notification tone and I'm getting a few force closes tho I not sure what they are I will report them if and when I see them

you need to get audio resources and unzip to the sd card all the ringers. search xda for audio resources

The screen went dead again at 3pm this time after removing the sim card it stayed the same it was only after leaving the battery off it returned to normal again about 10 minutes later, I am also getting a vending core force close from time to time, please someone help me solve this issue.
P.s I've never actually seen the phone do this it happens when it is in my pocket when I get it out it happens also this time I have not installed any software and it is still happening

Jonnibravo said:
The screen went dead again at 3pm this time after removing the sim card it stayed the same it was only after leaving the battery off it returned to normal again about 10 minutes later, I am also getting a vending core force close from time to time, please someone help me solve this issue.
P.s I've never actually seen the phone do this it happens when it is in my pocket when I get it out it happens also this time I have not installed any software and it is still happening
Click to expand...
Click to collapse
Because you lost your ringtones, it sounds like your SD card is acting funny, I would format it using this guide (make only 2 partitions for the time being, fat32 and ext3).
See if that works...May be complete reflash with wipe wouldn't be a bad idea neither.
That's all I can suggest at this point, I'll need to see a log to be anymore specific, but try this out, sounds like you've got nothing to loose
Good luck.

Thanks for your reply I am very greatful, I have tried a different sd card without setting up partitions and it still happens. I think the latter is true and a complete reflash is definately the thing to do.
I think this may be a hardware issue because as I mentioned it only happens when it has been in my pocket for a while, perhaps it is overheating or something.
I'll try a complete reflash and let you know if it happens again.

Wipe, re-flash, reformat your sd (or take it out altogether, just to rule it out see what happens... This is all I can tell you....
good luck

Black Screen, but Recovery Console works

This has been an ongoing problem with my G1, related to modded ROMs from what I can tell.
I suppose I should point out, before going into my problems, that I am indeed a noob.
So, back to when I first got my G1.
Quite quickly, I decide I want to root my phone. I follow Cyanogen's guide through every step, and I am able to boot. Cyanogenmod works fine for about a couple weeks.
Suddenly, while I'm listening to music and on the home screen, the screen seems to tear, I suppose you could call it. I don't know the real term for it; it's a problem that usually occurs when programs use indirect allocation of memory. This causes my screen to freeze. When I hit the power button, followed by the menu button (to turn off and on the screen) the backlight turns on, but there is no display. Restarting does nothing, no G1 screen and no recovery.
Just pulling the battery for a brief amount of time seemed to fix it. This quickly stopped working, forcing me to flash ROMs until I had enough of a screen to go back to scratch. It used to only happen when multitasking on the home screen, but with a modded rom, this has started to occur even on boot. Eventually I had to go back to using unrooted OTAs.
I've had this happen with TheOriginal AOSP 1.6, Cyanogenmod 4.2.14.1, and Super-D 1.9.2. I've tried both Amon's and Cyanogen's recovery images, with and without the Danger SPL. Actually, the Danger SPL would stop the screen after a shutdown.
Does anyone have any idea what's going on or if I can run modded roms on my phone?

Tony_SpaZ said:
This has been an ongoing problem with my G1, related to modded ROMs from what I can tell.
I suppose I should point out, before going into my problems, that I am indeed a noob.
So, back to when I first got my G1.
Quite quickly, I decide I want to root my phone. I follow Cyanogen's guide through every step, and I am able to boot. Cyanogenmod works fine for about a couple weeks.
Suddenly, while I'm listening to music and on the home screen, the screen seems to tear, I suppose you could call it. I don't know the real term for it; it's a problem that usually occurs when programs use indirect allocation of memory. This causes my screen to freeze. When I hit the power button, followed by the menu button (to turn off and on the screen) the backlight turns on, but there is no display. Restarting does nothing, no G1 screen and no recovery.
Just pulling the battery for a brief amount of time seemed to fix it. This quickly stopped working, forcing me to flash ROMs until I had enough of a screen to go back to scratch. It used to only happen when multitasking on the home screen, but with a modded rom, this has started to occur even on boot. Eventually I had to go back to using unrooted OTAs.
I've had this happen with TheOriginal AOSP 1.6, Cyanogenmod 4.2.14.1, and Super-D 1.9.2. I've tried both Amon's and Cyanogen's recovery images, with and without the Danger SPL. Actually, the Danger SPL would stop the screen after a shutdown.
Does anyone have any idea what's going on or if I can run modded roms on my phone?
Click to expand...
Click to collapse
Please post what you have on your SD card, partitions, sizes, like that. Make your self a signature with all that stuff and you'll only have to do it once.
Also include if you are running swap compcache or whatnot. I know some of the roms you tried do some of those by default.

I'm still using the 1gb that comes with the phone with one FAT32 partition, should be getting a 8gb class 6 tomorrow. I had tried using a 256mb ext3 and a 64mb swap, but reformatted in case that was the problem.

Tony_SpaZ said:
I'm still using the 1gb that comes with the phone with one FAT32 partition, should be getting a 8gb class 6 tomorrow. I had tried using a 256mb ext3 and a 64mb swap, but reformatted in case that was the problem.
Click to expand...
Click to collapse
I have to admit, I was thinking the same thing. I have never tried one of the modded roms without the ext partition but it should run fine. Usually slow downs that occur over time are cache (swap) related.
I would get your new card, partition it using amon-ra, wipe everything, and use the newest super D.
If it still fails, you may want to look for a stock version. There should be one here somewhere with only root added.

Alright, just got the new card. Should be done with all installing within a few hours. Fingers crossed, eh?

<crosses fingers> lol

Hmm, phone is acting even weirder than before. As of right now, I get my screen back every reboot, but with a custom rom, it fails on boot. The boot screen will freeze, followed by a backlit black screen. I'll keep trying, but I thought I'd see if anyone had any helpful tips, perchance?
(This is attempting to get Super-D going, although I had tried Cyanogenmod earlier with the same result. Downgrading with the dreaimg.nbh still boots fine, however.)
E: Although I'm not sure what exactly did it, it seems to be working now... for now. The fact that the glitch was similar but still improved gives me hope, however.

Crap, it died again on me using Cyanogenmod with Enoch, both fully updated. Anyone know where one of those stock with root roms are?
E: Actually, better yet, anyone know if there's any way I can tell what I'm doing with my black screen? I'm trying to apply stuff with RA-dream, but it's kinda hard, what with the lack of vision and what-not.

Tony_SpaZ said:
Crap, it died again on me using Cyanogenmod with Enoch, both fully updated. Anyone know where one of those stock with root roms are?
E: Actually, better yet, anyone know if there's any way I can tell what I'm doing with my black screen? I'm trying to apply stuff with RA-dream, but it's kinda hard, what with the lack of vision and what-not.
Click to expand...
Click to collapse
you can do a logcat right before it goes out connect your phone to your comp and do adb logcat and do everything your normally would do and if it goes out again and you see a significant in the log from the phone dying then copy that text and post it here. maybe someone can help out.

Ah, I may have explained badly. I've no display at all; no G1 logo, recovery console, or spl. They still work, though. Alt + T while in the recovery console still throws it into USB mode.

If you install the android sdk on your PC, you can use the USB lead to log all activity on your phone.
You would then see where it is crashing (and with any luck why)
It would be painfull because it seems random and intermittant, but atleast you would know why and have a point to look at.
http://developer.android.com/sdk/index.html
btw, original rom (rooted)
http://forum.xda-developers.com/showthread.php?t=538456

Sadly, it locked up yet again. It seems this is the logcat entry linked to the problem;
W/SurfaceComposerClient( 1297): lock_layer timed out (is the CPU pegged?) layer=0, lcblk=0x
42664020, state=00000042 (was 00000042)
W/SurfaceComposerClient( 101): lock_layer timed out (is the CPU pegged?) layer=3, lcblk=0x
426301a0, state=00000007 (was 00000007)
This is looped until the power button is hit, which then keeps anything from appearing on the screen.

Ah, now I can't boot. It seems my GPU is acting up in some way shape or form.
I/SurfaceFlinger( 110): SurfaceFlinger is starting
I/SurfaceFlinger( 110): SurfaceFlinger's main thread ready to run. Initializing graphics H
/W...
D/SurfaceFlinger( 110): pid 110 requesting gpu core (owner = -1)
W/SurfaceFlinger( 110): couldn't grant gpu core to pid 110
D/EGL ( 110): requestGPU returned -1
E/libEGL ( 110): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
Shortly followed by...
E/libEGL ( 110): validate_display_surface:536 error 300d (EGL_BAD_SURFACE)
E/libEGL ( 110): call to OpenGL ES API with no current context
I/SurfaceFlinger( 110): OpenGL informations:
E/libEGL ( 110): call to OpenGL ES API with no current context
Which then throws it into a loop.

I would install the latest Cyanogen and make sure the phone is clean.
Run a logcat from boot, and then when it crashes post the full logcat + info on the bugs cyanogen page.
http://code.google.com/p/cyanogenmod/issues/list
The support seems to be good there, but they will want a clean install etc..

Camera Error - Cannot connect to camera

Ok, so everything was working fine yesterday. I woke up this morning and decided to play a little 'world of photo'. It FC's, so I mess with it for a little bit before just trying to open my normal camera. When I try to open my camera, it puts the screen in sleep mode, so I have to hit the power button and unlock the screen like normal, then it gives me the error "Cannot connect to camera".
My phone is rooted and flashed with the latest Cyanogen business, but like I said, nothing was altered, updated, downloaded, etc. My camera just stopped working. Anyone have any thoughts or ideas? Really hoping to get this resolved without having to contact HTC, as I'm sure the unlocked bootloader screen will cost me a small fortune.
If I open an alternative camera app, it opens, but doesn't work. I can back out and then go to my default camera and it works until I close it. Then it won't open again without having to go through the steps of opening the other app, etc.

I'd try a nandroid restore.

Tried it already. Tried restoring back to original, wiping, everything else. Nothing worked. Camera wasn't working all morning, now all of a sudden it's working again. Guess I'll just count my lucky chickens and chalk this up as a win...

Well, my happiness was short lived. Still having the same problem. I'm really not sure what exactly it could be. But the fact it worked the one time today gives me hope.

also having this problem. tried a nand backup and also wiping and re-flashing the gapps and the cm-5.0.4.1 update.. still nothing

it seems my camera went bad somehow, tried even flashing the stock rom, nothing... i'm calling htc, crap my phone is unlocked.. wish me luck.
update: yeap, im getting a replacement. they put $529 on hold on a credit card, send you the device and once they get the "damaged" device they release the funds... meh..

Hey velazcod, you think we can get an update on his this worked out? I'm having the same camera problem and I too am bootloader unlocked. I'd like to hear how HTC handled your unlocked device.

sorry for not posting a status before... so here is what happened:
- Called HTC and they didnt have any issues replacing the phone since the issue seemed to he a hardware issue. They have been nice about this, depends on the hardware issue, I guess if you burn the motherboard they will probably get *****y.
- You can send it to get repaired or replaced, both are in warranty, unless they find some other issue (water damage, etc). However, if you decide to get it replaced they would take your credit card, and put $528 on hold for a few days until they get the original phone back. They dont actually charge it to the credit card, just an authorization, it all depends in your bank, for example my bank (chase) put the money back in my account after 5 days.
- Anyway, I got my "new" N1, and I double checked everything before unlocking the bootloader and doing our stuff. The phone was crap, it was slow and the sticker on the battery cover seemed like it was removed, maybe a refurbished unit. I called and *****ed about it, and they said I needed to send my original phone back, and then later on request another replacement. I kept *****ing because I could live with a bad camera for a few weeks, but not with a slow phone
- Anyways, in the end they allowed me to send back that refurbished unit. After a few weeks i had no response from them and I had to call them, a day after i got my new phone, this time it was good, so i unlocked it, did my thing, factory reset the original phone and sent it on its way.
- It all seemed good for a few weeks, until i got a call from HTC saying that I needed to pay for a repair fee ($60 something) because they had found the problem had been user damage. the girl had no idea how to back that up, and i kept saying that i had never drop the phone or broken the camera in purpose (which is true). She said she was going to escalate the issue and I would get a call back. Still waiting.
In the end I got my new phone and we are all happy, but be careful, I love HTC but don't let them screw you.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

$60 isn't that bad. I would be interested in exactly what they found.

yes that isnt that bad. and i would pay it no problems if it really was my fault. but really, i take care badly of my phones and i had never drop or have done anything to my phone that would cause this camera issue.
besides, the girl that called me had no idea what really happened or what they found, when they call me i will post the info here.

Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.

moto211 said:
Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.
Click to expand...
Click to collapse
Well, keep in mind that it could be a placebo effect, and you think you are fixing it by fiddling the SD card but its not real.
The reason I tell you that is because, when the issue started happening for me, I would get that error randomly, and then it started happening more frequently until it totally stopped working.
Also, the Camera app not detecting the SD card gets an error when you try to take a picture and it actually says the specific SD card error. Try taking the SD card out and try it out, you will get a visual of the camera on the display, but when you try to take the picture it gives out the "SD card not detected" error... on the other hand, you might be experiencing something totally different.
This error "cannot connect to camera" also comes with the camera app not loading completely and visual of the camera not loading on the screen. Also try loading up the Barcode Scanner, you should get a similar error and no visual of the camera.

I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.

moto211 said:
I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.
Click to expand...
Click to collapse
I see what you mean. Makes sense, keep us posted.

Update:
So, although the fix I previously mentioned did work, I started having other issues that indicated that the actual camera hardware was failing. When I would start up the camera app the camera image displayed on the screen started showing color distortion. Sometimes it would do that and sometimes it wouldn't. I noticed that if it wasn't distorted, I could lightly squeeze the sides of the phone and the image would become distorted and would not go back to normal after I stopped squeezing. I figured that indicated hardware issues but decided to try a low level format on my memory card just in case it was an issue of bad blocks on the card. The format didn't fix anything. A few hours later, the camera died and never came back. I started a ticket with HTC for an advanced replacement. I received my new phone on Friday and am sending back the old one today. I restored it to unrooted factory ROM and recovery image. I will keep you guys posted as to what, if any charges they try to stick me with.

moto211 said:
Update:
So, although the fix I previously mentioned did work,......
Click to expand...
Click to collapse
crap, that's what i thought. that sucks. keep us posted :-/

Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.

moto211 said:
Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.
Click to expand...
Click to collapse
Good to hear that.
On my case, I was never contacted again by the "escalated rep"... but I just checked my ticket/case and it seemed to have been closed, so I guess good news.

Hello Guys,
I am having the same problem as you both had. Í am seeing the same symptoms such as not able to run the camera app. My phone screen goes blank when i try to open the camera app and the bar scanner program says it cannot connect to the camera and that I might need to restart my device. I have tried to use previous roms and removed the sd card but nothing seems to work. I am wanting to send it in for repair but I wanted to know what else I should do to my phone besides reflashing the stock rom. Did either of you have the amonRa recovery program and how did you remove it if you did. Is there anything else I should do?
Thanks.

I got the original shipping rom package from modaco and renamed it PASSIMG.zip and flashed it from the bootloader. It restored everything to stock...recovery, radio, and os.

Second time phone randomly froze, bootloop, then apps corrupted on SD card

I think it's honestly apps2sd or something hardware related. I'm rooted on stock without unlocking the bootloader and I believe I've had this issues with my phone before I rooted.. leading me to believe it's just something with apps2sd.
Phone just crashed when I was doing something on twitter (in the twitter app). It is now in a long boot up phase, and it eventually reaches the home screen however it's slow and then eventually unresponsive and goes into a boot sequence again. I'm pretty sure pulling the battery will fix it.. but I've let it keep going.
Here's some logcat's started at various times in the boot sequence.. eventually it reboots but it just keeps on spitting out the unexpected exception collecting process stats crap which is in the following logs (along with other potentially useful information):
Paste1:http://pastebin.com/tuGs0ctD
Paste2:http://pastebin.com/gdxEG9b
3rd which is started after it boots and then decides to go into a boot loop after. http://pastebin.com/v3MWHcw9
It has now finally stopped without me pulling the battery. However I LOST APPS. This has happened before. Any apps on my SD card are now just the default android icon and they don't launch. They show up without the right icons also in manage apps when I have the list of apps on the sd card. In adp logcat I keep getting this repeating no matter what's going on:
Code:
E/ActivityManager( 406): Unexpected exception collecting process stats
E/ActivityManager( 406): java.util.NoSuchElementException
E/ActivityManager( 406): at java.util.StringTokenizer.nextToken(StringTokenizer.java:272)
E/ActivityManager( 406): at com.android.server.ProcessStats.getCpuSpeedTimes(ProcessStats.java:520)
E/ActivityManager( 406): at com.android.server.ProcessStats.getLastCpuSpeedTimes(ProcessStats.java:486)
E/ActivityManager( 406): at com.android.server.am.ActivityManagerService.updateCpuStatsNow(ActivityManagerService.java:1540)
E/ActivityManager( 406): at com.android.server.am.ActivityManagerService$3.run(ActivityManagerService.java:1466)
What the **** is going on with my phone? Has apps2sd ****ed up on anyone else like this corrupting all the apps installed the sd card and causing a boot loop like this? This is pissing me off... I now have to redo everything *again* installed on my phone just when I got it how I liked it.
Edit: I can confirm this is some sort of ****ty apps2sd bug or application causing this. It's at this point not all apps that are affected (unlike last time) it seems but going into the manage apps and going to apps2sd and trying to uninstall one of the ones (about 4 or 5 apps out of 20 on sd) that doesn't have its own icon (guessing its corrupt) caused the phone to instantly restart.
Edit2: Pulled the battery. Seems to be more responsive and without the repeating bs in the logs over and over again. There was alot of activity and have the full log from when it turned on after the pull here: http://fedora.pastebin.com/U2hFN8gT . It somehow fixed itself and there doesn't seem to be any apps missing or apps corrupted from the SD card. Different outcome than last time. Anyone know how to prevent this in the future or what triggered it?

The very first time I rebooted my Nexus One about two months ago I had similar; said the SD card was corrupted, offered to format it. I powered down, was thinking about putting the card in my computer to run fsck on it but then realized I didn't have an adaptor, so figured I'd do it in the phone, powered back up. No problem. Timing?
Otherwise, a fsck often fixes weirdness with this sort of thing, but who knows what breaks if it finds bad chains etc..
In the case of Apps2SD, I wonder what happens.. do you get broken apps, but at least you can remove/reinstall them, or are they just gone and you don't really know what's missing now?
Other problem with reinstalling is most apps in Android are set to remove all data, setup etc, so then you gotta set it all back up again.

I honestly have no idea what happened. This is the second time this has happened and last time every app on my SD card was replaced with a generic android os icon (if they were on my homescreen) and when i went to manage apps and clicked on sd card all of them had that same icon without their respective icon's. Obviously i couldn't launch them. Further more I couldn't install any apps at that point, even ones different than the ones installed on my sd card. It would just stay at "installing" until I canceled it out in market. So I wrote down the ones on the sd card, had a recent backup, and did a factory reset/nandroid and deleted all the stored apps on my sd because after that it was still the same issue when I did the backup (the saved files on the sd being corrupted).
I've checked the sd card now 3 times reading and writing to it with a program to detect flash drive problems. I'm pretty certain I had the problem the first time on my old sd card that came stock with the phone.

Bad SD for me.
Sent from my Hero using XDA App

poochie2 said:
Bad SD for me.
Sent from my Hero using XDA App
Click to expand...
Click to collapse
How did you know it was bad? Mine has been tested abuot 4 times now on reading and writing to it using a program I googled. Reformated, ran the program to write/read to the flash drive and no issues.

Crashed internal sd card...

Does anyone have any idea on how to revive a crashed internal sd card.. since mine refusing to boot
send from mah magic toaster
nvm fixed it by dropping the phone on the floor.. (vip service as a backup makes stuff like dropping phones a bit easier xD)