Problem with Qviart dual

[cokeaddict]

The two names is RomUpdate and RomUpdate.bin and without bin

Are you 100% sure, the RomUpdate.bin is the Qviart 5.0.0 and not 1.0.7 ?

 

[doctor no]

5.0.0 not 1.0.7

 

[cokeaddict]

I don't know what else to suggest, other than another usb stick.

 

[kegnkiwi]

When I first tried the update process, the usb did not work correctly. I looked like it started flashing but only tried for a couple of minutes then it rebooted to the previous image. I formatted a better usb stick and then it worked. Takes about 10-15 mins.
Are you updating via the turn off procedure and turn on holding the power button?

 

[doctor no]

yes exactly and I updated before 1.0.7 inside the andriode 1.0.6 from update usb and worked and accepted the firmware on the usb without existing folder named RomUpdate

 

[doctor no]

I think an android recovery software should be exist and to be access from recovery menu , this will end the suffering of the user to download firmware after boot loop problem.

 

[cokeaddict]

I think an android recovery software should be exist and to be access from recovery menu , this will end the suffering of the user to download firmware after boot loop problem.

To be fair, the 1.0.7 update is meant to have fixed any bootloops due to software issues.

So maybe you have been unlucky and have a hardware issue that is causing the bootloop.

However maybe start again, first with a low level format tool, to format the usb fat32 again.

Then re-download the qviart 5.0.0 incase the one you have is corrupted.

Then rename the file making 100% certain it's called RomUpdate.bin and not RomUpdate.bin.bin etc etc.

 

[doctor no]

To be fair, the 1.0.7 update is meant to have fixed any bootloops due to software issues.

So maybe you have been unlucky and have a hardware issue that is causing the bootloop.

However maybe start again, first with a low level format tool, to format the usb fat32 again.

Then re-download the qviart 5.0.0 incase the one you have is corrupted.

Then rename the file making 100% certain it's called RomUpdate.bin and not RomUpdate.bin.bin etc etc.

Thanks but I am not the only one have this problem there are another two users ( this is what I know )have the same problem, any way I will get another flash usb tomorrow 8gb hoping it will help.

 

[kegnkiwi]

Just one other once you are sure you have the android file name RomUpdate.bin inside the folder called the same without the .bin you are trying the update via turning the receiver off and then keep your finger on the power button whilst you turn it on? The screen should start scrolling through update, and e2 update and one other. Release your finger and then press it again until you see the update on the lcd screen. Leave it on that and it should automatically start the update.

 

[doctor no]

Just one other once you are sure you have the android file name RomUpdate.bin inside the folder called the same without the .bin you are trying the update via turning the receiver off and then keep your finger on the power button whilst you turn it on? The screen should start scrolling through update, and e2 update and one other. Release your finger and then press it again until you see the update on the lcd screen. Leave it on that and it should automatically start the update.

Ok I will do that with the new usb flash and I will inform you with the result.

BR

 

[doctor no]

Finally I succeeded to download the firmware I insirst on usb flash in the front drive and another one in the back having the same firmware without .bin
and its ok now,
now firmware 1.04 called ( cw special ) ?

 

[kegnkiwi]

Finally I succeeded to download the firmware I insirst on usb flash in the front drive and another one in the back having the same firmware without .bin
and its ok now,
now firmware 1.04 called ( cw special ) ?

Factory reset after each install, then 1.04 special, then 1.06 factory reset again, and then 1.07 and factory reset.
It might be that you don't need to do 1.06 but just to make sure do it.

 

[cokeaddict]

Factory reset after each install, then 1.04 special, then 1.06 factory reset again, and then 1.07 and factory reset.
It might be that you don't need to do 1.06 but just to make sure do it.

I think you should be able to go from 1.04 to 1.07 direct, without having to install 1.06.

Also the factory reset after each update isn't really needed, 5.00, then 1.04 then 1.07 then factory reset should be fine.

 

[doctor no]

Factory reset after each install, then 1.04 special, then 1.06 factory reset again, and then 1.07 and factory reset.
It might be that you don't need to do 1.06 but just to make sure do it.

I downloaded 1.04 but it called cw spesial its ok ?

 

[cokeaddict]

I downloaded 1.04 but it called cw spesial its ok ?

Yes if it's called special, then it is the one you need

 

[Ferret]

I downloaded 1.04 but it called cw spesial its ok ?

104 Speacial these days its just called special

618.25 MB file on MEGA

mega.nz

 

[doctor no]

Yes if it's called special, then it is the one you need

Done thanks for all your help was appreciated for me.

BR

 

[doctor no]

Unfortunately I switched to Enigma2 and when I go back to android I go back to square zero boot and restart.
This is not happen with 1.06. I am tired and upset

 

[kegnkiwi]

Unfortunately I switched to Enigma2 and when I go back to android I go back to square zero boot and restart.
This is not happen with 1.06. I am tired and upset

I wonder if it is worth resetting the e2 side before going through the process with the android site again. I've had some bad drivers or something that corrupted my colours on both the android side and E2. It's similar to what you did with the android side but just choose an E2 recovery image such as openatv 7.2 or 7.3 extract it so the folder says dual and put it on the usb stick. Turn the box off and turn on and keep your finger on the button. When it starts to scroll remove your finger and select E2update. Leave it a moment and it will reflash slot one with the recovery image. It will also wipe the other slots.

 

[doctor no]

I finshed installing androide side and it was working fine so I go back to e2 to be sure its working fine and I downloaded the backup images I did them before updating the androide side and everything was ok so I go back to android to be sure the problem will not comes back and it comes unfortunately
and now the deco do not detect the usb flash again .
Corrupted colours was happened with me when I downloaded database channels to the androide and its cleared after I deleted it.