Is my Hudl 2 bricked? Boot/update loop

[Guest Minnericht]

Hey guys so I've searched for a while and haven't found any solutions to this problem I am having. 

 

My Hudl 2 was rooted, and like everybody else I had the start show up in the notifications bar to update, but I decided to leave it as every time I did, my hudl would crash into an error stating update.zip failed with status one.

Eventually I decided it was time to update so I downloaded the update, restarted and of course - it crashed - so i selected factory reset hoping it would fix my problem, and instead it made it worse, as now whenever I boot up, my Hudl goes through its initial start-up procedure, and asks if i want to install the update with no bypass.

This means that if I do update, the Hudl crashes, and I'm sent into an endless loop, I've tried wiping the cache, factory resetting multiple times, my device cannot be found by adb and I'm clueless as to what options i have left. Is it bricked?

 

Thanks for reading and for any help that may come of this.

[Guest]

http://www.modaco.com/topic/374615-think-i-have-killed-it/?view=getnewpost

Read that and walk towards the light. The issue is slightly different but the solution is the same.

[Guest Minnericht]

http://www.modaco.com/topic/374615-think-i-have-killed-it/?view=getnewpost

Read that and walk towards the light. The issue is slightly different but the solution is the same.

That helped a lot, thank you, however now when I have tried to follow the root guide, while in the bootloader i get this:

 

E:installer device ignored

FASTBOOT INIT....

E:installer device ignored

FASTBOOT CMD WAITING...

E:installer device ignored

E:No valid installer medium found

 

and my cmd window shows <waiting for device> indefinitely, Ive also searched around this problem with no success .

[Guest]

I'd 'suggest' you probably haven't got both sets of drivers loaded correctly look at post #388 (I think). In the pinned rooting thread.

Edited March 5, 2015 by Guest

[Guest Flipper_Al]

I had the same issue, 

 

I closed the cmd window opened it again with run as administrator, and it found the device

 

:)

[Guest]

Sorry, I take it for granted that when doing stuff like this on Windows you would do it with Administrator privileges and when doing this on Linux you would as sudo or with SU privileges.