Hello, has anyone got the latest updates (July 2015) ROM rooted or stock? If so please add a link below. Thanks

I factory reset my (already rooted) device, which was running KitKat, and it was driving me insane how the hudl's setup wizard was forcing me to download and install the Lollipop update. I managed to find a way around it, and since I hadn't seen anyone post a method here on how to do that, I thought that I'd post it to help out anyone else in the same predicament.

NOTE: THIS REQUIRES YOUR DEVICE TO ALREADY BE ROOTED PRIOR TO FACTORY RESET (although maybe you can flash the rooted image file and then try this but I'm not sure)

CREDIT TO NORMOLA FOR THIS PART

Quote

 

Well, after some fiddling I've managed to find a way around the forced update for a first time install.

 

1. First off, wipe the device from recovery.
2. Boot up and select 'Add Network' from the wifi selection screen.
3. Hold down the microphone key on the google keyboard and select the settings icon and select the settings icon.  This will show 'Input Options'.
4. Select 'Google Keyboard Settings'
5. Select 'About Google Keyboard'
6. Select 'Open-source licences'
7. Highlight some text with a long press then select 'WEB SEARCH' from the top right
8. This will take you to the Google Now search page and show a not connected error.
9. Type 'Settings' into the search box and select the settings page from the drop down.

 

From here you can enable developer mode, enable adb and fix any stupid changes to the system partition that you might have made (whoops :P )

 

There's probably a shorter route than this but I'm just pretty happy to have the chance to repair the damage :D

 

After this, you should be able to successfully enable "USB debugging" in "Developer options" which will allow you to use adb. Connect your hudl to your computer (make sure you have the ADB drivers installed), open command prompt, type in "adb devices" and a prompt should appear on your device asking you to confirm the debugging. Accept it.

Go back to the setup wizard and continue with it, up until the point where it informs you that there's a new update available - BUT DO NOT BEGIN THE DOWNLOAD.

Instead, inside command prompt type "adb shell" (make sure you have ADB tools installed) which will start a shell, and then elevate it to root using "su". A prompt from SuperSU should appear on your device, asking to allow root permissions for ADB shell - accept it.

Then in command prompt type "pm disable hudl.ota", the response should be "Package hudl.ota new state: disabled".

Then, you want to kill the process, to do this you must figure out its process id. Type in "ps | grep hudl.ota" which should return you information about the hudl.ota process. You want to read off the second value of the hudl.ota line, starting from the left (it's the number next to system). 

Once you have this id, type in "kill IDHERE" which should then close out of the new update available screen and take you to a screen where it says it's updating your apps. After that, the setup wizard will finish and you're free to use it.

As a side note, if you ever want to upgrade to Lollipop for some reason, then you will need to re-enable hudl.ota. To do this, just open a shell again and type in "pm enable hudl.ota".

Hi my girlfriends Hudl 2 has an unusual charging problem. When in use the charge level displayed stops changing and it will not alter if charged or left in use. If it is left in use it will eventually shutdown as the battery has drained. This doesn’t happen all the time but seems to happen mostly when it is left to fully charge. Fully charging again seems to resolve the issue, until the next time. This problem has existed in KitKat and after a recent Lollipop update. I have tried installing Battery Monitor Widget but the same battery levels are displayed. We have also preformed a factory reset, no change. Has anybody else expired a similar issue and do you have a resolution?

Hi,

From being a quiet observer on this forum, picking up valuable help and tips, I now need some help.

Since upgrading to Lollipop, I seem to have lost the ability to connect devices to the USB port using an OTG cable.

Previously, I was able to connect a usb stick or SD card in a a reader to transfer files. Also, I was able to connect a keyboard or mouse and use these (i think the mouse worked!).

Since Lollipop, the Hudl 2 will not detect anything connected to the USB port.

Either the upgrade has disabled this feature or my tablet has a fault. It no longer seems to provide any power to devices, e.g. USB stick LED does not come on or optical mouse does not light up.

To confirm, i went into Tesco with my USB OTG cable and connected my mouse and USB to a device still on Kitkat and it worked perfectly.

Can anyone else check their device to see if this issue is just on my tablet or if this is linked to the update?

Please note this guide is for rooted tablets only. It will help you to stop the forced Android 5.0xx OTA bootloop by  removing the Hudl2 update package. Warning, this procedure means no more Lollipop. The tablet must be factory formated!

1-Select your WI FI and connect. On the  Google account set up, click yes, click yes on do you have an account.
2- click and hold the comma or microphone icon.
Select the cog (setting) key.
Select google keyboard setting.
Select about keyboard and then open source licence. Now long press on text and click on share and select e mail.

3-Setup up your google e mail account.
On final set up screen go to the e mail in box. To do this, click compose (top left)

4-Using phone browser, download jumobile system app remover free apk. Send apk from phone by e mail to your Google e mail account.

5-Click on the e mail and then on the apk to install.

If you get a security warning, click settings and then click unknown sources.

You may need to back tab and re install apk if you have had to select unknown sources.

Install jummobile apk and open when the instillation has finished. Allow superuser access. Now uninstall hudl update package.

6-Reboot tablet.

Warning! If you have uninstalled the Hudl launcher you will get a system setup and ui crash. If this happens follow steps above but install a free launcher apk(Nova Free) in addition to the jumobile apk. If you need to install launcher, format tablet and re start guide. Install launcher apk first but do not open, then install jumobile apk. Open jumobile and remove Hudl update. Reboot.

All credit to other users for there efforts.
I apologise for any duplication of topic/thread. Other Apk are available!!

.

Thanks

Hello,

I have received a hudl2 and I wanted to get past the update nag, so I removed root, this didnt help and now I cant use the apps that get past it, 

My fastboot/Droidboot is also just not working as windows cmd fastboot doesn't detect it but device manager does (tried all kinds of drivers.)

Any help would be appreciated 

I have 2 Hudl 2s, both updated to Lollipop. One works fine with OTG, one does not, therefore I know all my OTG cables and USB devices should be working with both Hudls.

I spent a day trying to get OTG to work and I think I have found a workaround. It's not a perfect solution, I'll explain later, but try this:

1) enable USB Debugging in Developer Options

• (to enable Developer Options) goto Settings > About Phone and tap Build Number several times
• (to enable USB Debugging) goto Settings > Developer Options and enable USB  Debugging

2) Turn off Hudl (Full off, not just Standby)

3) Charge to 100%

4) Turn on Hudl and try OTG and it might just work, for a bit.

Why work for a bit? When charge falls to 93%, OTG stops working.

You might find you can skip steps 2 and 3 and just charge to 94+%, but for consistent, reproducible results please do follow the above.

Hope this helps.

Does anybody here know whether the hudl2 supports simultaneous OTG and charging?

Has anyone got Showbox running on their Hudle 2 lollipop. The app is starting up but when I pick a show or movie to stream the app stops and closes with the message showbow has stopped.

Since updating to 5.1, I haven't been able to log in to Ingress. The app starts but never asks for Google App Engine access permission, so it never fully loads. I called tech support and spoke to a guy who took me through the usual steps (reinstalling webview updates and reformatting the cache partition in the bootloader) which didn't work. He spoke to the devs who were able to replicate the problem and said they would look at it and try to get a fix in to the next patch, due in a few weeks. I did say that if I had the full 4.X image I could flash it but he neatly avoided saying yes/no!

If anyone else is experiencing this, a few more calls might help them up the priority a bit...

Hi,

I have a Hudl2 where the wifi will not stay connected for long enough.  I wanted to upgrade the operating system as it seems to me to be a software issue.

First of all I formatted the Hudl2 which seemed to be a mistake as now every time it boots it starts the setup but because the wifi wont stay on long enough i cant get any further.

Once the Hudl did connect to wifi long enough to start an update download but stops a few % in.

I wondered if someome would be able to advise how I can update the Hudl using my laptop or SD card to see if this helps or if you know of a way to resolve the wifi issue.

In the command screen it says i have: KOT49H.rel.android-build.20151102.170607

Thanks in advance..

I think my daughters hudl 2 has bitten the dust , It will not get past the initial bootup stage , sometimes freezes at various times whilst doing this on some of the start up items ,the android logo even the hudl logo, somtimes on the hudl logo the star doesn't flash and the tune in the background is stuck on ! ,then tries to reboot , I have even got as far as conncting to wi-fi and it crashes again ,sometimes going into recovery mode without me even selecting it , I have tried the options in recovery mode ie, full system factory restore,wipe cache etc and nothing works , it still hangs on the bootup . It appears to hold charge ok . Is it fit for the bin or can the operating system be reinstalled to save it or would rooting fix it ? not sure how to enable the de-bugging thing as it won't get that far . My pc knowledge is very basic , please go easy on me lol.

thanks in advance

• Rooted Image for 20150106.154003 (r1): DOWNLOAD (ROMraid) - ZIP MD5: 837b0a8beb5c0e21a6521b94c68d1fe0 / Image MD5: 4feb49cd6845aebcef96f05048bd6062
• Rooted Image for 20141009.191216 (r1): DOWNLOAD (ROMraid) - ZIP MD5: 3861a3769b08b671fd86c8d9d748e4a2 / Image MD5: 6d424b3f32c1b0fe94f1e841d5042e63
• Rooted Image for 20140924.194555 (r3): DOWNLOAD (ROMraid) - ZIP MD5: 9c58e25f5d9786555dc0f5e5f777fda1 / Image MD5: 9329255e0928c69e3ba6f5e4cde7fc6c
• ADB / Fastboot tools: DOWNLOAD (ROMraid) - ZIP MD5: 299162039f527bc361221fb526976fc7

• Ensure your device is fully charged. This is a safety net really, but good practice. It gives you time if something goes wrong. At the very least i'd recommmend 50% battery. If your device powers off for any reason or the flash is interrupted, your hudl 2 is toast.
• Ensure USB debugging is enabled. In 'Settings -> About', tap the 'build number' like a madman until a message appears stating developer mode has been enabled. Then use 'Settings -> Development' to enable USB debugging.
• Plug the device into your computer using the microUSB cable. A message will pop up on screen asking you to authorise the connection.
• Download and extract the zip file above to a directory on your computer. If you don't have ADB / Fastboot already, you should also download and extract that.
• Open a command prompt / terminal window to the location where you extracted the files
• ON A WINDOWS PC: enter 'adb-windows reboot bootloader', when the device has rebooted to bootloader enter 'fastboot-windows -i 0x1d4d flash system filename.img' - DO NOT INTERRUPT THIS PROCESS (where filename.img is the image file you extracted from the download zip)
• ON A MAC: enter 'chmod +x adb-mac' followed by 'chmod +x fastboot-mac' followed by './adb-mac reboot bootloader', when the device has rebooted to bootloader enter './fastboot-mac -i 0x1d4d flash system filename.img' - DO NOT INTERRUPT THIS PROCESS (where filename.img is the image file you extracted from the download zip)
• ON A LINUX PC: enter 'chmod +x adb-linux' followed by 'chmod +x fastboot-linux' followed by './adb-linux reboot bootloader', when the device has rebooted to bootloader enter './fastboot-linux -i 0x1d4d flash system filename.img' - DO NOT INTERRUPT THIS PROCESS (where filename.img is the image file you extracted from the download zip)
• Use the volume buttons to select 'REBOOT' on the device and choose the option with the power button
• Enjoy your rooted device!

I have a strange issue with the h2 - I plug the charger into the socket, the led goes red, but the device's battery drops instead of charging. The issue is temporarily fixed if I restart the hudl2.

Does anyone else have a similar issue?

I am on vanilla (un-rooted) firmware with the latest update on it.

EDIT: A solution has been found for the time being! Thanks to Chris for stepping in for us! All credits go to him and the Tesco dev team.

Hi All - we've just updated the story with a quote from Tesco confirming that it is aware of the problem and will be rolling out a software update to fix affected tablets. I think that's an FTW right there. Oh yes.

http://www.theinquirer.net/inquirer/news/2382075/tescos-hudl-2-tablet-doesnt-recognise-its-own-charger

OK, so just wondering if anyone has tried taking the hudl2 apart yet?

Someone posted an early teardown of the original hudl which was pretty useful for simple fixes and hardware hacks. Hoping for something similar if anyone has the inclination....?

How much juice does this baby need?! I've got it on my ipad charger at work and always draining reporting 'insufficient Power to charge'. Is it just me or are there other hudl'ites with this?

Hi

First post and I'm asking for help here, so apologies straight away for that, but I'm desperate here as I love my Hudl 2 and want it back.......

......quick history of what has happened to my Hudl:

• Hudl was working perfectly up until some time last (Wednesday to be precise) week.
• I turned the hudl on and it wouldn't do anything else than keep on repeating the boot up sequence (with the annoying loud tune that you can't turn off.....). It kept repeating this constantly never getting beyond the "hudl" logo on the screen. So, I cleared the cache and tried rebooting but this didn't work.
• I decided to do a full factory reset and this partially worked in that I could get it switched on and started on the set up screens, but I'd only manage to get so far before it would decide to reboot itself.
• Eventually I managed to get past the initial set up screens and got it up and running, however I am still plagued with random crashes for no apparent reason.
• Update as of today - the random crashes have become much worse ending back up with constant reboots and never getting any further than the hudl boot screen. After awhile it decides to sit on the recovery screen.

I've read some of the posts on this issue and what surprises me is that I didn't get any notification that my hudl was being updated, if I had I would have backed things up. So I'm very annoyed and frustrated at the moment. Currently it says "LMY47I.rel.android-build.20150917.142239 release-keys" on the recovery screen (doesn't mean much to me, but thought it might be useful).

I've read about being able to update from the micro SD card, is this possible and will it cure the issues? If so, how do I do this please?

I should just add that I'm not tech savy with tablets/android, so really want something that will work for a dummy! Any help very gratefully received!!

Thought I'd start a thread about it but anyone experimented with this yet? What happens when trying to get into fastboot to do it like with the tegra tablets it just took the line fastboot OEM unlock to do it.

I'm gonna mess around with my fastboot see where I can get since there's not many devs yet for the hudl so I'll play my part too.

Hi folks,

Owing to an oversight on my part, I accidentally let my Hudl 2 battery run flat this past weekend.  I have since charged it for over 24 hours - there is no life whatsoever, not even the red charging light.  I've tried multiple chargers, all of which charge other Android devices with no problems, to no avail.  I've also tried charging via USB connection to my laptop.  Still no red charging light.  No change when I hold down the Power button.  No change when I hold down the Power button and (every) combination of the Volume +/- buttons.  There is of course - bizarrely - no "hard reset" button (to press with a paperclip/pin) on the Hudl 2.  For all intents and purposes, the tablet is completely dead.

Tesco's online help have been entirely useless.  Does anyone have any advice/tips?  Is it just a matter of chasing up the warranty for a new device?  If so, has anyone gone through that procedure before..?

Thanks in advance!

Here is how to root the HUDL running the latest software update. Has worked for myself on a few hudls and others have verified it here also.​

• Download this zip file (click the downward arrow at the top) and unzip it:  https://drive.google...iew?usp=sharing
• Mirrors of download: http://www76.zippyshare.com/v/imcXp8oH/file.html

• Copy the su update zip (named “UPDATE-SuperSU-v2.46” in the extracted folder from step 1) to your Hudl 2’s internal memory or preferably, its microSD card. Remember where you put it!

• Ensure drivers for adb are installed. Run them from the “adbfastboothudl” folder in the zip folder from step 1. Install these ADB drivers also: https://drive.google.com/file/d/0B0MKgCbUM0itVVFWRC02Q0VBQnc/view

• Enable USB debugging from developer settings on the hudl. . 

• If you don't know how to turn on USB Debugging, here is how: 

• • 1. Go to Settings menu on your device.
  • 2.Go to About tablet submenu. 
  • 3.Now scroll to “Build Number” and tap it multiple times.
  • 4.After tapping it enough times you will see an alert saying “You are now a developer”/”Developer mode has been enabled”.
  • 5.Now if you go to your Settings menu, you will see the developer options submenu over there.
  • 6.Tap on the Developer options and then turn on USB Debugging.

   

• Start the root process by clicking double clicking “launcher” in the “IntelAndroid-FBRL-01-17-2015” folder and watch your HUDL screen. It may show a pop up asking to accept your PC’s “fingerprint” or something like that and show a long number of random characters. Click accept. 

• On the next window type “T3” without quotes when asked for options.

• The Hudl should reboot to the new recovery which is CWM recovery. The screen should be grey and show a Hat symbol. 

• Navigate to “install from SD Card” using the volume keys and the power button is enter. Then to install zip from SD card and chose the “UPDATE-SuperSU-v2.46” zip you copied earlier.

• Click enter and wait.

• It should reboot your hudl back to normal and it will be rooted.

• *OBLIGATORY* I am not responsible for a bricked HUDL or any damage done to it. I dont know if this voids the warranty also but it shouldn't. If you follow the guide it will be easy and hard to break your hudl.

Troubleshooting:

If you get "UNKNOWN DEVICE" error or something along those lines in red writing when using launcher.bat, install the pdanet drivers (http://pdanet.co/) and see if that fixes the issue. it did for me once.