Introduction

I couldn't find a guide to do this online, so I took notes while I figured it out myself. This guide probably also applies to other eReaders by Tolino, the Kobo Libra 2, and other Kobo eReaders. I only tested It with the Tolino Vision 6 on firmware version 16.1.0, so your mileage may vary (especially with the storage-increase part of the guide)

This guide was written in english, but some poeple translated it to various other languages. I'm not responsible if you break your device while following this guide, and I'm even less responsible if you break it while following the guide in a another language.

  1. oIU5UrhlBEgUZd1I
    oIU5UrhlBEgUZd1I
    65iUSRRcHDi4CdyF
    • Turn the eReader off by holding the power button on the back and selecting the appropriate option in the menu.

    • Lift the back panel upwards with a thin metal tool like the iFixit Jimmy or a flimsy butter knife.

    • Be careful around the area where the PCB resides so you don't damage it.

    • It's a bit tricky to start, but it becomes easier once you get it partly lifted.

  2. n5TMjHVMtFBYhysf
    n5TMjHVMtFBYhysf
    EwNaYMAqHXjPBFKs
    • Now that you have the device open comes the hardest part.

    • The SD Card is fixed in place inside the slot with double-sided tape on both sides.

    • You can approach this however you want, just make sure to take your time and not use excessive force.

    • I first wiggled it with my fingers a bit back and forth in the slot.

    • After that, I used a credit card to apply even pressure onto the raised section of the card away from the slot.

    • It also can be helpful to temporarily remove the screw on the bottom left of the card.

    Pushing with a pin on the opening on the back side of the slot did it for me.

    grmon -

  3. iVGnHHXGyafYPDUP
    • Now you need to create a Backup of the SD Card. You can use whatever software you like.

    • In the Screenshot, I'm using the built-in disk management of Linux Mint.

    • On Windows, you can use Programs like Win32DiskImager.

    • On Windows, you will also get a bunch of messages urging you to format the partitions. Do not format any of them. It will irrecoverably brick your device!

    • It's not enough to copy-paste the files from the partitions that have been recognized in your Operating system. You have to use a tool to create an image of the entire card.

  4. PIqMxtcySZf5HJcH
    • Now you do just the same thing "in reverse" with the new SD card.

    • Most programs that can create disk images also can write them. And the buttons are often right next to each other. You'll figure it out.

    • Don't delete the image after you're done. If your SD card ever suddenly dies you can revive your eReader with that backup.

  5. 3N2rba6xJZyoxPvj
    • If all you wanted to do was to replace the internal storage, the story ends here. You wake up in your bed with a repaired device and believe whatever you want to believe.

    • If you continue, you stay in Wonderland, and I show you how deep the rabbit hole goes to make the internal storage of your eReader bigger.

    • Increasing the internal storage of your eReader is the same as replacing it up to this point.

    • The rest of this guide is only relevant if you use an SD card with more capacity than the original one.

    • I also strongly recommend Linux for this. I used Linux Mint, but any modern distro will work.

    • You might be able to do this with some homebrew tools on macOS or WSL on Windows, but I haven't tested that.

    • In some screenshots I'm using a 512GB SD Card and and in others one with 32GB. That's because I had to go back and take more screenshots.

  6. YdIs11nOGWAr6aEV
    • The first step is to increase the size of the main data-partition to fill out the empty space at the end of the partition table.

    • Luckily the partition in question is at the end of the table.

    • Don't make the mistake I made and use GParted for this. It will break your system and you have to write the SD image again.

    • If you haven't installed them on your system, install f2fs-tools version >= 1.15 and gdisk.

    • f2fs-tools 1.14 (and maybe older versions as well) will throw some wrongful error messages depending on the size of the SD card.

    • Some/Most/All commands in this guide need to be run with superuser rights.

  7. A6kmD3OLohXMHlyk
    • Open gdisk to edit the partition: gdisk /dev/sdX where /dev/sdX is the USB device file. In my case, it's either sdb or sdc.

    • Sort the Partitions by Typing s

    • List all Partitions by Typing p

    • The console output should look somewhat like in the screenshots. Don't be stressed if some of the numbers don't line up.

  8. BetC2FtvnaL2n2ch
    • The partition you want to resize is called UDISK. Find its Partition number in the list from step two.

    • type i and enter the Partition number for our partition when prompted. (15 in this case)

    • Copy-paste the output of that somewhere save. You'll need it later.

    • As you can see, the entry Last sector has the value 31075328 (at 14.8 GiB) because that's where the old SD card ended.

  9. MBatY34BDJnfECls
    MBatY34BDJnfECls
    YMrRsOpUZSbVJuyc
    • Now you have to fix an issue that is caused by copying the entirety of a small SD card onto a large one.

    • By pressing v you can verify the partition table on the SD card. It'll come up with one problem and one warning.

    • We can safely ignore the warning but have to deal with the problem.

    • To do that you press x to get into expert mode.

    • In expert mode, you can press e to apply the fix.

    • Afterward, you press m to get back to the main menu.

    • Pay attention to the command prompt, so you know which mode you're in. Buttons have different functions in different modes.

  10. ALDbiNcrV34MnIrE
    • Now that this is over, you can finally resize the partition. For this, we'll delete the existing partition and create a bigger one at the same location.

    • Enter d to delete the partition. In this screenshot, it's number 1, in a previous one it was number 15. It might be a different one for you, make sure you get the correct one.

    • Enter n to create a new partition.

    • After entering d you'll be asked a bunch of questions.

    • The Partition number, First sector, and Hex code or GUID have to be the same as in the output you copy-pasted previously. Normally the default value for the First sector should be correct, but it doesn't hurt to double-check.

    • The default value for the Last sector will extend the partition over the remaining disk space. That's what you want, so just press enter to accept the default.

  11. UaZcqAxdANnsG3OE
    • Now we have to rename the new partition to the correct name.

    • Press c to enter renaming mode.

    • Enter the Partition number. Again: It might not be 1 for you.

    • Enter the name UDISK without any quotation marks.

    • Enter i and the Partition number. In that output, everything except Partition unique GUID, Last sector, and Partition size should be the same as in the copy-pasted info now.

  12. yQmrQTR3sIuF2mYv
    • Before you can wrap up the partition size increase you have to set the old Partition unique GUID again.

    • To do that you press x to get into expert mode.

    • In expert mode, you can enter c to change the GUID. It'll ask you again for the partition number.

    • After that, you can copy-paste in the GUID from the text you copy-pasted at the beginning.

    • When you're done, leave expert mode by pressing m.

  13. OPkgRCK1uE3EXwwj
    • Now you can check your work one last time before making it permanent.

    • Enter i and the Partition number. In that output, everything except Last sector and Partition size should be the same as in the copy-pasted info now.

    • If the other values don't line up the eReader probably won't boot. So go back now and change them.

    • Until now nothing has been changed on the SD card. So, if you're not sure if everything is right and want to try again, you can just exit the program now and give it another try.

  14. smEDNAWIHTvT3XIa
    • If everything is correct, you can now write the changes to the SD card.

    • enter w to save the changes.

    • The program will ask you if you're sure, enter Y to proceed.

  15. fbSHKvnk5PCALGQK
    • After you increase the partition size, you also have to increase the size of the file system on that partition. Don't worry, this is pretty quick in comparison to the other stuff I made you do.

    • Enter resize.f2fs /dev/sdXY where /dev/sdXY is the Partition file. In my case it was /dev/sdb15

    • If everything goes correctly, the command finishes pretty quickly.

    • If you get Mount unclean image to replay log first that means the partition wasn't unmounted correctly. Just mount and immediately unmount it in your OS and try again.

    • If you get Error: Device size is not sufficient for F2FS volume, more segment needed you might be using an old version of f2fs-tools. There's a bug that has been fixed with version 1.15. That's what happened on my machine, and is also the reason why the console looks different in this screenshot.

    • This screenshot looks different from the others because I switched to a VM for this step because the f2fs-tools version on my other device was too old. You can use the same linux terminal you used for the previous parts of the guide.

    sudo fsck.f2fs /dev/mmcblk0

    Error: In use by the system!

    This is what I'm getting at in the terminal what seems to be the issue?

    Gervie Macahia -

    I'm not sure what you're trying to do, tbh. While running fsck won't hurt it's not part of my guide.

    You're also running it on the whole disk (mmcblk0) instead of one partition of the disk (mmcblk0p1 for example)

    Maybe you get that error message because you're not supposed to run fsck on a disk, or maybe some of it's partitions are mounted.

    Dekkia -

    I also managed to get up to step 15 but at a lost if step 16 is to be executed in linux terminal. Is is possible to ask for the 512 image instead?

    Pan Maniego -

    Yes, step 16 needs to be executed in a linux terminal just like the steps before. I updated to guide to make this more clear.

    I won't share any images because I'm not sure about the legality of doing so.

    Dekkia -

    Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 2097152 (1024 MB) Magic Mismatch, valid(0xf2f52010) - read(0xfc00) Can't find a valid F2FS superblock at 0x0 Magic Mismatch, valid(0xf2f52010) - read(0x0) Can't find a valid F2FS superblock at 0x1

    ended with this, guess debian bookworm is the only choice to perform the last step.

    Gervie Macahia -

    This doesn't look like an issue with f2fs or a specific distro.

    It's more likely that you pointed the command to the wrong disk. (Or the right disk with the wrong formatting)

    Dekkia -

  16. xwJQNXTGUgohLHHd
    • Now's the time you'll find out if you did everything correctly.

    • Put the SD card into the eReader and press and hold the Power button on the back until the notification LED lights up or starts blinking.

    • Give it a few seconds to boot up.

    • After it's booted up, you can check out the newly acquired storage on the device.

    • If the device doesn't boot you probably messed up something with the partition table (been there, done that). If you connect it to your PC over USB it will show up as Allwinner Technology sunix Soc OTG connector in FEL/flashing mode when running lsusb if that's the case. In that situation it's best to start over at step 4.

    • If it boots but the storage hasn't increased, the file system size increase probably didn't work. Try repeating that step and make sure there are no errors.

    Thank you! Manage to expand up to 470ish as well using a sandisk 512 sdcard

    Gervie Macahia -

Conclusion

To reassemble your device, plop the back panel back on and you're done.

Dekkia

Member since: 29/07/16

433 Reputation

11 comments

A very well put together guide! In my case i used windows, but i had plenty of problems with my computer recognizing the partitions of the original sd card, so my solution was using a VM and it went smooth. The only thing is that after putting the sd card in the tolino i ended up with 45 gb of used space in a clean 128gb sd card that I don't know where it came from. But everything is working and i have more than enough space.

Jessemar -

Thank you!

The issue you're describing can happen with some versions of f2fs-tools below 1.15.

For the guide I used Debian Bookworm because the Ubuntu on my main machine still had 1.14.

Dekkia -

My sd card got broken before i could save the image and now my tolino vision 6 doesnt work. i have a new sd card and i can do the process, but i do not have the sd image. can yo please share the disk image?

1234 -

Sorry, I won't be sharing the SD card image because I'm unsure about the legalities of it.

Your best bet for finding an image is probably the mobileread forum.
Since the Tolino Vison 6 is based on the Kobo Libra 2 you might also get lucky with an image for the Libra 2.

Dekkia -

Please ask any questions on this page.

Either under the step that causes issues or in the comments at the end.

Maybe the answers are interesting for other people too.

Dekkia -

It worked! Thanks for the awesome guide and the suggestions, i fixed my eReader. The forum "mobileread" was really useful in troubleshooting the problem and i found someone had already found the solution there!!! Many thanks again for the suggestion!

1234 -

Dear Dekkia, thank you very much for this guide. I've followed it step-by-step and could recover my dead Tolino Vision 6 that got stuck at Recovery screed with a list of I/O errors.

Thanks once again for this awesome guide!

Lockitti -

Thank you!

I'm happy my guide was helpful.

Dekkia -

Meine sd Karte ist defekt. Sie ist am Pc nicht mehr erkennbar. Wo bekomme ich eine für vision6 formatierte SD Karte her? Oder wer hat einen „gebrochenen“ vision6

Winni -

Was tut man wenn sich der tolino vision 6 trotz neuer sd aufgehängt hat und man trotz langem Tastendruck nix passiert

Karin Walthert -

In diesem fall würde ich bei schritt 4 neu beginnen.

Auch würde ich empfehlen die englischsprachige anleitung zu verwenden. iFixit übersetzt Anleitungen automatisch in andere Sprachen und ist dabei nicht perfekt.

Dekkia -