It looks like that Apple is slapping new bootrom’s at the factory on more recently manufactured iPhone 3GS’. According to chainsaws and Mathieulh in #iphone, they discovered that the new bootrom is 359.3.2, where the original is 359.3. According to chainsaws, the new bootrom is causing issues with the latest PwnageTool and blackra1n jailbreak tools. It seems this bootrom came into the public domain last week.
If you purchased a new 3GS recently, make sure that you toss it into DFU mode to check the bootrom. If you do not have version 359.3 then you will more than likely have issues with the new jailbreak as PwnageTool and blackra1n make use of the 24kpwn exploit and it seems the new bootrom fixes this issue. We’re not 100% sure at the moment, but I’m sure that the iPhone Dev-Team will be looking at this info. It could be just a simple update to PwnageTool as it may be memory address changes only, who knows.
That’s all the info we have now, I’ll update if more info comes along.
EDIT: The new devices are tethered jailbreaks through blackra1n only. PwnageTool will not work on these newer devices as it relies on the 24kpwn exploit to make it bootable, which the new bootrom causes to fail, forcing you to run blackra1n everytime the device reboots.
Yes, it’s true. Chameleon 2.0 RC1 was released just recently, and I have to say, it’s everything we could dream of.
Download the binaries. To install to a normal setup (non-RAID, which I will only be covering as I do not use RAID), cd into the i386 directory inside the main extracted directory and do the following:
This will bring up a list of your attached volumes and partitions like so:
My startup disk name is “Macintosh HD”, so I want to install to that hard drives bootsector. It’s name is disk1s2. Yours will most likely be different, so be careful and pay attention to this part. For mine, I want to do the following to install chameleon:
First, install boot0 to the MBR with
sudo fdisk -f boot0 -u -y /dev/rdisk1
Install boot1h to the partitions bootsector with:
sudo dd if=boot1h of=/dev/rdisk1s2
Now, install boot to the partition’s root directory with:
sudo cp boot /
And that’s it! You should have the new Chameleon up and running the next reboot.
You can even theme it, copy /Extra and it’s contents to / and then you can play around with the images to your liking. There is also an smbios.plist file you can fiddle around with if you don’t like the default settings Chameleon will setup, just put that in /Extra and you’re set.
Now, most people who have Ubuntu or some other flavour installed on another partition or hard drive should have Chameleon auto detect the OS, but for some like me who just did a fresh default install of Ubuntu 8.10, this may not be the case. When you install Ubuntu 8.10 using the default install method, it doesn’t install GRUB to the MBR, only part of it. That part then looks at /boot for the rest, and then boots the system.
I have Ubuntu installed to my slave HD. It wasn’t detecting the OS as explained above because I used the default install method. I wasn’t sure if it installed GRUB properly. To check if GRUB was installed properly, I had to run the following:
sudo dd if=/dev/disk0s1 of=./bs bs=512 count=1
This will return some info, you can ignore it. Next run:
The last two bytes must be 55 aa. If they are not, then you will need to install GRUB to the MBR and bootsector. To do so, you must do a fresh install of Ubuntu. Unplug all your drives except the one you wish to install Ubuntu to, then boot the LiveCD, and go through the options MANUALLY. At the end, you must tell the installer to install GRUB to the boot or root partition, then finish the install. When it’s done, plug your drives back in and reboot into Ubuntu (if your BIOS doesn’t offer a boot selector, then set the default drive to boot as the Ubuntu drive). boot your installed copy of Ubuntu and run the following command:
sudo grub-install /dev/sdX
Replace X with the letter of your root Ubuntu partition (you can use GParted to find this). A bunch of text will follow, hopefully saying success. If so, you can now set your default boot volume in BIOS back to the drive with Chameleon on it, and you should see the Linux penguin appear at the Chameleon boot selection screen.
And that’s all there is to it. Happy booting!
Update: If you use Munky’s EFI booting method ( http://www.insanelymac.com/forum/index.php?showtopic=127330 ), then take a look at this post ( http://www.insanelymac.com/forum/index.php?showtopic=160014 ) to get Chameleon 2.0 RC1 working with this type of setup.
UPDATE 2: Here’s a video of my own theme for Chameleon 2.0 RC2, sorry for the blurryness, my digital camera sucks (need to replace it).
Recently, I’ve had (and so have many others apparently) a severe issue with iChat 4.0.7 on Leopard concerning the addition new contacts. They would show up, blink and then disappear and would only appear online/offline after logging out of iChat and then back in.
The first fix is simple, browse to ~/Library/Preferences and delete all the com.apple.iChat* plist files:
This seemed to work for some people, but for others, the problem lied a little deeper. It was more specifically an issue with the Address Book and a corrupt database of your contacts (improper permissions).
To rectify it, here is what you do. First, backup your current contacts to a vCard (select all and export to vCard) then quit all open applications except for Finder. Then, open up terminal.app and run the following command:
This removes the corrupt files with improper permissions. It is recommended that you reboot at this point. After you’ve booted back up, you should be all set. Open up iChat now to test, and add a new screen name (I have several so I simply used the new AIM.app and signed in with my alternative name and signed into my desired screen name via iChat). The contact should no longer disappear. If so, go ahead and add your vCard with all your backup contacts to the Address Book. I would now suggest testing adding a screen name again. In fact, try a few screen names to make sure it’s not just the one that is working.
At this point, iChat should be working as expected now. I hope that Apple takes note of this and adds some sort of fix soon. I struggled with this issue for months, and today I no longer have to.
UPDATE: It now looks like the issue is back, and the above steps don’t seem to be working at all as they used to. 10.5.7 must have some other method of control, as this method WORKS on 10.5.6, but not on 10.5.7. I will look into this issue.
UPDATE 2: Looks like the issue has gone away, I’ve recently been able to add new contacts without issue now again. I don’t know if it took a bit for my method to kick in, but it’s working fine now on 10.5.8.