kiddsinn / iphone-elite

Automatically exported from code.google.com/p/iphone-elite
GNU General Public License v2.0
0 stars 0 forks source link

How to rebuild seczone? IMEI 0049... #49

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

I ran AnySIM 1.1 on a new, jailbroken 1.1.1 device. It failed 
during "starting commcenter" 1st time but ran to completion a second time. 
The phone was left with the infamous 0049xxx IMEI. Downgrading, flashing 
baseband, virginizing etc hasn't fixed the problem. I believe my seczone 
is corrupt. Is it possible to rebuild my seczone in some way?

Original issue reported on code.google.com by siwat...@gmail.com on 2 Dec 2007 at 4:58

GoogleCodeExporter commented 8 years ago
the virginising process is a fragile one.
it might fail or succeed, i had to reflash about 20 times in an especially 
annoying case.

i suggest that you flash 3.14 after virginise has finished (and that means: 
_after_
you have run bbupdater -v and it complained the baseband didn't respond), and 
then
reboot the device. this should give you back a 011... imei. you should then 
upgrade
your baseband or directly use anysim.

here's a (with a little luck) working version of iPhixer (the graphical 
virginiser):
http://rapidshare.com/files/74261424/iPhixer.zip.html
sometimes the seczone dump will block infinitely, exit the program then, wait a
moment and try again. it might also be neccessary to open a terminal and kill 
hnorz.
a better baseband tool is in the works.

Original comment by onit...@gmail.com on 4 Dec 2007 at 5:07

GoogleCodeExporter commented 8 years ago
Thanks for the suggestion. Will this procedure actually rebuild the seczone 
file? 
Right now my seczone dump is showing the top half filled with FF..  

Original comment by siwat...@gmail.com on 4 Dec 2007 at 5:21

GoogleCodeExporter commented 8 years ago
Thanks for the suggestion. Will this procedure actually rebuild the seczone 
file? 
Right now my seczone dump is showing the top half filled with FF..  

Original comment by siwat...@gmail.com on 4 Dec 2007 at 5:30