madnav said:
unlocking the network lock is a permanent process. so dont worry.
as for automated processes.
The process basically handles the nv_data.bin , if that are based on turning the lock off without entering unlock code.
Yep, I didnt have to enter the unlock code. After reverting back to stock 2.1 rom and rooting the phone, I installed the app, pressed unlock and it said, "Unlock successful, Please reboot phone. " I shut down the phone, inserted my sim card and on the next boot, viola! Saw Vodafone IN on the notification window.
Did the same for the phone that was sealed. Only, I didnt need to reinstall ROM as it was on 2.1 already. Just rooted it and used the app to unlock successfully.
madnav said:
also, ask for pic of imei from phone settings>about>status
the messed imei, development imei 0044xxxxxxxx works with some carriers in US, they do not with indian carriers..
Checked my IMEI. Its a proper 15 digit code starting 35xxxxxxxxxxxxx.
bigbyte said:
I think we should put an advisory about unlocking the phones in the first page of this thread. Many of us have gone through this issue and as madnav said soulfire is still facing this issue. In my phone nothing worked, the adb shell refused to get su permissions though the phone was rooted.
The seller from whom I had bought the phone had updated it to 2.2 via Tmobile's software update and it had somehow made the rooting process impossible. It would not allow reinstalling from unsigned update.zip file. Kept giving signature verification errors. After scourging around XDA-dev for a while came across this solution to revert back to stock 2.1, root and then unlock. I hope you had tried to revert back to stock JFD, and tried to re-root the phone and then try the unlocking. Imo, then it should've been a fairly painless procedure.