Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Sat Sep 24, 2022 17:50 Post subject:
blkt wrote:
Right, stripped or webrevert file is only for use with dd-wrt UI and if not done correctly, like LOM, just more headaches.
For some reason, I'm thinking if you don't need stripped for TFTP, you don't need for webrevert. I can test this theory later since recovery is trivial for me. Just a word of advice: I wouldn't talk bad about Lars since all of his webrevert files work. Mine, on the other hand, were broken. At least make your bat connect to the right target
blkt wrote:
If either TFTP or TP-Link Web UI Recovery are available for TL-WR1043N V5 simply use regular unmodified factory files.
The two commits below reveal web recovery does in fact exist but mode access may be limited to a flag set in advance.
"Stock-firmware sets a flag in the "romfile" partition before beginning to write and removes it afterwards. If the router
boots with this flag set, bootloader will automatically start Web-recovery and listens on 192.168.0.1. This way, the
vendor-firmware or an OpenWRT factory image can be written.
By doing the same while performing sysupgrade, we can take advantage of the Web-recovery in OpenWRT.
It is important to note that Web-Recovery is only based on this flag. It can't detect e.g. a crashing kernel or other
means. Once activated it won't boot the OS before a recovery action (either via TFTP or HTTP) is performed.
This recovery-mode is indicated by an illuminated WPS-LED on boot."
Thank you for digging those out for me. One of those links was in one of the threads that was moved out of non-moderators' view. I think that was the mechanism that kept returning me to factory firmware every time I tried flashing bad firmware images during my last go-round.
@zappel: glad you got it sorted. The USB ethernet adapter probably would've been better served with an unmanaged switch between PC and router, as well as the (at least) 1024 anticipation window set in TFTPD32/64. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Sat Sep 24, 2022 22:28 Post subject:
Yeah, I guess I misread that part about LOM and should've taken offense at my blunders trying to create them
OpenWRT has a lot of conflicting information on their forum, there was a method to serial / tftp flash that didn't work when I was trying to figure this out - but it was the error messages that I was getting regarding flashing via ssh (mtd write file firmware) via OpenWRT, TFTP flash, and flashing via u-boot along with this thread that resulted in finding the key to the problem.
I've edited the supported devices wiki to reflect the minimum usable build, link to the ticket on Trac, and this thread, and will edit it again after the next public beta drops. There are a few things that do need to be removed from the firmware image for this router due to no USB port and other things that need to be looked into / corrected, but that's probably going to need to be a group effort.
I have two of these, the other one is running OpenWRT as it has been since I originally started looking at this two years ago and didn't want to leave stock 2016-era firmware on it. I had considered doing a custom OpenWRT build environment to make full use of the flash space as the firmware they provide is ~4MB and Gargoyle seems to take forever to drop new releases. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Tue Sep 27, 2022 0:36 Post subject:
Just wanted to update here real quick. The 50274 alpha test build is looking good except one cosmetic issue. All of the extra USB-related features are now removed. Not sure if we will see this build go public beta release or not yet, I haven't asked. Been a long day dealing with a customer's ISP snafu initiated by a sales representative that has no eyes in the field and ain't got a clue.
Good news: I succeeded flashing it.
Bad news: I tried to configure it as simple AP, can not access it anymore and realised, that 30s Hard reset does not work.
Are you sure you are accessing it at http://192.168.1.1 (default DD-WRT IP)? TP-Link default IP is 192.168.0.1. _________________ "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
Sure!
As I said, I flashed it successfully with dd-wrt and configured it as AP under …1.1
Somehow, even though I disabled Firewall etc. I can
not access it anymore. Therefore I wanted to reset it
To access it again, under 192.168.1.1 I try to reset it via 30s reset button.
but this is not possible.
Shouldn‘t also the wifi dd-wrt disappear after a successful reset?
Also no reset indication from the LEDs
Depends on router model usually wireless is available with hardcoded default password, but try an Ethernet cable.
If hard reset was successful you will no longer have Telnet access, or SSH if it was enabled, so http only to webUI.
Set username and password. Be sure not to lock yourself out with a stored password. Try a different web browser.