colin8208 / iphone-elite

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

iUnlock: FW differences found #11

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. I ran iUnlock ICE03.14.08_G.fls elite......
2.
3.

What is the expected output? What do you see instead?
got FW differences instead of identical FW

What version of the product are you using? On what operating system?
1.0.2 (never upgraded to 1.1.1 before)

Please provide any additional information below.
tried to downgrade baseband (even though i have never upgraded) by running 
bbupdater -f ICE03.14.08_G.fls -e ICE03.14.08_G.eep
and got the following error right after

.....
ProcessOutlineUpdated: Process time was 298 msec
Upgrade from to
Downloading EEP
ProcessOutlineUpdated: Start downloading from file ICE03.14.08_G.eep.
ProcessDetailUpdated: Sending sec-pack
ProcessDetailUpdated: Load region 0
ProcessDetailUpdated: Sending end-pack
ProcessOutlineUpdated: Process time was 2061 msec
Error: Failed to download .EEP: Expected checksum D510 got 0FAC
Done

thought both issues might be related

Original issue reported on code.google.com by honch...@gmail.com on 25 Oct 2007 at 3:35

GoogleCodeExporter commented 8 years ago
Your firmware files (ICE03.14.08_G.eep/fls) are probably corrupt.

Original comment by czim...@gmail.com on 26 Oct 2007 at 3:14

GoogleCodeExporter commented 8 years ago
i have tried firmware files from several sources, and tried extracting them 
myself. 
it leads to the same error. 

it was reported by other users that if they downgrade their baseband, "FW 
differences will be solved".. for my case.. i have never upgraded.. so trying 
to 
downgrade doesn't help

Original comment by honch...@gmail.com on 26 Oct 2007 at 8:15

GoogleCodeExporter commented 8 years ago
so iUnlock is comparing the firmware files with what is in the iphone embedded 
firmware, or some information in iUnlock itself before concluding the "FW 
differences" ??

it might work out for me if iUnlock can force the writting of firmware without 
comparing since my baseband is completely empty now.. and i cannot rewrite 
anything 
on it

Original comment by honch...@gmail.com on 26 Oct 2007 at 8:17

GoogleCodeExporter commented 8 years ago
I had a similar problem. You may try this:

 Download ierase to your virginator_pack directory

 cp 401secpack into secpack (not the 301secpack! used by ierase cmd) 
 chmod a+x ierase
 ./ierase
... iUnlock ....

Original comment by pollic...@gmail.com on 27 Oct 2007 at 12:16

GoogleCodeExporter commented 8 years ago
hi.. i've already done that

my baseband is completely empty now

Original comment by honch...@gmail.com on 27 Oct 2007 at 1:34

GoogleCodeExporter commented 8 years ago
In your shoes i'll try three methods:

1) manually run bbudater (remember to stop commcenter) 

2) reload 1.02

3) at least load 1.1.1, hen 1.0.2 reunlock and repeat the virginization 
sequence.

I'used firmare images inside the virginiator_pack

Original comment by pollic...@gmail.com on 28 Oct 2007 at 10:53

GoogleCodeExporter commented 8 years ago
Right!

Original comment by MThang.n...@gmail.com on 29 Oct 2007 at 3:22

GoogleCodeExporter commented 8 years ago
done that.. no help

Original comment by honch...@gmail.com on 30 Oct 2007 at 3:24

GoogleCodeExporter commented 8 years ago
honcheng contact me via YahooMessenger pls. 
my id: ta_mobile

Original comment by tuananh...@gmail.com on 31 Oct 2007 at 2:36

GoogleCodeExporter commented 8 years ago
i don't have yahoo messenger...  what is this about? you have a solution for me?

Original comment by honch...@gmail.com on 31 Oct 2007 at 2:41

GoogleCodeExporter commented 8 years ago
yes, i have to ask you some questions. Cos I never got you problem. Unlocked 
and 
repaired here over 300pcs without that problem.
my Skype: ta_mobile

Original comment by tuananh...@gmail.com on 31 Oct 2007 at 6:12

GoogleCodeExporter commented 8 years ago
hi tuananhgsm...,
ok.. hold on ok.. i just read your msg. it's night here. 
how about msging via googleTalk? mine will just be my gmail account

Original comment by honch...@gmail.com on 31 Oct 2007 at 3:47

GoogleCodeExporter commented 8 years ago
ok.. i mentioned earlier that when i tried 
bbupdater -f ICE03.14.08_G.fls -e ICE03.14.08_G.eep
i get
Error: Failed to download .EEP: Expected checksum D510 got 0FAC

now i try
bbupdater -f ICE03.12.06_G.fls -e ICE03.12.06_G.eep
i get
Error: Failed to download .EEP: Expected checksum D5BE got 0F02

so i don't think it's somethign wrong with my EEP file. this doesn't make sense 
at all. 

Original comment by honch...@gmail.com on 1 Nov 2007 at 5:02

GoogleCodeExporter commented 8 years ago
I think your physical eep was damage. Did you try erase eep area and reflash it 
? or 
maybe hardware jod will help. I have all solution for hardware repair BB chip 
(with 
good physical BB chip).

Original comment by tuananh...@gmail.com on 1 Nov 2007 at 9:34

GoogleCodeExporter commented 8 years ago
how to erase eep ? ieraser? tried that.. if you are online now.. we can chat via
gtalk. but i don't see u online in gmail now

Original comment by honch...@gmail.com on 1 Nov 2007 at 9:43

GoogleCodeExporter commented 8 years ago
Is there a "hardware" way to repair BB chip ? Tuananhdsm could you give details 
please ?

Original comment by lsdejar...@gmail.com on 1 Nov 2007 at 6:05

GoogleCodeExporter commented 8 years ago
if you are mobile phone technican, you should have some equipment to do. Put 
out the 
BB flash chip and rebuild by an IC reflash tool box, then put back the IC into 
phone. Phone should work again. But this method is very heary and risk.

Original comment by tuananh...@gmail.com on 2 Nov 2007 at 4:38

GoogleCodeExporter commented 8 years ago
does anybody know the way how to downgrade boot 4.6 to 3.9 
thanks

Original comment by phalegsm...@gmail.com on 23 Nov 2007 at 9:43