Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Have you checked the giant topic that holds all the JB Guides? They all hold your hand, in fact with the pictures included in one of them it's like having both hands held!


Do you happen to have a link to this......Yes I need some hand holding to get to the real hand holding.....Thanks :)
 
I hate to say it but all the automated jailbreak software is both good and bad.

Good for the fact it drastically lowers the competency level required to jailbreak a touch but bad for the very same reason because if something goes wrong then people have no clue how to fix it since they never stepped through the manual procedure.
 
I hate to say it but all the automated jailbreak software is both good and bad.

Good for the fact it drastically lowers the competency level required to jailbreak a touch but bad for the very same reason because if something goes wrong then people have no clue how to fix it since they never stepped through the manual procedure.

i agree, i think someone should do it manually so they know where things are going and what they are doing and also learn something about the file system.

I think people dont realize that these are somewhat thrown together apps (which is no knock on the creators). They arent going to try there hardest to reduce and work around the user errors...
 
I hate to say it but all the automated jailbreak software is both good and bad.

Good for the fact it drastically lowers the competency level required to jailbreak a touch but bad for the very same reason because if something goes wrong then people have no clue how to fix it since they never stepped through the manual procedure.

Actually, I disagree. The problem is in the competency level itself, not the method of jailbreak. Those with such low competency should not be attempting a jailbreak, 1-click or not. If they really have no clue how to fix the device after jailbreak, I don't think it matters which method they chose; it means they either specifically made a mistake of their own doing, or they dove into a task knowing they were not skilled enough to handle any exceptions. It's no fault but their own.
 
noob here...and gotta say, i'm pretty proud of my ipt hack and it was sooo worth it...

-first time using terminal
-first time SSHing
-took me all Friday night and into the wee hours of Saturday but that's cause I was using SEARCH and reading all the tips and repository info...

thanks to all of you guys for the help on this forum...

P.S - been lurking for a while but first post...
 
noob here...and gotta say, i'm pretty proud of my ipt hack and it was sooo worth it...

-first time using terminal
-first time SSHing
-took me all Friday night and into the wee hours of Saturday but that's cause I was using SEARCH and reading all the tips and repository info...

thanks to all of you guys for the help on this forum...

P.S - been lurking for a while but first post...

solid first post...
 
come on. you all KNEW this was coming. You knew that once the jailbreak was released people would come in here and rant it up about their "broken" ipods.

It's just how the world works :cool:

/me jumps back to the MacBook Pro Forums
 
I'd love to jailbreak mine but I'm too stupid at that sort of thing without someone holding my hand step by step :eek:

Done. Go to YouTube and search for videos by "ipodtouchmaster". He will walk you through anything you want to do with your touch.
 
Actually, I disagree. The problem is in the competency level itself, not the method of jailbreak. Those with such low competency should not be attempting a jailbreak, 1-click or not. If they really have no clue how to fix the device after jailbreak, I don't think it matters which method they chose; it means they either specifically made a mistake of their own doing, or they dove into a task knowing they were not skilled enough to handle any exceptions. It's no fault but their own.

While I agree that there's no fault but the owner's for diving into something they don't understand, I feel like the manual method gives the end user an idea of what the process actually is and will give you the information to fix problems rather than simply restore and try again. The GUI will appear friendly and enables access to newer users that won't be able to diagnose problems, while the command-line method will appear intimidating and bring a sense of reality of what you are actually doing and spare some newbies possible panic by steering them away. There's still those that lack common sense to do a little research, though...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.