Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Tue Aug 11, 2009 14:54 Post subject:
I really did it out of necessity...if you look at Miguelpe's picture...when it isn' bent, the motherboard won't fit in the case any longer. The JTAG comes off the front of that Mobo and there just isn't room for it.
But...yeah...I'll admit it...I'm a dd-HO!
redhawk _________________ The only stupid question....is the unasked one.
I have just fixed one bricked wrt310n using jtag method. Router was bricked after v2 firmware was flashed on v1 hardware. Thanks for useful information.
Joined: 06 Mar 2009 Posts: 107 Location: MinneSOTA!
Posted: Sat Dec 04, 2010 17:17 Post subject:
Can I get some help debricking my wrt310n?
I run jtag -probeonly, and it hangs on Enabling Memory Writes... and won't move. Im using EJTAG version 3.0.1 Tomato-Mod, and my router is a WRT310n V1. Any ideas? _________________ My Hardware:
1x WNDR3300 - 14853 NEWD C/AP Mini-HotSpot-Kaid
1x WRT54G2 - 13577 NEWD RB Micro
1x WRT310N - TomatoUSB Dev Test Build 9-22-10
1x RT-N16 - TomatoUSB SVN Build 9-13-10
You will always get some response, what is the screen output from tjtag and where does it fail/stop? _________________ Kernel panic: Aiee, killing interrupt handler!
the program response is exactly as pictured in PIKETEAM's first message.
Many possible errors..
Too long cable
Cable not connected correct (check pin numbers)
Wrong LPT port setting in bios
Win7 _________________ Kernel panic: Aiee, killing interrupt handler!
Ok, but is it even soldered to the right spot? I have seen conflicting posts that say the JTAG is where I have the connector soldered, and others say it is the pin holes to the left of it.
Ok, but is it even soldered to the right spot? I have seen conflicting posts that say the JTAG is where I have the connector soldered, and others say it is the pin holes to the left of it.
The pin holes to the left are apparently for the radio.
You would still get a valid cpu detection even in the wrong connector as someone demonstrated in the beginning of this thread.
All 1's is an error you get when the tjtag hardware is in error. _________________ Kernel panic: Aiee, killing interrupt handler!