iPod Touch stuck in recovery for no apparent reason!

[Darkfire314]

Hello everybody,

I have had a successful jailbreak for the past 4 months using redsn0w, and am on a 4.2.1 firmware on my iPod Touch 2G. Today, while going through my processes in SBSettings, I noticed my memory was so low, so I hit "free up memory." My iPod froze, then crashed, then went into recovery mode (the image of the cable plugging into iTunes.) It is stuck in this loop, even when using TinyUmbrella to try to kick it out. I have a verbose boot, so it tells me something along the lines of this:

-Checking catalog hierarchy... missing thread 999805
- Incorrect values (32,790 files instead of 32,792)

I really don't want to recover, as i have alot of un-backed up data on there. Any help at all would be much appreciated!

-Justin

[iYeow]

If tiny umbrella can't kick it out, you only option is a restore again

[Darkfire314]

If tiny umbrella can't kick it out, you only option is a restore again

Two things:

1. Could I try the "fix recovery" option in TinyUmbrella?

2. If I have to restore, is there any way to extract data from the iPod before I do so?

[iYeow]

Yes, you can try fix recovery . I don't think you can retrieve any data as. Your iPod is in recovery mode and you can't ssh into it.
But one thing you can do is after your restore , do the jailbreak first , only then setup your iPod as a backup restore from your previous backup.

[Darkfire314]

Yes, you can try fix recovery . I don't think you can retrieve any data as. Your iPod is in recovery mode and you can't ssh into it.
But one thing you can do is after your restore , do the jailbreak first , only then setup your iPod as a backup restore from your previous backup.

I think I am going to try iREB's loop fixer, I'll let you know if it works.

[iYeow]

Good idea as you are already in recovery loop.

[Darkfire314]

Good idea as you are already in recovery loop.

No dice. I watched the verbose boot closely and I noticed that it says something is missing in my "rdisk0s2". This is apparently where the missing two files are (it's in the directory of /var/private). I understand that a restore is probably my only option right now, but I really need to extract some data off of my iPod first! Any ideas on getting this, or perhaps even fixing this loop?

[iYeow]

Try the sticky thread regarding ramdisk , quite an elaborate work to do created by Mes if a restore still ends up in recovery or not booting up

[Darkfire314]

Try the sticky thread regarding ramdisk , quite an elaborate work to do created by Mes if a restore still ends up in recovery or not booting up

I see what you are saying, the problem lies within in the RAM disk (rdisk). Using the method described in the thread will create a new RAM disk? If so, that should theoretically solve my problem. Also, that whole process seems a little frightening, do you think I should be able to do it?

[Mes]

... Using the method described in the thread will create a new RAM disk? ...

Yes

. If so, that should theoretically solve my problem. Also, that whole process seems a little frightening, do you think I should be able to do it?

Hard to say. The process is complicated. Pre-existing *nix and iDevice knowledge is required. File names are slightly different between iDevices and iOS versions. It's not for the beginner or week-end programmer-want-to-be.

[Darkfire314]

Yes

Hard to say. The process is complicated. Pre-existing *nix and iDevice knowledge is required. File names are slightly different between iDevices and iOS versions. It's not for the beginner or week-end programmer-want-to-be.

Will this method retain all the data on the iPod? Because if it wipes it I might as well just restore and re-jailbreak it. And to be honest I don't have too much experience with iOS programming, so I'm not sure If I want to take that route.

[iYeow]

I , that whole process seems a little frightening, do you think I should be able to do it?

I dont know, I haven't had this problem and I haven't tried it, with my knowledge, I am not sure if I can do it too, lol.
Why don't you do a restore to 4.2.1 and see what happens

[Mes]

Will this method retain all the data on the iPod? ...

Yes. This was clearly stated in the write up post #1.

[Darkfire314]

I dont know, I haven't had this problem and I haven't tried it, with my knowledge, I am not sure if I can do it too, lol.
Why don't you do a restore to 4.2.1 and see what happens

I'm sure a restore would work no problem, and I would do that, except that I am stubborn and forgetful so I have not backed up my iPod since the jailbreak (very very stupid, indeed.) This is why I want to restore as a last resort, as all my data will be lost.

Yes. This was clearly stated in the write up post #1.

I am sorry. I just re-read it and it is clearly stated. My mistake. I have also just read through the whole thing and There is no clear indication that after building a new RAM disk, I can simply close all connections and be on my way, as you have provided instructions for using SSH commands, which I have no intention of doing, as I strongly believe my problem lies within the RAM disk. And while I realize the file names and such things as the keys will be different as it is a different device than a 3G, the process should be the same, correct? ( I do realize this is stated, I just wanted to confirm)

*EDIT* I was looking on the iPhone Wiki for my keys to my Ipod Touch and it describes the restore RAMdisk as wiping everything off the NAND, which in turn means erasing all data. Is this correct, or is the process you list in your thread use these keys differently?

[iYeow]

I have a feeling this Ramdisk method is not going to work as you have a 2g itouch.

[Darkfire314]

I have a feeling this Ramdisk method is not going to work as you have a 2g itouch.

Why not? I already have the keys for restoring and updating the RAM disk. Also, another idea I had: even though it is stuck in recovery, I can still go into DFU. Theoretically, then, couldn't I use redsn0w to re-jailbreak it (which builds a new RAMdisk and retains my data.)

[Mes]

I have a feeling this Ramdisk method is not going to work as you have a 2g itouch.

iYeow ... you're probably right! Never owned an iPod anything A 2G itouch is roughly hardware equivalent to a 2G/3G iPhone? If yes, then this will not work! Follow the msfgy link below (reposted) for methods that do work on older devices.
http://msftguy.blogspot.com/2010/11/...w-devices.html

...instructions for using SSH commands, which I have no intention of doing, ...

This method works and it uses SSH (technically CLI over USB). If you want to use another method, you're on your own.

[Darkfire314]

iYeow ... you're probably right! Never owned an iPod anything A 2G itouch is roughly hardware equivalent to a 2G/3G iPhone? If yes, then this will not work! Follow the msfgy links for older methods that do --- also based upon a ramdisk.

This method works and it uses SSH (technically CLI over USB). If you want to use another method, you're on your own.

I wrote that incorrectly. I meant after building the RAM disk, you give some "helpful SSH commands", which I'm not sure what I would do with that. I only want to rebuild the RAM disk. Also, the links your provided to msfgy's tutorial is based on 4.1 iOS, whereas yours is based on 4.2.1. (which I have.) Do you know if re-jailbreaking is possible?

[Mes]

...... Do you know if re-jailbreaking is possible?

Darkfire314 ... This method has little to do with jailbreaking. Use standard methods for that.

... "helpful SSH commands", which I'm not sure what I would do with that. I only want to rebuild the RAM disk....

Obviously you don't understand the purpose of using a ramdisk. Do a complete restore and quit messing around with stuff you don't understand.

[Darkfire314]

Darkfire314 ... This method has little to do with jailbreaking. Use standard methods for that.

Obviously you don't understand the purpose of using a ramdisk. Do a complete restore and quit messing around with stuff you don't understand.

Alright. Thank you for your help. I realize the method you described did not deal with jailbreaking, I was just wondering if re-jailbreaking it could fix it.... If you know, or if there is already a thread on re-jailbreaking, please let me know.