Volla phone in bootloop

Devices
#7

Full agree! (20 charakters)

#8

so finally had to buy another gs290. first attempt to install sfos failed already. (i did use the old 4.2 image and during update to 4.3 lost calls) may use the other one as spare part device.

is there a way to reflesh a volla phone using the script after sfos was installed ?
currently i always have to reflash it with flash-tool with gigaset image, then volla os then sfos, that is a little inconvinient.

1 Like
#9

i am now on the gs290 on 4.3.0.15. and have now the same waydroid behaviour: stuck with circle on start. did you ever found any solution for that problem ?

#10

I have to admit that I’ve always done either:
ubports installer (if I wanted to get the ‘correct’ android base installed) or
piggz script in the downloads from his CI (if reflashing with a correct android 10).

This has never failed (except once when I had ubuntu installed and forgot to install the android base).

#11

my problem is: once i have sfos installed, ubports nor e-installer will recognize my device thus no reflash
how do you bring your phone to fastboot / bootloader with sfos ? in my case it fails

#12

I just boot with volume up, select fastboot, (phone plugged into laptop, usb 2 port) and run the script from piggz ci generated archive. I’m running ubuntu 20 and 22.

What do you mean, it fails? Either you get to the menu and can select fastboot or not?

#13

Huh. Just to see if I’m blowing smoke, I tried it and now I can’t boot to fastboot :slight_smile: vol+ doesn’t work and vol- doesn’t either. I’ll try with the ubports installer

#14

Ah, I was in the wrong usb port (3-1). Ran ./flash-volla.sh, stuck the cable in the correct USB port, depressed Vol+ and power and bingo.

EDIT: damn and I just re-flashed :slight_smile: Ah, what the hell. It’s dev device 2.

#15

the menu pops up for a second and moves on to normal start

#16

sorry for that.
setup of a phone will all always takes ages …

this time i was able to get up whisperfish running with mybackup at least

#17

That’s good to know. I need to make myself tickets to implement that in all the apps.

Just to re-iterate what seems to ‘always work’:

  1. Shut down phone from SFOS
  2. attach to USB2 port
  3. run flash-vola (fastboot flash …) or ubports installer
  4. start with Vol+ and power depressed.

Correct?

1 Like
#18

Not for me, but might be a cable, port issue too.

allways for me is: flashtool for android :\

#19

Ah, but it’s interesting if the port usb standard, for instance, is irrelevant depending on the tool. ah, well.

#20

maybe different drivers ?

i was not able to connect flashtool on linux laptop, or to get the drivers …
so the flashing rom i did on windows pc, with drivers and flashtool

ubport installer and sfos script i did on linux laptop

but now that we are chating … waydroid starts but says forever: waiting for android ui
any idea how to re-install it ?
re-init -f does not much

#21

sadly I have zero knowledge of waydroid. @Seven.of.nine , didn’t you manage to get waydroid going on the volla?

#22

@poetaster Yes, in the end it was easy, but in beginning I had to try long time to find the right solution with the help of the community. I’ll explain later when back on computer, i’m on my way now…

edit:

I installed waydroid runner fron chum, then ran waydroid-init in CLI, then installed Waydroid Runner and (IMPORTANT) deinstalled dnsmasq, see

Waydroid in Chum-AppStore doesn´t start Session

post #6

See also this thread

WayDroid on SFOS?

I hope this is helpful for you.

1 Like
#23

This is different, i hang in waiting for ui
dnsmasq need to be disabled, that is true
i will checkout the waydroid thread

on what sfos version did you install waydroid ?
4.3 or higher ?

#24

edit: (understandable + in the right order)

  1. flashed 4.3.0.15 with UBPorts installer
  2. updated SFOS on the Volla step by step to 4.4.0.64 (4.4.0.68 didn’t work on Volla, going back to …64 with luck succeeded)
  3. I installed Waydroid on 4.4.0.64, don’t forget to init it. The init downloaded abt. 680 MB or so.
  4. installed MicroG and the app-stores and apps.

edit: Sometimes (very rare) this stucking on ‘waiting for UI’ happens also to me, and I have no idea why and can’t see any coincidences to some situations on the phone.
If this stucking happens, I have to close the Waydroid and start it again a few seconds later. This case I’m always careful to give the phone time to finish it’s background processes, because I know that SFOS sometimes is a little bit slow.
Starting Waydroid sometimes needs more, sometimes fewer time. After the UI has launched, the balls from right to left go slower or faster, always different, depending on the system status, the weather, the stars and the moon. I don’t know, but mostly it works.

edit: For every flashing on Xperia 10 and Volla i always use an USB 2 hub, because there are some known bugs in the USB firmware. Don’t know exactly what it is, but a lot of people here experienced this and also me. And, with USB 2.0 hub it works and with USB 3 not.

1 Like
#25

thanks for that detailed info, that only means that i do stuck in some other detail issues.
on my last gs290 i did install waydroid on 4.3.0.15, checked that it worked and then did all the updates till 4.4.0.58

with that replacement phone i did update till 4.4.0.58 to see that my sim card works which it did not on first installation, and now i can get waydroid up …

hmm
thanks anyway !

1 Like
#26

The broken phone, after two weeks stopped to reboot and seems to work again ?!
might have.been water.or somethng ?
who knows.

so closing this topic.
regarding waydroid: installed it again on the now working device, freshly fleshed, updated till 4.4.0.64, the installed waydroid, disabled dnsmasq but hangs in waiting for android ui, same as the other phone

thanks