DIG
Active topics
  1. Originally posted by drewhiggins:[..]

    Is that even with the EU restrictions? It is a bloody loud thing - it uses a different audio chipset (Wolfson) than what the classic uses (Cirrus Logic).


    Yep mine is restricted but massively loud. As loud as my 4th gen.

    Found another more major fault. It skips when playing apple lossless files!!! Whats that all about
  4. Originally posted by germcevoy:[..]

    I need the screen lock on though or else taking the thing out of my pocket will be impossible without changing a song or restarting it. Tut tut. all my U2 studio stuff is apple lossless.


    Confirmed the first-gen doesn't do it. Possibly the new hardware they used for the second-gen has caused the issue and software isn't written to handle it properly yet (which you think it would). I hope it's not another early-adopter classic case.

    I was having problems earlier. Albums that fade in were coming out all static and full of dead noise. Turns out Foobar had been configured to rip MP3s as 8-bit stereo hybrid, and apparently the touch struggles with 8-bit lossy audio and so does my laughable computer audio setup, so I changed it to 16-bit stereo - all is well now.

    Luckily I had them as WAV files ripped already, just do them back to 192 MP3.

    Alright, I'll be back probably tomorrow - it's getting a bit late. Night all!
  5. Converting all that lossless is gonna be a bastard.


  6. Use DBpowerAmp, it has a feature to convert a whole folder or disk or whatever to whatever you want. I love it, it can convert 30 lossless shows into lossy in 10 minutes with my 4 processors.


  8. I could do with saving the space to though so might be worth the while


  10. lol..........


  11. Alrighty. You do it like this:


    Download this file: http://www.mediafire.com/download.php?mt3amqhmzzl (170Kb)

    From Cydia, if you don't have it already, download Poof. This hides icons on your springboard (main application screen).

    SSH with WinSCP to your iPod and look for the /Applications folder. Drop and drag the blank apps to that folder, so you should have Blank.app, Blank1.app and so on.

    Reset your iPod, turn it back on and back in Poof, there should be some blank apps, toggle them on or off. Now drag them around and put your icons wherever you like. You can have an entirely empty top row, or just a few icons after doing this.
  12. One isn’t enough

    It’s becoming more evident that a jailbreaking tool for the new 2nd-generation (2G) iPod touch is unlikely - at least from the iPhone Dev Team. The members of this development team have labeled the task of unlocking the 3G iPhone as their top priority right now, and left 2nd-gen iPod touch owners hanging with their comment, “we are not looking at the iPod touch 2G at the moment.”

    But just has long is “at the moment” going to be? User ledhendrixman over at iPod touch Fans found a few interesting comments made by members of the iPhone Dev Team in regards to the 2nd-gen iPod touch jailbreak. Continue reading to find out what the team members had to say and for the full scoop on the progress of the 2nd-gen jailbreak.

    Reading through the thousands of comments that the iPhone Dev Team gets each time they write a blog post can be a nuisance, and isn’t something that a typical person like you or I would do. Maybe you, but certainly not me. But ledhendrixman did just that, and found some interesting comments made by two of the Dev Team members. After a user commented on one of the iPhone Dev Team’s blog posts, asking if they’ll ever be a jailbreak for the 2nd-gen iPod touch, Dev Team member pytey put it pretty straight forward:



    It isn’t even on our radar to be honest.




    That said, it looks more evident that the 2G iPod touch jailbreak isn’t next in line, it’s not in the line at all. Another member from the Dev Team, MuscleNerd, also had his own comments about the jailbreak for the 2nd-gen iPod touch:



    If the application CPU or bootrom used by the iPod 2G make their way into some future iPhone, then we’d definitely be motivated to talk more about it. I think it’s *still* the case that only one of us even has an iPod 2G




    In an earlier comment posted by MuscleNerd, he makes it obvious that the iPhone Dev Team are not working on a jailbreak method for the 2G jailbreak at all, by mentioning the amount of time they’ve worked on it:



    The iPhone DevTeam has tried to jailbreak the iPod Touch 2G for an accumulated total of 25 minutes, give or take 5 minutes.




    To make that easier to understand, unless the processor that is inside the new 2nd-gen iPod touch is used in a future iPhone, they aren’t interested. This is because there is a new processor in the 2nd-gen iPod touch (s5l8720x) with a new bootrom which makes the iPhone Dev Team unable to send old files to be exploited, and they don’t want to bother investigating it unless it’s released for an iPhone - which is the basis of the dev team anyways. Like he mentions, only one member of the Dev Team even has a 2nd-gen iPod touch. So unless the rest of the team is holding off on purchasing one of these shiny devices until Christmas rolls around, the impatient complaints from 2nd-gen owners aren’t going to go away. MuscleNerd says it right - it is the iPhone (not iPod) Dev Team anyways, right?

    What now?

    Although it’s clear that the iPhone Dev Team’s best interests don’t include a jailbreak method for the 2nd-gen iPod touch, there’s some hope.

    I’m not sure about Chronic Dev, but I’ll throw it out there anyways. They were up and running with a series of updates which led us to believe they were making some significant progress. Next, the huge controversy that resulted from the Chronic Dev Team’s site suddenly going *kaboom* (insert your favorite action word you know from a comic book here). This sparked a huge debate over whether or not Chronic Dev was a hoax. But they’re back up again, and at least give us a little faith and anticipation towards a jailbreak. What do you think: fake or real?

    Update: After discussion on iPod touch Fans, there’s more evidence that the Chronic Dev is definitely not a hoax, and are making some significant progress towards the 2G jailbreak. User King Chronic from over at iPod touch Fans posted some key facts about this topic:

    It is a clean slate, in a sense. dev never released a client to communicate with dfu.20, since that was obviously new, or the recovery mode protocol of 2.*, but I guess that is different because they were saying that was ‘cmws thing’. So once it was realized that we needed to be able to do this if we even wanted to think about jailbreaking the device , tom3q and wEsTbAeR– went at it. Over the course of something like three days, huge progress was made, and eventually we had a client that could have a 2 way interactive session with iBoot, the iPod / iPhone Bootloader, or if that sounds confusing, think of it like the BIOS on your computer.

    You see, in older iBoot revisions, the diags command would jump straight to any parameter you gave it and start executing code there, with no checks or anything. so you could just use mw to write a small amount of code to 0×9000000, or if it was a patched iboot you wanted to strap, you would just send it to 0×9000000, and from there you would just type “diags 0×9000000″ and it would execute the code there. now, in 2.*, there is a permission + range check in place, so if you do not have a provisioned engineering / debug device that they have locked up at Apple HQ, then you cannot use diags.

    In fact, you can follow Chronic Dev’s progress on the 2G iPod touch jailbreak by visiting their Google Code page. The updates that they have posted make me more confident that they’re not a hoax, and they’re actually going to pull through on this one. They did mention in a blog post months back that they were almost 100% confident the method would work, so let’s keep our fingers crossed. It would be a huge publicity stint for Chronic Dev if they do pull through and would actually form some sort of “friendly competition” with the iPhone Dev Team.

    Talking about hoaxes, there’s no better place to find them than YouTube. You’re wasting your time searching for “2g jailbreak” on YouTube, because you’ll just find yourself getting ‘rick rolled’ by another YouTube user with too much time on their hands. But there’s a few videos that I believe stand out from the rest, and might be considerable progress towards (or even at) a 2nd-gen iPod touch jailbreak. But before you go following the instructions based off a simple YouTube video, think twice. Any video that tells you to download an .exe file or other type of file is a virus 99% of the time. I’ll throw this YouTube fake at you, for example. It should be evident to you that it’s fake, unless your very gullible.

    Either way, whoever releases a method will be praised and appreciated by so many - so it’s definitely something many people are taking a look at. Whether Chronic, iPhone Dev or a random YouTuber release the method, we’ll be happy regardless!




    This is the current status of the touch 2G. A bit technical, but certainly understandable.


    -Create iBoot 2.x Communication Tool (DONE - See 'iRecovery' in SVN trunk)

    -Look at new DFU Mode proctool (DONE - It seems to be the equivalant of WTF 2.0 that iTunes attempts to strap onto old devices (iTouch 1G, iPhones) when they are plugged in. Device ID is 0x1227 instead of 0x1222)

    -Get Filesystem Dump (DONE)

    -Get ASR Key for Root filesystem DMG (Not yet complete - See GoalGetRootFSKey)

    -Decrypt Ramdisk (Not yet complete - See GoalGetRootFSKey)

    -Find iBoot Exploit (Pending...)

    -Find userland exploit, for the time being (Not yet completed)

    -Implement exploit, and pwn (Not yet completed)
    Enable full /dev/kmem access on 2.x

    -Get /dev/kmem and /dev/mem to mount at devfs setup (DONE - via a simple flag patch)

    -Test if /dev/mem works with initial patch (DONE - can be dumped with 'dd' just fine)

    -Test if /dev/kmem works with initial patch (DONE - it will mount, but cannot be accessed for either reading or writing)

    -Patch kern.securelevel and kern.secure_kernel to 0 (DONE - but for some reason, with securelevel and secure_kernel at 0, we still cannot read/write to /dev/kmem)

    -Find out how to make secure_kernel 0, without a sysctl -w command everytime (DONE)

    -Find out how to make /dev/kmem rw, since usually secure_kernel and securelevel just need to be at 0 (Not yet completed)

    -Find out how to allow the getting of task port for pid 0 kernel (Not yet completed)
U2start is run by fans for fans. Help us reduce personal costs. Consider to make a donation to support us.
U2start is run by fans for fans. Help us reduce personal costs. Consider to make a donation to support us.
U2start is run by fans for fans. Help us reduce personal costs. Consider to make a donation to support us.
U2start is run by fans for fans. Help us reduce personal costs. Consider to make a donation to support us.