Chinese tablet keep random rebooting? Trojan cause?

[Mattypompy]

Oh dear!

I have a trojan embedded in the system files of the elecost q10.1 tab and am suffering random reboots. I cannot remove it and think I have to un-root and manually remove or flash a new rom?

I ran Stubborn Trojan Killer and Malwarebytes and yes I have a trojan, Android/Trojan.Dapper.Agent.Apw in the googlesync system file. The device is un-rooted. I have disabled Googlesync app.

My questions really are,
A) Is this the cause of the above instability?
B) How do I remove it? Is it a case of rooting/renaming file? Apparently someone else removed it and it bricked the device.
Or can I just install a new ROM?

Any pointers, even to best rooting method, would be really appreciated!


I'm trying to put up a comprehensive post but keep getting exceed spam threshold error!

Kernel 3.18.22 zhengqf@roco-mtk-svr3#4
Build num: c805mo-v11bsfm16gn16GEN-01.1682
Cstom Build: roco-2017/03/15

 

[Golfdriver97]

Or can I just install a new ROM?

Welcome to the forums. Reflashing the ROM should work. The caveat is are the files available?

You shouldn't need to unroot. You can reflash the ROMs with fastboot commands. You may have to unlock the bootloader, and that will wipe the device.

 

[Mattypompy]

Welcome to the forums. Reflashing the ROM should work. The caveat is are the files available?

You shouldn't need to unroot. You can reflash the ROMs with fastboot commands. You may have to unlock the bootloader, and that will wipe the device.

Thanks for the reply.

I was thinking of unrooting to maybe remove manually the trojan but I would invalidate the warranty and risk bricking!?

I'm correct in saying a ROM is completely device specific isn't it? Doubt there's one around for this device. It's on Marshmallow which is quite old! I couldn't shoehorn a generic image could I?

 

[Rukbat]

1. Unrooting wouldn't invalidate the warranty, rooting might.

2. The ROM (bad name for it, since ROM actually refers to hardware) is very hardware specific - even a different model number of the same device usually uses a different ROM.

3. You could use a generic Nougat, or even Oreo, ROM - if you could write the device-specific part of it. The generic ones that come from Google are for the current Google phone.

 

[Golfdriver97]

Thanks for the reply.

I was thinking of unrooting to maybe remove manually the trojan but I would invalidate the warranty and risk bricking!?

I'm correct in saying a ROM is completely device specific isn't it? Doubt there's one around for this device. It's on Marshmallow which is quite old! I couldn't shoehorn a generic image could I?

You should, in theory, have better luck removing the Trojan with root access. But reflashing the ROM will effectively do the same thing.

 

[Mattypompy]

Thanks for the reply.

I was thinking of unrooting to maybe remove manually the trojan but I would invalidate the warranty and risk bricking!?

I'm correct in saying a ROM is completely device specific isn't it? Doubt there's one around for this device. It's on Marshmallow which is quite old! I couldn't shoehorn a generic image could I?

My bad. I meant rooting lol

 

[Mattypompy]

1. Unrooting wouldn't invalidate the warranty, rooting might.

2. The ROM (bad name for it, since ROM actually refers to hardware) is very hardware specific - even a different model number of the same device usually uses a different ROM.

3. You could use a generic Nougat, or even Oreo, ROM - if you could write the device-specific part of it. The generic ones that come from Google are for the current Google phone.

Thank you for the information.

I'm thinking of returning it and getting a different model from the supplier? They said don't root it or the warranty will be invalidated. I'm not even certain that it's an Android issue as they claim the trojan is a defunkt file and not active malware.

Yes I thought each version of Android may be device specific. Thanks for confirming. I may search for any release that may be available online. I'm not even sure that updating the FW will cure it. Just strange that this issue is following me from different units they have supplied. Probably hardware instability and poor component quality?

Thanks again

 

[Golfdriver97]

Thank you for the information.

I'm thinking of returning it and getting a different model from the supplier? They said don't root it or the warranty will be invalidated. I'm not even certain that it's an Android issue as they claim the trojan is a defunkt file and not active malware.

Yes I thought each version of Android may be device specific. Thanks for confirming. I may search for any release that may be available online. I'm not even sure that updating the FW will cure it. Just strange that this issue is following me from different units they have supplied. Probably hardware instability and poor component quality?

Thanks again

If you are still within your return period, you may want to consider it. This could be anything, from a trojan (which in theory is difficult to apply to Android devices), to like you said; bad hardware.

 

[Mattypompy]

If you are still within your return period, you may want to consider it. This could be anything, from a trojan (which in theory is difficult to apply to Android devices), to like you said; bad hardware.

Thanks buddy!

 

[Golfdriver97]

Thanks buddy!

I can try to help you reflash the stock ROM, depending if the files are up for download. It's a lot of prep work if you can find them.

 

[Mattypompy]

I can try to help you reflash the stock ROM, depending if the files are up for download. It's a lot of prep work if you can find them.

That's very kind of you! I'm going to see what the supplier offers first. Then I may see if the appropriate ROM is available. I may be back in touch!