Jump to content

Update boot loop


Guest divvykev
 Share

Recommended Posts

Guest divvykev

Wow. Been trying to fix this for two days now and getting ready to use it as a doorstop!!!!!

 

I know it has been mentioned a few times in few different threads but whatever I try I just cannot get past that update page. 

 

Here is what happenned and what I tried.

 

1. My Hudl was rooted using the newest method and working fine.

2. Fell asleep watching Netflix and woke up and saw the little star so without thinking started the update process. (Lesson learnt on that one!!!!)

3. Update failed with the Update.zip Error 7 and the Status error 1 message.

4. Factory reset and tried again. No deal

5. Manage to get into the settings using the nifty keyboard route and saw SuperSU still there so uninstalled that from the apps settings. Hopes go up thinking "Must be because of that". Same problem.

6. Tried resetting from settings - No joy

7. Sulked and walked away from it.

8. Flashed PaulOBrien's image and again wouldnt let me past the update page.

9. Tried without wifi. "Check wifi" comes up and cant get past the update page.

10. Reset that image file in every way I could think of and keep ending in the same green page knowing whats coming up.

 

Only really use the tablet for netflix when in bath/bed but am totally miffed that it is unusable purely because of some damn update.

 

Any help gratefully received. It's probably one little thing that I am not doing or am doing and that's the damn infuriating bit. 

 

Kev

Link to comment
Share on other sites

Guest divvykev

Hah. Classic quote from a Tesco tech fella. 

 

"Well it shouldn't do that so it must be broken"

 

"How did it break?" I asked

 

"Well sometimes when you stick the cable in a bit too roughly it can break the tablet".

 

I looked open mouth and walked away from him before I said anything which could have got me into trouble.

Link to comment
Share on other sites

Guest Archie  Godfrey

Same problem here. Read something about using the keyboard to do something or other but guess what, I uninstalled the keyboard after rooting!

Link to comment
Share on other sites

Guest alfiedoghudl

Hi just an update based/ on my own experience .... when you purchase a hudl2 it has an older version of the googe keyboard installed so you can take a BRAND NEW HUDL and use the keyboard trick to get into settings and then activate developer mode and hence enable usb debugging and from there you can root the hudl2 by loading one of Pauls ready to go rooted roms......

or you take a brand new hudl .... let it get OTA updates and root it using the latest tools listed on this site.....

OK so you now have a rooted hudl .....as we cannot predict what the next OTA update will contain ...the following should be considered

IF YOU REMOVED OR CHANGE OR MOVE THE CONTENTS OF THE ROOT SYSTEM IN ANY WAY you could end up with a boot loop problem as any OTA download could fail as it may expect a file to be present that you have changed.....

So if you root a hudl2 then move /system/app/otaclient.apk and otaclient.odex to a place where they won't be found for example move them to a new directory /system/moved which you could create ...

This will prevent OTA updates from downloading and from failing if you use root to change the system directory contents ....also if you do a restore to factory default ..the lack of otaclient makes the tablet not download an OTA update as part of its first run install.

If you are in the OTA download and it fails bootloop and the newer keyboard is installed and you have lost USB debugging mode ...you are stuffed .... Take it back to tesco or buy a screen broken hudl2 off a well known auction site and change the main board over

Hope this sets the record straight

Link to comment
Share on other sites

Guest alfiedoghudl

Just to add to this ...DONT DO A FACTORY RESET ON A ROOTED HUDL2 AS YOU LOOSE USB DEBUGGING SO COULD END UP IN A BOOT LOOP WITH OTA FAILURE AND NO WAY TO ENABLE USB DEBUGGING AS THE NEWER KEYBOARD FROM GOOGLE DOESNT ALLOW YOU TO GET TO SETTINGS AND RE ENABLE USB DEBUG

SO DONT DO FACTORY RESET ON A CHANGED ROOTED HUDL2 UNLESS YOU HAVE MOVED THE OTACLIENT FILES !!!!!

Link to comment
Share on other sites

Guest vampirefo

Just to add to this ...DONT DO A FACTORY RESET ON A ROOTED HUDL2 AS YOU LOOSE USB DEBUGGING SO COULD END UP IN A BOOT LOOP WITH OTA FAILURE AND NO WAY TO ENABLE USB DEBUGGING AS THE NEWER KEYBOARD FROM GOOGLE DOESNT ALLOW YOU TO GET TO SETTINGS AND RE ENABLE USB DEBUG

SO DONT DO FACTORY RESET ON A CHANGED ROOTED HUDL2 UNLESS YOU HAVE MOVED THE OTACLIENT FILES !!!!!

What does the keyboard have to do with settings?
Link to comment
Share on other sites

Guest divvykev

So if you root a hudl2 then move /system/app/otaclient.apk and otaclient.odex to a place where they won't be found for example move them to a new directory /system/moved which you could create ...

This will prevent OTA updates from downloading and from failing if you use root to change the system directory contents ....also if you do a restore to factory default ..the lack of otaclient makes the tablet not download an OTA update as part of its first run install.

 

Thanks for this. 

 

Just to make sure I dont make things worse, would the adb command be mv /system/app/otaclient.apk  /system/moved

 

Command line stuff a bit rusty

Link to comment
Share on other sites

Guest vampirefo

Thanks for this.

Just to make sure I dont make things worse, would the adb command be mv /system/app/otaclient.apk /system/moved

Command line stuff a bit rusty

Just use a rooted file explorer and add .bak to the end of the files and save.

When you want to use then in the future remove the .bak from files and they are ready to work again.

Link to comment
Share on other sites

Guest divvykev

Just use a rooted file explorer and add .bak to the end of the files and save.

When you want to use then in the future remove the .bak from files and they are ready to work again.

Getting a bit confused here. How can I use a file explorer when I cant boot further than the settings using the keyboard test?

 

Like the idea of chaning the names. a bit easier than moving (and easier to remember) 

 

Thanks

Link to comment
Share on other sites

Guest vampirefo

Getting a bit confused here. How can I use a file explorer when I cant boot further than the settings using the keyboard test?

 

Like the idea of chaning the names. a bit easier than moving (and easier to remember) 

 

Thanks

I posted what you should have done the second after you rooted, stop all OTA until your tablet is ready for update.

 

Anyway same thing can be done via adb assuming you installed busybox.

 

adb shell

 

mount -o rw,remount /system

 

busybox mv /system/app/otaclient.apk /system/app/otaclient.apk.bak

 

busybox mv  /system/app/otaclient.odex /system/app/otaclient.odex.bak

 

 

without busybox

 

 mv /system/app/otaclient.apk /system/app/otaclient.apk.bak

 mv  /system/app/otaclient.odex /system/app/otaclient.odex.bak

Edited by vampirefo
Link to comment
Share on other sites

Guest divvykev

I posted what you should have done the second after you rooted, stop all OTA until your tablet is ready for update.

 

Anyway same thing can be done via adb assuming you installed busybox.

 

 

without busybox

 

 mv /system/app/otaclient.apk /system/app/otaclient.apk.bak

 mv  /system/app/otaclient.odex /system/app/otaclient.odex.bak

 

Superb. Thanks for your help. Will try it and update. Hopefully will be a way out of this loop and back to "normality"

 

Thanks again :)

Link to comment
Share on other sites

Guest divvykev

SOLVED!!!!! 

 

So here is what I did.

 

1. Restored to a stock OBrien image

2. Used the keyboard settings route to gain usb debugging. At some points it loses authorisation so you may have to go back and re-authorise.

3. adb shell

4. Gain root. you simply type su and grant root access on SuperSU on the tablet

5. Follow vampirefo instructions from message above #10 (Busybox not installed)

6. Type reboot

7. Dont panic when it seems to stick at "Updating apps" black screen.

8. Cringe at the Tesco introduction remembering how a simple update causes so much problems.

9. Thank Vampirefo and Normola for all their help and of course PaulOBrien.

 

I may get my life back now :) It got personal

Edited by divvykev
Link to comment
Share on other sites

Guest EananC

SOLVED!!!!! 

 

So here is what I did.

 

1. Restored to a stock OBrien image

2. Used the keyboard settings route to gain usb debugging. At some points it loses authorisation so you may have to go back and re-authorise.

3. adb shell

4. Gain root. you simply type su and grant root access on SuperSU on the tablet

5. Follow vampirefo instructions from message above #10 (Busybox not installed)

6. Type reboot

7. Dont panic when it seems to stick at "Updating apps" black screen.

8. Cringe at the Tesco introduction remembering how a simple update causes so much problems.

9. Thank Vampirefo and Normola for all their help and of course PaulOBrien.

 

I may get my life back now :) It got personal

Can you link me to this stock obrien image and how you restored to it, as i have the exact same issue as the OP.

 

Thanks

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
 Share

×
×
  • Create New...

Important Information

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