Advertisement
Guest User

Untitled

a guest
Feb 12th, 2011
126
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Bash 3.76 KB | None | 0 0
  1. 2011-02-13 03:41:38.213 greenpois0n[14735:e07] Could not connect the action buttonPressed: to target of class NSApplication
  2. 2011-02-13 03:41:38.217 greenpois0n[14735:e07] Could not connect the action buttonPressed: to target of class NSApplication
  3. 2011-02-13 03:41:38.218 greenpois0n[14735:e07] Could not connect the action buttonPressed: to target of class NSApplication
  4. 2011-02-13 03:41:38.220 greenpois0n[14735:e07] Could not connect the action buttonPressed: to target of class NSApplication
  5. Initializing libpois0n
  6. No matching processes were found
  7. Device must be in DFU mode to continue
  8. Device must be in DFU mode to continue
  9. Device must be in DFU mode to continue
  10. Device must be in DFU mode to continue
  11. No matching processes were found
  12. No matching processes were found
  13. Device must be in DFU mode to continue
  14. Device must be in DFU mode to continue
  15. Device must be in DFU mode to continue
  16. Device must be in DFU mode to continue
  17. Device must be in DFU mode to continue
  18. opening device 05ac:1227...
  19. Checking if device is compatible with this jailbreak
  20. Checking the device type
  21. Identified device as AppleTV2,1
  22. Preparing to upload limera1n exploit
  23. Resetting device counters
  24. Sending chunk headers
  25. libusb:error [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  26. libusb:error [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  27. libusb:error [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  28. libusb:error [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  29. libusb:error [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  30. libusb:error [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  31.  
  32. libusb:error [submit_control_transfer] control request failed: no connection to an IOService
  33. libusb:error [submit_control_transfer] control request failed: no connection to an IOService
  34. Sending exploit payload
  35. libusb:error [submit_control_transfer] control request failed: no connection to an IOService
  36. Sending fake data
  37. libusb:error [submit_control_transfer] control request failed: no connection to an IOService
  38. libusb:error [submit_control_transfer] control request failed: no connection to an IOService
  39. libusb:error [darwin_reset_device] ResetDevice: no connection to an IOService
  40. libusb:error [submit_control_transfer] control request failed: no connection to an IOService
  41. libusb:error [submit_control_transfer] control request failed: no connection to an IOService
  42. libusb:error [submit_control_transfer] control request failed: no connection to an IOService
  43. libusb:error [submit_control_transfer] control request failed: no connection to an IOService
  44. libusb:error [darwin_reset_device] ResetDevice: no connection to an IOService
  45. Exploit sent
  46. Reconnecting to device
  47. libusb:error [darwin_close] USBDeviceClose: no connection to an IOService
  48. Waiting 2 seconds for the device to pop up...
  49. Connection failed. Waiting 1 sec before retry.
  50. Connection failed. Waiting 1 sec before retry.
  51. Connection failed. Waiting 1 sec before retry.
  52. Connection failed. Waiting 1 sec before retry.
  53. Connection failed. Waiting 1 sec before retry.
  54. Connection failed. Waiting 1 sec before retry.
  55. Connection failed. Waiting 1 sec before retry.
  56. Connection failed. Waiting 1 sec before retry.
  57. Connection failed. Waiting 1 sec before retry.
  58. Connection failed. Waiting 1 sec before retry.
  59. Command completed successfully
  60. Unable to reconnect
  61. Unable to inject exploitDevice must be in DFU mode to continue
  62. Device must be in DFU mode to continue
  63. Device must be in DFU mode to continue
  64. Device must be in DFU mode to continue
  65. Device must be in DFU mode to continue
  66. Device must be in DFU mode to continue
  67. Device must be in DFU mode to continue
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement