"Invalid calibration data in device tree & eeprom is blank"


Source : GeeZuZz
Source add : http://www.hackint0sh.org/forum/showthread.php?p=81893

When a phone is unlocked (in a proper way), it will always be unlocked. Firmware upgrades never touches EEPROM, including lock data.

Here are my thought's on how iphone unlocking works - of course, it's just my thoughts based on my experience with other phones, and i may very well be wrong.

IPFS unlock solution is permanent, and will handle all future updates
Yes, i'm fairly sure that a phone unlocked with IPFS is a proper unlock (not firmware patch), making it permanent. But of course, unlike other's, iphone needs activation and IPFS therefore completely dependent on activation, which is depending on jailbreak. But when it comes to the operator lock itself, IPFS's permanently unlocks it.

I'm not sure exactly how IPFS does unlock it, but i'm feeling very sure it's one of these:
1. IPFS reads data from the baseband/EEPROM, and rebuilds the lock area in EEPROM with proper data - without any lock. This is exactly the same done on almost all other phones.

2. IPFS patches the baseband, but only as a temporary step in order to achive the above. When it's finished, it doesn't matter if the patch is removed (bb upgraded), because phone is already unlocked.

AnySIM and the other solutions are fimware patch solutions and will never survive baseband flashing/upgrade. Unlike IPFS (if IPFS also patches firmware), AnySIM patches firmware in order to bypass the lock, not in order to unlock it - or at least it's not unlocking it properly. The fact that anysim unlocked phones are bricked after upgrading, must be caused by changes the anySIM solution does to EEPROM, which is not properly done, and makes it "corrupted" as seen from the new firmware.

In my opinion there's no reason to be so negative about IPFS. They did the real unlock and so far noone have been able to recreate their solution. So don't expect a free real solution for 1.1.1 appearing very soon either. A free patch-unlock though is probably already possible now that they have decrypted the ramdisk, i will try that tomorrow. Of course iphone dev team are doing the most important work, and let's hope they soon will be able to work out a direct unlock solution as well.


"Invalid Calibration data in device tree" is growing everyday. Please make this sticky and hope there is solution for this soon.



Solution found.
The steps are below:

# launchctl unload /System/Library/LaunchDaemons/com.apple.CommCenter.plist
# killall -9 CommCenter
# chmod 755 swifi
# swifi
wifi fixer
by MuscleNerd, gray, and the iPhone Dev Team
Actions taken:
Backup table checksum was corrected
Active table was restored from backup

Restore All to default settings...

After a reboot, my wifi button was no longer grey and swifi reports good tables

I have this problem ("Invalid Calibration data in device tree") and so far no solution found

Still waiting for a solution to come...

http://www.hackint0sh.org/forum/showthread.php?t=34713

http://www.hackint0sh.org/forum/showthread.php?t=29995

__________________
*****************************
Iphone 1: 113->114->sw unlock->fully working phone
Iphone 2: 112otb->jb/act->hw unlock->brick..?!
workin' as an ipod touch...no solution for now
*****************************

I have that problem too

i have exactly the same problem...

same to mine.... i have that problem too... and i did evrything but no luck... i tried the top board from old broken iphone and that make the problem solve... but it is nice if we could fix it by software...

Which board did you changed? The comm board? cause I'm suspecting a Hardware issue.


I Have the same problem invalid calibration data in device tree and No WiFi, No Bluetooth and phone doesn't ring on sleep mode.

It's a problem caused by software and will be resolved by software. No board needed. And the component involved on this is the COMMboard.
The problem is on BB or EEPROM of the commboard. it needs correct reflashing

i see... do u know any method that can solve this problem?

i have this problem too

I don't But some DEV TEAM Top Person Are looking at this problem