Definitely sounds like a bootloop. Hard power cycle didn't do anything? If not, the best thing to try is rolling back one release at a time from the 26 June build until you find one that boots all the way up. That way, the developer can be contacted and will know where to look. Going by ticket 6883, it may be as far back as 06-02-2022-r49049 to find a good build. Serial logs would be ideal to have information to pinpoint the problem, though. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
So those files are quite different once you are running DD-WRT you need dir615i1-firmware.bin over web interface or via terminal with write fwname.bin linux or if you want to recover it you can use the dir615i1-factory-to-ddwrt-firmware.bin,.
Never use the dir615i1-factory-to-ddwrt-firmware.bin to upgrade via web interface after youre on dd-wrt.
Since flashing that file via DD-WRT webUI failed already, I suggested Emergency Room flashing the factory-to-ddwrt file, which is a known workaround on several D-Link devices. Only other way to check is to flash via command line over telnet/ssh per this example:
Code:
cd /tmp
wget http:download1.dd-wrt.com/dd-wrtv2/downloads/betas/2022/06-02-2022-r49049/dlink-dir615i1/dir615i1-firmware.bin
write dir615i1-firmware.bin linux
(wait for write/erase to finish)
reboot
The size differences in files leads me to believe the firmware.bin file is bunked:
On the current relase, that's 520164 bytes. Given that it has u-boot, LANG, and ART partitions (in stock flash layout), that could explain the file size difference, but I don't recall seeing such a large difference between files for other devices.
I'm not reading through nearly 50 pages of mostly "I need to post to see a link" (which is incorrect, I was able to see attachments right away - all that nonsense should be removed from the thread) to see if the DD-WRT flash layout is different, but a cat /proc/mtd on the working build initially flashed will reveal the layout in DD-WRT:
Maybe there have been many bad firmware images for this device without any oversight due to lack of reports? _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
-snip-
Just to let you know, only help here is to provide a serial log detailing this error.
-snip-
Also note this device has no kernel log output to keep things small enough, so a complete serial log pls.
-snip-
Or door nr 2 Solve this via TFTP recovery
-snip-
There is only one recovery mode on this device that I am aware of, and that is D-Link Emergency Room. Some folks advise against Firefox, but if you use an antique version of FF portable, it is known to be successful. There is this thread about a DIR-615 E* version that recommends command line upgrading, but from the known good build, Pale Moon portable or previously used FF portable should work for upgrades from DD-WRT to DD-WRT just fine. Chromium browsers have been known to be problematic on these in general. Maybe a hard reset from stock after initial flash of DD-WRT and prior to upgrade might be a missed step that is resulting in this issue? _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
- how do I get the serial log?
- Yes I did not do hard reset after initial instal of ddwrt 2020 fw. I just used portable firefox and went to recovery site and selected june 2022 ddwrt factory fw and it said it was successfully.
- when u say hard rest - it is that 30-30-30 rule? could u ple let me know how to hard reset?
- what is hard power cycle?
- I will try command line too. lets c if it works.
Last edited by aaragorn86 on Sun Jul 03, 2022 0:03; edited 1 time in total
Hard reset on Atheros is via telnet or ssh in PuTTY or Terminal 'nvram erase && reboot'. It is always a good idea to do at least a normal reset via button or via DD-WRT webUI under Administration -> Factory Defaults after flashing from stock firmware to ensure no stale nvram variables exist. Usually Emergency Room flashing shouldn't necessitate this, but this is always a good added measure just to be sure. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Hard reset on Atheros is via telnet or ssh in PuTTY or Terminal 'nvram erase && reboot'. It is always a good idea to do at least a normal reset via button or via DD-WRT webUI under Administration -> Factory Defaults after flashing from stock firmware to ensure no stale nvram variables exist. Usually Emergency Room flashing shouldn't necessitate this, but this is always a good added measure just to be sure.
what hard reset via telnet or ssh in PuTTY or Terminal 'nvram erase && reboot'? I am assuming terminal is for linux users. I have windows 10. can I do it in CMD? I just tried 30-30-30 reset and installed latest version via ER but no use same results. how do I get the log?
PuTTY can also be used for serial console access, so it's the best option out of the three. You will need a 3.3V level shifting USB to UART TTL serial adapter to connect to the serial console of the router mainboard to get the logs.
D-Link DIR-615 - OpenWRT Wiki _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
I reset the router with ssh client and following commands and installed July 4th fw but same result - stuck in boot loop. I dont have cables to get the serial logs to check further.
nvram erase && reboot
I will playround with other version to see something sticks.
