Posted: Tue Dec 24, 2013 19:02 Post subject: WinSCP Access denied
Hi
I've just dug up my old WRT320N which I intend to use as a WAP. It had Tomato on there but I've removed it using the instructions on the Wiki and have put dd-wrt.v24-18946_NEWD-2_K2.6_mini_wrt320n on it.
I've followed the instructions here and edited the HEX file. I'm ready to put the CFE file in the temp directory on the router but I keep getting "Access Denied". I have reset the router to defaults many times, changed the password and even user name but I can't get to login.
I am using WinSCP version 5.5. I hope someone can help me as it seems converting the WRT320N into E2000 is a good thing to do.
Posted: Sat Jan 11, 2014 23:29 Post subject: Re: WinSCP Access denied
hi2shy wrote:
Hi
I've just dug up my old WRT320N which I intend to use as a WAP. It had Tomato on there but I've removed it using the instructions on the Wiki and have put dd-wrt.v24-18946_NEWD-2_K2.6_mini_wrt320n on it.
I've followed the instructions here and edited the HEX file. I'm ready to put the CFE file in the temp directory on the router but I keep getting "Access Denied". I have reset the router to defaults many times, changed the password and even user name but I can't get to login.
I am using WinSCP version 5.5. I hope someone can help me as it seems converting the WRT320N into E2000 is a good thing to do.
Many thanks!
Not sure if you still need help on this, but I ran into this issue as well and I had to install dd-wrt.v24-14896_NEWD-2_K2.6_mini_wrt320n.bin
on my WRT320N for SSH to work. Also remember to use SCP not SFTP in WinSCP.
Hey guys! I already have a successfully converted WRT320N to E2000 unit. Can I somehow revert it back to its original wrt320n state? I need to use it on its stock 320n's linksys firmware. Don't ask me why, I just wonder is it possible? Thanks!
20675 nv60k big fit my E2000 as well despite my doubts LOL. first flashed branded mini then that and it went through.
I think that something got improved with broadcom driver in this or earlier build as it nicely downgrades the speed when connected wifi devices go to power save mode, but it brings the speed up nicely as well when devices are used actively. so far seeing 104Mbps on average when using devices actively, that's an improvement, I think.
Also a big plus is that now the CPU speed get clocked by default at 300MHz, so no more need to downclock it manually through nvram commands. that's a big plus too.
Lastly, on 18946 QoS was NOT working at all for me, now it seems to run flawlessly. another big plus.
so far liking 20675 very much on my converted E2000 (WRT320N actually), pretty solid firmware! thanks!
EDIT:
QoS didn't survive the BitTorrent download test (with Bulk settings on torrent packets), had to restart the router because it became unresponsive. After disabling QoS,no more problems.
and also the N-band Wifi speeds jumped up to max 144, sometimes between 104-117 when more devices are connected.
If not for QoS issues, I'd call this firmware the best, well it still is hehe.
I've installed 20675 an got 354MHz as always.
Thank you for the instruccions buddee very good tutorial.
Joined: 04 Jun 2015 Posts: 9 Location: benz0l_Hamburg
Posted: Thu Jun 04, 2015 16:00 Post subject:
Hi,
i'm finally joining the dd-wrt world too and i'm preparing to convert a untouched/ootb wrt320n to E2000
and i want to use dd-wrt.v24-25697_NEWD-2_K3.x_mega-e2000.bin as my target firmware
(as i understand i have to pick from the broadcom_K26 or broadcom_K3x section of the given build
and then look for the big/mega-e2000.bin files, or for the K26 it would be named big-nv60k.bin)?
I am following the doc posted by blikjebier on page 14
My questions:
from which point of the procedure is it ok to use the most current build?
or from the other perspective: at which points do i have to stick to the exact versions/filenames as stated in the doc?
the only K2.6_std_mod-e2000.bin i could find is the 14853 on the first page attached to a post from buddee so i guess i'll be starting with
dd-wrt.v24-14853_NEWD-2_K2.6_mini_wrt320n.bin ?
aree there any newer std_mod-e2000 versions available via the official "other-downloads" site?
as i am from Germany i'll be editing the e2000_eu_generic.cfe as posted on page 23 of this thread, right?
Joined: 07 May 2017 Posts: 3 Location: Salt Lake City, UT
Posted: Tue May 09, 2017 3:34 Post subject:
When trying to implement the cfe part, I always get the following error message.
Unlocking cfe...
Could not unlock MTD device: cfe
cfe: Operation not supported
I have attached a screenshot. Am I missing anything?
In the end it said
writing from cfe_e2k.bin to cfe... [w]
Did it work after all and could I proceed with flashing the firmware?
Additionally, Underneath my router the mac address ends in in :16, but when I go into the Router Information/Status window in the GUI my Mac address ends with :17. To edit the cfe I used the Mac address underneath my router, but could the sticker be wrong? Does this even have anything to do with my problem?
Joined: 18 Mar 2014 Posts: 12881 Location: Netherlands
Posted: Tue May 09, 2017 12:20 Post subject:
I did it some time ago so I am not absolutely sure.
The unlock error could be due to the fact that you did not start with the recommend 14896 build. Later builds throw an error BUT it writes anyway so be patient and ignore the error.
Regarding MAC address use the address at the bottom, your router has more than one MAC address, your LAN/WAN/WIFI all have different (albeit related) MAC addresses.
The MAC addres at the bottom should correspond with your LAN MAC address, your WAN is one up and WIFI again one up.
So just follow the guide _________________ Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399 Install guide R7800/XR500:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614 Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Posted: Tue Jun 27, 2017 0:28 Post subject: problem
Guys. I followed the instructions verbatim. Flashed the firmware with the modified headers, set it to "Reset to Defaults". Went for coffee.
When I came back, the router has no telnet, no DHCP. If I connect it to my main router, it works as a router and I can access the internet just fine. It even broadcasts the "dd-wrt" wifi network! But I cant access the router.
This doesn't look like typical bricked behavior to me? I did 30/30/30 reset through the now-working reset button, same problem. Tried setting static DHCP to 192.168.1.1 to try tftp, but ping doesn't work at any time during boot.
Posted: Tue Jun 27, 2017 19:30 Post subject: Re: problem
x0a wrote:
Tried setting static DHCP to 192.168.1.1 to try tftp, but ping doesn't work at any time during boot.
You didn't set your PC to a static IP of 192.168.1.1, right? As that's the default DD address. Gateway and DNS are 1.1, but IP is not (use e.g. 1.10), and you TFTP to 1.1.
Posted: Sun Jul 02, 2017 5:25 Post subject: Bricked WRT320N, my fault. How to fix?
Code:
You didn't set your PC to a static IP of 192.168.1.1, right? As that's the default DD address. Gateway and DNS are 1.1, but IP is not (use e.g. 1.10), and you TFTP to 1.1.
No, I messed up I used the wrong MAC address (was slightly covered by sharpie). It boots, and functions as a router, but I cant communicate with the router.
I spent the last two days trying to figure out a way to JTAG flash the original CFE (bought TUMPA lite). I'm seeing a lot of conflicting information about whether or not this router can actually be JTAGd. Tornado isn't responding to donations so I'm using zjtag. It doesn't recognize the flash chip (mx25l6405dmi-12g), so I set it to /fc:107 (a slightly similar chip). It works.. to download the CFE on the router, but it can't actually flash the new CFE.
Posted: Wed Jul 05, 2017 14:21 Post subject: Re: Bricked WRT320N, my fault. How to fix?
x0a wrote:
Has anyone actually been able to JTAG this thing?
You should be able to hook up serial, no need for JTAG. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
I used the wrong MAC address (was slightly covered by sharpie). It boots, and functions as a router, but I cant communicate with the router.