planetbeing

planetbeing

31p

16 comments posted · 2 followers · following 0

13 years ago @ http://linuxoniphone.b... - iPhone 3G binaries! · 2 replies · +6 points

I don't really get what's so hard about it, to be honest. The only thing you need to know are: 1. how to download files from the Internet, 2. how to unzip files, 3. how to transfer files over SFTP and 4. how to copy and paste commands into Terminal.

However, on the bright side, I'm sure someone will come along with a tutorial that breaks it down even further than this one does. Someone will probably also come out with an easy to use tool to do the same thing.

13 years ago @ http://linuxoniphone.b... - Status update · 0 replies · +1 points

Yes. This is now fixed.

13 years ago @ http://linuxoniphone.b... - Status update · 0 replies · +4 points

True enough, though there is a way to bootstrap Android or Linux with just Spirit if we get desperate:http://code.google.com/p/iphone-linux/source/brow...

This was the very first idea people had for iPhone Linux (before we had bootloader level access). We can write it better now, but I'd rather not put in the effort until it is clear it is necessary.

14 years ago @ blog.iphone-dev.org - blog.iphone-dev.org/po... · 1 reply · +1 points

3.0 just has lower battery life.

http://www.google.com/search?q=3.0+battery+iphone

14 years ago @ blog.iphone-dev.org - blog.iphone-dev.org/po... · 7 replies · +1 points

It's pretty much impossible for ultrasn0w to be responsible for that. The only way to find the culprit of stuff like this right now is to login to your iPhone over SSH (or install MobileTerminal) and use the following command: "ps -e -otime,utime,stime,command"

This will display a list of all running processes. Whichever process(es) that have an exorbitant running time is probably the culprit.

14 years ago @ blog.iphone-dev.org - blog.iphone-dev.org/po... · 1 reply · +2 points

We were too busy working to pick apart his RC2 until a couple of hours ago. I read the code and it messes up 8 KB of it in nearly the same way. The problem isn't that he's using up "extra memory" but more that he trashed a megabyte of it before. Now he only trashes 8 KB, but there's at least seven references in the code to that area so it's very much used. He unmaps it after he does the unlock... but the area he WAS using is still trashed. Merely unmapping it doesn't really accomplish that much.

Maybe for RC3 he'll actually malloc the area of memory he uses.

14 years ago @ blog.iphone-dev.org - blog.iphone-dev.org/po... · 0 replies · +3 points

Don't really care too much.

14 years ago @ blog.iphone-dev.org - blog.iphone-dev.org/po... · 1 reply · +3 points

Don't really care too much. =P

14 years ago @ blog.iphone-dev.org - blog.iphone-dev.org/po... · 1 reply · +1 points

Try to buy 3.0 if possible. 3.1 will probably have the bug we're using (for the SIM unlock) fixed. Buying a 3.1 phone for jailbreaking purposes only is (probably) safe.

14 years ago @ blog.iphone-dev.org - blog.iphone-dev.org/po... · 3 replies · +4 points

The other part of the equation is that it's just not ready for primetime yet. No easy to use tool exists. We don't even have a standardized long set of instructions everyone can follow (generating one would take effort as well).

Notice I didn't show you the process of HOW I jailbroke my particular phone. That's a ten hour video right there. =P (well, I was still working out all the bugs and caveats as I came across them)