Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About samac

  • Rank

Profile Information

  • Your Current Device(s)
    hudl 2

Recent Profile Visitors

1,539 profile views
  1. Just tried it no luck, I can run mouse/keyboard or mouse/pendrive, but doesn't power through at all. samac
  2. @dennissingh99 You can't write to the /system partition on the Hudl2 so those command won't work, but you can tear apart the update and access /system there and add in those files, but when you put it back together it doesn't load because of a signature error. samac
  3. It's been 12 days since my minor rant and no one has chipped in ..... So I guess I'll call it a day and hope that Paul O'Brien can get Lollipop on the Hudl2 rooted. samac
  4. Slightly tongue in cheek suggestion, but IMHO you are better off keeping the Hudl2 on KitKat. samac
  5. I'll swap you. Send me your working 4.4.2 Hudl2 and I'll send my Lollipop Hudl2, then I get a machine I can root and you get a machine with Lollipop. samac
  6. OK so looking at init in boot.img makes me think that it is the one to play with, but we would also have to modify other parts of the system such as fstab /dev/block/by-name/factory /factory ext4 nosuid,nodev,noatime,barrier=1,data=ordered wait /dev/block/by-name/system /system ext4 ro,noatime wait,verify /dev/block/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1,data=ordered wait,check /dev/block/by-name/config /config ext4 nosuid,nodev,noatime,barrier=1,data=ordered wait /dev/block/by-name/data /data ext4 nosuid,nodev,noatime,discard,barrier=1,data=ordered,noauto_da_alloc wait,check,forceencrypt=/factory/userdata_footer /dev/block/by-name/logs /logs ext4 nosuid,nodev,barrier=1,data=ordered wait,check */block/mmcblk1* auto vfat None wait,voldmanaged=sdcard1:auto,noemulatedsd */block/sd* auto vfat None wait,voldmanaged=usbcard1:auto This is where system is made ro and the encryption is called and the nosuid bit is set. However I'm still at a loss as to why there is apparent duplication in droidboot.img samac
  7. There is an init system in each of them and it would be kind of nice if someone actually answered the question which I have asked in several different ways ie. what is the boot procedure for the update. My intention on starting this thread was to get a number of people to actually collaborate to try to A) root the new update and B) learn something. As I have mentioned on a number of occasions I know Linux but am an Android Newbie. It is not and has never been my intention to do all the work. So if any one else would like to chip in ..... Once the question has been fully dealt with then I might be able to get a bit further, however I'm just not interested enough to put all the hours in myself. samac
  8. I would love to help. I can get into all parts of the update, modify it any way I choose, but until I find out which init file is called first then I'm stuck. Normally for linux the installation media starts a small linux system that sets up your hard drive and then installs the new linux system, when you reboot the new system takes over. I need to know if is is the same with Lollipop on the Hudl2 and if the setup image is boot.img or droidboot.img or if it is a completely different method, then perhaps I can make the partitions writeable, then possibly and only possibly I might have a rooted image. samac
  9. So what is the first file called? Is it init from boot.img, droidboot.img or the files copied into place. Or have they used some other odd method? samac
  10. Have a look at this, go to the bottom of the article. samac
  11. @robin0800 Thanks for the info. I'm not a programmer and don't recognise the scripting language, but what I get is: Check the bios version Check the build date and only update if update is newer Make sure it is installing on a Hudl2 block_image_update("/dev/block/by-name/system" NOT SURE WHAT THIS DOES Extract and copy to correct location system.new.dat Extract and copy to correct location boot.img Extract and copy to correct location esp.zip Flash esp.zip Extract and copy to correct location droidboot.img wipe cache OK so that is how the OTA update gets on to the Hudl2, but the update was a major update which changed many things, for example there is no mention of signatures, encryption, partitioning, permissions etc. This just seems to be a "make sure I'm on the correct device and copy everything over to make it ready for updating." How does the upgrade happen? samac
  12. So I can fully explode boot.img, droidboot.img and system.new.dat. So it should be possible to modify them to remove or change various aspects of the Hudl2 OTA update. Can someone point me to, or explain, the Android update procedure. In other words how does the OTA go about replacing the installed system. samac
  13. Found this, it allows access to boot.img split_image Having a look around, but I thought I would share. samac
  14. +1 Also could you detail the process to help us newbies learn something. PLEASE. samac
  15. Here is my email to and the response from Tesco. Curt, I would have thought that a more thoughtful answer would have been appropriate, makes you think that it wasn't passed along as requested. Please keep asking them to do the correct thing. samac
  • Create New...

Important Information

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