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

[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

 

[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