Closed speedtoys closed 6 months ago
Hey. Marauder is one of the most used apps, wouldn't it be stupid if we release with a broken marauder?
Unplug the board, if that doesn't fix it reflash it via the ESP Flasher in the GPIO folder..
@ivanrylov Apps->WiFi->Marauder
It's all the way at the bottom
just saw that the person saying its resolved is not OP
@speedtoys do this
Hey guys I tried all of the advices flashed marauder even reinstalled it but it still seems to not scan anything. I'm currently using unleashed firmware if you know how to fix it let me know. Thank you all
@jiriceKKK Marauder works fine. You are clearly doing something wrong.
Reflash your board. open the app in APPS->WIFI->MARAUDER
I'm seeing the same issue as @speedtoys
I flashed XFW-0052 08-12-2023 on the F0. On the Dev board, I flashed Marauder 13.6 via fzeeflasher.github.io, successfully based on the messages. I did this by connecting the board directly to the computer (without the F0)
---> Flashing firmware.
Image header, Magic=0xE9, FlashMode=0x02, FlashSizeFreq=0x2F
Writing data with filesize: 926048
Erase size 926048, blocks 57, block size 0x4000, offset 0x10000, encrypted no
Took 11772ms to write 926048 bytes
Erase size 0, blocks 0, block size 0x4000, offset 0x0000, encrypted no
---> Finished flashing firmware.
---> FLASHING PROCESS COMPLETED!
When I go to Apps->WiFi->[ESP32] WiFi Marauder
and try scan, nothing happens.
When I try to flash from the F0 itself, Apps -> GPIO -> Quick Flash -> WiFi Dev and choose Marauder (has Evil Portal)
, I get
Cannot connect to target. Error: 2
Make sure the device is in bootloader/reflash mode, then try again.
When I disconnect the board, hold the boot button, then reconnect, release the boot button, and try again, the same thing happens.
Can anyone describe possible diagnosis steps/different things to try?
PS: I got it work as follows:
Also, when everything is powered down, and I connect the wifi board to the F0, then connect via USB to the computer, it will also not work. Disconnecting from the computer makes it start working, but the reconnecting it doesn't make it stop working.
Very odd. Wish there was more diagnostic output.
you should NEVER have the wifi board connected to the PC and flipper at the same time when flashing it...
@godmar open esp flasher, then connect the board to flipper while holding the boot button. You need to use the quick flash option appropriate for your board, if you need to use the boot button, you most likely do not have an official WiFi dev board. Look at the chip, it most likely says "wroom". So use the "wroom" quick flash option. Then the apps in WiFi folder will work correctly.
Thanks for the replies. I ordered the official WiFi dev board from the official site. From what I can see, the chip reads ESP32-S2-WRQVER
if I'm looking at the correct label:
@godmar open esp flasher, then connect the board to flipper while holding the boot button. You need to use the quick flash option appropriate for your board,
When I tried this procedure while neither board nor F0 were connected via a USB cable, it worked. (Although it doesn't seem to have the latest Marauder version, it flashed v0.13.5 instead of v0.13.6.)
yeah that board supports automatic bootloader mode. your issue was being plugged in. and yes, marauder is updated along with the flipper firmware. use the devbuilds if you need something newer.
yeah that board supports automatic bootloader mode. your issue was being plugged in. and yes, marauder is updated along with the flipper firmware. use the devbuilds if you need something newer.
Just to clarify: the issue was the WiFi Dev board being plugged into the USB, correct?
It doesn't hurt to have the F0 plugged in and I can be using qFlipper, or do I need to unplug the F0 as well?
board was the issue
just saw that the person saying its resolved is not OP
@speedtoys do this
1. Plug board to flipper 2. Apps > GPIO > ESP Flasher > Quick Flash > WiFi Dev> Marauder 3. When done, back out 4. Apps > WiFi > Marauder 5. Everything works as intended
These are the correct steps that got my board to work. Yall are assholes in this thread.
@f0rg-02 It didn't work.
Describe the bug.
Just installed XFW-0052_09122023 using the downloaded Qflipper image, and this was after installing the same via WWW, just to make sure.
I have the ESP32, and in prev firmware it worked very well.
But when I start it and do an AP scan, it just sits there telling me to 'Press BACK to send stopscan' and no APs show up.
When I go to list APs, there are none to list.
The flipper installed code says 08122023, while the latest release says 09122023. Just something I noticed.
Reproduction
Pretty simple, application doesnt do anything, no significant steps other than opening and trying to use it.
Target
No response
Logs
No response
Anything else?
No response