Database Info

Asus P525 - Invalid or missing sim card ???

Hi All, I've down a fair bit of web searching but haven't found a reason as to why this would be happening. So here goes:
Basically, I bought the Asus P525 when it was about 9 months old, and after about 4 months it decided to flash this up on my screen - Invalid or Missing Sim Card. It seemed to fix itself, however, and I had another week of using it. Then, it did it again, and fixed itself again shortly after, but it wasn't long before it was dong it so often that the phone became unusable. It would flash that up, and usually stay that way, it would become a rarer thing for it to fix itself. So, back to my crappy old nokia with half working buttons I went, telling myself I should ring an Asus repair center and talk to them about it. Anyway, a couple of months later I got around to ringing them, they told me they'd probably have to replace the mainboard, and it could cost me more to do that than to get a replacement phone. Not very impressed as I was, I decided to boot the phone back up, and amazingly it worked again, and gave me another week of usage before packing it in. Now it's stopped working, so I tried different roms and different firmware, to see if that would fix it... nope.
So here I am. Anybody experienced this? Any idea what I can do? I don't have heaps of bucks to throw around on phones, I really like this phone except for this obvious problem, so would like to keep using it. But I don't think the future looks bright for it
Any help is extremely appreciated.
Thanks
Matt

Seems I've asked the impossible...? Anybody have any ideas? I'm going out of my brain trying to work this one out...
Matt

It seems noone in this part of the forum likes to answer questions I'm afraid.
As to your problem, it's likely a hardware fault and theres a loose connection betweeb SIM and phone somewhere.
You could try cleaning the contacts with an electrical contact cleaner solution sprayed on a cotton bud and wipe the pins that sit on the SIM.
Maybe you could also try using a needle underneath the pins and gently pull them up so that they make better contact with the SIM (maybe some are bent).
Bear in mind, I have no experience with this device and the sensible option would be to take it to a repair shop for service.
Hope that helps.

yeah I know what you mean
Thanks for the suggestions. I have tried to bend the pins up but that didn't work. I haven't tried cleaning the contacts... sadly though I think that may not be the issue. I'll definitely give that a go, I'll try just about anything, because obviously if I can't get it to work it will just sit in my girlfriend's car so she can use the maps and camera on it. Seems such a sad waste really...
thanks again for your help
Matt

I just powered it up, and it's working again. God knows for how long though... could it be a battery or cpu issue?

Unable to boot up until I plug my G2x into my notebook for 2 seconds. Normal?

Hey all,
I've got a rather funky bug going on here. I'm told it's not uncommon for G2x phones to suddenly turn off and require users to take out the battery for a reboot. But I recently ran into a super weird issue.
Tried to use my phone, encountered a black screen. Tried to turn it on, even took out battery and placed it back in with no luck. Went home and plugged it into adapter, got a screen showing the battery charging but that's it. With the battery out, pressed the boot screen, got the white LG logo before it turned off again.
Problem was solved as soon as I plugged the phone into my notebook instead. Booted up normally with no problems!
Is this a common occurrence?
If this problem persists, I might have to sell this phone (bought it on fleabay) and get a different one. Dang LG really rushed the G2x in spite of flaws!
If that happens, I'll be needing recommendations for a new phone.

I don't think this issue is common, this is my 1st time reading about it, and it certainly hasn't happened to me! good luck, if you're changing phones I'd suggest the galaxy Nexus

jj_z1 said:
I don't think this issue is common, this is my 1st time reading about it, and it certainly hasn't happened to me! good luck, if you're changing phones I'd suggest the galaxy Nexus
Click to expand...
Click to collapse
GSN is too expensive for me. Was hoping for under $300.
Was contemplating the G4SG, but I hear that while having fewer bugs, it's also a lot slower overall. I can't live without my cheap dualcore!

That's an odd one, a couple of things I will say:
I've noticed that for me if I have it plugged in and powered down then try to boot it, the thing won't start. I have to unplug it, boot it and plug it back in once it's started up initially.
Also, if you're considering loading a custom ROM, do it and if the thing is still acting like that, throw it at the nearest T-mobile store, and be sure to hit someone with it.

Волк said:
That's an odd one, a couple of things I will say:
I've noticed that for me if I have it plugged in and powered down then try to boot it, the thing won't start. I have to unplug it, boot it and plug it back in once it's started up initially.
Also, if you're considering loading a custom ROM, do it and if the thing is still acting like that, throw it at the nearest T-mobile store, and be sure to hit someone with it.
Click to expand...
Click to collapse
It was rooted with Tsugi. I haven't had any other issues yet. Rooted/flashed it yesterday, this is the 2nd day in.
And I don't have a receipt for the phone. Bought it used from another person. :/

zeth006 said:
It was rooted with Tsugi. I haven't had any other issues yet. Rooted/flashed it yesterday, this is the 2nd day in.
And I don't have a receipt for the phone. Bought it used from another person. :/
Click to expand...
Click to collapse
Try a different ROM, didn't you buy it off E-bay? If nothing else, either e-bay or paypal (assuming you used it) should cover you if you were given a lemon.

Волк said:
Try a different ROM, didn't you buy it off E-bay? If nothing else, either e-bay or paypal (assuming you used it) should cover you if you were given a lemon.
Click to expand...
Click to collapse
I'll see what happens. If the phone turns out to be a lemon, I'm going to request a refund and go the paypal dispute route if I must. I'd rather not have to.
It's a real shame too. This is a really nice phone.

Flash phoenixblood 1.7 rom and use faux123 stock cm or DS. 0.4.8 kernel, I can almost 100% guarantee you that will solve your problem.
Sent from my LG-P999 using xda premium

something similar happens to me never tried the rom your on but what i did to fix was: Settings>Applications>Development> check stay awake it helped me out maybe it will help you. let me know how everything goes.

zeth006 said:
GSN is too expensive for me. Was hoping for under $300.
Was contemplating the G4SG, but I hear that while having fewer bugs, it's also a lot slower overall. I can't live without my cheap dualcore!
Click to expand...
Click to collapse
I actually just sold my g2x and went back to my GS4G and don't regret it. Running octane 3.0 the speed difference is so negligible you won't even notice it unless your comparing them side by side.
Sent from my SGH-T959V using xda premium

If it happens again then sell it, the only thing that makes this phone unable to compete with the Galaxy Nexus is that it doesn't have ICS yet, and the screen is smaller and in lower resolution. But I believe if you get a good one then performance is better than the Gnex seeing as the highest clock speed I've seen achievable and stable for the Gnex is 1.35, and the GPU is slow and outdated. The camera on the G2x is also higher resolution, but lacks the lagless shutter.
This phone may be cheap, but it is very powerful. The only reason it had so many complaints is poor quality control, and very bad software developers. Hardware is crazy though.
If you were to sell your G2x, I'd take the Galaxy S II HD version over the Gnex.

Possible to flash radio / rom / anything with broken USB?

After I got my skyrocket, many of my friends and family also decided on the skyrocket Well, now it's up to me to make sure they're all in working order.
So one of my family members left her skyrocket in a bag of water for a while while she was at the beach, and it was completely unresponsive. I fully disassembled it (not my first time), dried out the majority of the water, then left the phone in rice for a few days. The good news is, the phone boots up and seems to work. The battery still works and it charges over USB.
The bad news is, the cellular radio does not work, IMEI comes up as unknown, bluetooth mac is "unavailable", front facing camera is also unresponsive. Really bad news: data/adb over usb does not register at all. A few more days in rice haven't helped.
The phone is completely stock. My first thought was that flashing a new radio might reset the cellular somehow, but not having cwm/odin makes that impossible. I can't seem to get the phone into download mode either because of the USB problem.
One thing that DOES work is the stock recovery. I can tell it to flash the official ATT ICS build, which contains a radio!
However when I try flashing it says.. "E: Short write of /tmp/sideload/package.zip (No space left on device) Installation aborted". Other zips "failed to verify whole-file signature"
Any ideas? My next step will be buying a used skyrocket with a cracked screen, and transplanting the working screen from this unit...
Tom

First off, please use the Q&A section for, you know, questions and answers. Don't create a new thread; I'm going to ask the mods to move this one instead.
Second, your issue is that the hardware radio is dead. The stock ROM only has a software radio included. To put it a different way, the stock ROM includes programming that tells the cell radio what to do. It can't fix the cell radio if it's broken, though. Unfortunately, based on the amount of damage you've got there, I'd say your phone is pretty much toast.
If you're completely stock, try to warranty it out. Just be up front with Sammy about what happened (because, in this instance, they will figure it out if you make up a story or play dumb), and the worst thing they can say is no. You might get a sympathetic rep who'll help you out. If they won't take it, you've already got your backup plan in the working SR.

T.J. Bender said:
First off, please use the Q&A section for, you know, questions and answers. Don't create a new thread; I'm going to ask the mods to move this one instead.
Second, your issue is that the hardware radio is dead. The stock ROM only has a software radio included. To put it a different way, the stock ROM includes programming that tells the cell radio what to do. It can't fix the cell radio if it's broken, though. Unfortunately, based on the amount of damage you've got there, I'd say your phone is pretty much toast.
If you're completely stock, try to warranty it out. Just be up front with Sammy about what happened (because, in this instance, they will figure it out if you make up a story or play dumb), and the worst thing they can say is no. You might get a sympathetic rep who'll help you out. If they won't take it, you've already got your backup plan in the working SR.
Click to expand...
Click to collapse
Meant to post this in Q&A, woops. Too many xda tabs open trying to figure this out. Sorry about that
I do know the difference between the hardware/software radios... My thought was that while the phone was turned on and submerged, the software radio could have become corrupt... A long shot perhaps
I'll try contacting samsung, but somehow I doubt they'll cover it. Sidenote, do you really think they have a more sophisticated way to check for water damage than the internal water-damage indicator sticker?
The question still stands though, if anyone is interested. Even without a cell radio, I'd like to be able to root it for other purposes
Thanks for the advice
Tom

dutchthomas said:
Meant to post this in Q&A, woops. Too many xda tabs open trying to figure this out. Sorry about that
I do know the difference between the hardware/software radios... My thought was that while the phone was turned on and submerged, the software radio could have become corrupt... A long shot perhaps
I'll try contacting samsung, but somehow I doubt they'll cover it. Sidenote, do you really think they have a more sophisticated way to check for water damage than the internal water-damage indicator sticker?
The question still stands though, if anyone is interested. Even without a cell radio, I'd like to be able to root it for other purposes
Thanks for the advice
Tom
Click to expand...
Click to collapse
Yeah, based on the amount of things going wrong, it's hardware. If the software radio was corrupt, it would be because the internal storage had been corrupted, and your phone likely would not boot.
And yes, they can find water damage beyond the sticker. They can see corrosion plain as day when they open it up and look at the internals.
You can root it without USB working. Is your wifi working? If so, download GooManager off the market, then follow the instructions in the TWRP thread to get TWRP on your phone. Download a custom ROM to your PC, then transfer it to your external SD using an adapter/card reader so you can place it on the card directly (instead of going through the USB port). Use TWRP to flash the pre-rooted ROM onto your phone and viola. Unless there's a pre-rooted stock out there (and I don't think there is for SR), a custom ROM is the only way I can think of to do it.
Be advised, though, that because of the amount of damage done to your phone's internals, there's a better-than-normal chance that something won't work and you'll brick. I'm not responsible for your decisions or for the brick if that happens.
Long story short, just get a replacement SR.

Same thing happened to my girls Atrix. She gave it a nice bath in Green Tea. After shutting it down and pulling it apart I gave it the rice treatment for 48 hours. Booted but returned a radio error. Her USB port was working so I was able to root it and install a few custom ROMs on it. No change. So I would bet you actually fried the chip. Call Sammi and get a quote to cover the repair which will be a new mobo. They pay shipping both ways and are usually pretty cheap.

hechoen said:
Same thing happened to my girls Atrix. She gave it a nice bath in Green Tea. After shutting it down and pulling it apart I gave it the rice treatment for 48 hours. Booted but returned a radio error. Her USB port was working so I was able to root it and install a few custom ROMs on it. No change. So I would bet you actually fried the chip. Call Sammi and get a quote to cover the repair which will be a new mobo. They pay shipping both ways and are usually pretty cheap.
Click to expand...
Click to collapse
Heh, this is my mother's phone actually. First she ripped the screen ribbon cable on a nokia E75. Then she smashed her Atrix's screen, tried to fix it herself with a new screen, and managed to rip part of a ribbon cable... so it no longer has a working touch digitizer. Now she left her skyrocket in a bag of water. The girlfriend managed to crack her skyrocket's screen, which I replaced... I've also had to fix 2x nokia N95's, an N97, and a bunch of water damaged dumb phones over the years...
FWIW, the skyrocket seems to have the best repairability / internal layout of any of the phones I've messed with
The cracked screen skyrockets on ebay seem to be going for more than I thought, so I'll be giving sammy a call for sure

[Q] Intermittent "No SIM Card-Emergency Calls Only"

Alright everyone, I've Googled my brains out (not in a dirty way) and haven't found any real resolution to the above issue. I've tried all the usual suspects; replacing the SIM Card, cleaning the SIM Card, adding tape to the back side of the card to ensure good contact, replacing SIM/MicroSD PCB Board, fresh Wipe of ROMs and Radios, etc. None of those things have had any real results except replacing the PCB-it seems to be less frequently occurring with the new SIM tray. Does anyone have any other ideas? I'm willing to try just about anything.
Thanks in advance.

mrfeuss said:
Alright everyone, I've Googled my brains out (not in a dirty way) and haven't found any real resolution to the above issue. I've tried all the usual suspects; replacing the SIM Card, cleaning the SIM Card, adding tape to the back side of the card to ensure good contact, replacing SIM/MicroSD PCB Board, fresh Wipe of ROMs and Radios, etc. None of those things have had any real results except replacing the PCB-it seems to be less frequently occurring with the new SIM tray. Does anyone have any other ideas? I'm willing to try just about anything.
Thanks in advance.
Click to expand...
Click to collapse
How often does this happen?
It only happens to me when I have to change the network mode. I've rarely seen it other except for maybe when my phone finds an LTE signal.
Otherwise, it could be the antennas. My mom once dropped her Samsung Focus and the antennas got screwed up.

Hangampalli said:
How often does this happen?
It only happens to me when I have to change the network mode. I've rarely seen it other except for maybe when my phone finds an LTE signal.
Otherwise, it could be the antennas. My mom once dropped her Samsung Focus and the antennas got screwed up.
Click to expand...
Click to collapse
Sometimes it'll happen through several reboots within a few minutes. It'll also happen when my phone is sitting, untouched, on my desk. There shouldn't be any network mode switching if my phone isn't moving.

mrfeuss said:
Sometimes it'll happen through several reboots within a few minutes. It'll also happen when my phone is sitting, untouched, on my desk. There shouldn't be any network mode switching if my phone isn't moving.
Click to expand...
Click to collapse
The only thing I can think of is to flash back to Stock AT&T software and see what happens. If you still have the same problem, it's most likely an antenna issue and you might be better off buying a new phone.

Time to return to stock and see what happens. Ugh, what an annoying issue.
EDIT: After returning to stock and installing TWRP I ran the stock UCMC1 software for a little while without incident. While I was setting up CM I got the dreaded "No SIM-Emergency Calls Only" message. I'm at a loss here. I guess it might just be time to start shopping for a new phone.
EDIT: I'm going to try running *SHUDDERS* stock Samsung/AT&T software for a few days to see if the problem persists. I'm pretty skeptical that this is a software issue, though, since I haven't seen too many people reporting this issue.

Good effort
Given all your efforts in eliminating various variables, I'm starting to believe Hangampalli is probably right and it might be a Hardware issue.
But it is a simple observation to stay on a solid stock ROM like the recent UCMC1 (original att version) for a couple of days and see what happens.
You remind me of myself with my Samsung Galaxy S (Captivate) random shutdowns last year. I chewed up all the threads at XDA back to back and tried anything, and it still did it ... but we all know when to quit.
Cheers to your efforts:good:
I727-UCMC1-CM10.1

Well after about 20 minutes into running the phone on UCMC1 Stock my phone came up with the same stupid error. I'm going to see if AT&T is willing to do anything for me since I just got this phone as a replacement in October. But if not, I guess I'll be phone shopping. :-/ Such a shame because I really love this phone and its community of users and devs.

mrfeuss said:
Well after about 20 minutes into running the phone on UCMC1 Stock my phone came up with the same stupid error. I'm going to see if AT&T is willing to do anything for me since I just got this phone as a replacement in October. But if not, I guess I'll be phone shopping. :-/ Such a shame because I really love this phone and its community of users and devs.
Click to expand...
Click to collapse
its the phone, is it still under warranty

I got the phone as a replacement from AT&T (bad headphone jack, last time) in about October. I'm going to try to see if they'll replace it for me. Fingers crossed.

Ya I have had this same problem. Changing ROMs fixed it for me though.
Sent from my SAMSUNG-SGH-I727 using xda premium

AT&T apparently warranties their replacement devices for 90 days or until the end of the original device's warranty, whichever is longer.
What does that mean for me? I'm boned. I guess I'm stuck with my iPhone until I buy a new phone. It's going to be hard leaving this great community of Developers and Users and shedding such a great device.

Humm... I wonder if I have the same problem, is there any tests you can do to see if it is the sim card tray or something like the attenna ? I seem to have service sometimes, not all the time.

No phone audio after rooting and new ROM

So I rooted my Skyrocket last week and I screwed something up and since than I've had problems with the audio on the phone part. So I'm running Odin and even after double and triple checking I managed to screw it up by not having Auto Reboot checked. In a panic (and after waiting a long time) I unplugged the phone and powered it down. I booted into Recovery and did a wipe and installed CM 10.1.2 and I swear it worked fine for a week but all of a sudden I started having this weird issue with the phone audio. I'll call a number up and I won't be able to hear anything but I can put it on Speaker and it comes through fine or if I use my Bluetooth Headset it works fine.
I reloaded CM 10.1.2 and still nothing. I tried a nightly, I tried 10.1, I tried Beanstalk, and I now I'm back to stock and no luck on the phone audio. I have no idea what to do. I've tried Google searching and I'm coming up with a bunch of things but not what I'm looking for. I've even found some people having similar problems but they got no answer as well and I'm waiting to hear back from them (I found at least three people reporting the problem over on Cyanogenmod's Skyrocket Forum). I found some reference to it possibly being a Kernel problem. Thoughts?? I'll do some reading up on that tonight.
As a last resort I'm looking into buying a used Skyrocket to replace this one because I'm still 6 or 7 months till I'm eligible for an upgrade. HELP!

Edit, sounds like a hardware problem.
Have you tried to odin back to stock?

jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?

jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Oh and yes I've tried back to stock with no luck.

dfwjose said:
Oh and yes I've tried back to stock with no luck.
Click to expand...
Click to collapse
Seems like you have your answer then. If the problem persists regardless of which ROM or kernel you're using then logically it would seem that it can't really be software related, right?
Brought to you but time and relative dimensions in space.

dfwjose said:
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
Click to expand...
Click to collapse
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4

And just like that I'm up and running again and my phone works. I had given up and was having problems with a CM nightly so I did another wipe and loaded a stockish AT&T ROM that I've installed before and no my phone is working fine. I'm going to leave this thing alone until I pick up a spare phone!!
xcrazydx said:
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm sure it is and that's why I took the phone apart to see if I could get to it. I tried all kinds of things to get that tip out before tearing the phone down and I had no luck. I should have taken some pictures but I've tried tweezers (everything I had was to big or to weak to pull it out) and even glue before resorting to taking the phone apart. Unfortunately with the design it's enclosed all the way around with no way to really get to it. I even thought about replacing it but that piece looks to be soldered on.
In the end, I might just send it back to Samsung and see if they will fix it. Not sure if it's worth it but I never got serious about it because I didn't have a spare smart phone other than my work iPhone.

I shouldn't have spoken so soon. Rebooted the phone and it's locking up now. I give up. I can't find anything that will work. I either have sound with a phone that locks up or have to live with Speakerphone/Bluetooth and be able to reboot.