Problem with toastman build flash

Discussion in 'Tomato Firmware' started by nomejodas, Jan 20, 2012.

  1. nomejodas

    nomejodas Network Guru Member

    I have a Linksys WRT54G v1.1 router. I bought this yesterday for cheap ($5) and proceeded to flash it with a toastman build. It had the original Linksys firmware on it. I used ND-MIPS32R1 Kernel 2.4 (WRT etc ONLY): tomato-ND-1.28.7632-Toastman-IPT-ND-Std.trx. When I tried to flash it it kept saying 'Incorrect image file'. Then I changed the .trx extension to .bin and it accepted it. After a minute I got the message "Upgrade are successful" (yes it said 'are') and then the power led started blinking non-stop. I wait a few minutes but it didn't stop. I tried logging into the router webpage but was unable. Then I unplugged the power and waited a minute and plugged it back in. It powered up and immediately the power led kept blinking again. Factory resets did nothing.

    After determining I most likely bricked my router as I couldn't ping it at all, I resorted to the only option left and opened up the case to try shorting out the pins. I tried pins 15 and 16 first but that didn't work so I did 16 and 17 and thankfully that worked. I was able to ping the router. I tried to upload the latest linksys firmware but was unable so I tried polarcloud's tomato. Finally it was successful and the router was functional again. Thank god for the internet as this was the first time anything like this has happened to me.

    I decided to give the tomato-ND-1.28.7632-Toastman-IPT-ND-Std build another try. It bricked the router again. So I had to short the pins again and reload original tomato firmware. Now I don't know which build to use. What was wrong with the build that I tried? It's the right firmware for my router right? I've still got the router mainboard out of its case as I want to finish flashing with toastman before I put it back together. What build should I use???
  2. Toastman

    Toastman Super Moderator Staff Member Member

    I don't know what could be wrong, you might just try flashing an earlier version to see if that resolves the problem for you. I only have 54GL's here but they flash fine.Try 7628 first.
  3. nomejodas

    nomejodas Network Guru Member

    7628 didn't work either. Bricked it again. Maybe there's something about your mod that the router doesn't like?? I will try shibby instead and see what happens. Oh btw pins 15 and 16 did work I must not have been making proper contact.
  4. nomejodas

    nomejodas Network Guru Member

    Ok I tried the latest Shibby (tomato-ND-1.28.5x-083V-Std.trx) and it bricked the router also. Has anyone successfully installed toastman or shibby onto a WRT54G v.1.1 or 1.0? I'm able to install dd-wrt though. Strange thing is after I brick it and have to use tftp to flash, the official linksys firmware won't upload. It keeps timing out. On the other hand the original tomato firmware loads instantly and I have to use that one to flash.

    I noticed when installing dd-wrt I was required to install the mini generic version .bin before I could install the standard one. Maybe I need to do this with toastman also. I'll give it a try.
  5. Toastman

    Toastman Super Moderator Staff Member Member

    Could be. I have hundreds of GL's and they are fine, but I have never used the model you have. Nevertheless, it ought to work fine. And shibby's also. Hmmm. Anyone else tried it?
  6. nomejodas

    nomejodas Network Guru Member

    well I tried installing your mini version but it bricked also. It was even worse because I thought it was permanently bricked this time. I kept shorting pins 15 and 16 but nothing happened so I had to do 16 and 17 and then I had to upload the firmware twice. Screw it I give up I'm done experimenting. I'll just use regular Tomato. I really wanted to use the QOS settings from your mod but I guess I'll just have to make due with regular Tomato's settings.
  7. Toastman

    Toastman Super Moderator Staff Member Member

    Pity :) Good luck!
  8. bucher

    bucher Networkin' Nut Member

  9. nomejodas

    nomejodas Network Guru Member

    According to wikipedia the WRT54G has the same amount of RAM and flash mem as the WRT54GL. One major difference is my router v1.1 and v1.0 have a slower CPU. Don't know if that has anything to do with the problem.

    Not sure if I want to try tomato usb. I already put the mainboard back in the case. If it bricks again I'll have to pull it out. Also it doesn't look like tomato usb has that many more features than regular Tomato. I really wanted the QOS presets and B/W limiter of toastman or shibby's and tomato usb doesn't have that. This pisses me off. The QOS settings for regular Tomato are confusing. Thinking about changing back to dd-wrt.
  10. teaman

    teaman LI Guru Member

    There's some things that might be relevant, specific to the WRT54G v1.1 as this particular device (which is unfortunately not very common these days) might have slightly different hardware than some of their 'equivalent' counterparts (i.e. SoC vs. separate chips for radio/cpu/switch, processor speed, internal connections, etc...),8985696

    Also, as a WRT54GL user myself, there's something I've learned over the years: stay away from .trx images when flashing that kind of unit. There are two main advantages in using .bin images built/tailored for some specific models/families:
    a) they usually contain an extra header which some sort of 'magic number' matching the HW model/family (i.e. extra validation step sometimes required when flashing a Tomato firmware image from something else running on the router)
    b) .bin images can be used to recover via TFTP (whenever I tried to do that with any .trx images, the router simply refused and would only accept .bin images with that special header)

    Anyways - I should be releasing new Teaman-ND versions/builds over the next few days (and I might be able to include these new QoS features on some of them...), so you might wanna check this page in a few days ;)

    HitheLightz likes this.
  11. nomejodas

    nomejodas Network Guru Member

    I did notice that every firmware I downloaded with the .trx extension resulted in a brick. Every firmware with a .bin extension was flashed successfully. Is there a reason why these modders don't just stick with the .bin images? Have you bricked a router using a .trx file with the 54GL? Toastman uses the 54GL's like you and apparently doesn't have any problems with .trx files.

    Anyways, since I'm stubborn and can't leave well enough alone I kept trying different firmware versions. I was finally able to successfully flash one of toastman's firmware: 1.28.8025.2 from the older builds folder. But the version number must be a typo because in the router's page it's listed as Tomato 1.25. Anyone know what the difference in QOS settings is between 8025.2 and his recent versions? I remember reading he updated it or something.

    I was also able to flash with Victek's 'Tomato RAF based in Original Tomato source code. Last Release. K2.4.20 MIPSR1' - Tomato RAF 1.28.121006. This uses original Tomato's QOS settings though.

    Both of these firmwares were .bin images.

    Are the ND versions in .trx format because they use the new driver? Or is it just out of convenience so they don't have to upload separate .bin images for different routers? Is your ND version going to be in .bin?
  12. teaman

    teaman LI Guru Member

    Since I probably should include myself in the group of these modders out there... here's a something to consider: generation of .bin firmware images got broken a while ago on some of the branches mostly being used/focused in compiling K26 builds, so probably this particular issue wasn't exactly noticed as a problem until someone brought it up ;) In fact... I've struggled to figure that out for quite a while myself ;)

    I've brought this up with Toastman already - so there's a good chance some of his new/upcoming builds will be including .bin images in the near future...

    Also, keep in mind that using .trx files on my WRT54GL worked just fine most of the times - just not every time ;)

    There's no typo: you just flashed a very old Toastman build. Back in those days, Tomato could well be still at version 1.25...

    What's different from v8025.2 to most recent versions? Lots of things - there might be hundreds/thousands of relevant commits with possibly important changes/enhancements/fixes/improvements between the version you currently have on your router and the most recent versions being published these days ;) If you're interested, you might wanna have a look at the logs on the git repo:

    As far as I know, .trx images should work in most situations (and if I'm not mistaken, those are actually recommended on Asus devices, but I'm not entirely sure about this). But still: as we can see, there are a few cases that might require using .bin images.

    When/if I'm able to bundle/include these whole Toastman/Tiomo QoS improvements thingies in one of my K24 builds, I'll probably be posted somewhere in this forum ;) Unfortunately, the builds currently available for download do not include those patches.

    Still, if you're experimenting and flashing different firmware/versions, you can find a few not-so-recent versions of Tomato-SDHC-VLAN you might wish to try/experiment (v13 is the latest in there):

    Best of luck!
  13. nomejodas

    nomejodas Network Guru Member

    If you're coming out with a new build with nice improvements that can work on my prehistoric router then I'll definitely wait for that. Thanks!
  14. Toastman

    Toastman Super Moderator Staff Member Member

    Greetings! Yes, I fixed up the broken compile code that Augusto mentioned, and now seem to have generated around 80 builds, mostly a huge choice of .bin versions for different named routers. :eek:

    Never mind, I'll sort that out later. I will upload them as 7632.2 soon. I hope this is the answer to your flash problem on the G, please report back!

    Oh, one cautionary note - I have flashed these only on an AP - but not tested online as I no longer have a router in position to do that. I think everything is OK though, as the last build seemed to work fine.
  15. pharma

    pharma Network Guru Member

    I used a WRT 54G v1.1 a long time ago, but remember when flashing with the Jon's original Tomato firmware it was done very carefully because I did brick the router a few times. As I remember it didn't have so much to so with the firmware size (even though important) as the features the firmware offered. I do remember using tftp2 to load firmware.

    Anyway, it sounds like you might need a router upgrade in the near future. Good Luck!
  16. Toastman

    Toastman Super Moderator Staff Member Member

    New version 1.28.7632.2 uploading now :)

    There are about a million builds, have fun!
  17. nomejodas

    nomejodas Network Guru Member

    I tried the new .bin builds and they did not work! I tried "tomato-WRT54G_WRT54GL-1.28.7632.2-Toastman-IPT-ND-Std.bin" and "tomato-WRT54G_WRT54GL-1.28.7632.2-Toastman-IPT-ND-Tiny.bin" multiple times. Luckily I could still ping the router so I didn't have to open up the case and short it again.

    So if it's not the .bin that's the problem maybe it's the 'ND'? Something in the new driver that's not compatible with this router?

    I was so hoping it would work this time. Any other ideas?
  18. bucher

    bucher Networkin' Nut Member

    Buy a new router on craigslist :)
  19. teaman

    teaman LI Guru Member

    I'm afraid there's a good chance your router didn't "like" those .bin images just because of this 'ND' thingie... Tomato firmware images used to be available in two flavors: 'standard' and those containing this New wireless Driver. From Victek's page (
    So... I'd suggest running this command to verify which would be your case:
    nvram show | grep corerev
    Best of luck!
  20. nomejodas

    nomejodas Network Guru Member

    Yes I've already done that test before I installed Victek's build. Mine is wl0_corerev=4

    So I guess nothing further can be done? Have we exhausted all possibilities? It's not a big deal I can always use this router as an access point.

    Maybe someone should make an official note that the WRT54G v1.1 can't be used with ND builds.
  21. Toastman

    Toastman Super Moderator Staff Member Member

    You know, I think it's been such a long time since anyone raised this issue of older non-ND drivers that most of us had forgotten all about the corerev. I guess it'll make a fine AP.
  22. nomejodas

    nomejodas Network Guru Member

    Well thanks toastman and teaman and anyone else for taking the time to help and for creating the .bin builds also, that must have taken some time. Even though I couldn't use it I'm sure other people could.

    I was thinking about getting the Asus RT-N10 or N12. Is this a good router and fully compatible with tomato ND builds?
  23. e-gaulue

    e-gaulue Networkin' Nut Member


    Sorry to push this message up.

    On the polarcloud Tomato website there are two release for Tomato 1.28: one without ND (New Drivers) and one with.

    About the differences in the drivers, I see that everybody use the ND (RAF, Teaman, Toastman, Shiby...) drivers now. Would it be possible to provide release with the old ones or has the stuff became so different that it's not possible anymore ?

    I'm juste looking for Tomato 1.28 + OpenVPN + PPTP server for WRT54G v1.1 (yes, old but working well, why rising the worldwide CO2 level), so old drivers. I needn't VLAN and lots of new things (multissid...). I used to compile hyperwrt a very long time ago for rtsp support, when it wasen't inside yet. Would it be possible to realize such a build rather easily (I mean just asking to compile old drivers instead of new ones) ? If yes, where can I find information on how to do this ?
  24. mito

    mito Network Guru Member

    Che, nomejodas, go for the rt-16n that is strong and powerfull and here has lots of Tomato firmware updates & support with this guys that are great.
  25. teaman

    teaman LI Guru Member

    Good news: that's one of the greatest things with open-source projects - all you really need can be found somewhere (mostly at this git repo):

    Short version - all you need to do would be checkout a 'base' branch, such as this one:

    Then, merge or cherry-pick the commits you want from some other 'feature' branch, like this one:

    Not-so-good news is: Teaman-PPTP is based on branch 'tomato-ND-USBmod', which uses a slightly different build system and kernel version, so... I can't say this would be exactly 'easy' as I suspect there might be quite a bit of patching/stitching/glueing in order to resolve conflicts in some files between those two... The whole PPPd + kernel/MPPE/encryption + PPTPd can be specially tricky since those came from different versions/branches/sources. Still: it's not an impossible task, considering there are /sources/ available.

    Best of luck, though!
  26. e-gaulue

    e-gaulue Networkin' Nut Member

    Teaman, thanks for your reply,

    I've look at polarcloud tomato 1.28 source code to see the differences between ND and standard drivers, and it's not as simple as thought (not just a change in the kernel make menuconfig). Some files are replaced by others, so it's not a build option too as for K26. After that, tomatousb build were always based on ND, and there has never been a standard drivers branch on the git.

    I think it would be possible to merge one of the last tomato release with the polarcloud 1.28 but it looks to me as an enormous work for finally few demands. And I'm not a "git" professional.

    So, as I haven't got so much time, I ordred a WRT54GL. I will always find a place for my WRT54G v1.1.
  27. johncc

    johncc Serious Server Member

    I have had similar experience with the v1.1, that none of the "ND" builds will work.

    So, using "plain" Tomato 1.28, I am trying to utilize gpio 4 input and gpio 7 (DMZ led) as output, and having trouble with that as well. I posted a question about that on a different thread--

  28. myersw

    myersw Network Guru Member

    The v1.1 has some differences from the other wrt54's. When Jon was first starting out with Tomato he had things working for all the available versions except the v1.1. Would brick when you tried to load Tomato, I know because I did several times while working with Jon to get things working. Since I also had another wrt54g I donated to Jon my v1.1 so he could get things working, which he did. That said, what ever he did to get the v1.1 working has since been lost I am guessing it the later builds.
  29. johncc

    johncc Serious Server Member

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice