Whereas with stock firmware I had a location in my house (behind two walls and far distance), where my phone constantly lost connection to the repeater (I assume it was because stock firmware automatically tries to switch between 2.4G and 5G, when low signal strength is detected), now with OpenWRT, there are no connection issues at all when I am with my phone in this specific location. OpenWRT has higher range than stock firmware. I'm not familiar with telnet, only SSH so I dont know how to get any benefit of that (flash OpenWRT somehow maybe)Īnyway, with great joy I can announce that Rolandos Image from, works pretty well! I also noticed there is telnet access possible on stock firmware. For some reason different filename of the same file means also different byte size showed in Firefox,(but alway < 1301 Bytes), really strange behaviour of this WebGUI. Maybe its only a small thing that makes the difference which makes it work for you but not for me. I tried another computer but that didn't help. So it seems to has something to do with browser. I do have serial access but im not sure how to flash it using tried Edge again now a few times, didn't helped me on OpenWRT files but with the extracted stock fw file it worked to flash on Edge, but same <1301 Bytes problem on Firefox. Name: openwrt-ramips-mt7621-dlink_dap-x1860-a1-squashfs-factory.bin For the OpenWRT, i tried your posted file from OpenWrt Support for D-Link DAP-X1860 - #62 by RolandoMagico and the last 2 releases from your github repo (-22). I needed to flash it twice for some reason to work. Thanks in used DAP-X1860_RevA_Firmware_101b94.bin, thanks for the help, i was now able to get back to stock using this technique described in the pull request you mentioned. Maybe someone has a little hint for me on what I could try next or where could be a possible reason. One of the devices was in use already (linked wifi) the other one put directly to recovery mode Oh and the devices were on the 1.0 FW they came with from factory as i started trying maybe this is important because of the recovery mode version is updated on newer stock fw versions idk. I also tried different browsers(Opera, Firefox, Edge, Seamonkey, Chrome)ītw i have two devices in the same state now, so its definitely not a hardware problem. (my bad i wrote them by mistake about DIR device not DAP, thats why i got a wrong link from them, however, the problem persists) This was the link they sent me btw if it helps for anything: Finally the chat was out of informations and asked me to open a ticket for the experts to reach out to me, i agreed, i got now answer on the ticket after few minutes, they offer me a RMA. Tried to reset the device by holding the reset button some seconds after power onĭifferent OpenWRT factory and initramfs-kernel images linked in this Thread directly and newer files from RolandoMagico's Githubĭ-LINK support chat trying to get an unencrypted file or anything i could flash they send me an link to try but i think it is also encrypted and not meant for recovery use, however it leads me to the same result as the newer stock fw from the d-link support site I tried first. Renaming the openwrt files (to factory.bin and to the name of a stock d-link fw file) Only thing that shows correct size and MD5 information is when I upload a stock d-link FW. "Size: 1259 Bytes" or "Size: 1301 Bytes", depending on which browser I use and on every upload the MD5 is different for the same file. When I try to upload the OpenWrt images I always get something like: I tried to flash the fw but I always get stuck in recovery mode. As a casual OpenWRT user i hope to get a little help on flashing this device as i really stuck rn.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |