Jump to content

Search the Community

Showing results for tags 'recovery'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Talk
    • Everything Else
    • Gaming
    • Questions
    • Business and Enterprise IT
    • Security
    • Hacks & Mods
    • Applications & Coding
    • Trading Post
  • WiFi Pineapple
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • WiFi Pineapple Mark V
    • WiFi Pineapple Mark IV
    • Pineapple Modules
    • WiFi Pineapples Mark I, II, III
  • Hak5 Gear
    • Hak5 Cloud C²
    • Plunder Bug
    • Bash Bunny
    • Signal Owl
    • USB Rubber Ducky
    • Packet Squirrel
    • LAN Turtle
    • Screen Crab
    • Shark Jack
    • Key Croc
  • O.MG (Mischief Gadgets)
    • O.MG Cable
    • O.MG DemonSeed EDU
  • Hak5 Shows
  • Community
    • Forums and Wiki
    • #Hak5
  • Projects
    • SDR - Software Defined Radio
    • Community Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Enter a five letter word.

Found 9 results

  1. So anyone who's seen the other firmware post has probably seen my adventures in trying to figure out the firmware upgrade process as the suggested tool in the post just doesn't exist, is available on github if you need it, but the links in the download center appeared to be broken earlier. I ended up bricking my shark to some degree - Turns out though as it's based on openwrt it has the inbuilt recovery features. So these are the steps I took to restore its functionality - you can follow, but it is by no means the official help, nor is it without massive risk. I was willing to chalk my jack up to being a lost cause. 1. Charge it - You probably won't have LEDS here to help you out (no charge level indication) but you only need sufficient power to "wait" for it to actually boot, so plug it in for 5 minutes and just let it charge. 2. Using either a pin*, sim-card removal tool, etc locate the hole on the back of the case and insert it most of the way, you should feel a button at the end of the travel. Rest it on it, but do not depress it. *I found it difficult to "aim" my pin, at the button as it's tiny... so I removed the casing of the shark jack... there are no screws, it comes apart with a spudger inserted down the side, really easily. 3. Power on the device to ARMING mode (middle position). Depress button using your pin now. Count 1000, 1, 1000 2... etc until 1000 7. remove pin! 4. Plug device into your Network Jack within a minute or so you should see green lights, indicating activity on the network port. 5. Set your host's IP to 192.168.1.2 and attempt to browse using a web browser to 192.168.1.1 you should see a screen like the following: 6. Once you've proven connectivity to the recovery webpage, PLUG IN YOUR USB-C... KEEP THE SHARK JACK POWERED THROUGHOUT THIS PROCESS. 7. Select the OS tab. 8. Using a normal "upgrade-*.*.bin' firmware file available from the hak5 download center (download it, check the checksum), browse to the firmware. 9. CONFIRM YOU ARE ON THE OS TAB AND IT SAYS "e.g: OpenWRT.bin" DO NOT DO ANY OTHER TAB or you will be on your own. - select "start upload file". 10. Page will switch to a loading screen informing you to wait until the device reboots. 11. Once the device has rebooted you should notice this... the LEDs will have done their boot cycle (flashing greens) and turned to either flashing amber, indicating arming mode, or flashing/static blue to indicate the device is either charging or charged. 12. Set your host's IP to 172.16.24.2 and attempt to SSH to the device. You may get prompted about the SSH host key having been changed and may need to delete it from your known_hosts file, but once done... you can log back into the device using the default credentials of root:hak5shark. Now go get a celebratory beverage of your choice and get your hack on.
  2. I can't connect to my wifi pineapple nano. I was able to connect to it before but I was experiencing some problems so I decided to do a firmware recovery. I followed the instructions: Next, follow these steps to access the recovery web interface and update the firmware. Unplug the WiFi Pineapple completely from all power sources. Begin holding the RESET button on the device. With the RESET button held, power on the device. Continue holding the RESET button for 10 seconds, then release. NANO: The blue LED will remain solid TETRA: The yellow LED will remain solid Connect the host PC to the WiFi Pineapple via the USB Ethernet Port NANO: The male USB A plug TETRA: The Micro USB port labeled ETH From the host PC, configure a static IP address on the WiFi Pineapple facing Ethernet interface to 192.168.1.2 with netmask 255.255.255.0 For example, in Linux run ifconfig eth1 192.168.1.2 netmask 255.255.255.0 up (where eth1 is the interface name of the WiFi Pineapple). From the host PC, browse to http://192.168.1.1 Click Choose File and select the factory firmware image downloaded above. Click Update Firmware. This process will take several minutes. Do not interrupt the power supply while the firmware is updating. Once complete, the WiFi Pineapple will restart. Reset the the WiFi Pineapple facing USB Ethernet interface back to DHCP or 172.16.42.42 with netmask 255.255.255.0 But when I try to connect to it via 192.168.1.1 it goes to my router login. Please Help. What am I doing wrong?
  3. I Read The Instructions for How to do this on the WifiPineapple Website, But I don't Understand the Step Where Your Supposed To Power On The Device But Not Connect it to your pc... Any Help?
  4. Powered the tetra up out of the box, got a solid yellow light on power up, tried following setup instructions in Kali, no joy, setup through Windows 7 no joy. Windows 10, no joy. Ubuntu 16.04 no joy. Been searching forums but I have yet to find a solution. Cannot connect to either setup webpage or recovery webpage. Connected to uart, here is reset output: resetting... U-Boot 1.1.4 (Dec 22 2015 - 12:54:58) DB120 DRAM: sri Wasp 1.3 wasp_ddr_initial_config(249): (32bit) ddr2 init wasp_ddr_initial_config(426): Wasp ddr init done Tap value selected = 0xf [0x0 - 0x1f] 128 MB Top of RAM usable for U-Boot at: 88000000 Reserving 276k for U-Boot at: 87fb8000 Reserving 192k for malloc() at: 87f88000 Reserving 44 Bytes for Board Info at: 87f87fd4 Reserving 36 Bytes for Global Data at: 87f87fb0 Reserving 128k for boot params() at: 87f67fb0 Stack Pointer at: 87f67f98 Now running in RAM - U-Boot at: 87fb8000 Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x14 flash size 1MB, sector count = 16 Flash: 1 MB *** Warning - bad CRC, using default environment Now starting pci_init process pci_init_board: PCIe PLL not set for 40MHz refclk BOARD IS NOT CALIBRATED!!! pci_init finished In: serial Out: serial Err: serial Net: ag934x_enet_initialize... No valid address in Flash. Using fixed address No valid address in Flash. Using fixed address wasp reset mask:c02200 WASP ----> S27 PHY s27 reg init : cfg1 0x80000000 cfg2 0x7114 eth0: 00:03:7f:09:0b:ad athrs27_phy_setup ATHR_PHY_CONTROL 4 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 4 :10 eth0 up WASP ----> S27 PHY s27 reg init lan ATHRS27: resetting s27 ATHRS27: s27 reset done : cfg1 0x800c0000 cfg2 0x7214 eth1: 00:03:7f:09:0b:ad athrs27_phy_setup ATHR_PHY_CONTROL 0 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 0 :10 athrs27_phy_setup ATHR_PHY_CONTROL 1 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 1 :10 athrs27_phy_setup ATHR_PHY_CONTROL 2 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 2 :10 athrs27_phy_setup ATHR_PHY_CONTROL 3 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 3 :10 eth1 up eth0, eth1 Atheros on-chip NAND FLash Controller Driver, Version 0.1 (c) 2010 Atheros Communications, Ltd. Ath Nand ID[87fef17c]: 2c:48:00:26:89 Attempting to use unknown device Micronset ns -0x0-0x1000 ====== NAND Parameters ====== sc = 0x87fef158 bbt = 0x87f98538 bbt_size = 0x0 nf_ctrl = 0x405 page = 0x1000 block = 0x0 oob = 0x0 size = 0MB Setting 0xb8116290 to 0x20402d0f Hit any key to stop autoboot: 0 Loading from device 0: ath-nand (offset 0x0) Booting image at: 0x81000000 Image Name: MIPS OpenWrt Linux-3.18.23 Created: 2015-12-22 4:23:13 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 1965951 Bytes = 1.9 MB Load Address: 80060000 Entry Point: 80060000 Uncompressing kernel image... OK! No initrd ## Transferring control to Linux (at address 80060000) ... ## Giving linux memsize in bytes, 134217728 Starting kernel ... [ 0.000000] Linux version 3.18.23 (sebkinne@buildtop) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47951) ) #3 Tue Dec 22 05:23:06 CET 2015 [ 0.000000] bootconsole [early0] enabled [ 0.000000] CPU0 revision is: 0001974c (MIPS 74Kc) [ 0.000000] SoC: Atheros AR9344 rev 3 [ 0.000000] Determined physical RAM map: [ 0.000000] memory: 08000000 @ 00000000 (usable) [ 0.000000] Initrd not found or empty - disabling initrd [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x00000000-0x07ffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00000000-0x07ffffff] [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x07ffffff] [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: board=TETRA console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,256k(u-boot-env),256k(caldata),-(mb0);ar934x-nfc:2048k(kernel),-(ubi) rootfstype=squashfs noinitrd [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] Writing ErrCtl register=00000000 [ 0.000000] Readback ErrCtl register=00000000 [ 0.000000] Memory: 125796K/131072K available (2642K kernel code, 125K rwdata, 556K rodata, 188K init, 186K bss, 5276K reserved) [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS:51 [ 0.000000] Clocks: CPU:560.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:40.000MHz [ 0.000000] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688) [ 0.070000] pid_max: default: 32768 minimum: 301 [ 0.070000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.080000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.080000] NET: Registered protocol family 16 [ 0.090000] MIPS: machine is tetra [ 0.530000] registering PCI controller with io_map_base unset [ 0.540000] PCI host bridge to bus 0000:00 [ 0.540000] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff] [ 0.550000] pci_bus 0000:00: root bus resource [io 0x0000] [ 0.550000] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff] [ 0.560000] pci 0000:00:00.0: invalid calibration data [ 0.560000] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit] [ 0.570000] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref] [ 0.570000] pci 0000:00:00.0: using irq 40 for pin 1 [ 0.580000] Switched to clocksource MIPS [ 0.580000] NET: Registered protocol family 2 [ 0.590000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [ 0.590000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [ 0.600000] TCP: Hash tables configured (established 1024 bind 1024) [ 0.600000] TCP: reno registered [ 0.610000] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 0.610000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 0.620000] NET: Registered protocol family 1 [ 0.620000] futex hash table entries: 256 (order: -1, 3072 bytes) [ 0.650000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.660000] msgmni has been set to 245 [ 0.660000] io scheduler noop registered [ 0.670000] io scheduler deadline registered (default) [ 0.670000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled �[ 0.700000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 2500000) is a 16550A [ 0.710000] console [ttyS0] enabled [ 0.710000] console [ttyS0] enabled [ 0.720000] bootconsole [early0] disabled [ 0.720000] bootconsole [early0] disabled [ 0.730000] m25p80 spi0.0: found s25fl008k, expected m25p80 [ 0.730000] m25p80 spi0.0: s25fl008k (1024 Kbytes) [ 0.740000] 4 cmdlinepart partitions found on MTD device spi0.0 [ 0.740000] Creating 4 MTD partitions on "spi0.0": [ 0.750000] 0x000000000000-0x000000040000 : "u-boot" [ 0.750000] 0x000000040000-0x000000080000 : "u-boot-env" [ 0.760000] 0x000000080000-0x0000000c0000 : "caldata" [ 0.770000] 0x0000000c0000-0x000000100000 : "mb0" [ 0.770000] nand: No NAND device found [ 0.780000] ar934x-nfc ar934x-nfc: nand_scan_ident failed, err:-19 [ 0.790000] libphy: ag71xx_mdio: probed [ 1.390000] ag71xx-mdio.1: Found an AR934X built-in switch [ 1.430000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII [ 2.030000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd042, driver=Generic PHY] [ 2.040000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII [ 2.040000] TCP: cubic registered [ 2.050000] NET: Registered protocol family 17 [ 2.050000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 2.070000] 8021q: 802.1Q VLAN Support v1.8 [ 2.070000] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19 [ 2.080000] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [ 2.090000] Please append a correct "root=" boot option; here are the available partitions: [ 2.100000] 1f00 256 mtdblock0 (driver?) [ 2.100000] 1f01 256 mtdblock1 (driver?) [ 2.110000] 1f02 256 mtdblock2 (driver?) [ 2.110000] 1f03 256 mtdblock3 (driver?) [ 2.120000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 2.120000] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 78.370000] random: nonblocking pool is initialized That is were it hangs, now no LED lights at all, no further output from uart. same results via AC power, USB only, UART only, USB +UART, USB+AC, USB+AC+UART. I also tried to get it to load the factory reset bin via tftp, but it wouldn't see the directory as it states all interfaces are down. I'm probably making a complete n00b mistake, so please advise. Thank you for your time, Marcus
  5. I desided find my Bashbunny today and to update it to firmware 1.5 and find some nice scripts I could test on it. I tried the Password Grabber. After I run the PasswordGrabber on the Bashbunny and checked the lootfolder, I noticed it was alot of strange content in it. Alot of folders and other files that I could not open. Check attatched screen. After wondering about it, I was gonna check the size of it, and it says 56TB ? I am not able to delete the lootfolder from either windows or linux by rm -rv. I just get an errormessage that it's readonly and I don't have permissions to do that! Strange I have tried this: Remove the lootfolder Move the lootfolder to another folder, then delete (that's what I've doing on the screenshoots attatched to this post) Do a factoryreset on the bashbunny upto several time. (Unplug three times on green blink) Even upgraded by the bashbunny upgradetool and manually by downloading the .tar file and copy it into the root of the bashbynny Do any of you have any ideas how I can recover my bashbunny and hopefully bring it back to life?
  6. I have just reset my bashbunny and since then, my explorer shows me this! what's up?
  7. Apparently I've tried to update to 1.1 incorrectly. It has a solid green on startup then it turns blank. After three times it goes into recovery mode I am assuming. Then once there it blinks red for a while. Then it turns blank again. I've waited ten minutes tried to replug it in assuming something went wrong it it was done. But it never blinks or goes solid green or blue after the red blinking. But just now It was blinking red then started to alternate red to blue. Now it's blank again, I will wait another fifteen minutes before I try anything else. What exactly is going on? I am assuming it's either trying to recover then flash. I moved the upgrade contents to the root file system. I don't know exactly what went wrong. Easier way to understand the problem: Plug In > Solid Green > Blank LED ........ Ten minutes has passed.... Replug In > Solid Green > Blank LED ....... Ten minutes has passed.... Replug In > Solid Green Blank LED ...... Ten minutes has passed.... Replug In > Blinking Red > Couple of Minutes Passed > Blinking Red . Blinking Blue . Blinking Red > Couple of Minutes Passed > Blinking Red > Couple of Minutes Passed > BLANK LED!!!! Ten minutes has passed... Replug In > Solid Green > Blank LED Every time it tries to recover then it will try to boot three times and try to recover again. It will never fully boot up nor will Kali recognize the file system or that it's plugged in.
  8. Ok so I think there have been a problem with my bashbunny because I have had trouble installing both the tools and duckytools so what I would like is to reset it like it was when I got it, but using the recoverymode does nothing... All my files are still there, including those in udisk and /root/tools/ :/ Could anyone help me out?
  9. Played around with my bashbunny and installed tools. While I tried to setup a shared connection the LED started blinking red (Recovery mode). I have now been stuck in this mode for 15 minutes pls help :(
×
×
  • Create New...