Database Info

can sim card or sd card get virus?

My g1 rebooted itself randomely even its only been 2weeks so I exchanged it and the guy said its maybe virused . But the exchaged one also rebooted just now I don't kno why and I'm using previous battery,sim card, sd card so ilm. Thinking one of them are problem
Hiow do you think?

The odds of it being a "virus" are slim to none. Give us more information on when it reboots, what you were doing prior to the reboot, etc...But it's not "virused".

Also tell us what apps you have installed and whether or not your phone is rooted.
It could be an app that is causing your phone to reboot...

do you reboot your phone everyday?? sometimes when its 'over used' the phone may reboot, i power cycle mines daily and it never reboots (by itself anymore also as the guy above said what/how many apps do u have, do you have root and what were/are you doing when the phone restarts? it most likely an app or ur very unlucky and got two defective phones

sorry, but you deserve to be called noob for that.

That pesky battery virus got your g1 2!!!!

Possible cause of reboots / hard locks?

I could be off on this one, but I'm curious if anyone else has had a similar experience to mine.
My phone locks up or restarts multiple times a day. I figured it was a hardware issue, and I've already got a replacement on the way. However, I noticed that when I removed my 32GB sdcard and placed it back in my old phone, that the G2X stopped freezing and rebooting. I placed the 32GB card back in, and the rebooting resumed.
I'm curious if there's a chance that the G2X doesn't play nice with certain brands/sizes/speeds of sdcards. Has anyone else noticed this same trend?
I'm using a Sandisk 32GB C2 card. Works great on my MT4G (still), worked great on my Epic 4G & Droid 2. Card tests out fine, so I'm curious if this may be the "source" of the bug some users are experiencing. 32GB cards causing an issue? Slower cards? Anyone have any thoughts on this?

My phone has no SD card, and I have had a few freezes and 1 reboot since I got it on 4/20.

I can't put my phone on charger without having to pull the battery to get it to turn back on.

I noticed almost everytime I accessed my 32gb sdcard that 1/2 the time it locked up.... it seems to scan the card way more than was done with my N1. Anyway...I had antivirus installed. Y the one by avg. So I uninstalled it and since I had lookout on my phone Amway...I enabledits antivirus. And it cut down. severly on freezes.
The other thing I noticed is only do your overnight charging with the LG charger that came with your G2x. Or any long term charging I think.
Also... I know this sucks...but if I turn off my phone and turn it back off every morning I do not get reboots or wake up to a dead phone. I saw this mentioned in another thread somewhere and it seems to work. After I hit about 24-48 hours of uptimei get issues.
Well I hope some of this helps.

Removal of battery while charging

Heya! Im new on this site, but i got it recommended by a friend of mine. I have this mindbreaking problem. The thing is, a couple of nights ago, i came home from this party, and i was, very tired. To this party, i had brought my old phone instead of my brand new Desire S, so that no damage would be inflicted. So i removed the battery, to put my sim card in, while it was charging. The charging light was green tho' (dont know if that makes any difference). Now, the next morning, my phone went crazy, saying the sim card was full. And the phone was just generally really slow, not really responding and stuff. I restarted it, and then it said it had recovered from a system breakdown. Now my phone seems normal, but it brings me in such pain, not knowing wether my phone works as it should, or not. I could possibly know this since i only had my Desire S one day before the incident.
What to do?
Could anyone help me?

BTW i would've lovede og someone answered

willi0201 said:
BTW i would've lovede og someone answered
Click to expand...
Click to collapse
The green light indicated that the battery was charged to 100% so therefore didn't need further charging.
The error message that you received comes as a result of you removing the battery while the phone was party operational, in deep sleep mode. You need to disable the fast boot option (within Settings->power->Fast boot) in order to fully power it off.
I can't explain the phone slow behavior but unless the same thing has happened again since, I don't believe that this is anything to worry about.
I don't really understand the SIM card full comment, has the limit of SIM card contacts possibly been reached? Check the number of ocntacts that are stored on the SIM. Although with a phone like this contacts should ideally be stored in the cloud ie, Google/Facebook etc and not directly on the SIM, so I'd suggest moving them.
So, I'd do nothing and see what happens if anything again.

However if it continues, a factory reset would be my next move.
Sent from my HTC Desire S using XDA Premium App

Is My VZW S3 Dead? (Symptoms in Text)

About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.
Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.
The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.
Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.
----------------------------------------------
The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).
I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.
Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).
The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks

Armando Penblade said:
About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.
Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.
The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.
Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.
----------------------------------------------
The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).
I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.
Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).
The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks
Click to expand...
Click to collapse
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This doesn't seem to have any effect on the proceedings.
I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.

Armando Penblade said:
This doesn't seem to have any effect on the proceedings.
I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.
Click to expand...
Click to collapse
But that's what it's supposed to look like when it's hard bricked, keep trying to write it then boot with it. Eventually it's going to work, unless you somehow fried your motherboard.
Sent from my SCH-I535 using Tapatalk 2

Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.
Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?

Armando Penblade said:
Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.
Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?
Click to expand...
Click to collapse
Not really, if you're getting that error message I'm assuming this should work. At the very least you could get a jtag repair and that'll definitely fix it. You could always try the other debrick file available from that thread also.
Sent from my SCH-I535 using Tapatalk 2

Verizon s3 SIM and SD card Failure

So, my mom's phone started acting up yesterday.. and a few months before...
Long Story:
A few months back, I noticed that my old s3(my mom took it, she liked it a lot) didn't recognize the SD card. I didn't think much of it(it was long out of warranty both ways). It didn't matter much either since I had everything backed up and my mom had only 3-4 apps. Lately, she was saying that it ran slow, and today, she said the phone would restart. I did not see it until 3 hours later. The warning said the SIM card was undetected and it rebooted. I took the battery, SD, and SIM out. I tested the SIM in my s4(which reads a 16 gig SD fine) and it didn't see anything. I assume that either A) it died or B) the phone somehow killed it. I cleaned all of the ports with some compressed air and put everything back in. Now, I cleared the cache and did a odin back to NE1 as well. So far, no issues, but I'm still worried. What is causing this?
TL;DR: Phone does not like the SIM and SD card all of a sudden.