Any advice would be great - can I try reflashing the original tesco firmward, or custom firmware or somthing? Would prefer not to but appears maybe the only route back from useless paperweight status...

EDIT: I think I have got to the bottom of it - the tesco server is down/switched off (https://device.mobile.tesco.com)

The device can access the internet, use chrome, etc., using the google keyboard servicdes workaround, but hudl can't be updated from within settings and all the hudl legal information links on the about tablet page are dead (non Tesco links work fine).

So Hudl 2s which are factory reset are now bricked unless Tesco turn the server back on or they are rooted...

Infuriating...

can anyone point me to a working download for these images please?

Rooted Image for 20141009.191216 (r1): DOWNLOAD (ROMraid) - ZIP MD5: 3861a3769b08b671fd86c8d9d748e4a2 / Image MD5: 6d424b3f32c1b0fe94f1e841d5042e63

ADB / Fastboot tools: DOWNLOAD (ROMraid) - ZIP MD5: 299162039f527bc361221fb526976fc7

I can't believe that nobody has a copy spinning on a disk somewhere?

Thanks in advance!

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.

I realise I'm late to the Hudl party, but my daughters Hudl 2 build 20150917.142239 has stopped working by going into a repeating boot sequence.  I've tried the factory reset but that hasn't helped so my only other option as far as I know is to try to re flash it.  Does anyone know if there are any other things to try? and would someone have a suitable image I could try the re-flash with.

Any help gratefully appreciated.

Many thanks,

Stuart

• 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!

When it boots it goes straight to a black screen with the andriod bot with erasing under the bot and basically stays there and switches off. Tried the power on with volume + key but wont go into boot menu it just goes back to above screen 

Tried connecting to pc but nothing happans so is this tablet dead or is there anyhthing else i can do ?

• 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.

I don't know very much about Android but I have reasonable experience with Linux, so hopefully the learning curve won't be too bad.

Step 1. The package is unzipped and explored.

Step 2. Try to mount the boot.img

quad hudl2# simg2img boot.img boot.raw

Invalid sparse file format at header magi
Failed to read sparse file

 

As you can see failure at the first attempt.

What I hope will happen is that a few people will chip in and we will be able to get some progress made, and at the very least we will all learn something.

Any ideas?

samac

I've a rooted Hudl2 running KitKat, it's downloaded the update files and will install them on next reboot (unless battery is low). I don't need Lollipop and don't want to lose root, is there a way to cancel this update so I can turn this thing off? I've not rebooted it now for weeks...   Maybe just delete (or save for later) the update files.

System upgrade failed (downloaded but kept giving an assert failed message when attempting to patch something from the bootloader/recovery)

I erased all user data/factory reset, thinking something on it might be causing the problem

Now it seems I have no firmware at all, it just boots straight into the stock recovery -.-

My question is, where can I find the official signed firmware for flashing from recovery (or some other bootloader mode)? I can see no sign of any firmware or recovery procedure for it anywhere...

Thanks

I've been lurking here for a little while in efforts to try and fix my fathers failed Hudl 2.

His tablet doesn't charge, no red light, no current draw from USB and I've confirmed that the charge port is fine and that battery power is reaching the board. The board was corroded and it looks like a series of power supply chips, most notably the DA6021 has failed.

I've gotten hold of another dead Hudl 2 but this one shows more life. 

No red light but it does draw power from the USB port and it has charged the battery so I know at least the battery charging circuits are fine. Equally, I do know that the device tries to boot as the PMIC fires up and presents 3.3V and 1.8V for other circuits on the board but it only appears for about 5-10 seconds and then turns off again. 

Is there any kind of serial terminal on the board with access to see what the board is trying to do during this startup sequence?

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..

Incidentally, does it seem to anyone else like no development has occurred since the Hudl 2? I got used to specifications improving for a given price (or price coming down for a given specification) but when I try to find possible upgrades it seems there aren't any (only "side-grades").

(My Hudl is still marginally functional but the touch screen has become considerably less responsive).

Any suggestions?

Yesterday I performed a factory reset through the menu accessed when holding the volume up and power key. My HUDL 2 was working fine, I was just clearing it as I wanted to give it to a family member.
 

However, now it will not turn on. I get the 'Powered by Android' screen for a few seconds and then the screen just flashes on and off (in plain black with no text). It's really frustrating because it was working fine, If I knew resetting it was risky I wouldn't have bothered. It still charges, I've tried letting it charge fully and then turned it on but it still does the same thing. 

Is there anything I can try?
Thanks for your help.

edit- I can still access the menu with the factory reset. 

edit#2-  I did a second factory reset not expecting anything to change but it seemed to fix the issue. My hudl turned on, downloaded an update, rebooted and appears to be working fine now. 

Thanks

I've emailed Tesco who just told me to do a reset but that doesn't fix the problem. Anyone managed a workaround for this?

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".