Tolino Vision 2 stuck in reset menu (possibly missing firmware)

[erayosm]

Hi everyone,

I have a Tolino Vision 2 that powers on, but it is constantly stuck in the reset menu. It seems like there is no firmware installed (or it might be corrupted).

Has anyone experienced a similar issue or knows how to fix it? I would really appreciate any guidance, especially if there is a way to reinstall the firmware or restore the device.

Thanks in advance!

[Waldy]

What happens after you run "Recover the system"?
After starting, does it return to the receiver menu?

[erayosm]

No matter what I do, it always returns to the same menu/screen.

[erayosm]

Originally Posted by Waldy

What happens after you run "Recover the system"?
After starting, does it return to the receiver menu?

When I turn on my Tolino, the Tolino logo appears on the startup screen, blinks twice, and then the device goes back to the recovery menu again.

[Waldy]

You can first try restoring using a TWRP backup, but to do this, you need to know whether your device is running Android 4.0.4 or 4.4.2.
To do this, boot TWRP and look in the device.xml file (.adobe-digital-editions folder) to see what firmware your device is running.

I'll send you the appropriate backup.

[erayosm]

First of all, sorry for the long post and I’m new to forums.

I’m having a serious issue with my Tolino Vision 2 and I’ve run out of ideas, so I’m hoping someone here can help.

When I turn the device on, the Tolino logo appears, blinks twice, and then it goes straight back to the recovery menu. No matter what I try, it always returns to the same screen.

What I’ve tried so far:

Used the “Recover the system” option → no change, it keeps looping
Tried other options in the recovery menu → same result
Fully charged the battery
Tried connecting it to a PC via USB → the device is not recognized at all
Opened the device and checked the internal hardware

Important note:
My device does not seem to have a removable SD card. Instead, it has a soldered SanDisk memory chip (eMMC), so I cannot use the usual SD card imaging method.

I also tried accessing the device through its serial interface and I can get some output, but I don’t know how to proceed from there.

At this point, I suspect the firmware might be corrupted, but I have no way to reinstall it.

Has anyone experienced a similar issue with this version of the Vision 2?
Is there any way to recover the device or force a firmware reinstall in this state?

Any help would be greatly appreciated.

Thanks in advance!

[Waldy]

Connect Tolino to your computer.
On Tolino, press and hold power button for 10-15 seconds to completely turn off the device (the LED on the power button should go out).
Release Power-Taste.
Now you need to boot into fastboot.
On Tolino, press and hold the backlight button, then press the power button and continue holding both buttons for about 5-6 seconds until the e-reader enters Fastboot mode.
This will also be confirmed by a beep from the computer speakers.
Check fastboot
1_TEST_fastboot.bat
and start TWRP
2_TWRP_boot.bat
The device will boot into TWRP Recovery mode.
See if your PC recognizes the device.
Here's a short video:
https://mega.nz/file/LZEBFIgA#Rf6fHX...5UchnLp4gqEDlg

And since you've opened the device, please let me know whether it has a 4A2 or 4B0 motherboard. There are two types of Vision 2. If a backup doesn't help, I'll prepare a full dump.

[erayosm]

Originally Posted by Waldy

Connect Tolino to your computer.
On Tolino, press and hold power button for 10-15 seconds to completely turn off the device (the LED on the power button should go out).
Release Power-Taste.
Now you need to boot into fastboot.
On Tolino, press and hold the backlight button, then press the power button and continue holding both buttons for about 5-6 seconds until the e-reader enters Fastboot mode.
This will also be confirmed by a beep from the computer speakers.
Check fastboot
1_TEST_fastboot.bat
and start TWRP
2_TWRP_boot.bat
The device will boot into TWRP Recovery mode.
See if your PC recognizes the device.
Here's a short video:
https://mega.nz/file/LZEBFIgA#Rf6fHX...5UchnLp4gqEDlg

And since you've opened the device, please let me know whether it has a 4A2 or 4B0 motherboard. There are two types of Vision 2. If a backup doesn't help, I'll prepare a full dump.

I followed every single step exactly as described, without skipping anything.
The device powers off correctly and I try to enter fastboot mode by holding the backlight and power buttons as instructed. However, my PC does not recognize the device at all — no new device in Device Manager, and fastboot commands do not detect anything.

https://mega.nz/file/ipZFxJ5K#SfiiyJ...BlHJGy2H4vh2Vk

I am using a 4B0 motherboard version of the Tolino Vision 2.

At this point, it seems like the device is not entering fastboot mode properly or the connection is not being established. Could this be a driver issue, or is it possible that the 4B0 version behaves differently?

[Waldy]

For Windows 11, you need to install drivers. There's a lot of information about this online. For example, here: https://www.youtube.com/watch?v=3UbxD7Cs2KA

[erayosm]

Originally Posted by Waldy

You can first try restoring using a TWRP backup, but to do this, you need to know whether your device is running Android 4.0.4 or 4.4.2.
To do this, boot TWRP and look in the device.xml file (.adobe-digital-editions folder) to see what firmware your device is running.

I'll send you the appropriate backup.

<version name="tolino" value="14.0.1"/>

[erayosm]

version name = "tolino" value=" 14.0.1 "

[Waldy]

Boot into TWRP.
Copy the "BACKUPS..." folder to the "SD Card".
https://www.mobileread.com/forums/at...1&d=1774639702
Next steps:https://www.mobileread.com/forums/at...1&d=1774639898
This is the simplest solution, but it doesn't always help, depending on how the device was bricked.
If this doesn't help, we'll restore it another way.

[erayosm]

Originally Posted by Waldy

Boot into TWRP.
Copy the "BACKUPS..." folder to the "SD Card".
https://www.mobileread.com/forums/at...1&d=1774639702
Next steps:https://www.mobileread.com/forums/at...1&d=1774639898
This is the simplest solution, but it doesn't always help, depending on how the device was bricked.
If this doesn't help, we'll restore it another way.

I just wanted to say that my e-reader is now working perfectly again. Everything is fixed and running smoothly.

Thank you all for your help and support, especially Waldy — I really appreciate the time and effort you put into helping me.

Problem solved 👍