Jump to content

Cannot Flash Device


xpelican

Recommended Posts

Posted

Hi all,

I'm trying to perform a firmware recovery on my device because I cannot remember my password.

 

Password recovery method did not work. Holding down the button for 7 seconds does not make it flash in any color except blue.

So I tried the firmware recovery method. Holding down the button, I plug the device in, but again, nothing but blue LED.

 

Can anyone please advise? I only used this device once, surely it can't have been broken this quickly? I can still see the AP and go to the administration panel, just can't remember my password so I need to reset somehow.

 

Thanks in advance!

Posted

It's not rocket science really, just press the button and apply power. The LED should blink red, then release the button. Try using something else than your finger if you have problems pressing the button properly. It's not difficult though, I never fail when doing this and I have done it a "few" times. Don't press the button for too long. If you keep pressing it, the Pineapple will go to the "blue LED state". Press and hold for a few seconds, then release it.

Posted

Yeah but it's never showing red, at all. Only blue. I'm supposed to see it blink red before it turns blue again, but mine doesn't do that.

I have no problems pushing the button hard enough, I push on it hard until I hear it "click". I even used a pen tip etc. to make sure it's being pushed, it's definitely pushed.

Posted

It should not turn blue. When the red blinking has started, it should stay that way (solid red though as the button is released after three red blinks) and you can continue the recovery procedure. Anyway, if you aren't successful, then submit a support ticket to get it all resolved.

  • 2 weeks later...
Posted

Having a similar issue. I'm using Linux. When I unplug my pineapple, I hold down the putton. As I hold down the button, I re-insert the USB-C plug (note that the USB-A plug will not work to power the device). After I re-insert the USB-C plug, while holding the button at the same time, on mine, the blue LED, which was off, lights up with a RED light, and flashes about every second.

According to the procedure, we are meant to let this flash red three times. After letting it flash the required three flashes, we are supposed to let go, and the LED is supposed to display a "rainbow" color. On mine this does not work either. 

On mine, the blue light comes back on, and the blue light begins to flash. It flashes for at least 30 seconds, then becomes solid.

When I attempt to log into the device, using the IP adress, 172.16.42.42:80 - with a browser, the site is not reachable. There is no connection. Since this didn't work, I tried this over again with an old laptop that I use for a back up computer. I went through the entire reset procedure again, using the terminal commands: 

root# sudo ip link set eth0 down
root# sudo ip addr add 172.16.42.42/255.255.255.0 dev eth0
root# sudo ip link set eth0 up
root# ifconfig

So, now, the same result - with a slight difference (may be that this was going on with the desktop, but didn't see it till I tried the laptop). I had already switched off the laptop's WIFI with the physical switch on the side of the laptop - and there was no ethernet plugged in. I did this to make sure that the pineapple would be the only connected device. So, when trying to navigate the laptop's browser to the pineapple's IP (172.16.42.42:80), not only did that fail, but strangely enough, the laptop was online. I could browse with it. The pineapple was acting like a WIFI dongle.

To verify this, I browsed to a "What's my IP" site, and verified that the pineapple had logged into my network and was providing the laptop with an internet connection. When I turned off my modem, the laptop lost the internet connection, but the network, using the pineapple was still active. Still, even then, I could not navigate into the pineapple's IP address. When I turned the modem back on, the pineapple, once again, began to provide the laptop with an internet connection. This is useful, but not wanted, as the laptop already has an internal WIFI receiver.

So, I re-started the same procedure, but this time, after disconnecting the pineapple, I held down the reset button and let the red light flash for a full 30-40 seconds. The result? No difference, I still cannot navigate to 172.16.42.42:80.

All I want to do is reset the pineapple and begin to configure it. What is my next step?

Thanks in advance. 

בס'ד

 

 

Posted
1 hour ago, Kelikaku said:

Having a similar issue. I'm using Linux. When I unplug my pineapple, I hold down the putton. As I hold down the button, I re-insert the USB-C plug (note that the USB-A plug will not work to power the device). After I re-insert the USB-C plug, while holding the button at the same time, on mine, the blue LED, which was off, lights up with a RED light, and flashes about every second.

According to the procedure, we are meant to let this flash red three times. After letting it flash the required three flashes, we are supposed to let go, and the LED is supposed to display a "rainbow" color. On mine this does not work either. 

On mine, the blue light comes back on, and the blue light begins to flash. It flashes for at least 30 seconds, then becomes solid.

When I attempt to log into the device, using the IP adress, 172.16.42.42:80 - with a browser, the site is not reachable. There is no connection. Since this didn't work, I tried this over again with an old laptop that I use for a back up computer. I went through the entire reset procedure again, using the terminal commands: 

root# sudo ip link set eth0 down
root# sudo ip addr add 172.16.42.42/255.255.255.0 dev eth0
root# sudo ip link set eth0 up
root# ifconfig

So, now, the same result - with a slight difference (may be that this was going on with the desktop, but didn't see it till I tried the laptop). I had already switched off the laptop's WIFI with the physical switch on the side of the laptop - and there was no ethernet plugged in. I did this to make sure that the pineapple would be the only connected device. So, when trying to navigate the laptop's browser to the pineapple's IP (172.16.42.42:80), not only did that fail, but strangely enough, the laptop was online. I could browse with it. The pineapple was acting like a WIFI dongle.

To verify this, I browsed to a "What's my IP" site, and verified that the pineapple had logged into my network and was providing the laptop with an internet connection. When I turned off my modem, the laptop lost the internet connection, but the network, using the pineapple was still active. Still, even then, I could not navigate into the pineapple's IP address. When I turned the modem back on, the pineapple, once again, began to provide the laptop with an internet connection. This is useful, but not wanted, as the laptop already has an internal WIFI receiver.

So, I re-started the same procedure, but this time, after disconnecting the pineapple, I held down the reset button and let the red light flash for a full 30-40 seconds. The result? No difference, I still cannot navigate to 172.16.42.42:80.

All I want to do is reset the pineapple and begin to configure it. What is my next step?

Thanks in advance. 

בס'ד

 

 

UPDATE: For some reason, it just started working, on the desktop, at the same time as I was using the pineapple as a wireless dongle. I just logged into it, and the PC is not connected to the ethernet in any way, other than through the USB on the pineapple. I'm online now, through the pineapple, and logged into its configuration screen: 

Just to show I'm not crazy, here is the output from ifconfig in my terminal. The pineapple is serving as eth2:

root# ifconfig
eth2      Link encap:Ethernet  HWaddr 00:13:37:A7:34:DB  
          inet addr:172.16.42.248  Bcast:172.16.42.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:104056 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83928 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:55035920 (52.4 MiB)  TX bytes:20708276 (19.7 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:483574 errors:0 dropped:0 overruns:0 frame:0
          TX packets:483574 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:645227918 (615.3 MiB)  TX bytes:645227918 (615.3 MiB)

In any case, I'm not sure why the pineapple is now responding. Maybe the ip address I was using was the issue (although it's the one in the directions - 172.16.42.42:80). It began to work while I was reading another forum post, and I clicked this link:

http://172.16.42.1:1471/assets/icons/logo.png

Then I was able to navigate back to 1:1471, and I was greeted with the login window of the pineapple. It was reset. My old username and password were no longer active. I had to use username: root, and password: hak5pineapple. Hope this may help someone.

Posted
53 minutes ago, Kelikaku said:

Maybe the ip address I was using was the issue (although it's the one in the directions - 172.16.42.42:80)

Just curious, where did you find that information? The Pineapple always uses 172.16.42.1 and I've never read any documentation that says the Pineapple has the .42 address, it's the device from which you are connecting to the Pineapple that should have the .42 address. You have even posted terminal commands where you set the .42 address for your computer.

2 hours ago, Kelikaku said:

When I attempt to log into the device, using the IP adress, 172.16.42.42:80 - with a browser, the site is not reachable. There is no connection. Since this didn't work, I tried this over again with an old laptop that I use for a back up computer. I went through the entire reset procedure again, using the terminal commands: 

root# sudo ip link set eth0 down
root# sudo ip addr add 172.16.42.42/255.255.255.0 dev eth0
root# sudo ip link set eth0 up
root# ifconfig

So, now, the same result - with a slight difference (may be that this was going on with the desktop, but didn't see it till I tried the laptop). I had already switched off the laptop's WIFI with the physical switch on the side of the laptop - and there was no ethernet plugged in. I did this to make sure that the pineapple would be the only connected device. So, when trying to navigate the laptop's browser to the pineapple's IP (172.16.42.42:80)

 

Posted
49 minutes ago, dark_pyrro said:

Just curious, where did you find that information? The Pineapple always uses 172.16.42.1 ...

I've never read any documentation that says the Pineapple has the .42 address ...

https://docs.hak5.org/wifi-pineapple/faq/factory-reset-and-recovery#assigning-a-static-ip-address

Assigning a Static IP Address
Linux
Assign the WiFi Pineapple's interface a static IP address of 172.16.42.42. More in-depth instructions can be found in the
Linux Setup page.
Windows
Assign the WiFi Pineapple's interface a static IP address of 172.16.42.42. More in-depth instructions can be found in the Windows Setup page.

===============================
https://docs.hak5.org/wifi-pineapple/setup/connecting-to-the-wifi-pineapple-on-linux#configuration-via-gui

hak5image.png

===============================
https://docs.hak5.org/wifi-pineapple/setup/connecting-to-the-wifi-pineapple-on-linux#configuration-via-cli
$ sudo ip link set eth0 down
$ sudo ip addr add 172.16.42.42/255.255.255.0 dev eth0
$ sudo ip link set eth0 up

================================

In the instruction video - from Kitchen himsel, making the exact sme error:

 

------------------------------------------------

Pretty consistent, it is in the Hak5 documentation as well as in the instruction video. Looks like we found a blooper.

 

Posted

No, you misunderstand it. 172.16.42.42 is for the interface of the computer that you attach/connect to the Pineapple, not the address of the Pineapple itself (which is 172.16.42.1). Trying to access the Pineapple at 172.16.42.42:80 just makes you try to connect to your own PC on port 80 and since you most likely is not having any service running on your PC that answers on port 80, well, you won't get any response.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...