You can simply try to use the recovery mode to flash to another firmware. This is unfortunately the only way to recover the unit - if it doesn't work you, you will need to bring it back to your vendor. As you notice this is not normal behavior - sorry for the inconveniences for the time being.


br,

Same problem

Veolo stuck @ AC Ryan Logo and nothing is happening anymore .

Reflashing it in recovery mode with the same firmware version 932 did not help at all.

Flashing it with V.849 did finally make it work again.

Even upgrading to V.932 afterwards did work just fine.

However, this should not happen and i wonder how many user run into such a problem.

I am really hoping for Android V 2.3.xxxx


-A

hi,


please read the 2 posts above. We advised you to try 'another' version not the same. You can try for example r849 to revive it. Please also note that this happens to very few users and might also come down to some app incompatibility (previously installed etc.), rooting problems and so on.

Let us know if something doesn't work still.

best regards,

If you tun into such troubles again i would suggest you to return the unit to your vendor for a switch just as mentioned in the initial post. It is not normal behavior that this happens and you should save yourself the troubles.

Hope it works now as you wish & best regards,

So,

my Veolo just stopped working the SECOND time and got stuck while restarting at this "AC Ryan Logo" and does not work anymore.

I am now "officially irritated" ....grumpppfff !!!

Of course reflashing it with an older version 849 and then upgrading back to 932 made the unit work again.

But i am really far from calling this my regular "modus operandi" to use this box

However, when it failed the procedure had been pretty much the same- like the first time.

Using the video player and watching 5 or more episodes of a season of "something".
The videoplayer with firmware 932 seems to support to jump to the next episode automatically when the latter one is over , which is convient cos the 849 version didn`t do this .

BUT... switching the player off or restarting it after this- both times- the veolo got stuck at the "ac ryan logo" and didn`t work no mo !

Since the box doesn´t get stuck, when i do not use it as a video player , my guess iss there is something buggy with the player or there is a thermal issue with long movie play sessions ???

I am wondering if this failure is happening with firmware >849 or also with the V849 ???????

At this point i would appreciate some professional help ....!

Akbahz

Hi akbahz, sorry for any inconvenience. Did you try to stop first the video playback before you shut down the set? You can try to install some task manager app like "ES task Manager" this will help to clear memory and cache, so that the device will have faster response specially when rebooting.

If in case your set does always hang then I suggest to contact your vendor for you to know how to get replacement just like Arne mentioned above.

Yes i did stop the videoplayer before shutting down the device.

The device had been shut down for a day and when i restarted it hung up (the second time) at the AC Ryan Logo.

I can install the "ES task Manager" and clear the memory but up till now i fail to see the purpose.
When i (successfully) restart the device the memory seems to be free ....(or at it´s max)

If the device will freeze up a third time i will go back to V.849 and see if i run into the same problem.

I am still thinking that V.932 might have a little hidden bug, hidden because it did only occur after using the videoplayer

Of course i could send the device in for a replacement, but i do not believe in a hardware bug ......yet

Sorry for any inconvenience. Please do contact your vendor or any of our Service Centers in case you still having the same problem with the set. But I really suggest that you have the unit replace first, we will be glad to help you replace it.

Hi,

I'm experiencing the same issue. Yesterday I discovered my Veolo was stuck booting at the AC Ryan bootscreen. No way it could be revived by turning off and on again. Also tried to flash it with the current FW version 923. Close, but no sigar, still stuck at the bootscreen, downloaded the 849 FW version. Tried to flash it with that FW twice, still no luck, will try later on with 627 FW. But my fear is that this will not work either.

How can it be a hardware issue when this specific showstopper only occurs with the updated firmwares? Come on guys put away the porkies. Just at least blame this version of Android if it is indeed so hopelessly un-selfhealing, otherwise it's clear to any software engineer like myself that you have QA issues.