Installation problem with E/OS on Volla tablet

[Grouchox]

So, day 1. I figured my problem lay in the Windows drivers, so I switched to Ubuntu and used the command line method. I had some problems with getting into Fastboot - somehow, the Volla tablet is behaving weird on boot, no matter what I do - but eventually managed to install the latest versoin of e/OS.

I couldn’t believe that just worked. And indeed, it didn’t. When I try to start the tablet, I get caught in a loop - there a “Orange State” warning, which should be dismissed after 5 seconds, but before that happens, the tablet resets and and starts again. It’s on a loop that even a hard reset doesn’t seem to be able to break.

Suggestions? Should I try an older e/OS build? Give the online installer another go?

[aibd]

Simplest thing first, were you sure to observe

Warning: Before proceeding with the installation, log out of any accounts you may have set on the stock ROM. Also, remove any screen locks that have been set on the device.

There is no warning in the instructions (implies that it should not be a problem) but did you change Android version between your previous Android and /e/OS?

@Grouchox

Give the online installer another go?

Please read some eosinstaller threads before you consider this; if any problem arises there may be no log to share if you need help.

---

… or …

---

@Grouchox

I hae the exact same issue as the original poster.

We read that the OP issue might be

@piero

look like issue was android SPL date mismatch

Did you perhaps have this?

[Grouchox]

@piero

android SPL date

Thanks for jumping in. I’m not familiar with Android SPL dates. Please elaborate. I got the tablet used, with a factory reset Volla OS.

[piero]

@piero

• You will find this information about stock OS on the device :

settings --> about phone --> android version 15 --> android security update

Install /e/OS on a Volla Volla Tablet - “mimir”

[Grouchox]

Hi. Since I can’t get into the old OS nor the new, this doesn’t work - or am I missing something?

On the plus side, I did manage to get into recovery mode, tried flashing the same eOS build again, but got the same result.

So what now? Should I try flashing the Volla OS instead? Or another build of OS? (That doesn’t seem helpful - it would be an older version, and if I understand correctly that means an older SPL date, which is exactly what I don’t want, correct?)

[piero]

@Grouchox

So what now?

reInstalling Fairphone OS Manually reinstalling the StockOS
as a sane base ?

[Grouchox]

But it’s not a fairphone?

[Grouchox]

It looks like Recovery mode is all I can do at this point. So what exactly can I sideload there? The same file that I use for flashing (in other words, the current version from /e/OS official mimir download )? Or is an “update” something else?

[piero]

@Grouchox

It looks like Recovery mode is all I can do at this point.

so you also can boot in bootloader mode ?

.

this recovery ?

[HOWTO] a Clear Guide to install "IMG-e-builds" when /e/ web installer fails

. in 3 copy / paste actions ! . because even well illustrated, the “web-installer” often don’t work, and because the install instructions provided by /e/ can be imbuvable for some new users. . . here we take the Fairphone 6 as example, but it is the same logical and quite the same process for all the devices that have : only "IMG-e-xxxxxxxxxxx.zip" file on their download page, no "recovery-e-xxxxxxxxxx.img" file on their download page, no "recovery-IMG-e-xxxxxxxxxx.zip" file on their d…

[HOWTO] Upgrade my /e/OS to major Android version without loosing /data

. the Universal Method détailled DO NOT APPLY FACTORY-RESET → do not format /data . Install the platform-tools on your computer : Install adb and fastboot on a computer running macOS or Linux Install adb and fastboot on a computer running Windows not a major issue if not properly "installed in your path” as explained above, but only downloaded and extracted, simply add ./ at the beginning of all your adb or fastboot commands, it will use the version included into the relative folder (the …

[HOWTO] an Unified Install Guide Project for /e/

. . Now the easiest part : install /e/ ! . 8) Install the image of /e/OS on the ROM of your device without computer, from the “custom recovery manager” using the SDcard or internal storage method (forked from @Anonyme) Now you’re in TWRP, congratulations, you’ve done the hardest part. using TWRP . using recovery-e . 9) Install the image of /e/OS on the rom of your device from your Computer using the ADB sideload method. . using TWRP . using recovery-e . Thanks for reading ! Sh…

[Grouchox]

No, booting into bootloader results in a boot loop. Yes, it that recovery, but V3.4.

Hm, I think I might have bricked the tablet by not paying attention to the SPL date. Will waiting for a new e/OS with a new SPL date and then applying that via sideload work?

[piero]

try that : Universal Method, download the file on a computer, boot the phone into the recovery mode and use “apply update” then “from ADB” :
using this file : e-3.4-a14-20260114569180-official-mimir.zip (not the IMG one)

[Grouchox]

Wow, that worked. Thanks a mil!

The only issue now is the “Code Orange”. Any chance I can get rid of that, too?

[piero]

did you relock the bootloader ?

[Grouchox]

No. I can’t get into fastboot either, just recovery. So from what I got from this thread, I guess that means I wait for the next update and then check again?

Bootloader lock

I tried, here’s what happens: $ fastboot flashing get_unlock_ability < waiting for any device > fastboot devices also does not return anything. adb devices shows my phone. I suppose the fastboot command needs to be executed from the bootloader, after “adb reboot bootloader” was executed?

[piero]

@Grouchox

No. I can’t get into fastboot either,

No,
you must be able to get the bootloader mode, if not, you could not get the followings modes, recovery and system.