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?