Volla tablet stuck in reboot loop after installing e/os

I recently bought a Volla Tablet direct from Volla and went through the process to install e/os on it.

I followed the guide here and downloaded IMG-e-3.4-a14-20260114569180-official-mimir.zip from here.

**I got to the step “**Run the installer script on Terminal(Linux) or on Git Bash UI(Windows)" and used Git bash and it worked. The script flashed all the files and then device rebooted just like the guide said.

After the auto reboot the device screen lit up for a few seconds, went dim for about a second, then went black. Then it repeated that over and over. I have tried holding power and volume up to enter recovery mode and it doesn’t work. It has been doing this for hours now and I’ve tried holding the power and volume buttons in every combination possible at different timings. The only thing I can get it to do is if I hold power and volume up long enough the screen stays black, but as soon as I release either button the screen lights up and resumes its cycle of bright, dim, dark, over and over. There is no text, no logos, nothing.

My device manager in windows briefly recognizes the tablet while the screen is black and it shows up under the MT65XX preloader. If I let the battery die, will I be able to use this to fix it?

I am beyond frustrated at this point. Does anyone know how to get this thing to work? Was the IMG file i downloaded the wrong one? Please help!

Could you try to boot into recovery, button combination should be in the install doc? Does it show /e/OS recovery?

Sounds like missing drivers caused not all steps to be done. Did you watch the process on the computer?

Hi @salewis42 shared the issue details with the development team. This was the response:

Since the device has been purchased from Volla, it is a new unit with a different hardware, for which we are adding support in v3.5 (release due this week)

The current state of the device is as it was flashed using fastboot flash script from our IMG package built for a previous version.

The device itself is fine. It needs to be flashed to v3.5 either via:

User has to contact Volla and send the tablet over to them to get it re-flashed

OR

They have to enter fastboot mode without visual cues. This means holding volume UP and power for 10 seconds, then releasing power key while still keeping volume UP pressed.

  • It should stop going back and forth between modes at this point and screen should be lit up and should be at a prompt (but blank).
  • At this point, they have to release volume up key then press it once again to select fastboot mode from the prompt (without visual cues) then press power (might take a few tries to get it into fastboot this way)

Pl can you raise an issue in gitlab so that the developers can directly contact you

2 Likes

does someone with the device can take photos of expected screens to help the blind @salewis42

Thank you for this. Using this button combination I was able to get the tablet to stop rebooting. The screen is still blank and doesn’t show anything, but it seems like it’s on. Pressing the power button causes the screen to light up (still blank) and after a few second the screen goes black. Pressing the power button again causes the screen to light up again. If i press the power button while the screen is lit up, it immediately goes black. So it seems like it’s on and the power button is locking/unlocking the screen. I’ve tried doing the abd devices and fast boot devices commands but neither one show the tablet.

I will submit an issue in Gitlab like you’ve recommended. If we aren’t able to figure out how to get the right version of e/os flashed onto the device I will try contacting Volla to see if I can send it to them for them to flash it back to factory settings. Thank you!

I guess this is just a typo but the command is

fastboot devices

And adb devices :slightly_smiling_face:

I am having the same issue after manually trying to flash 3.7 to my volla tablet according to the documentation. It is now in a bootloop, still showing the volla logo despite the flashing process finishing without an error. How can I solve this?

I passed on this feedback to the developer. The developer was asking if you could try the installation using the webinstaller

An observation. I have no experience of this device and you already had the official advice.

The script on similar devices finishes with a comment like “Reboot the phone now” or “Your phone will reboot now”.

The scripts (for other devices) also include a long list of partitions to write. The script command is flash or abort. If unfinished this sometimes results in terminal output with no obvious error, except the list of flashed partitions is incomplete and no “Reboot signoff”.

Did you save the terminal output?

I had tried the webinstaller, but it aborted late in the process due to some signature mismatch. I do not recall the error message, unfortunately.

My Volla tablet started life as the linux version, and i manually flashed it to android (Volla OS official image, Android 15). Maybe there is yet another hardware revision you are still unaware of?

If possible DM me the output of

fastboot getvar all

It just says “waiting for any device” in terminal

On the device, it displays the volla bootlogo and at the bottom, there is a line “crc abnormal,retry:0data read(addr:90) and so on…

Are you on linux or windows? If windows can you confirm if the USB drivers are installed properly?

“waiting for any device”

I am on linux, this is the same PC that I was manually flashing from, so at least the adb fastboot command was working properly before the volla tablet rebooted by itself after finishing the flashing.

1 Like