• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

Modified SystemUI without Tesco button

46 posts in this topic

Posted

I made a modified SystemUI APK without the Tesco button.

To install you need to download and extract this ZIP - DOWNLOAD (ROMraid) - and have ADB installed and ready to use. If this is a bit too complex - wait, an easier method is coming. Only use this guide on a Hudl running ROM version 20130923.020558 (check in Settings -> About -> Hudl Updates) - do NOT install on other versions.

After downloading, and with the device booted and USB debugging enabled, do the following:

  • Open a command prompt / terminal window to the directory containing the extracted zip
  • Do the following commands:
    • adb pull /system/app/SystemUI.apk SystemUI.mybackup.apk
    • adb push SystemUI.apk /sdcard/SystemUI.apk
    • adb shell
    • su
    • stop
    • mount -o remount,rw /system
    • cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
    • chmod 644 /system/app/SystemUI.apk
    • reboot
  • The device will reboot and you should be set!
To restore (for OTAs perhaps), do the same but instead push your 'SystemUI.mybackup.apk' in the process.

Enjoy! :)

P

hudlnotescoss.png

7

Share this post


Link to post
Share on other sites

Posted

Nice work - again :)

0

Share this post


Link to post
Share on other sites

Posted

I'm guessing this is the stock Jelly Bean SystemUI.apk file? I've had a look at how Tesco added the button and it's manky to say the least. They've actually added a couple of methods to com.android.systemui.statusbar.phone.PhoneStatusBar:

  • openTescoDock
  • closeTescoDock

Which appear to call the intents tesco.open.DOCK and tesco.close.DOCK.

 

The methods have been added between awakenDreams() and prepareNavigationBarView().

 

I wasn't expecting code amendment on the Hudl!

0

Share this post


Link to post
Share on other sites

Posted

I'm guessing this is the stock Jelly Bean SystemUI.apk file? I've had a look at how Tesco added the button and it's manky to say the least. They've actually added a couple of methods to com.android.systemui.statusbar.phone.PhoneStatusBar:

  • openTescoDock

     

     

  • closeTescoDock
Which appear to call the intents tesco.open.DOCK and tesco.close.DOCK.

 

The methods have been added between awakenDreams() and prepareNavigationBarView().

 

I wasn't expecting code amendment on the Hudl!

No, it's the stock one patched to hide the button.

P

0

Share this post


Link to post
Share on other sites

Posted

I made a modified SystemUI APK without the Tesco button.

To install you need to download and extract this ZIP - DOWNLOAD (ROMraid) - and have ADB installed and ready to use. If this is a bit too complex - wait, an easier method is coming. Only use this guide on a Hudl running ROM version 20130923.020558 (check in Settings -> About -> Hudl Updates) - do NOT install on other versions.

After downloading, and with the device booted and USB debugging enabled, do the following:

  • Open a command prompt / terminal window to the directory containing the extracted zip
  • Do the following commands:
    • adb pull /system/app/SystemUI.apk SystemUI.mybackup.apk
    • adb push SystemUI.apk /sdcard/SystemUI.apk
    • adb shell
    • su
    • stop
    • mount -o remount,rw /system
    • cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
    • chmod 644 /system/app/SystemUI.apk
    • reboot
  • The device will reboot and you should be set!
To restore (for OTAs perhaps), do the same but instead push your 'SystemUI.mybackup.apk' in the process.

Enjoy! :)

P

 

Thank you mucho!!!

0

Share this post


Link to post
Share on other sites

Posted

I transfered the file via Bluetooth then completed the instructions via SSH. Much simpler.

0

Share this post


Link to post
Share on other sites

Posted (edited)

Are there any generic android drivers available for the Hudl?

 

I am not able to run adb commands as the device cannot be found; when running

adb devices

It is just blank, although it is recognised by Windows 8 as a 'Portable Media Player'.

 

Thanks

Paul

 

OK, problem solved under device manager, besides the portable media player entry there was another entry for 'unknown device', I installed it as an 'Adb Interface' , this was originally for a Samsung Galaxy but it's worked just fine <_<

 

And thanks to the good work of Mr O'Brien I am now most definitely sorted!

 

post-640351-0-27759100-1381654838_thumb.

Edited by Jazman
0

Share this post


Link to post
Share on other sites

Posted

Are there any generic android drivers available for the Hudl?

 

I am not able to run adb commands as the device cannot be found; when running

adb devices
It is just blank, although it is recognised by Windows 8 as a 'Portable Media Player'.

 

Thanks

Paul

Are you sure you have USB debugging enabled in the Hudl's settings? It probably isn't enabled by default, and adb won't work without it enabled.
0

Share this post


Link to post
Share on other sites

Posted

Hello SifJar, you really are a most helpful chap I must say!

As you will see from the post that I have just edited all is now sorted; USB debugging was enabled but I had to resolve the adb interface issue first before adb recognised the hudl as a device, in any event that pesky [ T ] button has now disappeared thanks to the apk and steps provided by Mr O'Brien.

1

Share this post


Link to post
Share on other sites

Posted

Why can't things be simple... I've read the comments above but nobody has really said how to sort the problem out?

 

hg76.png

 

nwy5xtE.png

1

Share this post


Link to post
Share on other sites

Posted

Step by step would be useful...

 

I'm in a similar position, but have 2 entries :

 

1 - Portable devices > Hudl

2 - Android Device > ROMaster Composite ADB Interface

 

No devices attaches per pic above also.  Probably picked the wrong time to learn this stuff... lol.

 

ANy help would be much appreciated/.

0

Share this post


Link to post
Share on other sites

Posted (edited)

Hello @TescoHudl Under Other devices you have Hudl, if you right click and select

'Update Driver Software' and then select

'Browse my computer for driver software' and then select

'Let me pick from a list of device drivers on my computer'

I'm hoping that you will see 'Android Composite ADB Interface' select that, you will get a warning message 'Update Driver Warning' I believe that you can click OK and then the device should be recognised.

This is all assuming that you have 'Android Composite ADB Interface' as a selectable option of course.

 

post-640351-0-57023600-1381662926_thumb.

 

Although under ADB Interface I have 'SAMSUNG Android ADB Interface', it is in fact the Tesco Hudl.
 

Cheers

Paul

Edited by Jazman
0

Share this post


Link to post
Share on other sites

Posted

Hello @TescoHudl Under Other devices you have Hudl, if you right click and select

'Update Driver Software' and then select

'Browse my computer for driver software' and then select

'Let me pick from a list of device drivers on my computer'

I'm hoping that you will see 'Android Composite ADB Interface' select that, you will get a warning message 'Update Driver Warning' I believe that you can click OK and then the device should be recognised.

This is all assuming that you have 'Android Composite ADB Interface' as a selectable option of course.

 

attachicon.gifDevice Mgr.PNG

 

Although under ADB Interface I have 'SAMSUNG Android ADB Interface', it is in fact the Tesco Hudl.

 

Cheers

Paul

 

Hooray!! Thank you very much!! :D

 

lh1JPFt.png

 

rl4p.png

0

Share this post


Link to post
Share on other sites

Posted

:) Excellent, now you should be able to remove that pesky [ T ] button!

0

Share this post


Link to post
Share on other sites

Posted

Just started the removal process, but i'm just wondering whether it is supposed to say 'Operation not permitted' here, in the command prompt? Is this supposed to happen?

 

i7ge.png

 

Cheers

0

Share this post


Link to post
Share on other sites

Posted

Why can't things be simple... I've read the comments above but nobody has really said how to sort the problem out?

Posted Image

Posted Image

Have you tried using the drivers included with the RKBatchTool on windows, I know they're meant for a device in recovery/boot loader mode, but they might work.

0

Share this post


Link to post
Share on other sites

Posted

Have you tried using the drivers included with the RKBatchTool on windows, I know they're meant for a device in recovery/boot loader mode, but they might work.

 

We've already solved that issue, but thanks for your suggestion anyway! ;)

0

Share this post


Link to post
Share on other sites

Posted

We've already solved that issue, but thanks for your suggestion anyway! ;)

Ah, I didn't look past the first page to see if it got solved, no problem :)

0

Share this post


Link to post
Share on other sites

Posted

Hey guys = whilst the smart people are about, any ideas on my issue :

 

Step by step would be useful...

 

I'm in a similar position, but have 2 entries :

 

1 - Portable devices > Hudl

2 - Android Device > ROMaster Composite ADB Interface

 

No devices attaches per pic above also.  Probably picked the wrong time to learn this stuff... lol.

 

ANy help would be much appreciated/.

0

Share this post


Link to post
Share on other sites

Posted

Hey guys = whilst the smart people are about, any ideas on my issue :

 

Step by step would be useful...

 

I'm in a similar position, but have 2 entries :

 

1 - Portable devices > Hudl

2 - Android Device > ROMaster Composite ADB Interface

 

No devices attaches per pic above also.  Probably picked the wrong time to learn this stuff... lol.

 

ANy help would be much appreciated/.

 

Have you tried Jazman's method with entry number one? Post #12 in this thread.

0

Share this post


Link to post
Share on other sites

Posted

Just started the removal process, but i'm just wondering whether it is supposed to say 'Operation not permitted' here, in the command prompt? Is this supposed to happen?

 

i7ge.png

 

Cheers

Hello TescoHudl

No, operation not permitted is not supposed to happen

I see that there's a 1: after stop whilst in shell, perhaps an inadverant key press?

Maybe exit and try again?

0

Share this post


Link to post
Share on other sites

Posted

slightly different issue for me - i have 2 entries, and when i try to update the hudl one, it doesnt give the option for adb composite device.

 

I updated the other one (at the top of the page) but still no joy.

 

Currently get "no devices attached" error...

post-797054-0-79033500-1381665858_thumb.

0

Share this post


Link to post
Share on other sites

Posted

Just started the removal process, but i'm just wondering whether it is supposed to say 'Operation not permitted' here, in the command prompt? Is this supposed to happen?

 

i7ge.png

 

Cheers

Hi, I had this issue the first time I tried to adb too. When you type su it's supposed to give you a different command prompt, but I just got blank lines like you did, and it turned out to be because adb hadn't been authorised for root access (by the SuperSU app). Did you check the Hudl's screen at this point in case there was a pop-up? In my case the problem seemed to be because I was using a secondary user account, so I didn't get a pop-up from SuperSU, but when I tried again as the primary user it worked (and once I'd done that, the next time as the secondary user worked too).
0

Share this post


Link to post
Share on other sites

Posted

Hello @QLF I assume that when you run adb you are just getting a blank space?

I can only suggets that you delete the ROMaster Composite ADB Interface entry and start again?

Not a great deal of help I'm afraid

Paul

0

Share this post


Link to post
Share on other sites

Posted

slightly different issue for me - i have 2 entries, and when i try to update the hudl one, it doesnt give the option for adb composite device.

 

I updated the other one (at the top of the page) but still no joy.

 

Currently get "no devices attached" error...

 

It didn't give me the option for ADB composite device either. I can't quite remember how i managed to get it now, but i think i clicked on 'Android' or something, and then it came up in the next menu. :)

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

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