Jump to content

Think i have killed it


Guest Flipper_Al

Recommended Posts

Guest Flipper_Al
My hudl2 is stuck trying to load the new OTA update
 
the update fails with see image
 
IMG_20150202_184632_zpscj43fqkq.jpg
 
So can i stop it trying to update.....?
 
Any other suggestions....
Link to comment
Share on other sites

Guest mrrog

I think this error is caused when the update does not find the precise apk it is expecting, have you rooted and deleted blinkbox?

I think you need to return to stock ROM and try again.

Link to comment
Share on other sites

Guest Flipper_Al

Yes rooted, and i expect i removed blinkbox..... :)

 

Is there a link to the stock ROM.....?

 

I have tried to run adb-windows reboot bootloader, but i just get device not found, im thinking usb debugging is not enabled

 

If i can stop the device trying to load the OTA, im sure i can get it back up and running

Edited by Flipper_Al
Link to comment
Share on other sites

Guest Flipper_Al

No it wont, data has been wiped, therefore it needs to connect to wifi, then by default, it checks for updates... which fails

 

If i can find a way of stopping it checking for updates, i think i can recover it :)

Link to comment
Share on other sites

Guest George Styles

No it wont, data has been wiped, therefore it needs to connect to wifi, then by default, it checks for updates... which fails

 

If i can find a way of stopping it checking for updates, i think i can recover it :)

Couldnt u just turn your wifi router off so it cant see the update server?

edit: my bad - can see from ss its got a cached local copy...

g

Edited by George Styles
Link to comment
Share on other sites

You could also flash one of the rooted images posted by Paul in the pinned thread - that would ensure your files are correct/ restored.

Just a thought, something I've had to do before (adjusted the build.prop etc).

Link to comment
Share on other sites

Guest Flipper_Al

Tried reflashing, but the device is not seen, i guess developer mode and usb debugging is not enabled  :(

 

:)

Edited by Flipper_Al
Link to comment
Share on other sites

Well I'm fairly sure in the (prob) rooting thread someone explained breaking out of the forced looking for updates during the inital setup process.

Edited by Guest
Link to comment
Share on other sites

Guest Sparkey159

I had that problem with my Hudl 2, There seems to be no way to fix it. Your best bet is to go to your local tesco and hope they will give you a new one. Lots of people have this problem (Even with unrooted devices). Tesco tech support online don't help at all, they will just tell you to do all the usual things...

Link to comment
Share on other sites

Will have a look :)

 

Here you go Flipper_Al, have a look at this post #396 by Normola, he's shown how to break out of the initial forced update at the end of the first time install.

 

Once you've broken out of the forced update screen and enabled developer mode etc etc, I'd flash the most relevant rooted image supplied by Paul in the 1st post of that thread. This way, you should end up rooted and have all the original files restored in the system partition.  :D

 

Sparkey159, these hudl2's are more fixable than people (including Tesco Support) think they are - obviously this relates to software issues only - hardware failures are hard faults.

 

:ninja:

Link to comment
Share on other sites

Guest Flipper_Al

BOOM..... she lives again :) :) :) :)

 

What a cracking little "hack" to get back into it 

 

Many thanks to all those who took the time to post/help 

 

ATB

Flip :) 

Link to comment
Share on other sites

  • 3 months later...
Guest Archie  Godfrey

I uninstalled the keyboard prior to this happening to me. I don't think even Normola's thread can help me now!

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.