DON'T DO THIS ON RECEIVERS. Only do it on modules. For receivers, flash to 2.5.1 first, then 3.x. If you flash a receiver with repartitioner, it will be bricked, and you will have to flash it again using ftdi or passthrough to recover it.
Exactly what happened. I bricked my AIO Betafpv f4 5a ELRS. I guess i was in a hurry and missed this information before flashing. So how exactly do you unbrick an Elrs receiver on a AIO Board? I have'nt found any Information regarding this. I tried ELRS Configuration with the Passthrough option and the correct Port selected but it still would not work. It says cannot detect RX target, blindly flashing. Then finally a Flash error message. Is there a way to unbrick an AIO Elrs board? I would be happy to have an info on this.
I actually solved this using this method: Press and hold the button on FC Plug in USB Open Betaflight configurator, go to firmware flasher tab Let go of the button on FC Click Exit DFU mode Close BF configurator Build and flash via passthrough using the ELRS Configurator Then everything worked again. 😀
I bricked my DIY ELRS PWM receiver using repartitioner.bin file, and was later able to unbrick it also. Followed these steps to bring it back to life: 1) Connect your FTDI to receiver's tx/rx/+/- pins. On receiver, pin 2 and 3 are usually Tx and Rx. You need to connect Tx to Rx and Rx to Tx. 2) Press and hold Boot button (firmly, very important) and connect the FTDI to computer. The receiver will enter in boot mode. If your receiver LED was already solid light, you wont see any difference. But in other cases it should go into solid green status. 3) Using ExpressLRS configurator or any other flashing utility, flash the required ELRS firmware to your receiver. 4) You should get a successful message and receiver will reboot into a normal slow blinking mode.
hey these videos also help for when people ask in groups online how to fix this instead of searching it, now we can just paste The Bardwell video so that people can learn something today
I ran into this last week but, at the time, there was nothing about it on my Google searches. And did a quick search for 'bad file size' on the wiki and came up with nothing. Didn't have much time to mess with it without sacrificing fly time. Not saying I wouldn't have found it but glad this video showed up on my feed today. And I'm happy to be a Patreon supporter!
Wow, thank you, I was stuck on this problem for so long thinking there was an issue with the space on my SD card lol. I took a journey in the wrong direction trying to fix it. Just donated to your Patreon, your videos have been a tremendous help.
Thank you very much for your videos, I have been following you for a long time from Spain and almost no one could fly without you. Hahaha, I have that problem but in an rx happymodel, thanks for your help and happy new year
OMG, Joshua, I got this exact problem and your video googles first, way earlier than I managed to reach their wiki, so, sure I came to your channel :) thanks for making it short and precise! Sounds like I'm really going to join Patreon very soon!
Another thing you can probably do is upgrade thru the release candidates rather than jumping from 2.xxx to 3. That's what I had to do prior to launch-- go from 2.71 to 3rc1, then 3rc2. From 3rc1 to 3rc2 they did a change to fix one thing which caused this thing
Just over came this with a Betaflight Micro 1w TX, upgrading from 2.5.0 to 3.2.1, by going to the "support" tab in the ELRS configurator and "Clear PLatformio Dependencies" and "clear firmware files" and rebuilding from scratch. THEN flashing.
Great video man!.. I'm glad your always making videos about new and cool products! And videos like these too .. I think it's a little old now tho sooo .. you don't still have to do this do you? If yours already has 3.x ? ?
I have to assume you're just being sarcastic and joking. Because the title of this video says THIS WILL BRICK YOUR RX ONLY DO THIS TX and there is a pinned comment to that effect. At that point, any responsibility is on you.
Aaaah! Where were you last night when I was fighting this? 😂 Thanks Joshua, and yes, I was that person you were talking about at the start of the video!
Thank You this worked.. Now my problem is the LUA for Elrs on the older Taranis X9d plus 2018 does not work, the Lua size is too big.. OpenTx will work once if your lucky, EdgeTx will just say Not enough memory.. Surely more people have this problem? Thanks JB 👍👍
Tried the repartitioner, but got a "Not enough data uploaded!" error instead. Oscar says downgrade to v2 first then flash again, but it was for RX, should I do it to my Happymodel TX module on my TX16s over WIFI?
Flashing the repartioner.bin didn't work for me (HappyModel Non-Pro). It gave an additional error and stonewalled. I forget the actual error message but the workaround for me was to flash down to 2.0 then from there flash to 3.0. Worked for me.
I had a similar issue with the same module. After the "target mismatch" error, another error popped up. I think it said something about too few bytes uploaded. And it wouldn't flash the repartioner.bin file. I tried it multiple times without success. I was running ELRS 2.5.0. I upgraded the firmware to 2.5.1 and it let me flash the repartioner.bin file. Then I was able to upgrade to ELRS 3.
I think most people when facing a problem just focus on the "help me" instead of searching and understanding the reason of the problem. This issue was reported and the solution is on the elrs page, people just don't read. Joshua Bardwell always to the rescue. This one I bet will be shared a lot of times answering the same question all over the internet.
The build is the same regardless, as far as I know. The only difference is what happens if you hit build and flash. If you only intend to build, I don't think it matters.
@@JoshuaBardwell So, I had the same problem trying to flash 3.0.1 so I tried flashing this repartitioned bin and when it finished flashing it said wait for it to reboot before unplugging from FC and powering down.. well the light went out but never came back on .. waited 45 minutes and still nothing, never rebooted. So I unplugged the FC,plugged it back in, and surprise surprise the RX was bricked 🤦🏽♂️ I have the happymodel ep1 so I soldered the pad and ground together to put it in boot loader mode,made sure telemetry was off and tried to flash 3.0.1 via betaflight pass through but no luck.. not sure what to do now because it’s not like I can connect to Wi-Fi in boot loader mode and try flashing the repartitioned bin again🤷🏽♂️ Any chance The Godfather of FPV knows how to fix this? 🥺🙏🏽
“It’s not gonna work” has been my experience with ELRS in general. I am optimistic for it’s maturity and reliable hardware partners. I want to fly not futz and ELRS just as too many issues for me IMO. I know it works… just not on my quads.
Did this with an ep1 reciever and it stopped transmitting the wifi signal after flashing the partitioner.bin. Tried fixing it by bridging the pads on the ep1 and use betaflight passthrough but can't flash and get the wifi back.
I kind of wish elrs was like a cheap dji ecosystem. What I mean is when I get a new vista quad it just pairs so seamlessly to my V1 goggles and black remote but the hours I wasted on an elrs happymodel mobula7 after hours or frustration it just wouldn't bind, even as somebody who owned and ran elrs quads I just gave up and broke it down for spares. After that I swore I'd never elrs again.
hello, i ordered a new tx pro happymodel. I started again like the tutorial. same problem after the flash with partitioner.bin loses the wifi connection impossible to restart in wifi. and now I have a message: loading.... and nothing else
So with the recent HappyModel Moblite7 HDZero V3 running firmware 3.0.1. I get the ERROR[4]: Not Enough Space. I am trying to update to 3.3.1. In the comments you suggest flashing to 2.5.1 first, then 3.x. I am already in 3.0.1, should I flash back to the 2.5.1 in order to rectify the "Not Enough Space" error, then update to 3.3.1?
I didn't get a message. It said update complete on iflight commando 8 but now my quad won't arm. When I reconnect it shows down under Network devices it's on version 3.0.0
So, I had the same problem trying to flash 3.0.1 so I tried flashing this repartitioned bin and when it finished flashing it said wait for it to reboot before unplugging from FC and powering down.. well the light went out but never came back on .. waited 45 minutes and still nothing, never rebooted. So I unplugged the FC,plugged it back in, and surprise surprise the RX was bricked 🤦🏽♂️ I have the happymodel ep1 so I soldered the pad and ground together to put it in boot loader mode,made sure telemetry was off and tried to flash 3.0.1 via betaflight pass through but no luck.. not sure what to do now because it’s not like I can connect to Wi-Fi in boot loader mode and try flashing the repartitioned bin again🤷🏽♂️
I bumped similar problem with hglrc elrs rx yesterday . RX was bricked and wifi was not available. Betaflight passthru did not work either. I have FTDI usb-serial adapter and could flash the bricked RX with erls configuration using UART flashing method.
Hey Josh, a wild attempt to get a response off an old video. I’m currently trying to bind my Cinelog 35 ELrs 2.4g with my Commando 8 2400tx module. I come to the conclusion the quick bind method didn’t work because they are on different firmwares. The receiver being 3.2 firmware and the Commando 8 being 2.4 firmware (factory) I went to flash my TX module straight to 3.3 the current latest and now I can’t open my ExpressLrs tools menu to bind or even access the wifi to reflash firmware. I have only noticed after watching this video and going onto the Config guide that I needed to do this 2.51 firmware first before upgrading to firmware 3.0 and later. I’m stuck. What should I do next and how do I get back the Expresslrs script and reflash my module when I can’t access wifi pass through??! Hoping I can hear back from you. Thanks in advanced. I will definitely be paying forward to the patrion if you help lead me in the right direction. 👍🏽
i jsut opened it up. switched off switches 1 and 2 and switched on switch 5 and 6 for flashing. flashed it and put the switches back to original order.
I tried to update 3.2.1 firmware for elrs micro 1w module. But now the module has been suspended, the oled screen is not displayed. Is there any way to fix it?
Hi I was flashing the external module and it seems I make a mistake when selecting the bin flash file. I connect the module to USB-c and also try connecting to the external bay (jumper t pro) and Screen module is not turning on, but I let me to connect to generated wifi SSID. How could I recover the external module?
Does anyone have any idea why my PC wont connect to my transmitter WiFi? It shows up in networks, and when I enter the password (expresslrs) my PC says, Cannot connect to this network. I cant seem to find anyone else having this issue
Read the entire title of this video :-( THIS WILL BRICK YOUR RECEIVER. Read the pinned comment at the top of the comments section. This is only for modules. You need to re-flash your receiver using either serial passthrough or a programming adapter. ua-cam.com/video/TzAaYg47TSU/v-deo.html
@@JoshuaBardwell Yes I read that after the fact unfortunately. So I'm stuck without a FTDI programming board which I don't have? I'll order one but once I get it, not do I hook it up on an all in one board? I just flashed this to my brand new pavo pico 2.0 pro. I'm so mad at myself. I only did this because I got the not enough space error when trying to flash the receiver.
I've gone to both the expresslrs website and the github expresslrs/expresslrs wiki and can find no mention of not enough space or partition. Not even the troublshooting page of the expresslrs website mentions it?? I suck!
If you search "expresslrs not enough space" on Google, there are five or ten issues on the elrs github repo about the issue. It's also, mentioned in the release notes for elrs 3.0
It's me from the future. Flash to 3.0.0 first after 2.5.1 instead of latest (HM TX24pro) Didn't work for me to go to the latest. Had to recover over the internal micro usb (flashing over UART) 2.5.1 is possible this way.
Help! After downloading the repartitioner I couldn’t get the WiFi signal to come back I waited about 6-7 seconds after it completed before unplugging it??
struggling, the repartition update worked, but the module no longer shows up on WIfi, either by usb or on the radio. ELRS is killing me. I honestly can't believe how buggy this entire elrs world is
"Hello Joshua! I've installed the Repartitioner on an HGLRC Draknight, UART ExpressLRS 2.4G, and now I can't connect via wifi... perhaps I've messed it up?? THANK YOU!!"
hello, thank you for the video, unfortunately after flashing with repartitioner.bin I restarted my tx16s before flashing with firmware 3.0.0. now I have a screen with the message: loading.... Do you know how to reset? If it's possible
Thank you, so I have your radio with elrs v2 I partition that, then once partitioned, drop the v3 Lua into the sd card and then run the update as per normal and woolah , I have learnt something today ;-) Thank you again for your commitment to this sport, I have learnt so much and we all appreciate your dedication.
It can't be done fully automatically - you need to flash a separate repartitionwr firmware to undo the manufacturers screwup, and then put the device back into update mode once that's done for the actual update once its rebooted a couple of times.
Quick question. Do you run this update on the receiver's too? After months of fighting with my computer (Adobe wanted to interfere and i couldn't figure it out) I finally got 3.0 on my module with a binding password. I went to upgrade the receiver this morning and got the same error message for the receiver too. Do I partition it too?
@@georgepf Me to... I've bricked 2 receivers now trying to sort the issue out... So it's not as easy as it sounds here... just to repartition the receiver.
DON'T DO THIS ON RECEIVERS. Only do it on modules. For receivers, flash to 2.5.1 first, then 3.x. If you flash a receiver with repartitioner, it will be bricked, and you will have to flash it again using ftdi or passthrough to recover it.
Exactly what happened. I bricked my AIO Betafpv f4 5a ELRS. I guess i was in a hurry and missed this information before flashing. So how exactly do you unbrick an Elrs receiver on a AIO Board? I have'nt found any Information regarding this. I tried ELRS Configuration with the Passthrough option and the correct Port selected but it still would not work. It says cannot detect RX target, blindly flashing. Then finally a Flash error message. Is there a way to unbrick an AIO Elrs board? I would be happy to have an info on this.
@@brilliantyoungminds8111 Re-flash it using pass-through or FTDI adapter.
I actually solved this using this method:
Press and hold the button on FC
Plug in USB
Open Betaflight configurator,
go to firmware flasher tab
Let go of the button on FC
Click Exit DFU mode
Close BF configurator
Build and flash via passthrough using the ELRS Configurator
Then everything worked again. 😀
@@brilliantyoungminds8111 bei mir hat es leider nicht geklappt ewig fehler :(
I bricked my DIY ELRS PWM receiver using repartitioner.bin file, and was later able to unbrick it also. Followed these steps to bring it back to life:
1) Connect your FTDI to receiver's tx/rx/+/- pins. On receiver, pin 2 and 3 are usually Tx and Rx. You need to connect Tx to Rx and Rx to Tx.
2) Press and hold Boot button (firmly, very important) and connect the FTDI to computer. The receiver will enter in boot mode. If your receiver LED was already solid light, you wont see any difference. But in other cases it should go into solid green status.
3) Using ExpressLRS configurator or any other flashing utility, flash the required ELRS firmware to your receiver.
4) You should get a successful message and receiver will reboot into a normal slow blinking mode.
hey these videos also help for when people ask in groups online how to fix this instead of searching it, now we can just paste The Bardwell video so that people can learn something today
I did solve it for myself... By watching your video!!! Don't give me your attitude okay. Here's a cup of coffee
I ran into this last week but, at the time, there was nothing about it on my Google searches. And did a quick search for 'bad file size' on the wiki and came up with nothing. Didn't have much time to mess with it without sacrificing fly time. Not saying I wouldn't have found it but glad this video showed up on my feed today. And I'm happy to be a Patreon supporter!
I ran into this a few days ago and had to solve it myself. Glad to see you getting the information out to the masses.
As usual you are correct. I came here before reading the wiki. Thank you sir!!!
Thanks!
Wow, thank you, I was stuck on this problem for so long thinking there was an issue with the space on my SD card lol. I took a journey in the wrong direction trying to fix it. Just donated to your Patreon, your videos have been a tremendous help.
❤Thank you so much JB . I was struggling with it for days and couldn't find until I remember you teach something everyday! Thank you very much .
Thank you so much for your hard work very happy I chose your radio and will continue to buy your merch!🙌🏾🙌🏾
Great video. I had 2.5.1 running because of this… Now updated to 3.0.1. Thank you
Thank you very much for your videos, I have been following you for a long time from Spain and almost no one could fly without you. Hahaha, I have that problem but in an rx happymodel, thanks for your help and happy new year
Lifesaver tip, Joshua. Thanks! All the best!
OMG, Joshua, I got this exact problem and your video googles first, way earlier than I managed to reach their wiki, so, sure I came to your channel :) thanks for making it short and precise! Sounds like I'm really going to join Patreon very soon!
Thanks JB… your the go to source on our block.
This video needed to come out yesterday… it would have saved me bugging the devs last night!
Literally this morning I was trying to do this, thank you!
Excellent tutorial, Joshua! Thanks!!! 😊
Stay safe there with your family! 🖖😊
So awesome i havn't tryed flashing 3.0 but i m probably trying to Do this now nice Videos Keep it up
Another thing you can probably do is upgrade thru the release candidates rather than jumping from 2.xxx to 3. That's what I had to do prior to launch-- go from 2.71 to 3rc1, then 3rc2. From 3rc1 to 3rc2 they did a change to fix one thing which caused this thing
oh yeah is this true? sounds less intimidating lol
I tried doing that last week from 2.51 to RC1 and RC2 and that didn't work. Wonder if 2.7x repartitions the drive automatically?
Are you sure that will work ??
Gosh, this guys knows everything!!
Just over came this with a Betaflight Micro 1w TX, upgrading from 2.5.0 to 3.2.1, by going to the "support" tab in the ELRS configurator and "Clear PLatformio Dependencies" and "clear firmware files" and rebuilding from scratch. THEN flashing.
Great video man!.. I'm glad your always making videos about new and cool products! And videos like these too ..
I think it's a little old now tho sooo .. you don't still have to do this do you? If yours already has 3.x ? ?
Haven't run into this problem but I probably will soon. :) Thanks Joshua.
thank you for making this, i can point people to this vid now
my receiver was bricked, thanks a lot Joshua!!!
I have to assume you're just being sarcastic and joking. Because the title of this video says THIS WILL BRICK YOUR RX ONLY DO THIS TX and there is a pinned comment to that effect. At that point, any responsibility is on you.
@@JoshuaBardwell si jajaja...paso que llegue tarde a ver tu video y briquie mi ep2 jejej...no pude correr el modo bootloader nunca más...
Glad you made this but you should also advise use old lua v2 or you may get script errors flashing.
Thanks for your great work, helps me a lot
Aaaah! Where were you last night when I was fighting this? 😂
Thanks Joshua, and yes, I was that person you were talking about at the start of the video!
I'm a bit late to the party but thank you, that worked!
1:41 That's true!!! Thanks!
good 1 jb !!! you got me 😁😁
great work Joshua
great videeo!!!!!yet again I learned something today
Thank You! That was very helpful!
Thanks Joshua. It worked. That's why I'm a patreon 😂
Thank You this worked.. Now my problem is the LUA for Elrs on the older Taranis X9d plus 2018 does not work, the Lua size is too big.. OpenTx will work once if your lucky, EdgeTx will just say Not enough memory.. Surely more people have this problem? Thanks JB 👍👍
You are simply the best. tks!
BIG BIG BIG BIG BIG BIG thanks
Very informative video, thanks 👍🤓
I can add that I got a different error message: “Target mismatch” but it was also solved by the repartitioner fix
Tried the repartitioner, but got a "Not enough data uploaded!" error instead. Oscar says downgrade to v2 first then flash again, but it was for RX, should I do it to my Happymodel TX module on my TX16s over WIFI?
I have the same, did you fix it? also for HM 2.4 TX
@@HughSaunders If I remember it correctly, I've downgraded/flashed to 2.0 and directly updgraded to 3.0 after.
Flashing the repartioner.bin didn't work for me (HappyModel Non-Pro). It gave an additional error and stonewalled. I forget the actual error message but the workaround for me was to flash down to 2.0 then from there flash to 3.0. Worked for me.
I had a similar issue with the same module. After the "target mismatch" error, another error popped up. I think it said something about too few bytes uploaded. And it wouldn't flash the repartioner.bin file. I tried it multiple times without success. I was running ELRS 2.5.0. I upgraded the firmware to 2.5.1 and it let me flash the repartioner.bin file. Then I was able to upgrade to ELRS 3.
plain old simple, thank you for this..
Updated my Zorro to 3.0 today, luckily I didn’t get an error :) Matek r24d also no error :)
did you update to 3rc1 then 3rc2 before updating to 3.0?
@@likebliss yes i used the RC 1 and 2 before :)
I think most people when facing a problem just focus on the "help me" instead of searching and understanding the reason of the problem.
This issue was reported and the solution is on the elrs page, people just don't read.
Joshua Bardwell always to the rescue.
This one I bet will be shared a lot of times answering the same question all over the internet.
Flashed Jumper T-pro internal elrs - no errors! ^)
Nice video as always. However...your build was with UART flashing method and you flashed it over wi-fi 😁😝
The build is the same regardless, as far as I know. The only difference is what happens if you hit build and flash. If you only intend to build, I don't think it matters.
@@JoshuaBardwell Not trying to be smart... Just a friendly comment for fun. Thanks for answering though. I might have learned something today 🙂
@@JoshuaBardwell So, I had the same problem trying to flash 3.0.1 so I tried flashing this repartitioned bin and when it finished flashing it said wait for it to reboot before unplugging from FC and powering down.. well the light went out but never came back on .. waited 45 minutes and still nothing, never rebooted. So I unplugged the FC,plugged it back in, and surprise surprise the RX was bricked 🤦🏽♂️ I have the happymodel ep1 so I soldered the pad and ground together to put it in boot loader mode,made sure telemetry was off and tried to flash 3.0.1 via betaflight pass through but no luck.. not sure what to do now because it’s not like I can connect to Wi-Fi in boot loader mode and try flashing the repartitioned bin again🤷🏽♂️
Any chance The Godfather of FPV knows how to fix this? 🥺🙏🏽
Hi just wondering if we keep v2 Lula script or update it to v3? Many thanks.
“It’s not gonna work” has been my experience with ELRS in general. I am optimistic for it’s maturity and reliable hardware partners. I want to fly not futz and ELRS just as too many issues for me IMO. I know it works… just not on my quads.
#me2
Thank you sir you saved my ass once again🕹🕹
Man JB, I ran into this a figured it out Sunday (LOL I did read the Notes) and I was working on my own How to fix it video, guess I dont have to now.
Did this with an ep1 reciever and it stopped transmitting the wifi signal after flashing the partitioner.bin. Tried fixing it by bridging the pads on the ep1 and use betaflight passthrough but can't flash and get the wifi back.
It did not work for my Radio Master 16S ELRS. Internal ELRS bricked. No wifi, no serial communication.
Mine ran into a problem in the tx module it just keeps displaying "NO HANDSET"
I kind of wish elrs was like a cheap dji ecosystem. What I mean is when I get a new vista quad it just pairs so seamlessly to my V1 goggles and black remote but the hours I wasted on an elrs happymodel mobula7 after hours or frustration it just wouldn't bind, even as somebody who owned and ran elrs quads I just gave up and broke it down for spares. After that I swore I'd never elrs again.
hello, i ordered a new tx pro happymodel. I started again like the tutorial. same problem after the flash with partitioner.bin loses the wifi connection impossible to restart in wifi. and now I have a message: loading.... and nothing else
I got the massage "not enough data uploaded"
Trying to update from MATEK 2400 RX V2.5 to MATEK 2400 RX R24D V3.1.
Thank you so much!!
Vielen Dank für das Video, das hat geholfen
Awesome jb thanks. I’m getting that on my betafpv nano 2.4ghz receiver. Should I follow the same steps like you did on the tx module?
So with the recent HappyModel Moblite7 HDZero V3 running firmware 3.0.1. I get the ERROR[4]: Not Enough Space.
I am trying to update to 3.3.1.
In the comments you suggest flashing to 2.5.1 first, then 3.x.
I am already in 3.0.1, should I flash back to the 2.5.1 in order to rectify the "Not Enough Space" error, then update to 3.3.1?
I didn't get a message. It said update complete on iflight commando 8 but now my quad won't arm. When I reconnect it shows down under Network devices it's on version 3.0.0
My RM zorro keeps "timing out" flash won't work....
I have put the file in my Ex and now it does not open the Wi-Fi network...
I have broken the rx?
So, I had the same problem trying to flash 3.0.1 so I tried flashing this repartitioned bin and when it finished flashing it said wait for it to reboot before unplugging from FC and powering down.. well the light went out but never came back on .. waited 45 minutes and still nothing, never rebooted. So I unplugged the FC,plugged it back in, and surprise surprise the RX was bricked 🤦🏽♂️ I have the happymodel ep1 so I soldered the pad and ground together to put it in boot loader mode,made sure telemetry was off and tried to flash 3.0.1 via betaflight pass through but no luck.. not sure what to do now because it’s not like I can connect to Wi-Fi in boot loader mode and try flashing the repartitioned bin again🤷🏽♂️
I bumped similar problem with hglrc elrs rx yesterday . RX was bricked and wifi was not available. Betaflight passthru did not work either. I have FTDI usb-serial adapter and could flash the bricked RX with erls configuration using UART flashing method.
I just ran into this on micro Tx 1W . 3 buttons inside. Held boot one down to flash. If cap not installed will it effect operation? Thanks
Hey Josh, a wild attempt to get a response off an old video. I’m currently trying to bind my Cinelog 35 ELrs 2.4g with my Commando 8 2400tx module. I come to the conclusion the quick bind method didn’t work because they are on different firmwares. The receiver being 3.2 firmware and the Commando 8 being 2.4 firmware (factory) I went to flash my TX module straight to 3.3 the current latest and now I can’t open my ExpressLrs tools menu to bind or even access the wifi to reflash firmware. I have only noticed after watching this video and going onto the Config guide that I needed to do this 2.51 firmware first before upgrading to firmware 3.0 and later. I’m stuck. What should I do next and how do I get back the Expresslrs script and reflash my module when I can’t access wifi pass through??!
Hoping I can hear back from you. Thanks in advanced. I will definitely be paying forward to the patrion if you help lead me in the right direction. 👍🏽
i jsut opened it up. switched off switches 1 and 2 and switched on switch 5 and 6 for flashing. flashed it and put the switches back to original order.
I tried to update 3.2.1 firmware for elrs micro 1w module. But now the module has been suspended, the oled screen is not displayed. Is there any way to fix it?
I have put a version that does not have my children and now I don't think it will be bricked. Is there any way to restore it?
Hi
I was flashing the external module and it seems I make a mistake when selecting the bin flash file.
I connect the module to USB-c and also try connecting to the external bay (jumper t pro) and Screen module is not turning on, but I let me to connect to generated wifi SSID.
How could I recover the external module?
If you can connect to the module wifi then you could re flash it with the correct firmware.
I have other problem, once I updated the receiver it loose connectivity with the fc
nice of you to assume i can read. there is a reason i watch your videos.
seems like you can upgrade via wifi directly now. just upgraded my new commando 8 from 2.4.0 to 3.2.1 without the reparttioner or the 2.5.2.
Comando 8?
@@fernandotorrecilla5192 iflight commando 8 radio transmitter. The 8 was missing in my first text, added it :)
Can expresslrs be updated to 3.2 using the Speedy bee Configurator App in the Cloud?
One more question do I have to update my quad receiver to 3.0.0?
Does anyone have any idea why my PC wont connect to my transmitter WiFi? It shows up in networks, and when I enter the password (expresslrs) my PC says, Cannot connect to this network. I cant seem to find anyone else having this issue
Can Express LRS VS. 2.0 update to 2.5 and then VS. 3.0 without downloading the partition needed for VS. 3.0 to update?
I ran the repartitioner and now my XLRS reciever has a sold green light when power cycled. I'm not sure how to get it back into wifi mode.
Read the entire title of this video :-( THIS WILL BRICK YOUR RECEIVER. Read the pinned comment at the top of the comments section.
This is only for modules. You need to re-flash your receiver using either serial passthrough or a programming adapter. ua-cam.com/video/TzAaYg47TSU/v-deo.html
@@JoshuaBardwell Yes I read that after the fact unfortunately. So I'm stuck without a FTDI programming board which I don't have? I'll order one but once I get it, not do I hook it up on an all in one board? I just flashed this to my brand new pavo pico 2.0 pro. I'm so mad at myself. I only did this because I got the not enough space error when trying to flash the receiver.
I got it. It was a bug in BF 4.5.0 that was preventing me from using passthrough flashing. it worked in 4.4.3.
Glad you got it fixed!
Should I delete the old lua script? cause I now see 2 expresslrs in my menu
I've gone to both the expresslrs website and the github expresslrs/expresslrs wiki and can find no mention of not enough space or partition. Not even the troublshooting page of the expresslrs website mentions it?? I suck!
If you search "expresslrs not enough space" on Google, there are five or ten issues on the elrs github repo about the issue. It's also, mentioned in the release notes for elrs 3.0
It's me from the future.
Flash to 3.0.0 first after 2.5.1 instead of latest (HM TX24pro)
Didn't work for me to go to the latest.
Had to recover over the internal micro usb (flashing over UART)
2.5.1 is possible this way.
Help! After downloading the repartitioner I couldn’t get the WiFi signal to come back I waited about 6-7 seconds after it completed before unplugging it??
Just power cycle and all should be as normal?
@@JoshuaBardwell no luck… I have a zoro 4in1 with a es24tx slim pro
struggling, the repartition update worked, but the module no longer shows up on WIfi, either by usb or on the radio. ELRS is
killing me. I honestly can't believe how buggy this entire elrs world is
I got a syntax error when I tried to upload to 3.0. Any thoughts?
is this method only for HM Series Pro ? or for all ELRS Module out there include Radiomaster Ranger ?
All
@@JoshuaBardwell Thanks
@@JoshuaBardwell should i flash the Rx with repititioner file ? or just the module ?
"Hello Joshua! I've installed the Repartitioner on an HGLRC Draknight, UART ExpressLRS 2.4G, and now I can't connect via wifi... perhaps I've messed it up?? THANK YOU!!"
Wiki!! What Wiki!!! 🤣😂
thx, bros
I just flipped the internal switches to 5 and 6 and it worked through uart
hello, thank you for the video, unfortunately
after flashing with repartitioner.bin I restarted my tx16s before flashing with firmware 3.0.0. now I have a screen with the message: loading....
Do you know how to reset?
If it's possible
i have this too, what now ?
You also selected to update over uart not wifi.. not sure if that matters or not
It doesn't, since I hit the Build button and not the Build and Flash button.
Hi do we keep v2 Lula script when running the partition and update or do we have to update the Lula to v3 at some point here? Thanks.
If using elrs 3.x, you need the 3.x Lua script.
Thank you, so I have your radio with elrs v2 I partition that, then once partitioned, drop the v3 Lua into the sd card and then run the update as per normal and woolah
, I have learnt something today ;-) Thank you again for your commitment to this sport, I have learnt so much and we all appreciate your dedication.
If this works... I will be happy 🤣🤣🤣🤣 2 days searching the net haha..
I have your dawinfpv cin20 and it has elrs 3.0 and I would like to know if I can flash 2.0 on it to match my radio?And if so how?
I would recommend updating your radio to 3.x.
If the FC has an SPI receiver, the only way to go back to 2.x is to flash Betaflight 4.3.
@@JoshuaBardwell
No it's not spi so can I flash 2.5.1 to match my radio. I have alote with elrs 2.0
@@JoshuaBardwell
Thank you for your help. Can I flash 2.5.1 to match my radio?
If it's not SPI you can flash whatever target you want. But I still would recommend updating to 3.x.
@@JoshuaBardwell
Thank you
Why isn’t this done automatically by the 3.0.0 flash process then when it detects the size issue?
You can read the github repo link in the video description for more info about why this happens.
It can't be done fully automatically - you need to flash a separate repartitionwr firmware to undo the manufacturers screwup, and then put the device back into update mode once that's done for the actual update once its rebooted a couple of times.
Does this work For RX because I’m getting “not enough space” this message trying to flash my ep1 from 2.5 to 3.0
Yes it's the same.
how about for receiver ?
Flash 2.5.7 then 3.x.
To get this to work you cant do it from 2.5.1 but you need update to 3.0.0 RC1 then i did manage get it work :)
Quick question. Do you run this update on the receiver's too? After months of fighting with my computer (Adobe wanted to interfere and i couldn't figure it out) I finally got 3.0 on my module with a binding password. I went to upgrade the receiver this morning and got the same error message for the receiver too. Do I partition it too?
Yes you can also do it with receivers.
@Joshua Bardwell Thanks friend. Happy Thanksgiving!
@@georgepf Me to... I've bricked 2 receivers now trying to sort the issue out... So it's not as easy as it sounds here... just to repartition the receiver.
@@heliharris69 So what's the solution? Just run ELRS 2.x? Also, did you manage to un-brick those two receivers?
@@JoshuaBardwell got few ep2 that say not enough space,, dummy me will try on rx