Volla Installation guide

Hardware Adaptation
#51

Volla flash bircked it, cause I needed Android 11 to reflash sailfish. I had a broken display, send it to repair it and it came back with Android 12.

#52

Version Nr.? 5.xx xx xx

#53

probably 5.1924 ā€¦ I used 5.1916 for linux which worked fine (but not on a Volla22/GS5 but on a GS290)

#54

Thanks so far for all your help. Iā€™ll send it back in to pro repair. Must be a hardware defect. Iā€™m flashing since 2012 and never had so much trouble. Letā€™s see. But then I get it back with Android 12 again, I need a new method to flash sailfish. Otherwise new rephone are not flashebal with sailfish. The rephone is worth it to be supported for a longer time, would be nice and sustainable. Good thing that I have 2 working nicely.

1 Like
#55

My new Rephone is on Android 12 i have installed a GSI Image
https://github.com/MisterZtr/RisingOS_gsi/releases

works perfect

1 Like
#56

With the Gigaset GX4 (not PRO), de-bricking worked with SPFlashToolV6 only to restore the bootloader. Afterwards, flashing different operating systems worked without problems. It is further described here: https://forum.sailfishos.org/t/the-volla-x23-gx4-thread/15726/91

Thank you for your stories. They helped a lot. :slight_smile:

3 Likes
#57

Hello,

I am trying to follow the steps, but I get the following error:

product: k69v1_64_k419
Sending ā€˜boot_aā€™ (32768 KB) OKAY [ 1.401s]
Writing ā€˜boot_aā€™ OKAY [ 0.578s]
Finished. Total time: 2.080s
terminate called after throwing an instance of ā€˜std::out_of_rangeā€™
what(): basic_string::compare: __pos (which is 496) > this->size() (which is 0)
./flash.sh: lĆ­nea 38: 1367 Abortado (`coreā€™ generado) fastboot flash super super.img
flash super error

I have VollaOS 12-20240202 installed.

thank you very much

#58

hmm i have the dark feeling that i did experience that one too, but it is years ago, if at all
are you running the script on linux, windows, mac ?

search in the forum for:
basic_string::compare: __pos

and you will find some hits for other volla or gigaset devices, as the porter and the scripts are very similar, they may help you

2 Likes
#59

Which device was that? GS5 ?

Did you wipe the user data and cache partitions (in recovery)?

1 Like
#60

Iā€™m using Fedora, I will follow your search instructionsā€¦

Thank you very much!

#61

yes, GS5

I have deleted everythingā€¦

Thank you very much!

#62

If I recall correctly, I had the same or a similar problem. Check your platform-tools / fastboot version. I have fastboot version 33.0.3-8952118 installed myself while my package mananger has installed fastboot version 34.0.4-android-tools.

Might be a bug in the more recent version.

Good luck

1 Like
#63

was already weighing that probability.

I think thatā€™s the problemā€¦

thank you very much

#65

Hello,

I am trying to install waydroid by following GitHub - sailfishos-open/waydroid: Waydroid packaging for Sailfish OS but I have not been able to get it to work.

Is it possible to get it working?

I install the packages following another thread where they indicate to do it through Chum.

#66

@jmdlpino I can provide what I did successfully on my Volla:

You have to install packages from Chum - waydroid and waydroid-runner.

Then install from terminal -
$ devel-su
# zypper in waydroid-gbinder-config-hybris

Then as devel-su:
# vi /etc/gbinder.d/anbox-hybris.conf

Change aidl2 to aidl3, (appears 4 times in the file)

Save file.

# waydroid init

edit /etc/dnsmasq.conf to uncomment the following line (Volla, 4.4.0.72: line 124):
#bind-interfaces
# vi /etc/dnsmasq.conf

systemctl disable --now dnsmasq

Then reboot and start waydroid

Many thanks to @Sheigorath , who gaves me this hint long time ago.

And: NEVER update Waydroid if it reports an available OTA update. This may work a few times, but sooner or later it will break the system and even if it works it brings nothing.

1 Like
#67

Exactly, stick with a working image

1 Like
#68

Sorry,

I had high hopes with your instructions, because I was missing the step of modifying the /etc/dnsmasq.conf file.

I thought the problem was there.

But when I run it, it stays on the ā€œStarting Android session/Waiting for Android UIā€ screen.

I have to clarify that Iā€™m running SailfishOS from Boot Managerā€¦

Thank you very much for your help.

#69

When i had your issue, i had to use an older image. If you search my posts, you might find the description. Usually i do note evrything down.

The thing is: based on installation time you might endup with different image, some work, some not. At least my experience

1 Like
#70

It is in gs290 installation thread

check my posts, somewhere i had issues with space then image

1 Like
#72

I am using 4.4.0.72

you mean using older versions?

Thank you.