This discussion is archived
12278 Views 6 Replies Latest reply: Nov 12, 2008 1:05 PM by icebike
Currently Being ModeratedNov 4, 2008 5:18 PM (in response to naf-101)If you google "ICCID UNKNOWN" you get a lot of hits suggesting something to do with jail broken phones. I'm assuming this is not the case.
However, you are about the third report of this in recent days, many having to do with travel.
I think Apple has gone so berserk with preventing people from migrating this phone off of ATT that they are affecting honest paying customers by bricking phones that can't see towers or those that roam even to partners that ATT has roaming agreements.
I speculate that your phone wasn't actually in airplane mode, even if it said it was, and it saw no towers, or only other carrier's towers, and assumed its sim was bad, and goes into brick mode. It sets the sim to a state where it thinks its unregistered and you have re-register upon arrival back in ATT land.
Had you landed somewhere without ATT service, I suspect it would have been bricked for the duration - roaming partner agreements not withstanding.
Currently Being ModeratedNov 7, 2008 8:33 AM (in response to naf-101)iPhone 3G bought in offical Orange store (France).
No travel. Charge OK. During last night, the same adventure than naf-101 occured :
on my iPhone :
IMEI: Unknown ICCD: Unknown
With alert like that :
"Repair needed - iPhone can't send or receive call" and show the graphic to connect to iTune.
On iTunes: "iPhone can't be used with iTune, because no infos from iPhone for activation. Verify SIM card"
Clean SIM, reboot and Reset : no effect.
It seems that bug is neither jailbreak nor travel problem!iMac intel 24", Mac OS X (10.5.5), iPhone 3G
Currently Being ModeratedNov 11, 2008 11:31 PM (in response to uocram)Same here in germany. I got my iphone yesterday in official T-Mobile store. It registered fine. Had it charged up and played around a bit. Went to bed. This morning got the no Imei / No iccd need support thing on the screen. No hacks no jailbreak in any way. So i guess there is no travel issue. Now it keeps powering up and down when connected to itunes or it will just keep the connect to itunes screen open. Itunes says can't connect to the phone.Mac OS X (10.5.5)
Currently Being ModeratedNov 12, 2008 12:28 PM (in response to Zimnovember)You have to take it back.
That powering up and down bit will eventually corrupt the OS to the
point you have to do a restore, and then it will start all over again.
Its not worth your time fighting this, because I've never seen anyone
post here that they recovered from such cycling successfully.
You could try haveing T-Mobile give you a new Sim (that takes all
of 2 minutes) but don't hold your breath that it will solve the issue.
Once the reboot cycle starts the phone usually trashes itself in short order.
Currently Being ModeratedNov 12, 2008 12:36 PM (in response to icebike)In the end i didn't. I contactt-mobile first. They told me to contact apple. When i had tried what the support guy had in mind and it didn't work out he told me to get to t-mobile again. So they exchanged the iphone in the shop right away. I really can't complain there. I just can't accept the thing that a phone breaks within 24 hours of buying and only using official software...
Thanks for the reply anyways.Mac OS X (10.5.5)
Currently Being ModeratedNov 12, 2008 1:05 PM (in response to Zimnovember)
I just can't accept the thing that a phone breaks within 24 hours of buying and only using official software
This is a distressingly common occurrence. And not JUST with new phones.
You can be going along all fat and happy and for no obvious reason this error can pop up and your sim is unreadable.
There are many reports in these forums about this sequence of events, where for some reason the sim can't be read by the phone, and the phone's response is to immediately trash its operating system. Sometimes it adds the wrinkle that it can't read its IMEI (which is burned into the phone at manufacture). What possible excuse could there be for trashing the IMEI?
This all leads to the fact that you can never really trust this phone. It might work flawlessly for years, then it suddenly bricks for no reason, and when it does maybe a restore will work, and maybe you need a new phone.
Travel away from your home network carrier at your peril. Many reports of bricking phones when Canadians arrive in the States.
2.2 is said to be less than 10 days away. Maybe this will be fixed.