# Boot Loop with ESP-WROOM-32 **URL:** \ **Category:** Issues\ **Created:** [June 12, 2024, 7:12pm UTC](https://wled.discourse.group/t/boot-loop-with-esp-wroom-32/12027 "2024-06-12T19:12:37Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![NikolasE](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/nikolase/32/7888_2.png) [@NikolasE](https://wled.discourse.group/u/NikolasE)\ **Post date:** [June 12, 2024, 7:12pm UTC](https://wled.discourse.group/t/boot-loop-with-esp-wroom-32/12027/1 "2024-06-12T19:12:37Z")
Hey! I’m trying to install WLED (from binaries) to some ESP-Wroom-32 (aliexpress…), but they end up in a boot loop. Flashing looks good: "\> esptool.py write\_flash -z 0x1000 ./WLED\_0.14.3\_ESP32.bin esptool.py v4.7.0 Found 2 serial ports Serial port /dev/ttyUSB1 Connecting… Detecting chip type… Unsupported detection protocol, switching and trying again… Connecting… Detecting chip type… ESP32 Chip is ESP32-D0WD-V3 (revision v3.1) Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None Crystal is 40MHz Mac, etc " The board however ends up in a boot loop: " rst:0x10 (RTCWDT\_RTC\_RESET),boot:0x13 (SPI\_FAST\_FLASH\_BOOT) configsip: 0, SPIWP:0xee clk\_drv:0x00,q\_drv:0x00,d\_drv:0x00,cs0\_drv:0x00,hd\_drv:0x00,wp\_drv:0x00 mode:DOUT, clock div:2 load:0x3f400020,len:264984 ets Jul 29 2019 12:21:46" During debuggin, I found this page an especially this " If your ESP32 board has the GPIO6, GPIO7, GPIO8, GPIO9, GPIO10, and GPIO11 pins, **you must not use them** because they are connected to the flash memory of the ESP32" In a minimal program, I could send the esp in the bootloop if I only configure one of those pins as output (pinmode(6, OUTPUT). Is there any chance that WLED configures one of those pins as output during startup? I’m a bit running out of ideas, anything else I could test? ---
**Author:** ![dedehai](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/dedehai/32/7265_2.png) [@dedehai](https://wled.discourse.group/u/dedehai)\ **Post date:** [June 12, 2024, 7:15pm UTC](https://wled.discourse.group/t/boot-loop-with-esp-wroom-32/12027/2 "2024-06-12T19:15:58Z")
did you try this to install? [https://wled-install.github.io/](https://wled-install.github.io/) ---
**Author:** ![NikolasE](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/nikolase/32/7888_2.png) [@NikolasE](https://wled.discourse.group/u/NikolasE)\ **Post date:** [June 12, 2024, 7:40pm UTC](https://wled.discourse.group/t/boot-loop-with-esp-wroom-32/12027/3 "2024-06-12T19:40:12Z")
No, none of my boards (just also tested with an ESP8266 with a working WLED installation) is recognized as a device in Ubuntu/Chromium. Which binary should I test and why would this give a different result than the esptool? ---
**Author:** ![C0oL3r](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/c0ol3r/32/7889_2.png) [@C0oL3r](https://wled.discourse.group/u/C0oL3r)\ **Post date:** [June 13, 2024, 12:02am UTC](https://wled.discourse.group/t/boot-loop-with-esp-wroom-32/12027/4 "2024-06-13T00:02:17Z")
I think you should flash it at 0x10000 not 0x1000, i made that mistake just a few days ago. Erase flash, flash bootloader again and flash wled at 0x10000 ---
**Author:** ![NikolasE](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/nikolase/32/7888_2.png) [@NikolasE](https://wled.discourse.group/u/NikolasE)\ **Post date:** [June 13, 2024, 6:42am UTC](https://wled.discourse.group/t/boot-loop-with-esp-wroom-32/12027/5 "2024-06-13T06:42:35Z")
You are right… It really was just a typo. Thanks!