python2004

Yes I tried really everything! Nothing worked! But today I tried a tipp of another forum's user who said to wait a few hours after flashing before trying to reboot. I left my MK V alone for 48 hours after last flash-attempt and YIPPPIEEEE!!! Today it booted quite normally and I also could install an upgrade! I tried the update to 2.0.3 (actually I am still a little bit afraid to try 2.0.4 again), but not using the web interface but using WinSCP for file transfer and Putty for sysupgrade command. I still don't understand what was the cause for this problem. May be there was something bad in the 2.0.4 upgrade that only disappears after some hours without power supply???!?! Is that possible?

yes now I looked after it and it really was your post. I read that much the last days so I didn't remember whose post it was ;-) Have you actually installed 2.0.4 now?

My problem ist SOLVED!!!! :grin: :cool: I let my MK V alone for the last two days and today it booted up quite normally!!! I read this today in another forum that some guy let his MK V alone for 48 hours and then ist was able to boot. There seemed to be something bad in memory since the update to 2.0.4 that disappeared with the pineapple not having power for some time.... I don't know what that could be?? Now I updated to 2.0.3 with WinSCP and Putty - not over the webinterface. I am nit sure whether I dare to update to 2.0.4 Is there any known issue with 2.0.4? I am really happy now and looking forward to playing around with my pineapple!!!

as some of you might have seen I am struggling with boot problems after the update to 2.0.4 I can do what I want - I cannot manage to get any connection. So my question is whether there is some sort of tutorial for setting up a connection to the MK V over serial? I didn't find any - only for the MK IV! Would it be possible to connect over serial, while it is not possible to connect via ethernet? May be in this way I could avoid a replacement. In a shop nearby I discovered a "USB to serial"-cable for a raspberry Pi, but that should be suitable for the pineapple, too?!

Do you think it should be possible to connect via serial while it is not possible to connect via ethernet? I only found a video instruction for flashing over serial for the pineapple IV

I sent a question to hak5 concerning a replacement 2 days ago but unfortunately no answer yet...

No unfortunately I cant clear it with recovery mode. It allows me to flash the 1.2.0 factory.bin but then gets stuck with the blue light blinking

unfortunately in my case it cannot be solved through a factory reset

Unfortunately the factory reset is not working either. When powering on with dip switches 2 and 3 down, I also only get the soild green and blinking blue led inifinitely....

It happened after upgrade to 2.0.4 over the air. The question is not what caused the problem but how could it be solved!! Nothing works! Neither the factory reset via dip-switches nor the flashing with the factory.bin via the recovery interface. But yes, I can start recovery mode and I can flash the bin with the recovery gui, but after that I have the blue led blinking infinitely again... I think my MK V must be replaced

It is a solid green light and the blinking blue one. I WAS able to connect to the MK V BEFORE the OTA-update to 2.0.4! Bute now I can do what I want - I always end up with that combination of green solid and blue blinking LED...

Is it really possible that it has to do with a defective power-adapter? What kind of defect should that be? Everything was possible until the OTA update of 2.0.4 Now I tried out ALL kind of things from flashing with 1.2.0 factory.bin to factory reset - dozens of videos all describing the same steps but alwasy ending up in that blue light blinking I wil try another power adapter in the evening, but I can hardly imagine that this should really solve the problem - although of course I hope so!

Has yout problem been solved? I am experiencing the same issue!

Bu´t isnt't that file an "UPGRADE"-file and not a FACTORY-File like the factory-1.2.0.bin??? The Recovery web interface does not accept Upgrade-bins?!?!

What does 9 from above mean?? Solid green and blinking blue appears when the device is awaiting acceptance of EULA?? I thought that means the device is booting up?

I use the adapter that came with the MK V. It seems to be ok because before the update it seemed to work properly. I a mnow trying to get some similar power source to test whether that could be the cause. Also ordered a USB-cable to use an external battery pack. If that doesn't help, I will have to return my MK V to the hakshop

In my case the blue light does not stop flashing at all! Even if I leave it alone for hours. The factory flash with the last DIP switch down basically works, but after that the blue led just does not stop flashing. Same issue with factory reset with dip 2 and 3 down... Yesterday i tried dip 1 up al others down and suddenly booting was successful. I could log in but after firmware update via webinterface same issue again!

now it was suddenly possible to boot and to log into the GUI again!! i randomly tried the DIP-combination: 1: UP 2: DOWN 3: DOWN 4: DOWN 5: DOWN and after 2 mins I got all lights flashing and I could log in again! I had to define a new password and everything was fine. Then I tried to run the firmware upgrade again with the web interface and same problem again!!! It seems to have an issue with the 2.0.4 update over the webinterface. I hope I can reset it with the factory image again...

what have you done that the blue LED stopped flashing?? I am experiencing exactly the same problem after upgrade and nothing works....

I have the same problem after updating the firmware yesterday. Before that everything worked fine. Independent what I am trying out (factory reset, unbricking guide, ...) - nothing works - it always ends up in the blue LED flashing infinitely

Is the routine described in the video abover also possible in the status of my MK V? with all DIPS up, I can't connect to 172.16.42.1:22 with putty...

I just tried the following: with the last DIP-switch down I connected to the recovery UI and flashed the 1.2.0 recovery-bin as described in the unbricking guide. That works, but when finished I get the blue light constantly flashing. I don't know whether that is normal behaviour... The message tells me to reboot with all DIP-switches up. Before I did so, I formatted the SD-card and put the 1.2.0 update.bin on it (after renaming it to "update.bin" and put a text file named "md5" with the hash code in it in the root directory too. then I do a reboot, but the blue light keeps flashing and flashing and flashing.......

the sd card is actually formatted as FAT32. Is that ok or does it need to be FAT? How can I create the md5-Files on a MAC? Just copy the MD5-hash in an empty textfile and save it as "MD5" without extension? What verison of files should I put on the SD-card after flashing the MK V with the 1.2.0 via recovery mode?

Hello everyone! I received my MK V yesterday and after the initial setup everything was working fine. I even installed some infusions and did some tests. Then I mentioned that there was a firmware update available and so I started the installation routine over the webinterface just like bowlofgravy described above. I had exactly the same things happen. I let the update install overnight (6 hours) but there only was that constant green and the blinking blue LED. So after that time I disconnected the MK V from the power supply and tried to reboot, but unfortunately since that moment I still only get that combination of the solid green and flashinbg blue light! I haver to say that my delivered MK V did not contain any Micro SD so I took one of mine (I formatted it via the webinterface). So I thought it might have to do with the SD card which was pretty old so I bought an new one today (16GB SDHC class 10). But the problem remains! Can anyone tell me what this combination of LEDs does exactly mean? I also tried the factory reset via DIP. Only the same combination of lights. I also tried to flash the firmware 1.2.0 with the last DIP down - that works (I get into the recovery-webinterface). Until about 90% upgrade progress all four LEDs are active, but at about 90% progress I get the good old solid greed with flashing blue again. The Webinterface says the update is finished and I can restart the MK V with all DIPs up again and reboot, but that also results in the neverending LED-combination with the blue LED flashing. What exactly has to be on the SD-card? In different threads I read about ZIP-Files with the bin and MD5-Files in it, but on the download-page that all these links refer to there are only the bin-Files?! I also tried to create the MD5-Files by myself but whatever I tried it did not work. Please help me! I cannot imagine that - after the MK V worked just fine before the update - it is now damaged or something like that?!