hey guys,
i have accidentally updated my OTB 1.1.2 iPhone to 1.1.3.
I have been reading the tutorial on the i.unlock.no website and have noticed a few things. It says that the baseband firmware can only be downgraded if you have the old bootloader (3.9). However, the OTB 1.1.2 unlock method involves downgrading the bootloader from 4.6 to 3.9.
So, if i was to downgrade the main firmware from 1.1.3 to 1.1.1, and then jailbreak and activate as normal, and then downgrade the bootloader using this tutorial, surely this would rewrite the baseband firmware and i would have a working iPhone again?

Hi everyone,

Sorry if this is a stupid question or maybe it's not on his place here but hey...
Why do I keep hearing that people might just wait for the 1.1.4 to come out? Will all problems be solved with this firmware? and will I all of a sudden be able to use my TurboSim again with this firmware?
I don't understand...
I should think every new firmware is harder to break...

cheers!

Originally Posted by TheJA6E

hey guys,
i have accidentally updated my OTB 1.1.2 iPhone to 1.1.3.
I have been reading the tutorial on the i.unlock.no website and have noticed a few things. It says that the baseband firmware can only be downgraded if you have the old bootloader (3.9). However, the OTB 1.1.2 unlock method involves downgrading the bootloader from 4.6 to 3.9.
So, if i was to downgrade the main firmware from 1.1.3 to 1.1.1, and then jailbreak and activate as normal, and then downgrade the bootloader using this tutorial, surely this would rewrite the baseband firmware and i would have a working iPhone again?

The only method allowing you to downgrade your baseband is actually a hardware method and more of a bootloader hack anyway - I would strongly suggest against it, as you would probably end up bricking your iPhone

Having the secpack alone isn't the answer, since you need a secpack for a baseband version higher than the one you currently have. Since you're at 1.1.3 you need to wait till 1.1.4 comes out

ok thats cool, but....
i think i worded it slightly wrong,
if i was to downgrade, jailbreak, activate as normal.
i then do the bootloader hardware hack to downgrade my bootloader from 4.6 to 3.9.
then, i am able to run the bbdowngrader package in the installer as i know have bootloader 3.9.
then, ta da a working iPhone with 1.1.2, 3.9 and 4.02_13G (i think thats right)
is this more possible?

I have a major issue with 1.1.3 where some might be able to help:

I'm using T-Mobile Germany as my provider on an unlocked us phone. The issue is that the 1.1.3 firmware thinks to know the right EDGE settings for t-mobile and doesn't show me the EDGE menu.

I found out - through this forum - that the edge settings are managed in the System/Libary/Carrier Bundles Folder, but i don't know in which plist.

I tested it with the plist in the t-mobile folder and in the unknown folder, both doesn't bring up the EDGE menu.

As soon as i exchange my card, for example with a vodafone card, i can see the edge menu. So it's clearly something controlled in this plists...i just need to know where...

Any idea?

Hi
Can some1 please tell me an AnySim solution is coming out for 1.1.3? Is it coming out when the SDK is going to be released?

Sam

Can someone help me to activate EDGE on my uk 1.1.2 iphone that has just been updated to 1.1.3 using the method described in this website. I initially downloaded modfied o2 files and dragged them into 3 folders using transmit in mac.

thanks.

(step by step instruction is appreciated)

After updating a few iPhones from 1.1.1 and 1.1.2 to 1.1.3 I believe know what is creating all the problems with this jailbreak, maybe someone with more knowledge can look into it a little more...

I believe that Nate's Jailbreak doesn't set the correct permissions for the folders during the soft-update. Thats why resetting the settings, and running Navizon fixes some of the problems, because by running these programs, they are setting the permissions to what they should be. The mail.app doesnt save the password, maybe because the file that is suppose to save the password doesnt have write access in its permissions...

Can someone look into it a little, it seems to me the only real reason we are having all the problems with this jailbreak...

I mean, there are three or four little improvements over 1.1.2, so why is everybody in such a rush and accept the risk of a hastily released half-way-there upgrade? In particular when there are custom apps who do all the things that the upgrade does (Locate Me, Summerboard for Wigglies, Multiple Recipients)?
I just don't get it!

Figured I would post here to see if anyone had this similar experience after running iBrickr for 1.1.3 jailbreak.

Everything works fine, iBrickr states to go to the Installer.app and install the "1.1.3 soft upgrade" and sit back and wait.

I do that and I get the message "Error: Your iPhone is not ready to upgrade. See 'More Info'". But More Info is blank.

So I poked around with SSH, and found the following:

/var/root/Media/var/root/Media/softupgrade [not a typo] contains 113_upgrade_image.bin

Don't think this is where the .bin should be.

So I moved it to /var/root/Media/softupgrade tried the Installer.app; 1.1.3 soft_upgrade and still didn't work. Got script execution error and waited 15 minutes [as Nate True suggests] and nothing happened.

So my 1.1.1 phone is still on 1.1.1.

Anybody else see this?