Hello. I have a TP-Link 850RE device. I had some issues - no internet connection, although the WiFi was working. I decided to install the OpenWRT firmware. After the installation and reboot, I only see the following:
login as: root
BusyBox v1.28.4 () built-in shell (ash)
| |.-----.-----.-----.| | | |.----.| |_ | - || _ | -| || | | || || | |** || |||||____****||| |** | || W I R E L E S S F R E E D O M
OpenWrt 18.06.9, r8077-7cbbab7246
=== WARNING! ===================================== There is no root password defined on this device! Use the "passwd" command to set up a new password in order to prevent unauthorized SSH logins.
root@OpenWrt:~#
The web interface is not working!!! What should I do?
I am copying the firmware file to 192.168.1.1 into the tmp folder, but the folder turns out to be empty.
I have read everything. The firmware name does not contain the word "boot". However, all the firmwares from the OpenWRT website and the official website are showing an error.
root@OpenWrt:/# sysupgrade /tmp/*.bin
Image metadata not found
Invalid image type.
Image check 'platform_check_image' failed.
Brick? Seriously? Well, thank you! I followed the instructions exactly. I wonder how many devices your website turns into bricks every year? How many people throw away their devices and buy new ones? I think the companies that manufacture routers should be grateful to you. I think they should even pay for your hosting and advertising.
Just to make one point clear: You installed OpenWrt because the stock firmware didn't work as expected. Obviously, the installation went fine, but you never told us if you have a 850REv1 or v2 and if you installed the correct firmware in the first place (judging from the file names you posted, it's v2).
Stop complaining, attach serial and recover your device. As long as it's blinking, chances are good that it's recoverable.
Congratulations. Welcome to the club. By electing to install a different firmware than the vendor-supplied one, you have demonstrated an innate curiosity and willingness to tinker, because you're not satisfied with being spoon-fed something from the manufacturer. Such inquisitiveness will stand you in good stead.
If you can get to the SSH command line, then your device is not bricked. It boots, and boots successfully. There may be other issues preventing you from gaining access to LuCI, so your inquisitiveness that I mentioned above will help you get to the bottom of the problem.