[Apollo 136] stb stuck on the starting screen after reflash

[easymo3]

I have just tried to do a new reflash using the latest build from wos downloads build 136

It seemed to install ok, erased date ubifs upate etc, rebboted as would be normal.

The box is stuck at the starting screen, all I have on the tv is "Vu+ your smart linux tv player"

I re flashed it because I was having a few issues with it not responding to the remote well every time.

Anybody got any ideas on this issue please?

Many thanks.

[easymo3]

Sorry forgot to add.

I have no other usb installed, taken out the hdd and tried different usb sticks, all the same results.

[bbbuk]

I have the same problem with usb flash install of 135 or 136. Gets stuck on starting screen and nothing. Can't telnet in neither.

I tried redownloading several times and different usb stick. Same problem.

Then tried going back to 132 or a previous backup and it works fine.

I believe there has been an issue with the build of 135 and 136.

[easymo3]

thanks for that info mate, I will try an earlier build.

[joe2419]

Hi i to have the same problem have tried to reflash back to image 131 with the same results stuck on starting,that is on the solo2 original box,never had any trouble before any help would be grateful.:mad:

[bbbuk]

Hi i to have the same problem have tried to reflash back to image 131 with the same results stuck on starting,that is on the solo2 original box,never had any trouble before any help would be grateful.:mad:I managed to flash back to 132 which I already had previously downloaded and got it working again. I can also flash back to a previously saved backup without problem.

[nsw9154]

What was your last stable version of vix that you used as some of them (I can not remember the exact build number I think is was about 112) had a problem with the remotes not responding strait away and being sluggish

There where problems found with build's 135 and 136 Try Apollo 132 and see if that loads :)

you beat me to it bbbuk :D

[easymo3]

What was your last stable version of vix that you used as some of them (I can not remember the exact build number I think is was about 112) had a problem with the remotes not responding strait away and being sluggish

There where problems found with build's 135 and 136 Try Apollo 132 and see if that loads :)

you beat me to it bbbuk :D

I went back to build 108, that loaded fine, very happy now!

[stevesom]

Same here on a duo last night stuck on starting switched box on and off about 4 times until it came on, it crashed through the night so gone back to build 120 that was the last stable image I can remember for me.

[abu baniaz]

Can you try an update to 137 please?

[Spoof]

Latest in dowloads is 136 > that stuck me in "starting" so trying an older build now.

Spooooooooooooooo


Loaded 107 from USB stick > no problems

[bbbuk]

For those also having problems with builds 135/6, I've found an online update from 132 to 137 works fine.

[Spoof]

I too, had no probs. with an online update. Only a USB flash produced "starting".

[abu baniaz]

I too, had no probs. with an online update. Only a USB flash produced "starting".
Please clarify. Does a fresh flash of 137 cause an issue?

[bbbuk]

Can't do a fresh usb flash of 137 as it hasn't been uploaded to your FTP site yet.

I can confirm that fresh usb flash to 135/6 has problems.

But a fresh usb flash of 132 with an online update to 137 works fine.

[abu baniaz]

Can't do a fresh usb flash of 137 as it hasn't been uploaded to your FTP site yet.

:whistle::o Need tea.

[Spoof]

Please clarify. Does a fresh flash of 137 cause an issue?

I only found 136.

Answer was yes, for me.

[abu baniaz]

I only found 136.
Answer was yes, for me.
That is an incorrect answer. Please do not confuse issues. Whatever the problem was in 136, has been fixed in 137. to be identified

[Spoof]

That is an incorrect answer. Please do not confuse issues. Whatever the problem was in 136, has been fixed in 137.

I think you need more tea!
Answer was spot on > latest available build on VIX downloads is 136. That causes "starting".
No point talking of any other newer builds since they are not available on website.

[Larry-G]

I think you need more tea!
Answer was spot on > latest available build on VIX downloads is 136. That causes "starting".
No point talking of any other newer builds since they are not available on website.

As abu stated the issue was fixed with build 137 regardless of whether that build has been uploaded to the download site it is still available via the image online updates feature. menu> setup> software update. so either try build 137 or stop complaining.

[abu baniaz]

I asked if flashing 137 by USB caused an issue. That question was not applicable to you (or non-beta testers as it happens). Your answer is not spot on, it is misleading and incorrect and could have led to wasting valuable time tracing an issue that does not exist.

There is no need to respond.

[bbbuk]

I think this thread is getting out of hand :)

Abu asked, "Please clarify. Does a fresh flash of 137 cause an issue?"

Now as far as i'm aware, I personally see a usb flash as a fresh flash and NOT an online update. This is why I personally clarified that a fresh (usb) flash of 137 couldn't be done as not available yet but a fresh (usb) flash of builds 135/6 caused the starting issue but a online update from 132 to 137 is fine.

It looks like @Spoof also read "fresh flash" as being a usb flash hence why the reply was no because, at this moment, build 137 isn't available via your site.

I do agree it's getting all too confusing :confused:

[Spoof]

As abu stated the issue was fixed with build 137 regardless of whether that build has been uploaded to the download site it is still available via the image online updates feature. menu> setup> software update. so either try build 137 or stop complaining.

He asked me a question and I answered.
I am not complaining, I was trying to help.
I found (right or wrongly) his reply and your reaction borrdering on rude, so I will not bother in future.
I sincerely apologise that my attempts to help fell short.

Regards,
Spoooo

[Larry-G]

I'm busy rite now but in the next half hour or so ill flash my solo2 with build 137 and grab a log in the process.

Sent from my SM-G900F using Tapatalk

[duoduo]

Hi guys just to add my little bit, I updated to 136 this morning without any issues however got home this evening and using timeshift to pause and then play made the programmes jump and also the same issue with playing recordings. Just updated to 137 and everything seems stable again.

[abu baniaz]

Issue is with a fresh flash. Updating is fine.

Issue has been found and is being rectified.

[Spoof]

I asked if flashing 137 by USB caused an issue. That question was not applicable to you (or non-beta testers as it happens). Your answer is not spot on, it is misleading and incorrect and could have led to wasting valuable time tracing an issue that does not exist.

There is no need to respond.

Just for good order sake:
You ask me a direct question (you quoted my text) so I answered, so it DID apply to me. It was YOU who wasted time by asking me an incorrect and irrelevant question.

HTH
Spooooo

[abu baniaz]

As it happens, build 137 had an issue if flashed fresh. It had to be rebuilt to cure issue.

So question was relevant and appropriate. Just not to you.

Arguing with a mod is against the rules. I'm not in the habit of wanting to have the last word, but also cannot allow your behaviour to go unchecked.

[bbbuk]

I confirm that a fresh flash of build 137 works fine now on my solo2.

Thanks