Bledig,you don't have to restore , Carnaval only jailbreak and activates Youtube. You still need to unlock using AnySIM 1.1.

Doing things all over again may use up one of your reunlock counters. This is why is prudent that the you stick with one unlocking method and continue the process through and through. Starting an unlocking process and abandoning it to start over will leave you with a half-baked iPhone and may exhibit undocumented symptoms like the phone slowing down to a crawl, or corrupted baseband ,resulting in a "No Service" sim card.

This post has been edited by stringfellow: Oct 25 2007, 11:07 PM

Hmmmm DiGi's a little "sticky" tonight, loading up pages here slower compared to most nights.

You have 5 unlock attempts. After that, if you continue your unlocking attempts, chances are high that your iPhone will be permanently bricked.

This is the reason why i emphasize on continuing on with a particular method and stick with it through and through.

From my understanding, this is 5 attempts on a particular firmware update. Because every firmware update rewrites the seczone data and reflashes the baseband, and this resets the counter back to zero.

By the way, those guys are the folks from iPhone Elite, the very people who come up with the revirginizers.

This post has been edited by stringfellow: Oct 26 2007, 01:04 AM

That IS the VISUAL VOICEMAIL. Whenever voicemails are made and recorded for your number, the carrier then sends the whole bunch of them to your iPhone. You then get that red circle lighting up, and tapping it will send you to another page in the Voicemail screen where you can view and choose to play any voicemail at any order, based on which voicemail you tap to choose. That is why they call it Visual Voicemail, because you can VISUALLY choose which voicemail to playback and listen to. Not like the current voicemails we receive on our telcos where you have to play them back based in the order of which voicemail are made first, and this one's all aural/audio only.

Again, i repeat, local telcos here do not support this. My beloved is using T-Mobile on her unlocked iPhone in CA., and even on that carrier, it is not supported, only on AT&T and Cingular networks.

This post has been edited by stringfellow: Oct 26 2007, 01:21 AM

Yeah, but a restore is NOT a virginizer. So if you busted up an install because you didnt follow the guide closely, and perform a restore, and restart from there, your NCK Counter has chalked up one attempt. If the person unlocking is unaware, another 4 failed attempt and it's corrupted baseband and bricked up for good.

There are already unlockers for 1.1.1 Virgin iPhones available. This may be one of them, there are other alternative ways , but this one seems more reliable. I cant vouch for their effectiveness since i never had a 1.1.1 Virgin iPhone before.

If i am not mistaken, your NCK counter is used up by one everytime you run any unlocking application, and flash the baseband, on one particular firmware. The virginizer resets this back to 5, so if you have done the revirginizing process correctly , you should have 5 unlock attempts (NCK counter) left. Using the AnySIM 1.1 at the end of the process deducts one to make it 4. Why this was critical last time was during the time where the phones were 1.1.1, and users with 1.1.1 had to downgrade to 1.0.2 and unlock from 1.0.2 and then upgrade to 1.1.1 and run another unlock from there, reducing your NCK counter to 3. Any more botched attempts from there, would seriously pointing towards a permanently bricked iPhone. There wasnt a revirginizer application at that time.

Simply put, DONT muck about with the unlocking, unless you have read throughout the process, understand it, and have everything you need at hand. Sometimes, things like fluctuating Wifi signal, and your inability to SSH or WinSCP into your iPhone alone can fcuk up an unlocking attempt, and forces you to restart again. That poses a danger because you may unknowingly have used up one NCK counter/unlock attempt.

Which is the reason why i suggested last time that we wait. Anyone who uses an IPSF unlock, can see what danger they face, since their seczone data, as seen from that link there, is totally messed up, and probably beyond repair, unless IPSF comes up with their own revirginizers. AnySIM and iUnlock users also have their seczone data tampered, but they are recoverable.
Okay, if you want that little red dot thing, that i part of the visual voicemail as well. Again i reiterate, our local telcos do not support that. The way our telcos manage voicemails here , are using notification via SMS or callback to the customer.

This post has been edited by stringfellow: Oct 26 2007, 06:15 PM

Remember, get everything you need first, understand them and then proceed. I even go to the extent of saving the entire webpage into my laptop, so that i can view them offline. That way, if i lose connection, i still have my Wifi network to do the necessary stuff. Good luck, bro!

This post has been edited by stringfellow: Oct 26 2007, 04:06 PM

Wrong, wrong, wrong! Wrong again! That link i posted before, and reposted here, does that straight out of a VIRGIN 1.1.1. This method was used for jailbreaking the 1.1.1 iPod Touch, and works for iPhone 1.1.1. Tha link you posted carries more meaning than meets the eye. The staff of Hackint0sh, which are basically DevTeam lackeys, are suppressing all other hacking group attempts to post their virginisers and wanting their virginisers to look like the only one's available and reliable. The truth is, another iPhone hacking group called the iPhone Elite,had come with their virginizers already, and their's work flawlessly. That admin post is the attempt to sway the public's mind of the already available virginizer in hope that the Dev Team virginizer gets the credit for being the first and only virginizer around. Apparently, they got to your mind too, judging from your post above.

Keep up with the times, please. And stop spreading FUDs.

This post has been edited by stringfellow: Oct 26 2007, 06:27 PM

It's fun banking on an analyst's prediction, weeeeeeeeee!! I wish i have an analyst credential, people would quote me and take my word as gospel.

Noi doubt there will be a new iPhone some time in the future, but what's stopping you from waiting even more for iPhone 3.0? Just look at the refresh rates of Apple products , and that makes buying anything at any time on Apple's iPhone roadmap a risky business.

The iPhone is here, it is here now. If people want to play more waiting game, why not wait for iPhone 10.0 in year 2020? Plus that link you quoted are words from an analyst, which they have no absolute basis other than guesstimates and conjectures that make them look like they are a credible source. Those who know what these analysts do knows how much an "insider" they are when it comes to news.

Not on mine. In fact, the update *fixes* the Safari crash i had when multitasking between listening to songs and surfing on Safari. It may be partly due to EDGE but i hadnt any crashes since.

Not in this country. Back in the States, that statement holds true.

That's on diGi's end. You have to consult them. Your phone is unlocked already.

Uh oh. EDGE would go off once calls are made. Sounds like a botched job.

Which method did you use, and did you get the expected result?

Im tempted to diagnose this as a fault with your CommCenter, but unloading CommCenter would disable all wireless forms of communication inside iPhone. Did you get the desired result when you virginised?

Still sound like a fault on Digi's side from the way you put it.

Erkkk Independence? With that, i respectfully withdraw, and call upon the Mac unlockers. My experience is with PC only so far. Keyword "so far", tomorrow will be different

Yeah but the initial setup prompted this to happen when you were setting up GPRS for DiGi. I had issues with auto-config on Digi before, when they kept on sending config. sms to set up EDGE. I ignored it and manually set it myself.

Good luck!

Thoe garbled messages are inherent in all iPhones, since it is not made to receive SMSes from carriers using names as the sender header, rather than numbers. When those SMSes arrives, the iPhone cannot decipher them and pumps out those garbled messages.

Still cant call out? I'm puzzled as well, bro. Lemme try and see if there are any similar case in HAckint0sh, i suggest you do the same.

Thank God! Good call on those , Omni! This should be in post#1, just in case someone comes across similar case.