Bootneuter - Stuck on "Determining current settings"

Hi All,

I'm having a problem trying to unlock my iPhone 2G with 3.1.3 FW. Basically, whenever I open up Bootneuter, I get stuck at the "Determining current settings" screen. This happens no matter tool I use to jailbreak (I've tried all the tools compatible with 3.1.2 and 3.1.3) - so it's either a problem with Bootneuter, my iPhone, or a combination of both.

This issue has been brought up here a couple of times before, i.e.:

http://www.hackint0sh.org/f207/84345.htm

But to my knowledge, no one has found a solution. Just a bunch of "shot in the dark" type suggestions to downgrade to version x.xx, jailbreak, upgrade to version y.yy, etc - which ultimately don't really seem to do anything.

I'd like to try to get to the bottom of this issue in this thread. To start with, some questions:

1. Has *anyone* successfully unlocked (for the first time) an iPhone 2G with 3.1.3 FW? I.e. is it just a compatibility issue with 3.1.3 FW and bootneuter that needs to be addressed (after all, I have not seen any new updates to bootneuter in quite some time)?

2. What exactly is bootneuter doing at the "Determining current settings screen" that could cause it to hang indefinitely?

3. Who wrote bootneuter? Is it possible for me to get in contact with the dev(s) directly?

4. Is bootneuter open source? Is it possible for me to take a look through the source code?

5. Any other thoughts, anyone?



Thanks,
l0lcat

Quote:

---

Originally Posted by l0lcat

Hi All,

I'm having a problem trying to unlock my iPhone 2G with 3.1.3 FW. Basically, whenever I open up Bootneuter, I get stuck at the "Determining current settings" screen. This happens no matter tool I use to jailbreak (I've tried all the tools compatible with 3.1.2 and 3.1.3) - so it's either a problem with Bootneuter, my iPhone, or a combination of both.

This issue has been brought up here a couple of times before, i.e.:

http://www.hackint0sh.org/f207/84345.htm

But to my knowledge, no one has found a solution. Just a bunch of "shot in the dark" type suggestions to downgrade to version x.xx, jailbreak, upgrade to version y.yy, etc - which ultimately don't really seem to do anything.

I'd like to try to get to the bottom of this issue in this thread. To start with, some questions:

1. Has *anyone* successfully unlocked (for the first time) an iPhone 2G with 3.1.3 FW? I.e. is it just a compatibility issue with 3.1.3 FW and bootneuter that needs to be addressed (after all, I have not seen any new updates to bootneuter in quite some time)?

2. What exactly is bootneuter doing at the "Determining current settings screen" that could cause it to hang indefinitely?

3. Who wrote bootneuter? Is it possible for me to get in contact with the dev(s) directly?

4. Is bootneuter open source? Is it possible for me to take a look through the source code?

5. Any other thoughts, anyone?

---

Have you used redsn0w or pwnagetool to run bootneuter automatically?
The hang at determining current settings can be because CommCenter is getting in the way. Or it could be because your baseband bootloader or baseband are empty/corrupt.
What does your iPhone report in Settings - General - About?

Musclenerd was the main person behind bootneuter. The 2G iPhone is 3 years old now - unlock stable and permanent with bootneuter - not much need to update something if it works.

I seem to recall I tested redsn0w/bootneuter against 3.1.2 on my iPhone when beta testing for redsn0w 0.9.2 - don't think 3.1.3 was out then. So try 3.1.2

If you suspect that 3.1.3 is causing the problem - downgrade to an older iOS version. Most of the manual baseband tools work best on iOS 1.1.x for the 2G

Quote:

---

Originally Posted by Olethros

Have you used redsn0w or pwnagetool to run bootneuter automatically?

---

Yup. When I use those apps it also freezes on determining current settings - and since I need to power off in the middle of jailbreaking it also ends up requiring a restore from iTunes.

Quote:

---

Originally Posted by Olethros

The hang at determining current settings can be because CommCenter is getting in the way. Or it could be because your baseband bootloader or baseband are empty/corrupt.
What does your iPhone report in Settings - General - About?

---

Version 3.1.2 (I guess I had wound up reverting to 3.1.2 at some point)
Modem Firmware 04.05.04_G

I was given this phone by a friend and I believe they had previously mucked around with jailbreak/unlock tools - so it's possible they corrupted something important. By the time I got the phone it had been restored to normal 3.1.3 FW and was running on AT&T.

Any tips as to how I might figure out whether CommCenter is getting in the way or the baseband/baseband bootloader is corrupted?

Quote:

---

Originally Posted by Olethros

Musclenerd was the main person behind bootneuter. The 2G iPhone is 3 years old now - unlock stable and permanent with bootneuter - not much need to update something if it works.

---

Good to know, thanks.

Quote:

---

Originally Posted by Olethros

I seem to recall I tested redsn0w/bootneuter against 3.1.2 on my iPhone when beta testing for redsn0w 0.9.2 - don't think 3.1.3 was out then. So try 3.1.2

If you suspect that 3.1.3 is causing the problem - downgrade to an older iOS version. Most of the manual baseband tools work best on iOS 1.1.x for the 2G

---

I've been trying to avoid downgrading to 1.1.x - mainly because it is such a hassle and I have no idea whether it would actually fix anything. I suppose I've got to give it a try though just to rule it out.


Thanks very much for all of the work you put into these forums.
-lc

If bootneuter freezes during redsn0w/pwnagetool then you can rule out CommCenter as culprit.

Is the iPhone actually unlocked now? Can you use any SIM card with it? (even though the bootneuter fails)

Do you have valid wifi and bluetooth mac addresses?

You may need to try and reflash your baseband and baseband bootloader. Be careful - you can screw things up more.

I recommend iLiberty Plus on iOS 1.1.4 for all such operations.

Bluetooth and Wifi MAC addresses are valid - and I can confirm that wifi works on my home network.

Interesting thought about it already being unlocked and me just not knowing about it. I've got T-Mobile and AT&T prepaid sims that I'd like to use. When I drop in the T-Mobile SIM, the phone seems to recognize from the SIM that I have a voicemail. But the "Carrier" field in the "About" section shows as "Not Available" on both SIMs - and no calls of course.

Is that enough info to make a decision as to whether or not the phone might already be unlocked?

Also - this is kind of weird...

Just now after playing around with bootneuter and the AT&T SIM, I went back to the About section and there was a new section labeled "ttou" listed directly under the Modem Firmware field.

When I expanded that that section, it popped up a couple of new fields that said "Bad system call" and "Invalid serial".

I have no idea what that's all about. When I restarted, the "ttou" section was gone.

Stange - but your're not the first to see this - no i don't know what it means

Strange tab under "About" section "ttou"? - Mac Forums
iPhone: WTF is “ttou”? – Stephen Foskett, Pack Rat

Both users reported that a restart fixed it.