Posted: Sat Oct 17, 2015 14:11 Post subject: Re: Bricked R6300V1 Router
I tried to convert R6300V1 to R6300V2 as mentioned in below URL wherein BURNBOARDID is successfull after which uploaded V2 firmware through admin page which did restart after all the upload and I get a solid amber light which never changed later on.
So good news is that i bricked my device and managed to setup USB-TTL assuming that I could debrick it.
However, I hit another hard stop which I searched a while became invain hence bugging you all for any pointers.
AT CFE I am able to successfully upload R6300v2-V188.8.131.52_10.0.70.chk via tftp but on restart it gets stuck at 'Starting program at 0x80001000'
CFE for R6300 version: v1.0.5
Build Date: Wed Nov 21 15:03:38 CST 2012
Boot partition size = 262144(0x40000)
Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes
Device eth0: hwaddr , ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Checking crc...Loader:raw Filesys:raw Dev:nflash0.os File: Options:(null)
Loading: ........ 5048896 bytes read
Entry at 0x80001000
Starting program at 0x80001000
Stop the cfe, type tftpd and upload the r6300 factory firmware.
Although if you changed the board ID it won't accept the factory firmware.
May you can use a hex editor to change the the oem firmware so that the model number matches what you changed the boardid to.
Then you can possibly flash it back, use telnetable to change the boardid back to the original and flash the correct firmware.
I don't think you can change the boardid from the cfe. I could be wrong. _________________ I am far from a guru, I'm barely a novice.
Posted: Thu Dec 17, 2015 16:39 Post subject: USB SHARE OVER WEB
hi everyone... extremely new to dd-wrt
i have the R6300 v2
i have successfully installed the dd-wrt
and all seems to be working fine..
i was wondering if i could get some help setting up the router to allow me to be able to share the contents of my external usb drive ... i have managed to get it set up so i can access it from my smart tvs...my bluray players and all of my gaming consoles and mobile devices... while on my home network.... but i have alot of files for phone modding as well as movies that i would like to be able to share to those not on my network for anonymous log in (read only) because dropbox keeps disabling my share links for to many downloads....before i flashed dd-wrt i had my hdd set up to share my files through ftp ...but i am stumped on how to set it up with this firmware... i have googled my little fingers off and all i can find is how to set up file sharing through samba for home network...nothing on how to set it up for access over the web...any help would be appreciated!!! suggestions,links,anything would be appreciated
not sure if its relevant but the router i have has the blue stripe on the bottom of the face under the lights
and it was my understanding that the blue stripe on the r6300 v2 was the charter version(issued by an isp)
and the store bought router has a brown stripe??!!
when i got the router the firmware was the standard firmware not the charter(isp) firmware so i tried multiple times to install the regular dd-wrt for the non isp router and it would not work...so i tried kongs initial flash for the isp variant and everything worked perfect ...so im assuming someone had previously flashed the wrong stock firmware ...im running
Joined: 26 Apr 2011 Posts: 203 Location: Sacramento CA
Posted: Fri Dec 18, 2015 1:35 Post subject:
On the NAS tab you need to enable the WAN access and Anonymous Login (Read-only) options for FTP, Then provide the directory path. Assuming you have a static external address or using a DDNS service it should work for you. See attached screen capture.
Does anyone have recommendations for a long-term stable DD-WRT build for the AC1450? I flashed in a very old kong build back in the day (24045M) as it seemed like the most stable build available at the time. Unfortunately, I've noticed a consistent trend of WLAN chipset failures over the course of two months or so (one of the bands stops accepting connections, and the corresponding chipset temperature fails to update). Never did burnboardid, always did the recommended Kong solution instead flashing a different CHK first.
Anywho, my production router is a Cisco E2000, DD-WRT build 16785 with an uptime of 363 days - and the only times in the last few years it got restarted was when I thought it was the cause of an Internet failure, when in reality it was due to a combo cable modem crash and cable company outage. That's the level of reliability I'm looking for again =)