• Content count

  • Joined

  • Last visited

Community Reputation

19 Good

About flurry

  • Rank
  1. My partner bought a Smart Ultra 6 some months ago and I'm now considering doing the same. Whilst looking through the developer options menu on hers (running 5.1.1) I noticed there's an option for "OEM Unlocking - allow the bootloader to be unlocked". Is unlocking the bootloader as straight forward as enabling this setting then unlocking the bootloader via fastboot?
  2. Attempting to ubuntu up the hudl...

    This is very interesting and I'd be keen to see it working, but I don't understand enough to offer any real advice! I have, however, used Debian Kit to get linux running alongside Android on the hudl; maybe comparing to this could shed some light on the problems?
  3. Custom JellyBean Kernels compiled

    I'm following this and your FreakTab thread, though I currently have nothing to add or suggest
  4. Chip fallen off! Help needed please!

    how large is the chip and can you see where it's from?
  5. Android 4.4.4

    I think that's more relevant to the Hudl2, which uses in intel chip. The original Hudl uses an RK3188
  6. Can I upgrade a hudl to android 4.3 or 4.4?

    you can definitely install an adblocker once rooted
  7. Can I upgrade a hudl to android 4.3 or 4.4?

    there's no rom (comparable in a way to a linux distro) above 4.2.2 - I believe we're missing some of the hardware sources to be able to compile a version of 4.3 or 4.4 for it ourselves, though my understanding may be slightly wonky on that. there may be another way to acheive a restricted user type environment, what are you aiming to do?
  8. Launch by default

    settings > apps > all > chrome scroll down a bit and you should find an option to 'clear defaults'
  9. Remote support app needed for Hudl

    you'll probably have more luck searching more generally for something to remote control an android device - this forum is fairly quiet and any solution that works on android 4.2 should work on the hudl :)
  10. Stock Bootanimation for Tesco Hudl

    here you go :) EDIT: unzip first - the attached file contains the boot.ogg and the bootanimation.zip Hudl_Startup.zip
  11. Am A Bit Stuck...

    here's the original hudl partition map (starting address and length): ./rkflashtool-linux r 0x00002000 0x00002000 > hudl_misc.img ./rkflashtool-linux r 0x00004000 0x00004000 > hudl_kernel.img ./rkflashtool-linux r 0x00008000 0x00008000 > hudl_boot.img ./rkflashtool-linux r 0x00010000 0x00010000 > hudl_recovery.img ./rkflashtool-linux r 0x00020000 0x00020000 > hudl_backup.img ./rkflashtool-linux r 0x00040000 0x00100000 > hudl_cache.img ./rkflashtool-linux r 0x00140000 0x00002000 > hudl_kpanic.img ./rkflashtool-linux r 0x00142000 0x00200000 > hudl_system.img ./rkflashtool-linux r 0x00342000 0x00020000 > hudl_factory.img I think my first step would be to see if your partitions match these. It may be possible that Helios has changed the partition sizes - I can't say I've tried using the Helios rom. I'm afraid I'm not very familiar with windows, and as such haven't used RKbatchtool - only RKflashtool on linux. It maybe worth picking one tool and sticking with it? Though I thought they were both executing the same command line tools, just on different OS's?
  12. Am A Bit Stuck...

    okay, some questions first: 1.) what computer OS are you using? 2.) have you altered the partition sizes on the hudl at all? 3.) have you tried a backup/copy of the original recovery and system? EDIT: nevermind! glad you sorted it!
  13. Modified SystemUI without Tesco button

    Indeed, sounds like you'll be fine as long as you put the original unmodified SystemUI.apk back in place before updating.
  14. Modified SystemUI without Tesco button

    because it's on the stock navigation bar on the hudl 1, so the launcher doesn't change it. On the hudl2 your idea would work
  15. Modified SystemUI without Tesco button

    What build version are you on currently (settings > about tablet)? When the hudl update 1.3.1 update was released (build no. JDQ39.20140424.153851) I compared the updated SystemUI.apk to the original that I modified and there were no changes. As such, I've been using the modified SystemUI.apk on this build with zero problems. If you're currently on the 20131016.200812 build then the update is likely to be the 1.3.1 update. If you're currently on the 20140424.153851 build (which I believe is the latest) and you're receiving an update I would be keen to know! To update, I would put the original SystemUI.apk back, then once updated replace it with the modified one. The update is likely to fail with the modified file in place. You may well have to re-root once updated to be able to push the modified file into place

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.