The firmware source I downloaded this evening includes an /etc/passwd file with a different root password hash, so they probably changed it between firmware versions:
The firmware source I downloaded this evening includes an /etc/passwd file with a different root password hash, so they probably changed it between firmware versions:
I have bf running on root:$1$$oQoSkI0acntd1i from couple of days and can continue. what will help? stop on old one and start on new hashed? let me know if anything else I can help or test. _________________ Linksys WRT54G-TM DD-WRT v24-sp2 mega - svn11650
Linksys WRT54G V8 - DD-WRT v24-sp2 micro plus - svn11650
Linksys WTR54GS DD-WRT v24-sp2 mini - svn11296
Last edited by sai0x0x on Tue Jan 20, 2009 15:04; edited 1 time in total
I've had JTR running on the $1$$oQoSkI0 password from the 1.0.15 firmware for three days now. It's still working. I suspect the other password in the source tarball is from the older firmware. _________________ 2x Asus RT-AC68U
Those units had CFEs, though, not U-boot. I'm not familiar with U-boot and its bootstrap procedure, though, so I'm not qualified to speak about it. I might take a look at the sources when I get a chance. Now I'm interested.
It's wireless-G (non-MIMO), but with 8 meg Flash, 64 meg DRAM, two SIM card slots (USB-connected, I believe) and two RJ-11 UMA ports, it's got plenty of room for DD-WRT Mega. (The ADM8668 Wildpass SoC is MIPS R4000-based) Linksys/T-Mobile currently stores two separate copies of the Linux kernel and SquashFS partitions in the Flash. I guess one of those pairs is either their fall-back/recovery or a scratchpad area for live upgrades. I haven't powered it up or connected yet, but will probably open it up and install a console port soon.
Unless this device is built with two 8M Flash chips, what you said above that the device stores two separate copies of the Linux kernel and SquashFS partitions in the Flash does not make sense since a WRTU54G-TM firmware is bigger than 5M in size. The total of two WRTU54G-TM firmware copies will definitely occupy a bigger space than 10M and that won't fit on an 8MB Flash chip, will it? _________________ Mazi
UK non-geo DID #: +447031942574
I took a look at the source, and it doesn't appear to have a makefile or any build scripts that I can find... this is going to be tougher than I thought. _________________ WRT54G v3 - v24 r14471M NEWD Eko - AP
WRT350N v1.0
WRT600N v1.1 - halfway there!
Se7en is Darker...
Joined: 14 Feb 2007 Posts: 5 Location: San Antonio TX
Posted: Tue Feb 10, 2009 9:21 Post subject:
bump..... anyone thing its possible after all to get ddwrt ported? _________________ I have a few win7 boxes plus a few win 2k8 r2 boxes and a few linux vm's with a netgear router with an ipv6 HE tunnel
Unless this device is built with two 8M Flash chips, what you said above that the device stores two separate copies of the Linux kernel and SquashFS partitions in the Flash does not make sense since a WRTU54G-TM firmware is bigger than 5M in size. The total of two WRTU54G-TM firmware copies will definitely occupy a bigger space than 10M and that won't fit on an 8MB Flash chip, will it?
The second Linux partition is significantly smaller than the first, as is its SquashFS partition. I suspect these are a very minimal configuration used only for loading firmware updates onto the main partition, or possibly for recovery. _________________ 2x Asus RT-AC68U
I took a look at the source, and it doesn't appear to have a makefile or any build scripts that I can find... this is going to be tougher than I thought.
Look for a small shell script named easy.sh (or something very similar.) I believe it's the original ADMtek build script that calls two or three other scripts to perform the build. Or that might have only been in the Vinetic sources from Samsung. My memory isn't that good these days. _________________ 2x Asus RT-AC68U
Starting from the pin near the JP2 silkscreen lettering:
