Last month I used Redsn0w 0.8 to jailbreak my activated AT&T 3GS running 3.0 and I want to upgrade it to a jailbroken 3.1 but I want to be clear before I use PwnageTool 3.1.3 that it will work.

Since the requirement for using PwnageTool 3.1.3 on my 3GS is previously jailbreaking it with Pwnage 3.0, does Redsn0w 0.8 count?

If not, is there a solution for upgrading a 3GS to jailbroken 3.1 for my situation?

Thanks,

Aletheion

yes, you should have no problems.

redsn0w and purplera1n jailbreaks on 3.0 or 3.0.1 will work to restore to a jailbroken custom 3.1 from pwnage tool 3.1.3.

IHMO, there is no point to upgrade to 3.1 even with custom firmware.
MuscleNerd is still using older version.
I'm still using 3.0.

__________________
** If you just want to support hackint0sh.org with a donation click here **

Yeah, I'm on 3.0 as well, would love to have Dropbox though, which is 3.1+

__________________
16Gb iPhone - Unlocked via BootNeuter
32Gb iPhone 3GS - Officially unlocked

Isn't 3.1 suppose to have better wifi reception and better battery useage maintenance?

I have found the wifi to be more reliable on 3.1 Battery has not been dramatically different. My carrier isn't restricting tethering so that is not an issue at all.

There must have been some issues though with 3.1 because 3.1.2 is out now. I really hope that the iBoot vulnerability that has been made public was revealed too late to be fixed otherwise it was revealed for no good reason.

__________________
Please read the stickies and search the forum before posting!
----------
iPhone 3GS 32GB factory unlocked (3.1; Pwnagetool, Cydia, OpenSSH)
iPhone 8BG (3.1.2; Pwnagetool, Cydia, OpenSSH)

There were a lot of issues with 3.1, even for people using plain-vanilla phones with no JB or unlock. Apple had to replace many phones after they were upgraded to official 3.1.

George tweeted that his blackra1n JB still works on his 3GS, so it looks like the vulnerability wasn't fixed.

Thanks for that. I did the fat nasty last night and all went well. I only use a few jailbroken apps, but so far everything is good except tethering. But I'm using PDAnet so that's fine for tethering (wish it was free tho).

I also have the AT&T missing logo bug, but so what. I'd rather not see that anyway.

By the way, the apps I'm using are:
Cydelete
PrivaCy
SBSettings
BiteSMS
Backgrounder
Intelliscreen

They all work with no issues for me. And now, I get to use commands through the bluetooth which is really the only feature of 3.1 I wanted.

On a side note, it seems bandwidth is down. I was getting close to 2Mb but now I'm getting 800k at best. I'd like to upgrade the carrier, but think that's bad news if I do from what I've read. I thought about downgrading back to 3.0 since my SHSH is on file with Cydia to get the bandwidth back, but when I do the hosts hack (and confirm that the domain is resolving to the right IP) I get the Apple downgrade error during restore.

So I'm good like this. Everything works but bandwidth is a bit slower. Probably throttled... the bastards.

-Aletheion

Well, besides tethering not working which I fixed with PDAnet, and the possible bandwidth throttling to 800kbps, I've realized that Visual Voice Mail is not working. So I've spent a couple of hours trying to find a fix for it to no avail.

My OS (prolly a 3GS thing) does not have the Cellular Network Settings in the Network preferences. I tried the old tether VVM fix from help.BenM.at/help.php mobile configs, but that didn't do it either. So I'm stuck with no voicemail at the moment.

Anyone got a solution for that?

NEVERMIND - Update to the Update: I thought that it was not safe to install the carrier update, but apparently it is (at least for me as an AT&T customer) and VVM came back.

Update to the Update to the Update: Okay, today I got 1.8Mb again on the 2Wire bandwidth meter. Dunno what was going on when I was getting 800k, but I'm pleased to say that bandwidth throttling is NOT the case.

Sorry to drag the thread out, but I thought other's may experience this as well and wanted y'all to know that the carrier update fixed the VVM.


-Aletheion