Jump to content

Ubuntu and hudl2


Guest bryanchapman9999

Recommended Posts

Guest bryanchapman9999

Hoping someone can shed some light here.

 

got adb working fine when the hudl is booted normally.

 

I've tried running all of this as root and my normal user

 

adb devices show my hudl

 

adb logcat does indeed stream logs

 

lsusb shows - Bus 003 Device 007: ID 1d4d:504b PEGATRON CORPORATION

 

adb reboot bootloader does just that

 

now lsusb shows - Bus 003 Device 008: ID 1d4d:5044 PEGATRON CORPORATION

 

Is I unplug it and run the lsusb command, it is indeed gone. Plug back in and its back.

 

adb devices show nothing and of course the fastboot command to flash the rooted image just gives <waiting for device>

 

I'm at a loss

 

Or does anyone know how to get this working under windows 8? I can copy files to/from the device but adb devices is blank no matter what mode the hudl is in.

 

Many thanks

Bryan

Link to comment
Share on other sites

Guest bryanchapman9999

Starting to wonder if it might be my hudl.

 

Got adb to work under windows 8 and I've got the same thing.

 

adb <everything> but as soon as I get into the bootloader nothing

 

I do have a bit more visibility in windows though as device mnaager lists an unknown device - I've tried attaching the adb/bootloader drive to this but is says failed to start - I have not rebooted though, will do that now.

 

EDIT:

 

Have now rebooted - no change.

 

Disabled driver signing. Have now managed to get my unknown device to be an Android bootloader interface / ADB device and ADB composite device

 

All no change. Running adb/fastboot commands from an elevated cmp prompt.

 

Which drivers did you guys use? I'm just trying the generic google ones.

Edited by bryanchapman9999
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

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