View Single Post
Old 05-02-2016, 03:55 AM   #12
blkhawk
Bit Wrangler
blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.blkhawk is far, far better than a slap in the face with a wet fish.
 
blkhawk's Avatar
 
Posts: 31
Karma: 93324
Join Date: Sep 2010
Device: Oasis
Well theoretically yes - however this would only apply fairly late in the boot process since you need active monitoring of the resistance to that pin to select different modes for it. In development you usually need access right in the boot loader. That means in practice that a device would at first show up with a special USB device id - it defaults to the "development device" (for Android devices this is FASTBOOT) then when the kernel start to load it "unplugs" then replugs with the normal production dev id. After this point "Magic" cables might switch different modes. I think a early-boot magic cable is fairly unlikely for the kindle.

A usbnetwork activating cable is a possibility - I might investigate this with a decade-resistor and microusb-breakout board.
blkhawk is offline   Reply With Quote