Bootneuter hangs / freezes AFTER detecting current settings

@Speedy & others,
I've seen this issue with bootneuter 2.1 hanging at detecting the settings.
I've seen this with phone going from 1.1, 1.1.2, 1.1.4 to 2.x fw (note: bootneuter 2.1 came out after fw 2.x, prior to that it was bootneuter 2.0 for 1.x fw)
I never have to restore BB to 1.1.4 (04.04.05_g).

Prior to running bootneuter 2.1 do this:
- turn off the phone and turn it back on
- turn of wifi
- turn on Airplane mode
- wait 30 sec to make sure everything is off
- turn off airplane mode
- run bootneuter 2.1

The difference that I noticed with bootneuter 2.1 vs bootneuter 2.0 is:

- The first time you run bootneuter 2.1, it will not run right away but instead it will ask you to turn off/reboot the phone so that commcenter is completely shut down at the next boot up. After the reboot, bootneuter will run.

- Prior version (bootneuter 2.0) does not ask you to reboot.

My guess is bootneuter 2.1 have additional checking mechanism for safe operation. It will not run if it cannot detect the correct state of commcenter the first time.

Thanks dtube I will try that process

Quote:

---

Originally Posted by dtube

@Speedy & others,
I've seen this issue with bootneuter 2.1 hanging at detecting the settings.
I've seen this with phone going from 1.1, 1.1.2, 1.1.4 to 2.x fw (note: bootneuter 2.1 came out after fw 2.x, prior to that it was bootneuter 2.0 for 1.x fw)
I never have to restore BB to 1.1.4 (04.04.05_g).

Prior to running bootneuter 2.1 do this:
- turn off the phone and turn it back on
- turn of wifi
- turn on Airplane mode
- wait 30 sec to make sure everything is off
- turn off airplane mode
- run bootneuter 2.1

The difference that I noticed with bootneuter 2.1 vs bootneuter 2.0 is:

- The first time you run bootneuter 2.1, it will not run right away but instead it will ask you to turn off/reboot the phone so that commcenter is completely shut down at the next boot up. After the reboot, bootneuter will run.

- Prior version (bootneuter 2.0) does not ask you to reboot.

My guess is bootneuter 2.1 have additional checking mechanism for safe operation. It will not run if it cannot detect the correct state of commcenter the first time.

---

Doesn't work!!! :(

Has anyone solved this problem using windows? I don't have access to an OSX machine and it seems that people cant get kiphone to work on windows.

Hi guys,
Regarding the bootneuter hanging ... I've been testing a bit so I asked MuscleNerd on twitter:

Quote:

---

Originally Posted by dtube

@MuscleNerd - been hearing issue with bootneuter 2.1 hanging when detecting setting (prior to hitting flash). can u tell us diff 2.0 vs. 2.1

---

and he explained

Quote:

---

Originally Posted by musclenerd

@dtube BootNeuter has that issue when you use it outside of pwnage/quickpwn flow... it's just battling CommCenter but we're working on a fix

---

Just want to pass this along to you guys

Hi, guys, yesterday this happened to me, what I did to solve was, after being jailbreak in 2.2.1, I restore using DFU mode to an old restore I have to 2.1, after the restore completed bootneuter kicked in and told me it only needs to flash baseband, it did it in 2 minutes, now I have 2.1 unlocked with baseband 04.05.04 and my phone fully functional, Next I'm planning to create another restore using 2.2.1 and I will update the iphone, but I will do this in a couple of days, when I'm done I will post again to let you know how it went.
:pie:

@chevy45,
After you update to 2.2.1, all you have to do is use quickpwn 2.2.5-2 to jailbreak/activate it.
There is no need to select the installer + unlock option in quickpwn.

Quote:

---

Originally Posted by dtube

Hi guys,
Regarding the bootneuter hanging ... I've been testing a bit so I asked MuscleNerd on twitter:

---

Just an addition to what I saw when I used a custom firmware from PwnageTool 2.2.5 on my 2G test-iPhone. It seems to me that BootNeuter off-loaded the CommCenter, did a reboot, then (with CommCenter off) and started again BootNeuter did its job. After that the Commcenter is loaded again - reboot voila.
That matches Muscle's conversation with dtube where he said struggeling with the Commcenter inside the PwnageTool process is done by the Dev Team's software. If you use it "outside/stanalone" it may cause the descripted problems.
Thats why dtube suggested to offload all the comm services in the top post of this page.

just my 2 cent,
v.

Quote:

---

Originally Posted by dtube

@chevy45,
After you update to 2.2.1, all you have to do is use quickpwn 2.2.5-2 to jailbreak/activate it.
There is no need to select the installer + unlock option in quickpwn.

---

sorry I forgot to mention that I was on 1.1.4 and also That I'm on a Mac., I did used quickpwn 2.2.5 for mac it jailbreaked and activated the phone but my baseband was still locked, cause 1.1.4 have baseband 04.04.05 and after I upgrade to 2.2.1 I ended up with locked 04.05.04, after that I try bootneuter to unlock baseband but ended up with this problem, now is unlocked and I think I only have to upgrade to 2.2.1 and since it have same baseband my phone will still be unlocked, I will only have to jailbreak again after the update, please correct me if I'm wrong and thanks for your observation.

Quote:

---

Originally Posted by volkspost

Just an addition to what I saw when I used a custom firmware from PwnageTool 2.2.5 on my 2G test-iPhone. It seems to me that BootNeuter off-loaded the CommCenter, did a reboot, then (with CommCenter off) and started again BootNeuter did its job. After that the Commcenter is loaded again - reboot voila.
That matches Muscle's conversation with dtube where he said struggeling with the Commcenter inside the PwnageTool process is done by the Dev Team's software. If you use it "outside/stanalone" it may cause the descripted problems.
Thats why dtube suggested to offload all the comm services in the top post of this page.

just my 2 cent,
v.

---

Volks my problem seems to be when bootneuter try to restart the phone it hangs long time in doing it and then restart it to normal mode with commcenter loaded. hope this helps.