Support and General Use > Hardware
Having and using two volumes on an iPod 6th Gen classic
iPodVT:
Okay, all three photos are uploaded, albeit in reverse order. Sorry about that.
iPodVT:
--- Quote from: Frankenpod on October 21, 2024, 08:39:07 PM ---So you have two separate partitions, rather than one >128GB partition/"disk"?
--- End quote ---
[Edit]
Yes - that is correct. From what I have read of other users' experiences, if I had expanded the first partition, corruption would occur if I were to boot into the Apple firmware. It seems that if the size of the first "legit" partition is not expanded from its 'legal' allocation (and maybe also not shrunk), corruption will not occur when you boot into the Apple firmware. I'm guessing that the Apple firmware is satisfied if the first partition remains as expected, and the firmware doesn't look at or care about what might be beyond that first partition.
My curiosity makes me want to try shrinking that first partition to see what would happen. But not at this time. For now I am more than content...
Frankenpod:
Interesting. Very Useful to know that it works like that. Curious why RB itself seems to treat the second partition as if it were a folder within the first one. Can a developer say if that's the intended behaviour or if it sort of works by accident?
Going back to an old thread where I was wondering about this issue, I never got round to trying rockbox_dev123's suggestion (for preventing it booting in OF) - maybe it would work for you here? Just entirely self-interestedly suggesting it because I'd be interested to know if it works.
https://forums.rockbox.org/index.php/topic,54703.msg252999.html#msg252999
--- Quote from: rockbox_dev123 on November 25, 2023, 02:57:12 PM ---I've given some context that is hopefully useful in the previous messages I quoted.
Another thing that you can do - without needing to reflash the bootloader - is just to delete or erase the partition that holds the OFW. This should be a simple way to prevent it from booting.
--- End quote ---
iPodVT:
--- Quote from: Frankenpod on October 21, 2024, 11:09:36 PM ---Going back to an old thread where I was wondering about this issue, I never got round to trying rockbox_dev123's suggestion (for preventing it booting in OF) - maybe it would work for you here? Just entirely self-interestedly suggesting it because I'd be interested to know if it works.
https://forums.rockbox.org/index.php/topic,54703.msg252999.html#msg252999
--- Quote from: rockbox_dev123 on November 25, 2023, 02:57:12 PM ---I've given some context that is hopefully useful in the previous messages I quoted.
Another thing that you can do - without needing to reflash the bootloader - is just to delete or erase the partition that holds the OFW. This should be a simple way to prevent it from booting.
--- End quote ---
--- End quote ---
Haha - not only do I now remember having previously seen that thread - I was also a contributor to it.
Isn't that effectively the same as what is demonstrated in the video on the iFlash website [https://www.iflash.xyz/how-to-rockbox-installation-on-ipod-classic-using-new-bootloader/]? I think I tried it once and when the bootloader tried to boot into the OF, corruption occured even though the OF wasn't there. I might be misremembering...
In any case, the more I think about it the more I like the fact that Apple Disk Mode and Diagnostic Mode are both still available to me with my current setup.
I'm also now wondering if I were to delete the second partition would the OF once again be fully functional as when the iPod was initially reformatted/restored? I bet it would. So, another thing to try. But I can't (or shouldn't and am trying to not let myself) spend any more time on it this week.
iPodVT:
--- Quote from: Frankenpod on October 21, 2024, 11:09:36 PM ---Interesting. Very Useful to know that it works like that. Curious why RB itself seems to treat the second partition as if it were a folder within the first one. Can a developer say if that's the intended behaviour or if it sort of works by accident?
--- End quote ---
I'm guessing that they just display it that way because it was probably a lot easier and faster to implement than having to redesign the file browser UI for a truer visual representation of the hierarchy of two sibling volumes above each one's descendent directories and files. The functional user access is basically the same either way.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version