How to completely factory erase a Hudl v1?

poppellerant

I factory reset the device then created and used another another email address and still get the same problems.

pappa_golf

then it is not a virus on google apps , the "virus" must be on the recovery section


however , you commented that it restored quickly , have you cleared the cashe and followed the instructions correctly


more and more dribs of info are being added later and later in this thread , therefore I will leave you to play 20 questions , and might have a look at the FULL situation in a few days time

psychic_teabag

If it's been rooted, is there an app that allows control which apps have permission ? Can you withdraw permission from any apps that have been granted permanent permission ?

[Deleted User]

HappySeagull wrote: »

How do you do that? I'd love to get rid of the bloatware on my Hudl v1.

Not sure about the Hudl 1, but here's the guide to doing it on the Hudl 2. I can't imagine it's all that much different.

http://www.jdgleaver.co.uk/blog/2014/11/05/the_hudl_2_tips_and_tweaks_and_gaming.html

ETA: Will this be of use to you, OP?

http://ttselectrical.custhelp.com/app/answers/detail/a_id/3569/~/performing-a-hardware-factory-restore-on-your-hudl

poppellerant

As I said in my first post, I have also cleared the cache. I then saw a screen that shows it's erasing data for about 5 seconds - it is this screen that appeared to be too quick to be true.

I'm not sure that the device has been rooted, nor can I see any apps to control permissions for apps.

onzey

Do you think encryption followed by a factory reset might help and then create a new account

https://www.tescotechsupport.com/feature/how-to-really-wipe-an-android-phone-or-tablet/

Leo2020

Did AVG/Malwarebytes give a name for the offending Adware? If you Google how to remove it you might find instructions.

psychic_teabag

poppellerant wrote: »

I'm not sure that the device has been rooted, nor can I see any apps to control permissions for apps.

At the end of your first post you said you didn't want the device unrooted. I took that to mean it is currently rooted and you wanted to keep that. Perhaps you meant you didn't want it rooted.

But I guess if you've done a factory reset, the control app would have been removed anyway.

You could attack this at a lower level, attaching to a pc with usb and then using 'adb' on the host to get a linux shell on the device and look at what's running. Perhaps just post a list and let someone look for things out of place. (Bit alarming how many processes running on my hudl for apps that aren't supposed to be running - like on windows, lots of apps start them selves up at boot time. I seem to have amazon and iplayer all running as proceses, yet not mentioned in the list of apps the gui admits to.)

poppellerant

Thanks for replying, psychic teabag. To my knowledge reflashing the Hudl leaves it rooted and I don't want it to be rooted. As far as I know the device isn't currently rooted, but something has definitely infected the recovery image.

If I knew how to reflash the device with an offical, unrooted image I would choose this as it seems it's going to be less stressful. But I don't know where to get the image, how to flash the image and whether or not it will be rooted.

psychic_teabag

The forum at http://www.modaco.com/forums/forum/747-tesco-hudl/ seems to include some stock images. No idea how reliable that is, though. Could perhaps ask on there (or some other android specialist forum) for suggestions.

I wonder if you can fiddle with the properties and so make the hudl think it's running an older version, and hence decide that it needs to update itself ? Might need root to fiddle with the properties, though.

IIRC there are two aspects to rooting : one is to unlock the bootloader, which allows you to put on custom recovery images etc, and then a separate step to actually root android or put on a custom rom image. If you suspect a virus in the recovery area, maybe it's enough to change the recovery image. That said, I wasn't aware that the recovery image was involved during standard booting - I assumed it was only used if you asked the bootloader to load it as an alternative to the normal image (to update the main image, for example).

(I've not looked at any of this on my hudl 1 - I have rooted my ancient android phone, but it turned out that the bootloader had already been unlocked and so it wasn't much hassle.)