Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: antoniotrkdz on September 19, 2014, 10:44:50 PM
-
Hi All!
I just signed to this forum.
I got a TD-W8980 and I would like to crossflash it with the TD-W9980 firmware as I just upgraded my home to fibre (talktalk).
I am a bit confused so could any of you good guys be so kind to post a step by step guide on how to do it?
It doesn't need to be a super detailed guide, just a list of the logical steps to take, I think it would be beneficial for others (noobs) like me also.
I am using Debian GNU/Linux.
Thanks!
**/ NOTE by Admin / **
hatrix2006 has kindly made a video using information from this thread and uploaded it to YouTube - Crossflash TP-Link TD-W8980 to TD-W9980 (https://www.youtube.com/watch?v=vjSLGEkZd_E&feature=youtu.be)
-
I just finished crossflashing W8980 to W9980.
Look at picture [1] of the top part of the case and without causing damage use a plastic opening tool to free the back clip and the rest of the case should loosen.
Look at OpenWRT W8970 wiki page [2] for J7 serial header info. The square pad is 3.3V then it's GND, RX, TX. It also tells about press t to break into U-Boot and the serial username/password is admin/1234.
My W8980 factory oem firmware is 0.6.0 1.5 v000e.0 Build 140408 Rel.49241n. I created a backup of the flash (8MB) using U-Boot and putty logging:
sf read $(loadaddr) 0 0x800000
md.b $(loadaddr) 0x800000
I used the crc32 command to checksum the image in ram:
crc32 $(loadaddr) 0x800000
I cut the hex dump from the putty log and converted it to a binary image using xxf -r and used the tftp command to load the binary image into memory and verified it's checksum.
I used TP-Link's web interface Firmware Upgrade to update the router to the W8980 140627 firmware [3] so you should probably do that too. I did it so I could compare the contents with the flashed image to find out what to cut to flash the W9980 firmware using U-Boot. Also I just noticed the website and zip file say 140627 but the firmware in the zip is 140701, not that it matters though.
Download the W9980 140613 firmware [4] and use a Hex Editor to cut the first 0x20200 bytes and you should end up with a file size of 0x7a0000 bytes (TP-Link header is 0x200 and U-Boot etc is 0x20000). Setup a TFTP server on your PC. To load the cut image into memory and flash it via U-Boot:
tftp cut_image.bin
sf erase 0x20000 0x7a0000
sf write $(loadaddr) 0x20000 0x7a0000
Make sure you don't make a mistake to erase below 0x20000 (ie. don't do 3 zeros instead of 4) otherwise you could brick your router.
When the flashing is complete you should reboot the router and login to the web interface. It'll say there is an internal error but you can fix that by doing a factory reset (System Tools -> Factory Defaults).
We haven't updated to the W9980 U-Boot yet but you can do so by downloading the latest W9980 firmware update (140819) from TP-Link's Download page [5] but I haven't gotten that far yet.
[1] http://static.techarena.it/wp-content/uploads/2013/08/TP-Link-TD-W8980-Foto-16.jpg
[2] http://wiki.openwrt.org/toh/tp-link/td-w8970
[3] http://uk.tp-link.com/resources/software/TD-W8980_V1_140627_UK.zip
[4] http://uk.tp-link.com/resources/software/TD-W9980_V1_140613.zip
[5] http://uk.tp-link.com/support/download/?model=TD-W9980&version=V1#tbl_j
-
Thanks a lot for the time you spent putting together this guide!
-
Hi vs1 & welcome.
Thanks for putting together and sharing your guide on how to crossflash the TD-W8980 to the TD-W9980. Ive split this thread as it deserves its own topic :)
-
Thanks.
I used the web interface to upgrade to W9980 140819. I have it connected to a faulty broadband line and the connection speed is slightly different compared to 140613. It's also reporting the upstream line attenuation for the first time:
Upstream Downstream
Current Rate (Kbps) 9999 18000
Max Rate (Kbps) 22894 79709
SNR Margin (dB) 12.7 22.8
Line Attenuation (dB) 18.3 17.5
-
also reporting the upstream line attenuation for the first time
Upstream attenuation is one of the items that they fixed at my request. One of the other bug that should also have been fixed in that same version is the downstream Max rate now updates correctly.
connection speed is slightly different compared to 140613
I believe they did some tweaking to the bit loading and bit-swap. Bit swap should now be more efficient and the SNRm slightly more stable.
-
Good job. The upstream line attenuation was a very nice surprise.
-
Hello,
I just want to say that crossflash instructions are very clear and so my TD-W8980 is now a TD-W9980 with the latest firmware 140819.
But I'm disappointed to see that the router is not supporting the IPoA in VDSL mode.
Since my french ISP is using IPoA do you know if it is possible to patch manually a configuration file to enable this support ?
An example of manual patch is given here (in french): http://zwindler.wordpress.com/2013/11/17/configurer-le-thomson-789vn-en-vdsl2-sur-ligne-free-degroupee/ (http://zwindler.wordpress.com/2013/11/17/configurer-le-thomson-789vn-en-vdsl2-sur-ligne-free-degroupee/)
-
Hi Fuli and welcome :)
Im afraid I cant speak for a TD-W8980 thats been cross-flashed.... as mine are OEM TD-W9980 which supposedly support IPoA
PPP over ATM (RFC 2364)
PPP over Ethernet (RFC2516)
IPoA (RFC1577/2225)
PVC - Up to 8 PVCs
Perhaps one of the guys who have cross-flashed will be able to give more info.
-
Hi kitz
(thanks for the move of the post)
Even after the crossflash modem supports IPoA. The issue is that it is supported only for ADSL2+ link but not for VDSL.
That is quite stupid since VDSL is only a kind of line bandwidth optimization and have nothing (except maybe some small change) with ATM stack. So that IPoA stack should work the same on VDSL.
Sorry my fault. VDSL supports PTM instead of old ATM. I suppose I should ask my ISP if PTM is well used for VDSL and what is the correct VLAN ID.
If I found nothing to solve that in the near future, I think I will test openWRT for W8970.
(my current status now: trunk doesn't compile on my system, and it seams that 5GHz Wifi is not working yet)
-
Im afraid I dont know. :(
I do know that the firmware that has recently been released is aimed for TD-W9980 which has only just come on to the market in the UK.
Since we dont have IPoA vdsl in the UK it may be that its been omitted. Whether there is a way you can create some sort of new interface yourself I dont know sorry.
-
Hi, I see that TP-Link have added firmware 140925 on their website for the 9980 - anyone flashed this into their 8890 and verified if it still works?
There is no change log for the update. For some reason I cannot register on the official TP Link forum can maybe someone here who is registered ask what the changes are?
-
I havent, and I'd rather not put the TP-link on atm because Ive recently had some line instability issues, so its not the best time for me to be testing anything atm.
I have written to my contact at TP-link to see if he has any details.
The last I heard was on the 21st of Sept when they said they were looking at providing more detailed line stats, adding UK ISPs to the vdsl quick setup and improving the media server - their quote "I believe next version will be much better."
-
Thanks - I am not sure if I should try this new frimware - I secretly fear they might add something that prevents the 8980 HW from running the 9980 FW
-
Thanks - I am not sure if I should try this new frimware - I secretly fear they might add something that prevents the 8980 HW from running the 9980 FW
The 8980 and 9980 hardware is exactly the same. The only way of blocking this crossflash is disabling the cfe/u-boot capability of flash the spi memory.
Edit. Just tested the new firmware with my 8980@9980. It works fine.
-
Got this reply
This version fixed some UI bug, SNR issue in other regions, and improved the 5G performance.
There is also another f/w version which will be out very soon, that improves media TV streaming
-
Ok performed the upgrade - can confirm that 140925 works fine on the 8980.
-
BT fixed a HR fault so now my second line broadband is working fine again but the router often stops working requiring a reboot to resolve it. Here are a couple of serial logs showing it's running out of memory:
dsl_cpe_control invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0
Call Trace:
[<8000b9fc>] dump_stack+0x8/0x34
[<80062274>] oom_kill_process+0x68/0x200
[<800629a0>] __out_of_memory+0x17c/0x1b0
[<80062a44>] out_of_memory+0x70/0x9c
[<80066184>] __alloc_pages_nodemask+0x4b4/0x5e0
[<800685e8>] __do_page_cache_readahead+0xd8/0x284
[<800687bc>] ra_submit+0x28/0x34
[<80068d9c>] page_cache_sync_readahead+0x5c/0x68
[<8005f9b4>] filemap_fault+0x1c4/0x4b0
[<800735c0>] __do_fault+0x74/0x5bc
[<80074ccc>] handle_mm_fault+0x134/0xfd0
[<800205f0>] do_page_fault+0x110/0x314
[<80002480>] ret_from_exception+0x0/0xc
Mem-Info:
Normal per-cpu:
CPU 0: hi: 18, btch: 3 usd: 0
active_anon:409 inactive_anon:416 isolated_anon:0
active_file:10 inactive_file:13 isolated_file:0
unevictable:192 dirty:0 writeback:0 unstable:0
free:1280 slab_reclaimable:93 slab_unreclaimable:11046
mapped:69 shmem:0 pagetables:108 bounce:0
Normal free:5120kB min:5120kB low:6400kB high:7680kB active_anon:1636kB inactive_anon:1664kB active_file:40kB inactive_file:52kB unevictable:768kB isolated(anon):0kB isolated(file):0kB present:65024kB mlocked:0kB dirty:0kB writeback:0kB mapped:276kB shmem:0kB slab_reclaimable:372kB slab_unreclaimable:44184kB kernel_stack:552kB pagetables:432kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:144 all_unreclaimable? yes
lowmem_reserve[]: 0 0
Normal: 2*4kB 1*8kB 1*16kB 5*32kB 5*64kB 2*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 1*4096kB = 5120kB
215 total pagecache pages
16384 pages RAM
1172 pages reserved
126 pages shared
12824 pages non-shared
Out of memory: kill process 603 (cwmp) score 32 or a child
Killed process 603 (cwmp)
ushare invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0
Call Trace:
[<8000b9fc>] dump_stack+0x8/0x34
[<80062274>] oom_kill_process+0x68/0x200
[<800629a0>] __out_of_memory+0x17c/0x1b0
[<80062a44>] out_of_memory+0x70/0x9c
[<80066184>] __alloc_pages_nodemask+0x4b4/0x5e0
[<800685e8>] __do_page_cache_readahead+0xd8/0x284
[<800687bc>] ra_submit+0x28/0x34
[<8005fa20>] filemap_fault+0x230/0x4b0
[<800735c0>] __do_fault+0x74/0x5bc
[<80074ccc>] handle_mm_fault+0x134/0xfd0
[<800205f0>] do_page_fault+0x110/0x314
[<80002480>] ret_from_exception+0x0/0xc
Mem-Info:
Normal per-cpu:
CPU 0: hi: 18, btch: 3 usd: 14
active_anon:408 inactive_anon:416 isolated_anon:0
active_file:6 inactive_file:9 isolated_file:0
unevictable:192 dirty:0 writeback:0 unstable:0
free:1278 slab_reclaimable:88 slab_unreclaimable:11153
mapped:71 shmem:0 pagetables:108 bounce:0
Normal free:5112kB min:5120kB low:6400kB high:7680kB active_anon:1632kB inactive_anon:1664kB active_file:24kB inactive_file:36kB unevictable:768kB isolated(anon):0kB isolated(file):0kB present:65024kB mlocked:0kB dirty:0kB writeback:0kB mapped:284kB shmem:0kB slab_reclaimable:352kB slab_unreclaimable:44612kB kernel_stack:552kB pagetables:432kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:136 all_unreclaimable? no
lowmem_reserve[]: 0 0
Normal: 0*4kB 1*8kB 1*16kB 7*32kB 8*64kB 0*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 1*4096kB = 5112kB
207 total pagecache pages
16384 pages RAM
1172 pages reserved
118 pages shared
12820 pages non-shared
Out of memory: kill process 603 (cwmp) score 64 or a child
Killed process 603 (cwmp)
Currently it's providing internet access only for the Xbox 360 and Xbox One for Xbox Live.
It has the 140925 firmware but I will try downgrading to the previous firmware.
-
Hi, Just wondering if anyone has successfully flashed the 8980 with 141215 9980?
-
MASSIVE EDIT: I have now got a TD-W8980 @9980 with the latest firmware to date.
Followed everything over then backing the old firmware but followed the rest.
So i will now make a noboot image of a TD-W8980 firmware should i need to go backwards and TFTP flash that image should i need to get things back.
Thanks for the guide folks.
Also instead of using Hex edit i used DD command below.
dd if=originalfile.bin of=cutfile.bin skip=257 bs=512
Where Original file is the original firmware file and the cutfile is the end product with the first 0x2020 bytes removed.
-
@hacktrix2006
Hi have you updated to the latest 9980 firmware and have you any issues with it? I have flashed an older one but would like to use the latest but not sure if its stable. Thanks
-
Yes flashed latest and it worked well, flashed back to 8980 again though due missing PPP logs etc.
-
HI All first post so go gentle , I upgraded to SKY Fibre just after Xmas and then realised how usless the SR102 is . I had not long bought a TD-W8980 so this post interests me but will it actually work on SKY ? I have a HG612 but it seems only possible to get this working via Telent which works but not if the MODEM is restarted which if i'm out of the country will upset my wife slightly ;) I have never used any of the tools listed or coded a thing but think i can work it out if the modem will work on sky after the effort . all hep appreciated Jon
-
Hi mate it should work with Sky. On the TD-W9980 firmware there is a Quickstart area which has ISP profiles.
Just bare in mind that you need to cross flash the TD-W8980 to a TD-W9980 via serial to do fibre.
Its not that hard to do either.
I do have the latest firmware with boot removed should you need that too and following the guide on this thread should make the crossing flashing for you is as painless as possible.
If you need help with the flashing of the device i am very sure some one here on the forums will be willing to help.
-
when you say serial , is that an additional cable ?
-
when you say serial , is that an additional cable ?
Yes its additional cable which has to be done by end user. I have some pics of mine before and after with after having a Pin header so i could use a TTL cable via USB.
Here are the pics: (Click the links and it will open a new window/tab with the image!)
Before:
http://gdurl.com/Jb6b
After:
http://gdurl.com/Sqml
I then used a cable like one attached.
Then on my header i then used from the First pin to last
From the top down.
1st Black
2nd Green
3rd White
I then used a program called putty to connect via serial and followed the Guide in this thread minus the Backing up of the flash.
-
Cheers , so I need to put the pins on the board as well ? This should be fun ,it seems a shame to chuck a 2 week old router if i Can make this work
-
Cheers , so I need to put the pins on the board as well ? This should be fun ,it seems a shame to chuck a 2 week old router if i Can make this work
You can just solider wire to the pads, i used pins as it was a clean way of doing it. I.E you can just solder the pins in place connect a TTL USB Serial cable to it, then flash the TD-W9980 firmware then un-connect the TTL and close the lid when finished, Then reconnect back to the pins when you need them again.
If you do go for the Pin method, the best way i found was to remove the plastic that holds the pins then solder the pins on and then replace the plastic back. How ever a fine tip will be needed to do this on the soldering iron.
I am also going to do a image with the pin outs for you too.
Here is the pinout i used for the Connection using a Pin Header and Raspberry Pi USB to TTL Cable (which i got off ebay i can find some links for you if you wish.)
-
Thanks for that , Ordered a cable so will have a go when it turns up . does it take long to flash it ?
-
Thanks for that , Ordered a cable so will have a go when it turns up . does it take long to flash it ?
It took me a couple of minutes to do. If you get stuck you can PM me, i will then try my best to help you. Bare in mind once you flash the TD-W8980 to TD-W9980 only firmware from the TD-W9980 can be used in the WebGUI after, To go backwards will require a TD-W8980 to be cut to remove the boot segment and then reflashed via Serial TTL again.
But when i was running TD-W9980 firmware on the TD-W8980 i didn't see any issues at all, no overheating issues nothing.
Goodluck!
-
Ok , If possible some screen shots of the Putty would be appreciated so I know i'm doing the correct thing . I see no reason to go back once i have done this so not worried about going back , can I PM you my email so you could email me the firmware with boot already removed ?. Thanks once again
-
No need to give me your e-mail address i can just upload it and link it up for everyone else as well.
I can give you screenshots of how to set putty up for connecting but as the data feed after connection is live from the router it would be difficult to do so.
TFTP i can also screenshoot as well. If the Original poster to the method agree's i can make a proper tutorial for the Kitz Forum. I will contact the original poster first for that.
I will upload the images tonight and then PM you the links as I have Images for both ways with Boot removed and they worked as it was what i used myself during the flashing stage.
How ever i don't want to step on someones toes so to speak so i will PM the original poster first and get permission and then make a Tutorial after that.
Edit: Tutorial is now drafted up and i am awaiting approval from @vs1 Before Posting it. However, how one is going to turn a 9 page document into a 1 Post thread is anyone's guess. It does however have links to everything thats needed and a few pictures of the PCB and Settings for Putty and the TFTP.
-
I didnt think it would be long until I had to post , Write I have put PINs on the board I have received my Serial cable . Serial Cable drivers installed I have putty installed but don't seem to be able to get a connection , as soon as I switch the router on it locks putty screen ? . Any help greatly appreciated
-
Hi,
Let me first say sorry for bringing this thread back.
I've been following this thread periodically since I bought my W8980 in Octoberish. I'm going to attempt to do this tomorrow (when my serial adapter arrives) and just want to go through a few things.
1. I've tried cutting the firmware down from 0 - 20200 and I'm left with 79FFF0 instead of 7A0000 (one line before), am I cutting it to early or what?
2. Could this be because I'm using the latest firmware? (I think I tried with the firmware linked at the start of the thread and came back with the same results)
3. After I've done this once, it's just a case of updating through the web gui instead of using serial, correct? (Meaning no further cutting of firmware unless flashing back to stock)
If you could just help me with those three points that would be great.
Thanks,
Chess
-
Check your PM. Also cross flashing can not be done via a webGUI its done via a Serial connection which requires the Router to be modded to accept a communication between the Computer and Router at a lower level.
I have sent you a link to the Cut images (Which has Boot partition removed, done myself in linux using DD) and a unfinished guide i was making which would give you a very ruff idea on whats involved.
-
I've flashed the 9980 141215 firmware onto my 8970 via the web interface. First I uploaded a modified config file with some model numbers set to 9980 values. I wasn't really expecting it to work, but it did, and of course the config was reset to factory defaults. Everything at least superficially looks like it works OK, obviously it still doesn't have 5GHz wireless.
-
Nice one @ejs just a shame about open-wrt with 5ghz issue
-
I bricked my 8970 yesterday morning. First I downgraded the firmware to 9980 140613 via the web interface. I learnt nothing particularly useful about that firmware version apart from the saved config files are compressed somehow, the same way as with the latest. So I decided to upgrade back to the 9980 141215 firmware again - which bricked it. Not really surprising since all this messing about flashing firmware is going to be risky, but I was more expecting it to break at the first attempt to flash 9980 firmware, not the third time.
I'll have a go with the serial port in a few weeks time if/when the USB TTL serial adapter I ordered arrives. It wouldn't surprise me if I find that the bootloader is also trashed since TP-Link seem to upgrade or downgrade uboot in every different firmware version, in which case I might as well see what I can do with JTAG.
-
Oh dear. Its always best to use cut images when downgrading @ejs which requires TTL but it might no be a full brick it might be unpacking of the kernel at boot which is after uboots boot up. So long a uboot boots you should be OK unless uboot is messed up. Good luck mate if you was local I'd let to use my TTL and laptop to revive it. I even have the pins for TTL. Good luck all the same.
-
Hi all, is the W8980 end of life now? I picked one up last monthish for Ģ30 from Argos. Nice and stable currently running just as a wireless access point.
Is the crossflash process still applicable to the latest G.INP Beta firmware TD-W9980v1_0.6.0_1.10_up_boot(150409)_2015-04-09_11.19.29.zip (http://forum.kitz.co.uk/index.php/topic,15322.0.html)
Is the hardware really identical between the W8980 and W9980? If so why do we need to butcher bootloaders and such?
After upgrading will future updates always have to be done via serial?
Thanks for the info :)
-
Yes cross flash rules still apply for the latest beta w9980 firmware. Currently on that firmware myself. However you can flash the old precut image w9980 firmware then upgrade to the beta one via GUI after.
-
Yes cross flash rules still apply for the latest beta w9980 firmware. Currently on that firmware myself. However you can flash the old precut image w9980 firmware then upgrade to the beta one via GUI after.
Thank you for the weirdly fast reply ;D
Great to hear all is working.
-
Just make sure you have a secure serial connection and don't downgrade the w8980 firmware else it might go funky just get the precut w9980 image and flash over via ttl serial
-
Thanks for the advice, I found a precut image here (https://forum.openwrt.org/viewtopic.php?id=52127&p=2), is that the one you meant?
My soldering adventure was a total failure but at least I didn't brick anything. Wobbling my pins around actually gave me some (garbled) booting messages before the pin broke :lol:
Trying to think what I could steal a header from to recycle for serial attempt #16.
-
LOL, i used Break-Away 0.1" Male head stripe (3 pins only needed in total). Basically with the 3 pins you solder that on to the clump of 3 pin holes. There is a image of the connection i put in this thread somewhere lol. The trick my father used was to pull the plastic sleeve holding the pins up slightly and then tin the bottom of each ping with flux and solder then place the pins into the hole then solder to the PCB after the solder has set push the sleeve back down carefully.
I have pre-cut images in my mega account for all the thats required if you need it. As for Garbled screen output that would suggest you might have placed the RX and TX in the wrong place.
But goodluck if you need a helping hand just PM me. Just do not put a pin or connect to the pad near the Heatsink as that is VCC which is not required.
-
Good shout on the 0.1inch header, got one from Maplin for Ģ1. Garbledness seems to be ok now.
I wouldn't mind having a copy of your pre-cut images if you are willing to share that Mega link?
Yesterday I did have VCC attached hopefully I didn't do any damage.
Thanks again
-
Ya sure here is the Pre-Cuts: https://mega.co.nz/#!LElwWJRB!jJsXuIsni0K3eUJaFZAew6G1Wddgtj2lv5269HMRX8M
If the Router is still booting your blooming lucky mate. I'd never put anything to VCC just because it will sometimes fry the crap out of the Routers.
Have fun BTW do you need a Guide?
-
Thanks for the precuts! Sure, if the guide differs to what is on page one it would be more than welcome.
It boots (still stock firmware) I should probably buy a lottery ticket because I had no business even attempting to do the soldering + then I connected VCC :lol:
-
Check PM bud!
-
Thanks hacktrix2006!
Firmware Version:0.6.0 1.10 v0021.0 Build 150409 Rel.40749n
Hardware Version:TD-W9980 v1 00000000
I gave up trying to backup my stock device. But I flashed to your precut image as per the instructions and then upgraded to the G.INP Beta firmware (http://forum.kitz.co.uk/index.php/topic,15322.0.html) via the Web UI successfully.
I will go back to running in wireless AP mode for a little while before trying to retire my aging BT HomeHub.
Good stuff, I appreciate the sharing + it was good to see the output of the commands in your document.
Pretty promising device for the price!
-
Congrats mate glad it all went well. W9980 firmware is working well on my internet connection no issue other then the crappy aerials being 5db / 3.5db.
-
The aerial situation interests me.
The internal two 2.4Ghz antennas look fine but I will probably chop them off and add a set of RP-SMA connectors to open up other options.
The three external aerials for the 5Ghz radio appear to be needlessly large. I admit my understanding is limited but from what I can gather given the rating they should be much smaller in size than the 2.4Ghz antennas.
Some devices apparently share the same set of aerials to both 2.4Ghz and 5Ghz radios, but this is not the case with our device. When they get shared like that they seem to be called "dual band" aerials and are simply a cost saving compromise and are pretty much just 2.4Ghz aerials that work "ok" on 5Ghz, im wondering if we have been lumped with 3 of those because that's what TP-Link had laying around.
Either that or the aerial casing is 90% empty and just for show.
I haven't been able to open one of the aerials to confirm either theory and I would rather not destroy one by cutting it open. I am happy to be corrected, I am just trying to understand whats going on.
If you fancy chopping one of the aerials open let me know :D Also if you are interested in DIYing a new set of 5Ghz aerials there are many examples on this YouTube channel. (https://www.youtube.com/user/8bitandrewmcneil)
It would be nice if we could increase the transmit power of the radio's also but from my quick testing (iwconfig ath0 txpower) they appear to be limited to weedy 17dBm or 50Mw.
-
anyway to increase the power on TX. Its the 5GHZ that sucks for me 2.4GHZ is fine infact two walls between me and the router and it still is a full bar signal on 2.4GHZ but 5GHZ is less then 3 bars if i am lucky.
-
It's a simultaneous dual band device meaning it can use 2.4GHz and 5GHz as 2 separate networks at the same time.
I agree that the 5Ghz is very poor, I had to be in the same room to see any benefit from the 5GHz range. As soon as I moved to the next room it wasn't any better than 2.4Ghz.
The 2.4Ghz was ok......
.. but still not as good as my VMG8324 which has (2x2 MIMO) 11n, so although my Zyxel doesnt have 5Ghz it does appear to have a better range reach meaning I can use my ipad at the very bottom of my garden, which unfortunately just drops out of range if I use the TP-link.
Im not sooo not impressed with all the 5 GHz hype. :(
-
I've been using 5ghz for years and never had a problem with range. Originally I was using a HP Procurve A/B/G wireless access point, but recently I switched to an Asus RT-AC66U.
-
I also have an ASUS router (RT-AC56U) which supports 5ghz.
(I am running the latest custom Asuswrt-merlin (Ver:378.52_2) software)
It is much better than 2.4ghz in terms of throughput and range has never been a problem.
In fact the problem is that the range extends too far outside, in the wrong direction. ;D
(Cannot move the router from its location without routing long cables for power/ethernet etc.)
-
I'm not sure if anybody can help, but I'm stuck trying to crossflash my TP-Link TD-W8980. I'm moving over to Zen and an FTTC service (in 3 days). I already had the TD-W8980, and would rather use it over the Zen supplied Technicolor TG589vn v3. The part that isn't working, is loading the cut image into memory. I'm on Windows 7, but have tried it on WinXP as well.
I setup a Tftp (Tftp64 - Philippe Jounin). I can test this working via Cmd.exe and "tftp -i 192.168.1.73 get 123.bin".
When I try to copy the bin file over via putty, it just seems to time out.
Putty and the serial cable connection seem to be working fine.
I renamed the cutimage from TD-W9980_cutimage.bin to 123.bin to save time typing. ;D
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.05.04 19:25:36 =~=~=~=~=~=~=~=~=~=~=~=
ROM VER: 1.1.4
CFG 05
ROM VER: 1.1.4
CFG 05
DDR autotuning Rev 0.3ff
DDR size from 0xa0000000 - 0xa3ffffff
DDR check ok... start booting...
U-Boot 2010.06-LANTIQ-v-2.0.40-svn7415 (Jun 23 2014 - 17:30:19)
CLOCK CPU 500M RAM 250M
DRAM: 64 MiB
Using default environment
In: serial
Out: serial
Err: serial
Net: Internal phy(GE) firmware version: 0x8434
vr9 Switch8192 KiB EN25Q64 at 0:3 is now current device
Type "run flash_nfs" to mount root filesystem over NFS
Hit any key to stop autoboot: 1 0
VR9 # setenv ipaddr 192.168.1.70
VR9 # setenv serverip 192.168.1.73
VR9 # tftpboot 0x80800000 123.bin
8192 KiB EN25Q64 at 0:3 is now current device
Using vr9 Switch device
TFTP from server 192.168.1.73; our IP address is 192.168.1.70
Filename '123.bin'.
Load address: 0x80800000
Loading: *T T T T T T T T T T
Retry count exceeded; starting again
8192 KiB EN25Q64 at 0:3 is now current device
Abort
The original poster's instructions assume prior knowledge, which is a little frustrating. It's all new to me. It's a pity the guy with the putty screenshots didn't post that info. Any ideas anybody?
-
Try disabling windows firewall.
In my initial tests with tftpd32 I'm stucked using win7 because the firewall blocked the service. Winxp works fine without changes.
-
Epoch I can PM you the link that hacktrix2006 shared with me which includes some screenshots. I'm unsure if he wants it to be public or not.
I used the same Tftpd64 as you.
At a quick glance, you set your IP + serverip OK just like I did. But the next command appears to differ "tftp 123.bin" is what this guide suggests. Perhaps yet another way to do the same thing I am unsure.
Anyhow check your PM :)
-
Go for it, just be warned its a draft version. Its not perfect but will get job done. Also need some views of the drafting so it can be made perfect for public release.
-
I didn't set the IP via the router at all just set everything via the computer. I used 192.168.1.100 on PC and the default on router and then set the tftp server to be bound to 192.168.1.100 and the. Sent the file over just make sure that any firewall on PC is off
-
I am glad you approved hacktrix2006, I believe the draft is more than good enough for at least public review - much better than the alternative situation were people are unsure what to do and end up bricking things.
Lets see what Epoch thinks of it since he claims no prior knowledge.
Regarding setting the IP on the device itself or on Windows I guess that's down to personal preference, at least we can confirm either method works. "printenv" command may list a gateway env that may need to be set if doing it on the device itself.
-
Thank you all. It's worked! ;D
It could have been the firewall (thanks zhadoom), but was more likely my Local Area Connection properties not set right. I tried a few things and something worked.
The guide is great! When hacktrix2006 said it was a "draft", I though it might be kind of incomprehensible, but it is very well presented and clear. Previous posts in this thread had almost got me the whole way, but hacktrix2006's guide would have been sooo much easier to follow from the get-go. I really appreciate the fast replies and help. Can't wait to test this TP-Link on VDSL in a couple of days.
I would recommend posting your guide as-is hacktrix2006. In my humble view, it is more than polished enough.
-
Glad the guide helped ya, Will redo the Guide to make it slightly better and thank you for the compliment.
-
I second Epoch's complement + opinion, would be nice to have the guide in the first post :)
Let us know how it goes on VDSL Epoch, sadly by the time I had finished setting mine up I had lost 10mbit of sync and gained 10ms in pings (interleaving?) :( May I suggest not being daft and set it up before it goes near the phone line :lol:
-
Anyone getting lockups on w9980 beta firmware I.e complete lockup of WiFi and land ports plus DSL port?
-
I did have a lockup on day one about 12hours after flashing, nothing since. I have no idea why.
Since then I have personally logged in via telnet on each reboot to kill a few junk processes in order to free up memory.
How often are you locking up?
I hit five days of uptime yesterday.
-
I was locking up twice a day, flashed back to non beta w9980 firmware no issue
-
To confirm I am on the beta firmware with no issues.
Firmware Version:0.6.0 1.10 v0021.0 Build 150409 Rel.40749n
Hardware Version:TD-W9980 v1 00000000
System Up Time:5 day(s) 22:01:35
Killing those junk processes frees up a relatively large amount of memory so I wonder if that's helping long term.
-
Will flash it back to beta next week as overall the Beta Firmware gave better performance other then the stupid lockup with i think is down to ram usage.
-
Just had a good read of this... owing to me having the latest firmware on my tp link w8980. Does that make it a no go :-\
-
Just had a good read of this... owing to me having the latest firmware on my tp link w8980. Does that make it a no go :-\
I don't believe it matters currently. You just need to flash one of the "precut" images (probably downgrading as a result) and then upgrade back to the latest version via the web interface like normal. First steps is to take it apart + do your serial connection.
-
Well lets have a go then owing to the router not being much good to me now since i went VDSL with talktalk.
So i have got a TTL/Serial/Usb lead on order.Wont have no problems doing the soldering side of thing. Its the putty side of thing im concerned with :-[ I do have putty installed and do use it for a web besed webui. but all ive ever done with it is log in and copy & paste a programme restart line into it ...can this cross flash be done the same way or is there lots of typing to be done
TIA
-
Give @Mooingall a shout and will he'll give you the link to my Tutorial on cross flashing which has some pictures with it. I did forget to add a colouring section in though. I can't send the link as i currently have a very dodgy internet connection at this moment in time.
-
Many thanks for your reply will send him a Pm :fingers:
-
Well lets have a go then owing to the router not being much good to me now since i went VDSL with talktalk.
So i have got a TTL/Serial/Usb lead on order.Wont have no problems doing the soldering side of thing. Its the putty side of thing im concerned with :-[ I do have putty installed and do use it for a web besed webui. but all ive ever done with it is log in and copy & paste a programme restart line into it ...can this cross flash be done the same way or is there lots of typing to be done
TIA
After the soldering is done its smooth sailing with hacktrix2006's guide. If you didn't brick it by dodgy soldering I don't think there is much to worry about. His pictures are very reassuring and I believe all but the most serious of typos can be corrected.
It is just a few commands into putty or terminal app of choice and then visiting http://192.168.x.x (I forget the default IP of the unit) in your browser, logging in and clicking upgrade to get you back to the newest version again.
The version shuffling could be avoided if someone provided a newer "pre-cut" image though why change what works I guess.
I am using mine on VDSL BT infinity just fine so its worth the risk as you mentioned.
Links sent via PM. Also remember don't do what I did and connect the 4th wire for voltage to the router, I hear it normally doesn't end well.
-
Well lets have a go then owing to the router not being much good to me now since i went VDSL with talktalk.
So i have got a TTL/Serial/Usb lead on order.Wont have no problems doing the soldering side of thing. Its the putty side of thing im concerned with :-[ I do have putty installed and do use it for a web besed webui. but all ive ever done with it is log in and copy & paste a programme restart line into it ...can this cross flash be done the same way or is there lots of typing to be done
TIA
After the soldering is done its smooth sailing with hacktrix2006's guide. If you didn't brick it by dodgy soldering I don't think there is much to worry about. His pictures are very reassuring and I believe all but the most serious of typos can be corrected.
It is just a few commands into putty or terminal app of choice and then visiting http://192.168.x.x (I forget the default IP of the unit) in your browser, logging in and clicking upgrade to get you back to the newest version again.
The version shuffling could be avoided if someone provided a newer "pre-cut" image though why change what works I guess.
I am using mine on VDSL BT infinity just fine so its worth the risk as you mentioned.
Links sent via PM. Also remember don't do what I did and connect the 4th wire for voltage to the router, I hear it normally doesn't end well.
Many thanks for sending me the links... time to have a good read and play...noted your word of warning about the 4th wire :fingers:
-
How many typo's are in the guide bud? Going to try and download it later to redo it. Yes 4th wire is normally a Death warrent for the router, some have been very lucky!
What you think to the colouring section idea? LOL its fairly easy and i shell at some stage update the pre-cut images as well. Good luck though bud.
-
How many typo's are in the guide bud? Going to try and download it later to redo it. Yes 4th wire is normally a Death warrent for the router, some have been very lucky!
What you think to the colouring section idea? LOL its fairly easy and i shell at some stage update the pre-cut images as well. Good luck though bud.
Well just had a quick read of it and to me it looks spot on..Excellent work That is..There are a couple of minor typing errors but Does it matter.Again well done to you for doing this excellent guide
Edit
So although i have the latest firmware in mine....I still just go for it then with this excellent guide
-
Yep you still use the guide its the same bud. The W9980 Cut image is the important file required.
Follow the guide and reap the awards.
-
When I mentioned typos I was meaning even if a user trying to flash made their own typos it could probably still be recovered.
I am not following with this colouring in business, what did I miss?
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fcdn.photolabels.co%2Fimages%2Fwww.coloringprintables.net%2Fimages%2Fprintables%2Feducational-coloring-pages%2Fcomputer-coloring-page-printable.gif&hash=24fd44a9e2eebe0ee774ae0cad70ca78f50f44da)
-
Thought you were meaning spelling mistakes in your guide :-[
Scratch that ;D ;D
-
Thought you were meaning spelling mistakes in your guide :-[
Scratch that ;D ;D
Are you all sorted now?
-
@Mooingall you have got the joke LOL! did everything go alright for you @bigtimecube or are you still awaiting on your USB TTL cable?
-
Hi there both...ive ordered the usb gadget from the bay then i will jump in and go for it...Ive had a read of the pdf about 10 times.downloaded the TFTP/cutimage and ready to go.Will keep you kind gents up to date on how i progress :fingers:
-
Today i set about doing the cross Flash as per the Pdf fileKindly sent by @Mooingall.. Connected all up and powered on. And all the data like in the pdf file was on the putty screen. Ending with the VR9#
So i enter the first command line from the Guide And that is where it ends.. So i must be doing something Wrong :-\
(https://dl.dropboxusercontent.com/u/70807181/putty%20read.jpg)
-
Are you running a firewall bud, its looking like you are? If not try moving the RJ45 cable to port 2 of the router. Hope this helps
-
I Will look into the firewall :fingers:
-
Are you running a firewall bud, its looking like you are? If not try moving the RJ45 cable to port 2 of the router. Hope this helps
I turned the firewall off in control panel..Still same results...The RJ45 cable is not mentioned in the Pdf :-\
-
RJ45 = Ethernet cable. Is the Ethernet Cable plugged in.
Have you set the IP for Ethernet to 192.168.1.100 / 255.255.255.0 rest blank?
If you need more help if i can get a stable connection might be able to Teamviewer and flash it for you bud, but i won't be able to do that till after 9pm.
-
I Guess it was all down to me being a Bit Dim :-[ :-[
But i got there. ;D ;D ;D
(https://dl.dropboxusercontent.com/u/70807181/router.jpg)
-
Glad it worked out for you bud. If i have time i might just make a video on how to do it using computer might be helpful like.
Enjoy bud!
-
Glad it worked out for you bud. If i have time i might just make a video on how to do it using computer might be helpful like.
Enjoy bud!
Still not there Yet ;D ;D
Cannot still get router to go on Internet ::) Played around but it just dont wanna play ball.
Tried ADSL TalkTalk & others :-\
Just keeps saying Connecting
(https://dl.dropboxusercontent.com/u/70807181/screen1.jpg)
(https://dl.dropboxusercontent.com/u/70807181/screen2.jpg)
(https://dl.dropboxusercontent.com/u/70807181/screen3.jpg)
-
You need to set it to VDSL bud, hence why its not working, Best way is to Factory reset via the WebGUI and then use the Quick Setup section in the Webgui after it boots backup and then select VDSL it will then help you set it all correctly.
The modem is picking up the sync but its setup wrong.
Goodluck!
-
I see "VPI/VCI or VID" is blank in your picture, is that a requirement for TalkTalk?
That's the setting that caused me issues on BT. Without it I could sync yet could not get a IP - just like your picture.
In his last picture it is correctly set in VDSL mode (note the red text). I didn't use any of the qucikstart profiles myself.
It also seems like if you do a manual "new connection" and you screw it up, its best to delete it and start again. "Enable Vlan ID" may have been my stumbling block sorry for the confusion .
-
I think you probably should upgrade to the latest 9980 firmware, which can now be done via the web interface.
-
Good catch! Yes that was mentioned several times before hand :-X
You are not limited to running the pre-cut image. Upgrade like normal using your web browser.
-
Been playing since my last post and its just not having it..So will upgrade and see What that does
-
It Works Horay.Im on it now...
Once i downloaded and put the new firmware on the choice of ISP & Connections Changed.
Before
(https://dl.dropboxusercontent.com/u/70807181/screen1.jpg)
15057 Firmware
(https://dl.dropboxusercontent.com/u/70807181/screen4.jpg)
Many thanks all for helping Me ....
Right what can i Flash next with this great Usb Gadget ;D ;D ;D
-
Oh no what have we done, we've made a TTL Flashing monster! many things can be flashed with a TTL USB cable so long as its 3.3v and not 5.0v, however its best to put it aside for now and have it to hand just incase you need it.
-
Oh no what have we done, we've made a TTL Flashing monster! many things can be flashed with a TTL USB cable so long as its 3.3v and not 5.0v, however its best to put it aside for now and have it to hand just incase you need it.
Feel well chuffed that i done it ...You lot on here seem to be well clued up on all this stuff. Ive been through loads of threads on here And Think to myself..What they talking about ;D ;D ;D
I find it all very interesting..
PS: Can this usb thing be plugged into the wife and change the way she boots up too :-\ :-\
-
I heard it is very possible to infact to do such a thing, Most us the TTL to Wife connection to uninstall Wife v1.0 and reinstall Girlfriend v2.0, but i can't verify this personally but feel free to give it a shot! Just remember if it works disable the Automatic update to Wife v1.0 :lol:
-
Hello I buy a TD-w8980 here in Brazil. Fwr is 6017. I soldered 3 serial wires and pl2303hx ttl adapter. Connects all tested and are ok. Than a install tpftp32 an putty(115200 and 8N1 setup). When i open putty terminal and turn on de Modem green light became flashing, but u-boot is not shown in putty terminal. I really dont no if in my fwr version (6017) this u-boot was blockes. I find an old fw ( Ver 131012 http://www.userdrivers.com/LAN-Network- … er-131012/ ) that i can flash (only it, I dont no why) and no uboot is showing in putty terminal too. I read my firmware and uboot first byte is 0x03. In http://wiki.openwrt.org/toh/tp-link/td-w8980 i read that they dont now how this new version of uboot work and is rsa signed. I can downgrade only to this fw ( Version:0.6.0 1.3 v000e.0 Build 131012 Rel.51720n), that first uboot byte is 0x03 too. Please? Is there Any way to initialized this new uboot version?
-
Try running putty first to test the connection if it works keep the putty window open at all costs once your ready to TFTP the image over then open and run TFTP app on Windows. Sometimes Putty and the TFTP app conflicts if TFTP is ran first before putty!
-
Try running putty first to test the connection if it works keep the putty window open at all costs once your ready to TFTP the image over then open and run TFTP app on Windows. Sometimes Putty and the TFTP app conflicts if TFTP is ran first before putty!
When I open putty i know that connect with usb ttl is ok(yet no tftp) . When i turn on td-w8980 green led of ttl adapter became flashing, but no data is showing in Putty windows. Blue led flashing when i pless any key of keyboard. I really have doubt how to test if connect is ok. have you seen anyone that sucess flashed one TD-w8980 with uboot first byte 0x03? I have one old firmware that uboot first byte is 0x02, but i cant downgrade to that.
-
Crossflashing via TTL uboot images i have used for TD-W9980 was of the 0x02 byte set without issues. as TD-W9980 images are RSA Signed, however OpenWRT images are not RSA signed so there for you might need to use the 0x03 byte setup.
Also have you reversed the TX and RX on either in so that like
RX -> TX
TX -> RX
That might help
However i am heading for some shuteye.
-
have you seen anyone that sucess flashed one TD-w8980 with uboot first byte 0x03? I have one old firmware that uboot first byte is 0x02, but i cant downgrade to that.
Hi you are skipping too far ahead.
Unless you can make the device display its console output (booting messages/spam) then worrying about flashing is of no use.
You should be able to connect your serial cable to the device while it is powered on and see lots of readable English text instantly. You should also be able to interact with the device via your keyboard, press any key and it will ask you for a username and password. Once you finally see any kind of English you can reboot the device to enter uboot.
At this stage you do not need to worry about uboot or flashing. We are just trying to use your computer like a monitor.
My only guess is maybe you have the pins in the wrong order.
-
have you seen anyone that sucess flashed one TD-w8980 with uboot first byte 0x03? I have one old firmware that uboot first byte is 0x02, but i cant downgrade to that.
Hi you are skipping too far ahead.
Unless you can make the device display its console output (booting messages/spam) then worrying about flashing is of no use.
You should be able to connect your serial cable to the device while it is powered on and see lots of readable English text instantly. You should also be able to interact with the device via your keyboard, press any key and it will ask you for a username and password. Once you finally see any kind of English you can reboot the device to enter uboot.
At this stage you do not need to worry about uboot or flashing. We are just trying to use your computer like a monitor.
My only guess is maybe you have the pins in the wrong order.
I'm shure that connection is ok: RX to TX and TX to RX, but i try to invert and no go(green and blue led of ttd adapter dont flash anymore).
I really dont understand why my green led became flashing when i turn on device (I infer that the router is sending data to the ttl adapter), but putty console not show anything. I have no doubt that Putty connect with ttl adapter is ok too, because blue led flash when press any key in putty windows.
-
Glad it worked out for you bud. If i have time i might just make a video on how to do it using computer might be helpful like.
Enjoy bud!
If you ever do. Let me know and I'll link to it from the first post.
-
Glad it worked out for you bud. If i have time i might just make a video on how to do it using computer might be helpful like.
Enjoy bud!
If you ever do. Let me know and I'll link to it from the first post.
Well i will more then likely need to place it on a External Drive and post it to someone with a faster upload LOL, last video i uploaded took 3 days which left the internet crippled for surfing for them 3 days.
I will also need to ask nicely for someone Video camera (aka one of my family members) i don't think a mobile phone able to do 1080p with super shakey jakey at the helm will work but will see what i can do as the over stuff on Computer can be screen capped with either Nvidia's shadowplay or a screen Recorder.
-
Glad it worked out for you bud. If i have time i might just make a video on how to do it using computer might be helpful like.
Enjoy bud!
If you ever do. Let me know and I'll link to it from the first post.
Well i will more then likely need to place it on a External Drive and post it to someone with a faster upload LOL, last video i uploaded took 3 days which left the internet crippled for surfing for them 3 days.
I will also need to ask nicely for someone Video camera (aka one of my family members) i don't think a mobile phone able to do 1080p with super shakey jakey at the helm will work but will see what i can do as the over stuff on Computer can be screen capped with either Nvidia's shadowplay or a screen Recorder.
More than happy to help out here
The pdf file is very good and clear to be honest. And sort of went ok for me, My two Mistakes were leaving out the RJ45 cable And Once all is done,you need to Update with the latest firmware off the Tp link site
-
I will be able to do the Screen Caps next wensday as i am going to be flashing the W8980 back to W9980 again so that will be the best time to do that. Then its just the where to solder the pins too and the what is required parts.
So best suggestion for you all here is to buy stock in Coffee beans quickly as i will be using a lot to insure i don't blabber on :lol:
If the Video after Rendering is lower then 2GB i will try and upload it myself if however its greater then that then its beg for an uploader to do so on my Behalf. Does Kitz site have a Dedicated youtube channel it might be best as some people perfer Video then Text tutorials just a thought, it also could be another avenue for revenue.
-
I'm shure that connection is ok: RX to TX and TX to RX, but i try to invert and no go(green and blue led of ttd adapter dont flash anymore).
I really dont understand why my green led became flashing when i turn on device (I infer that the router is sending data to the ttl adapter), but putty console not show anything. I have no doubt that Putty connect with ttl adapter is ok too, because blue led flash when press any key in putty windows.
What you say makes sense.
Is your "speed"/baud setting ok within putty?
That's me out of ideas :no:
-
I'm shure that connection is ok: RX to TX and TX to RX, but i try to invert and no go(green and blue led of ttd adapter dont flash anymore).
I really dont understand why my green led became flashing when i turn on device (I infer that the router is sending data to the ttl adapter), but putty console not show anything. I have no doubt that Putty connect with ttl adapter is ok too, because blue led flash when press any key in putty windows.
What you say makes sense.
Is your "speed"/baud setting ok within putty?
That's me out of ideas :no:
My setup is 115200 and 8N1. I really dont known what is wrong.
-
And is the Com port in putty the same as in Device manager and drivers working ok for the TTL USB cable
-
I guess it must be using the correct com port if the LED on his cable is reacting to key presses in putty.
Mangueboy do you maybe have any other devices you could test the cable on? A Raspberry Pi maybe? Any other old junk routers/modems?
-
I guess it must be using the correct com port if the LED on his cable is reacting to key presses in putty.
Mangueboy do you maybe have any other devices you could test the cable on? A Raspberry Pi maybe? Any other old junk routers/modems?
Unfortunately no. I do a loop test in ttl adapter: RX(ttl adapter) to LX (ttl adapter), then putty return ok all pressed keys. I think that new u-boot version (rsa signed) with first 0x03 have other unknown procedure to be initialized :(. In OPenWRT Wiki home page http://wiki.openwrt.org/toh/tp-link/td-w8980 have this warns " DO NOT upgrade to the 12.10.2013 (or newer) firmware on TP-Link website. It has modified u-boot, and applies a NEW UNKNOWN header - first byte is 0x03. We don't know how is it working. It seems to be a rsa signed firmware upgrade..
You can see below my video with my putty setup e ttl adapter behavior when trying initialize uboot.
https://www.youtube.com/watch?v=tbzTaPcAlTA&feature=youtu.be
-
Several of us here flashed from 2014+ firmware. My uboot claims to be U-Boot 2010.06-LANTIQ-v-2.0.40-svn7369 (Jun 16 2014 - 11:12:49)
-
If your going from tp liink w8980 to w9980, you don't need to worry at all about the RSA headers you simply use a pre-cut image with out the uboot section, then after that upgrade to latest firmware via web gui. If your going to flash openwrt then you worry about RSA headers and simply downgrade each firmware till you get to the first firmware release.
Sent from my TegraNote-P1640 using Tapatalk
-
Several of us here flashed from 2014+ firmware. My uboot claims to be U-Boot 2010.06-LANTIQ-v-2.0.40-svn7369 (Jun 16 2014 - 11:12:49)
I buy my td - w8980 here in Brazil in 05/28/2015. Can you tell me if you device was unboxed with uboot version first with byte is 0x03?
-
Are you just wanting to CrossFlashing to W9980 Firmware or are you after installing OpenWRT Firmware.
If your just going to crossflash you don't need to worry about the uboot header bud, only if your trying to install OpenWRT are you going to need to worry about the uboot header.
-
If your going from tp liink w8980 to w9980, you don't need to worry at all about the RSA headers you simply use a pre-cut image with out the uboot section, then after that upgrade to latest firmware via web gui. If your going to flash openwrt then you worry about RSA headers and simply downgrade each firmware till you get to the first firmware release.
Sent from my TegraNote-P1640 using Tapatalk
My problem is i cant inicialize my uboot version and i think it have another unknown procedure to inicialize. Maybe 2015+ devices have this problem.
-
Are you just wanting to CrossFlashing to W9980 Firmware or are you after installing OpenWRT Firmware.
If your just going to crossflash you don't need to worry about the uboot header bud, only if your trying to install OpenWRT are you going to need to worry about the uboot header.
I want only crossflash my router to td w9980, since this router is not sold in Brazil.
-
So no need to worry about the uboot header just flash a w9980 firmware file via TTL thats pre-cut and boom your sorted.
-
Would anyone here had success inicialized u-boot by ttl adapter on a 2015+ TD-8980 device? :fingers:
-
Would anyone here had success inicialized u-boot by ttl adapter on a 2015+ TD-8980 device? :fingers:
To work the putty must be configured without xonxoff or hardware handshake.
See my guide to crossflash 8980 to 9980 here: http://adrenaline.uol.com.br/forum/showthread.php?t=497887&page=252&p=1070237896#post1070237896
To interrupt the boot just keep taping any key in putty after power on the modem.
-
Would anyone here had success inicialized u-boot by ttl adapter on a 2015+ TD-8980 device? :fingers:
To work the putty must be configured without xonxoff or hardware handshake.
See my guide to crossflash 8980 to 9980 here: http://adrenaline.uol.com.br/forum/showthread.php?t=497887&page=252&p=1070237896#post1070237896
To interrupt the boot just keep taping any key in putty after power on the modem.
Can you see if there are anything wrong in my video?
https://www.youtube.com/watch?v=tbzTaPcAlTA&feature=youtu.be
-
Would anyone here had success inicialized u-boot by ttl adapter on a 2015+ TD-8980 device? :fingers:
To work the putty must be configured without xonxoff or hardware handshake.
See my guide to crossflash 8980 to 9980 here: http://adrenaline.uol.com.br/forum/showthread.php?t=497887&page=252&p=1070237896#post1070237896
To interrupt the boot just keep taping any key in putty after power on the modem.
Can you see if there are anything wrong in my video?
https://www.youtube.com/watch?v=tbzTaPcAlTA&feature=youtu.be
The configuration of putty is OK.
The usb-serial adapter in video looks identical that I use. PL-2303HX.
Comparing to my adapter I noticed that the pins soldered doesn't match.
In my adapter the pins are 2-TXD , 3-RXD and 4-GND. The external pins 1 and 5 are for power only ( 1 - 3.3v and 5 - 5V ).
In the video the pins soldered are RXD, GND and 5V.
Could you please look if the pinout is the same ?
(https://www.mediafire.com/convkey/d167/hnzn6eznatl0sbl6g.jpg) (https://www.mediafire.com/view/?hnzn6eznatl0sbl)
-
Would anyone here had success inicialized u-boot by ttl adapter on a 2015+ TD-8980 device? :fingers:
To work the putty must be configured without xonxoff or hardware handshake.
See my guide to crossflash 8980 to 9980 here: http://adrenaline.uol.com.br/forum/showthread.php?t=497887&page=252&p=1070237896#post1070237896
To interrupt the boot just keep taping any key in putty after power on the modem.
Can you see if there are anything wrong in my video?
https://www.youtube.com/watch?v=tbzTaPcAlTA&feature=youtu.be
The configuration of putty is OK.
The usb-serial adapter in video looks identical that I use. PL-2303HX.
Comparing to my adapter I noticed that the pins soldered doesn't match.
In my adapter the pins are 2-TXD , 3-RXD and 4-GND. The external pins 1 and 5 are for power only ( 1 - 3.3v and 5 - 5V ).
In the video the pins soldered are RXD, GND and 5V.
Could you please look if the pinout is the same ?
(https://www.mediafire.com/convkey/d167/hnzn6eznatl0sbl6g.jpg) (https://www.mediafire.com/view/?hnzn6eznatl0sbl)
Really diferent.
-
Your clearly having problems with the ttl adaptor.With the cost of them only being a few UK pounds Why not get hold of another one from that well known auction site.
-
Glad it worked out for you bud. If i have time i might just make a video on how to do it using computer might be helpful like.
If you ever do. Let me know and I'll link to it from the first post.
Video now live - thanks hatrix for taking the time to do this.
I've amended the first post to show link too.
[youtube]vjSLGEkZd_E[/youtube]
-
Nice one hacktrix2006. :fingers: Done mine ten days ago now with no issues at all.
-
Hi guys, new to this forum, have ordered USB to TTL cable :) and would like to put openwrt on my 8980, if i read this correctly i can downgrade the firmware till i get to an openwrt compatible version?
can i use the image you provide on the youtube download link (8980 one) to downgrade to?
I like this router , seems to be fairly stable but would like a few more bells and whistles :)
Thx for your hard work
-
As far as i am aware its just a simple Flash via TTL for OpenWRT after you have removed the uboot partition for the openWRT image.
However certain functions are not working as of yet as i understand which are pointed out in this thread: https://forum.openwrt.org/viewtopic.php?id=49413
If it was fully working i would of made another video just to flash OpenWRT to our routers but i have held back from flashing it as its not classed to me as stable.
-
Your clearly having problems with the ttl adaptor.With the cost of them only being a few UK pounds Why not get hold of another one from that well known auction site.
I really dont know why to thank you. You finally solve my problem. I never would think that was my TTL Adapter that had any incompatibility or any defective function. I buy another D-SUN model and my Putty windows finally initialize uboot. I can now advise to not buy my model, below.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww.mediafire.com%2Fconvkey%2F4a96%2F31mq531o4h87x4dzg.jpg&hash=a3e879909a14726afb062a93f569a50457cb6270)
Now you can see what i was waiting for a long time. :silly:
U-Boot 2010.06-LANTIQ-v-2.0.40-svn4735 (Sep 24 2013 - 12:27:33)
CLOCK CPU 500M RAM 250M
DRAM: 64 MiB
Using default environment
In: serial
Out: serial
Err: serial
Net: Internal phy(GE) firmware version: 0x8434
vr9 Switch8192 KiB W25Q64 at 0:3 is now current device
Type "run flash_nfs" to mount root filesystem over NFS
Hit any key to stop autoboot: 0
8192 KiB W25Q64 at 0:3 is now current device
8192 KiB W25Q64 at 0:3 is now current device
Uncompressing ...
Starting kernel ...
-
Is this before or after a tftp session?
Sent from my TegraNote-P1640 using Tapatalk
-
Is this before or after a tftp session?
Sent from my TegraNote-P1640 using Tapatalk
Before. I have one doubt. In Zhadoon Brazilian post : http://adrenaline.uol.com.br/forum/showthread.php?t=497887&page=252&p=1070237896#post1070237896 the comand is " tftpboot 0x80800000 tplink9980.bin" and in your video only tftp 9980.bin. Why?
-
Even with just tftp w9980.bin it will autoload into the 0x80800000 area that's why I didn't include the area in the command. If it's before tftp you didn't spam the key to break into uboot quickly enough I have a video online now which is linked in op.
Sent from my TegraNote-P1640 using Tapatalk
-
Even with just tftp w9980.bin it will autoload into the 0x80800000 area that's why I didn't include the area in the command. If it's before tftp you didn't spam the key to break into uboot quickly enough I have a video online now which is linked in op.
Sent from my TegraNote-P1640 using Tapatalk
Very thanks, guy! :thumbs:
-
Even with just tftp w9980.bin it will autoload into the 0x80800000 area that's why I didn't include the area in the command. If it's before tftp you didn't spam the key to break into uboot quickly enough I have a video online now which is linked in op.
Sent from my TegraNote-P1640 using Tapatalk
Very thanks, guy! :thumbs:
I would like to thank for the help of all the guys here in the forum. Now, I sucess crossflash and upgrade my router.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww.mediafire.com%2Fconvkey%2Fe3db%2Frzrcwpx1qk57br6zg.jpg&hash=8af1071e49d5f4c252673fc8638c11a99e43a771)
-
Congrats mangueboy on the crossflashing.
Now me personally i used a USB to serial adapter PL2303 TTL console Recovery RS232 for Raspberry Pi (red cable is 5v but not used) to flash the firmware and never had trouble.
Now looking at your image of the adaptor you used, you only used two cables and it was split on one of them to RX + GND. that might have been the issue but heck your crossed flashed now.
-
Congrats mangueboy on the crossflashing.
Now me personally i used a USB to serial adapter PL2303 TTL console Recovery RS232 for Raspberry Pi (red cable is 5v but not used) to flash the firmware and never had trouble.
Now looking at your image of the adaptor you used, you only used two cables and it was split on one of them to RX + GND. that might have been the issue but heck your crossed flashed now.
Itīs seems that is only one splitted wire, but Rx was solded in a orange wire, and GND in red wire. All connection was ok. The issue is really with the device i bought. With D-SUN model thereīs no problem. I think that there's any incompatibility with my previous ttl adapter model, because I did a Loop test ( wire tx to rx) and what i press in keyboard was showing in Putty console. Then iīm shure there isn't any particular hardware problem with it.
-
Hi everyone. I owned td w8990. If I crossflash it to 9980 I'll have troubles with something??? If he will work same but with vdsl?
-
Dear Crossflashers,
during my effort to analyse the new RSA signed firmware, I found a way to crossflash routers which have already a RSA signed firmware installed, without opening the devices at all. Anyone who is interested in more detailed information, can get them from https://github.com/xdarklight/mktplinkfw3/blob/master/README.md.
All that has to be done, is to alter the first firmware header:
1. replace the values at the hex positions 0x34 to 0x3F of the to-be flashed firmware with the values of an stock firmware, that matches the running firmware (if the currently running firmware is a W8980 firmware use the values from a stock W8980 image, if the currently running firmware is a W8980B firmware use the values from a stock W8980B image and so on)
2. temporary replace the md5 hash at hex position 0x40 to 0x4F with 8C EF 33 5F D5 C5 CE FA AC 9C 28 DA B2 E9 0F 42
3. calculate the the md5 hash/checksum of the whole file
4. replace the temporary md5 hash at hex position 0x40 to 0x4F with the value from 3.
Now the firmware should be accepted by the the routers firmware upgrade page. Don't forget to restore the factory defaults afterwards.
I've made a video for the younger ones among us:
[youtube]https://youtu.be/noEVttStvSw[/youtube]
// Edit: temporary md5 hash was wrong
-
thank you, it works well ! 5 minuts and i'm on W9980 last firmware :)
Dear Crossflashers,
during my effort to analyse the new RSA signed firmware, I found a way to crossflash routers which have already a RSA signed firmware installed, without opening the devices at all.
-
My device has been rock solid, very happy:
System Up Time:84 day(s) 14:34:42
Now the firmware should be accepted by the the routers firmware upgrade page. Don't forget to restore the factory defaults afterwards.
That is amazing progress, good work :)
That was some hefty right up, so since we can resign we can now edit rootfs? That would sure be useful.
-
I don't think it has progressed quite that far yet. Well, we can re-sign a firmware image with our own personal key, but the stock firmware won't accept that. We don't have the TP-Link private key to sign modified images with.
Changing the model numbers only works for uploading stock firmware. An alternative place to change the model numbers is the config file, that's how I flashed the 9980 firmware to my 8970v1.
-
Hi all,
First post, thousand reads !!!
ejs, could you please tell me how to change the config file?
Iīve checked a saved config file and it seems to be written in Chinese !
I donīt have the usb/ttl adaptor and here itīs difficult to buy it. If buying from dx or aliexpress it takes around 90 days to arrive.
Thanks for any help
Edit
Sorry, I was checking with Notepad, when I check with HxD hex editor itīs a common binary file.
But I canīt find the model inside.
Eduardo
-
The basic idea is from this thread (http://forum.kitz.co.uk/index.php/topic,15738.0.html).
I don't know if the 8980 saved config file is compressed, if it's not compressed, the StatPOSTer program can decrypt it, and then you can edit it, and add the necessary bits, then encrypt the edited file and upload that. If the saved config file is compressed, it's less easy because you have to edit a default config file obtained elsewhere, and the ones from the 9980 firmware attached to that thread might not work.
The necessary parts that I added or changed were within the <DeviceInfo> tags, near the start of the file.
<ModelName val=TD-W9980 />
<HardwareVersion val="TD-W9980 v1 00000000" />
<X_TPLINK_ProductID val=2575302657 />
<X_TPLINK_ProductVersion val=33 />
If the saved config file is compressed, it's probably easier to use the hex editing method in reply #143 (http://forum.kitz.co.uk/index.php/topic,14461.msg296659.html#msg296659) above.
-
Dear ejs
Many thanks.
Iīm now studying all that info.
Very difficult, congratulations to your knowledge!!
Eduardo
-
Dear ejs
Those procedures are very complicated for my limited knowledge.
But isnīt it possible to modify the values inside the router through your software statposter?
I mean by the button "set value".
My xml decrypted file only has 1 instance of the 8980 values, but statposter grabs the others, so I was guessing I could change them inside the router.
<ModelName val=TD-W9980 />
<HardwareVersion val="TD-W9980 v1 00000000" /> this is the only one I can find on my file.
<X_TPLINK_ProductID val=2575302657 />
<X_TPLINK_ProductVersion val=33 />
Many Thanks
Eduardo
-
No, the StatPOSTer program can't change values that are declared as read only. But they can be changed by uploading a config file that contains new values for them.
You can add lines that aren't already in the config, so that the result looks something like the attached image.
-
Dear Ejs
Thanks for the picture.
I donīt see the xml formatted as the picture, I am looking with notepad and editing with HxD hex editor.
Iīll look for a software that shows xml formatted and try to edit my config file.
Besides that, my config is 5096 bytes and the decrypted xml file is exactly the same size, but after changing the string 8990 to 9980 on the xml, the encryped bin file gets smaller (4896) or larger (5512) according to checking the "add null bytes" or not.
Any hint?
Thanks
Eduardo
-
If the file is that small, it's compressed, and cannot be edited. You could try editing one of the attached config files on this thread (http://forum.kitz.co.uk/index.php/topic,15738.0.html), and encrypting it with "add null bytes" ticked. I don't know if it will work or not, if it doesn't, the most likely result is the file won't be accepted, and the upload page will say something like "you put a wrong file".
You'll probably have to use mkresin's hex editing the firmware header method.
-
I donīt see the xml formatted as the picture, I am looking with notepad and editing with HxD hex editor.
Get hold of a copy of Programmer's Notepad
http://www.pnotepad.org/ (http://www.pnotepad.org/)
Handles lots of formats. ;D
-
Thanks Ejs
I was guessing itīs compressed as you said it could be.
Regarding uploading your sample config file from the 9980, wonīt it change passwords and other stuff from vdsl values?
Regarding the mkresin's method of hex editing the firmware header, it seems much easier, but I guess Iīll have to edit future fw upgrades and I donīt know if it will work then.
Besides, the router page will stay saying 8980, what will be a lesser fun.
Thanks a lot.
-
I donīt see the xml formatted as the picture, I am looking with notepad and editing with HxD hex editor.
Get hold of a copy of Programmer's Notepad
http://www.pnotepad.org/ (http://www.pnotepad.org/)
Handles lots of formats. ;D
Thanks, AArdvark, Iīve just downloaded it.
Eduardo
-
Once the 9980 firmware has been installed on a device, it will then accept new 9980 firmware without any modifications (unless TP-Link do something to prevent us doing this crossflashing in a future firmware).
Uploading the sample config will reset everything to factory defaults, all settings will be lost. I think you lose all settings when crossflashing anyway, and if not, doing a factory reset after the flashing is a good idea.
-
Dear Ejs
Thanks for your effort. Iīll try the firmware editing method as soon as I can.
Eduardo.
-
I don't think it has progressed quite that far yet. Well, we can re-sign a firmware image with our own personal key, but the stock firmware won't accept that. We don't have the TP-Link private key to sign modified images with.
Changing the model numbers only works for uploading stock firmware. An alternative place to change the model numbers is the config file, that's how I flashed the 9980 firmware to my 8970v1.
According to his notes he was able to edit lib/libcmm.so and resigning + reflashing the firmware. It even mentions "patches applied; rootfs "
I don't know, very much over my head.
Its a shame he has vanished already.
-
libcmm.so contains a public key used to validate the firmware signature of an image you try to flash by uploading through the web interface. If you hex edit libcmm.so and change the key to your own public key, and presumably flash this modified firmware via the bootloader using a serial ttl connection, then your modified firmware will accept images signed with your own key.
Getting the firmware containing the modified libcmm.so onto the device couldn't be done via the web interface.
-
libcmm.so contains a public key used to validate the firmware signature of an image you try to flash by uploading through the web interface. If you hex edit libcmm.so and change the key to your own public key, and presumably flash this modified firmware via the bootloader using a serial ttl connection, then your modified firmware will accept images signed with your own key.
Getting the firmware containing the modified libcmm.so onto the device couldn't be done via the web interface.
That limitation is fine, I would just like to make small edits eventually. Nice to know it is possible.
Wish list:
Auto killing all the junk that starts in the background
Making syslogd actually log useful things
A drop in SSHD replacement (with SFTP)
Add missing common tools like grep / or updated busybox.
Questionable WiFi tweaks
-
I'm not vanished!
All questions I saw so far, are already answered by the document I linked to. No need to write the same stuff here again, sorry guys.
For illustration:
That was some hefty right up, so since we can resign we can now edit rootfs? That would sure be useful.
Summary from the linked document: We still need the private key used by tp-link to sign a firmware in way that it is accepted by the firmware upgrade webpage.
Regarding the mkresin's method of hex editing the firmware header, it seems much easier, but I guess Iīll have to edit future fw upgrades and I donīt know if it will work then.
As written in my first post, you need to change the header values to values that match the currently running firmware. If you already run a 9980 firmware and you want to flash a new 9980 firmware, you don't need to do anything.
According to his notes he was able to edit lib/libcmm.so and resigning + reflashing the firmware. It even mentions "patches applied; rootfs "
The patches applied + rootfs stuff is openwrt specific as indicated by the term "openwrt image".
As long as the bootloader does not validate the signature, you can write nearly any image you like directly to the flash and boot it. Either via the bootloader or via a flash programmer.
That limitation is fine, I would just like to make small edits eventually. Nice to know it is possible.
Wish list:
Auto killing all the junk that starts in the background
Making syslogd actually log useful things
A drop in SSHD replacement (with SFTP)
Add missing common tools like grep / or updated busybox.
Questionable WiFi tweaks
You should really consider using a 3rd party firmware like openwrt instead of of patching the stock firmware. Replacing busybox and sshd is a bit more than small edits.
-
Forgive me for not digesting your writeup better..... remember most of us are causal hobbyists..
Regarding OpenWRT I was lead to believe it was a total mess for our devices currently, and DSL stuff will never be officially supported?
-
Dear Mkresin
Thanks for sharing all this information.
Could you please explain a little more your quoted text, as I donīt have the expertise needed to understand it fully:
"As written in my first post, you need to change the header values to values that match the currently running firmware. If you already run a 9980 firmware and you want to flash a new 9980 firmware, you don't need to do anything."
I understand that I will be running a 9980 fw but with a header of the 8980, so when I upgrade to a newer 9980 fw, Iīll have to modify it also.
Anyway I guess I understood your method and I probably will be able to do it it. Iīm waiting an opportunity to install my old modem to make the mod. Congratulations for your finding.
Thanks, Eduardo
-
Regarding OpenWRT I was lead to believe it was a total mess for our devices currently, and DSL stuff will never be officially supported?
Oh no, the lantiq xDSL chip is well supported. The 2.4 GHz atheros chip should work with the latest development version of Openwrt as well. But there is no 8980 specific image. Someone send a patch to the openwrt devel mailing list for this, but the patch was malformed and never merged.
Only the 5 GHz wave 300 chip isn't supported at the moment. As far as I know, the required source code was released by lantiq, but it needs a lot of modifications to work with current linux kernel versions. I don't know if someone is working on this.
-
Dear Crossflashers,
during my effort to analyse the new RSA signed firmware, I found a way to crossflash routers which have already a RSA signed firmware installed, without opening the devices at all. Anyone who is interested in more detailed information, can get them from https://github.com/xdarklight/mktplinkfw3/blob/master/README.md.
...
CUT
...
First of all, thank you for your work. I have some questions on the crossflashing procedure:
1. Can you elaborate more about the temporary md5 sum? Is it by design that the md5 sum have to be calculated with that placeholder string? How have you found it?
2. Flashing the TD-W9980 firmware will completely transform my 8980 in the new model, including firmware updates, right?
3. Do you confirm me that I have to operate on the full, untouched update file, and not on the stripped one?
4. Is a modified configuration file needed or I can simply do a factory reset to start using the newly flashed modem?
Thank you so much for your effort.
-
Can someone please share with me the PDF mentioned earlier in the thread?
Thanks all xx
-
If the document to which you refer is hacktrix2006 (http://forum.kitz.co.uk/index.php?action=profile;u=7636)'s guide, it might be best for you to contact him directly via a PM . . .
-
The whole lot is linked in the YouTube videos description area [1] it has the download link with everything in it. Good luck bud
Sent from my MotoG3 using Tapatalk
Moderator edited to add the URL --
[1] https://www.youtube.com/watch?v=vjSLGEkZd_E
-
Hello guys.
I have 8890B, and my ISP is on Annex A. A don't have that mode in DSL settings, so is there an easy way to change Annex version? Is it safe just to flash 8890 FW?
Thanks in advance
-
Hi, Im pretty desperate,
I think I do some disaster forllowing different guide on the web.
I have a tp link w8980 that was bricked, I resurrect it by crossflash the w9980 rom.
The problem is that now everything works except the 2.4 ghz band
its doesnt show in any device. I try to flash openwrt, then lede, then the official w8980 and again the w9980 in any case the 2.4 band doent work, in the last two, only the 5ghz works :frowning:
The only reason I could think for this is that I mess the mtd partition from 7c0000 untill the end.
Can someone provide me a backup of these partition?
PLS!
-
Hi, I’m pretty desperate,
I think I do some disaster forllowing different guide on the web.
I have a tp link w8980 that was bricked, I resurrect it by crossflash the w9980 rom.
The problem is that now everything works except the 2.4 ghz band…it’s doesn’t show in any device. I try to flash openwrt, then lede, then the official w8980 and again the w9980 in any case the 2.4 band doen’t work, in the last two, only the 5ghz works :frowning:
The only reason I could think for this is that I mess the mtd partition from 7c0000 untill the end.
Can someone provide me a backup of these partition?
PLS!
I have managed to unbrick my TPlink router and another from a member on here that sent me it. Only issue because of how bad the one that was send to me the only way to recover it was to SPI dump mine once i got it back online and then SPI Flash it to the other, which now means i have to find away to Edit the Mac Addresses and serial to the correct ones now so once i have managed to figure that one out, all you'll need to do @Psygnosis is to send me a PM with your Ethernet MAC address (Inside the router on the yellow section) and then the Wifi Mac address which is on the back for one of them.
Edit: Flashed the brick firmware to the SPI Program clone and redid my steps i used on my personal router to get it working with its own proper mac address fix below.
-
Right i have Dumped the radio parition from a working TPlink W8980/9980 router.
For those that are having issues with the Radio aka Wifi not working please do the following
Download mtdblock6.bin from https://mega.nz/#!fFsyiZDD!Z_jPpjYdZkUXi5xp5ftlLxyumIDg6p5NHOwOlmPFDtc
Format a USB stick to Fat32 and copy the mtdblock6y.bin to the root of the USB Stick
Open up putty and dial into your serial connection, then press enter. Once done issue the following commands
cd /var/usbdisk/sda1
cat mtdblock6.bin > /dev/mtdblock6
reboot
If sda1 doesn't work use the following
cd /var/usbdisk/sdb1
cat mtdblock6.bin > /dev/mtdblock6
reboot
This should then bring back WiFi, no need to worry about MAC addresses changing as i have tested this on another W8980/9980 Router and MAC addresses have stayed the same.
If this doesn't work then the issue is else where.
-
Right i have Dumped the radio parition from a working TPlink W8980/9980 router.
For those that are having issues with the Radio aka Wifi not working please do the following
Download mtdblock6.bin from https://mega.nz/#!fFsyiZDD!Z_jPpjYdZkUXi5xp5ftlLxyumIDg6p5NHOwOlmPFDtc
Format a USB stick to Fat32 and copy the mtdblock6y.bin to the root of the USB Stick
Open up putty and dial into your serial connection, then press enter. Once done issue the following commands
cd /var/usbdisk/sda1
cat mtdblock6.bin > /dev/mtdblock6
reboot
If sda1 doesn't work use the following
cd /var/usbdisk/sdb1
cat mtdblock6.bin > /dev/mtdblock6
reboot
This should then bring back WiFi, no need to worry about MAC addresses changing as i have tested this on another W8980/9980 Router and MAC addresses have stayed the same.
If this doesn't work then the issue is else where.
First of all THANK YOU VERY MUCH with all my heart for help.
sadly it doen't work :( (5ghz band works and 2.4 just doesn't show in all the devices at home) BUT, I have a log:
!!!!pan wlan_updateL2DescriptionState, name is ath0
l2_packet_receive - recvfrom: Network is down
WARNING: Fragmentation with HT mode NOT ALLOWED!!
Error for wireless request "Set Fragmentation Threshold" (8B24) :
SET failed on device ath0 ; Invalid argument.
DES SSID SET=TP-LINK_2.4GHz
Reading topology file /var/Wireless/2_4G_topology.conf ...
445.779: Reading radio configuration file /var/Wireless/2_4G_80211g.ap_radio ...
445.790: ieee80211_ioctl_siwmode: imr.ifm_active=1442432, new mode=3, valid=1
Reading bss configuration file /var/Wireless/ath0.ap_bss ...
sh: grep: not found
Using interface ath0 with hwaddr ff:ff:ff:ff:ff:ff and ssid 'TP-LINK_2.4GHz'
DES SSID SET=TP-LINK_2.4GHz
l2_packet_receive - recvfrom: Network is down
Error for wireless request "Set ESSID" (8B1A) :
too few arguments.
l2_packet_receive - recvfrom: Network is down
Reading topology file /var/Wireless/2_4G_topolog ieee80211_ioctl_siwmode: imr.if m_active=197248, new mode=3, valid=1
y.conf ...
452.041: Reading radio configuration file /var/Wireless/2_4G_80211g.ap_radio ...
452.042: Reading bss configuration file /var/Wireless/ath0.ap_bss ...
sh: grep: not found
Using interface ath0 with hwaddr ff:ff:ff:ff:ff:ff and ssid 'TP-LINK_2.4GHz'
DES SSID SET=TP-LINK_2.4GHz
l2_packet_receive - recvfrom: Network is down
Erase from 7c0000 with 6fdb bytes .
Write flash to 7c0000, len is 6fdb
This is what I have on putty everytime I change somenthing in 2.4ghz wireless section that hwaddr ff:ff:ff:ff:ff:ff makes me think that my MAC adress where lost someway...if that is the MAC adress (I'm ignorant), I doubt that it can be just FF:FF....
-
First of all THANK YOU VERY MUCH with all my heart for help.
sadly it doen't work :( (5ghz band works and 2.4 just doesn't show in all the devices at home) BUT, I have a log:
This is what I have on putty everytime I change somenthing in 2.4ghz wireless section that hwaddr ff:ff:ff:ff:ff:ff makes me think that my MAC adress where lost someway...if that is the MAC adress (I'm ignorant), I doubt that it can be just FF:FF....
Looking more and more likely you have busted it, I do have a spi dump of all partitions in one file but it has my Mac addresses on it to which I can't find via hexedit to null out. However have your tried openwrt just to confirm that its not the firmware causing the issue.
Sent from my SHIELD Tablet K1 using Tapatalk
-
Looking more and more likely you have busted it
So...the next question is: is there any way to know what was the MAC adress and insert it through the partition image where it's stored? (I think now that the mtd6 radio partition doesn't have the wifi 2.4ghz mac adress there.)
I will try to install openwrt or lede now to see what's happend
-
Right first thing is first, using Putty and pressing T on boot so you get the VR9# part you need to print of the env use the command printenv copy and paste to the thread.
-
Right first thing is first, using Putty and pressing T on boot so you get the VR9# part you need to print of the env use the command printenv copy and paste to the thread.
Before copy the printenv I have to tell you a thing:
I try to flash LEDE, using the command:
tftp lede.bin
sf erase 0x20000 0x7a0000
sf write $(loadaddr) 0x20000 0x7a0000and...also if watching the image in the attach seems that the 0% signal seems scary, my phone found the 2.4ghz wifi (5ghz is unsupported by lede/openwrt) so...i really don't understand...maybe are the pre-cutted image I use from the youtube video??
I thinking this because I try to use HxD do cut the image on myself, and there is another strange thing:
cutting the from 20000 to 7C0000 of the TD-W9980v1_0.6.0_1.13_up_boot(160125)_2016-01-25_15.45.32.bin and the image result file is 7A0001 and not 7A0000
and if I try to flash this cutted image, using the same commands as above, router gives me an error on Uncompressed -1 etc etc...
This is the printenv log:
bootcmd=run flash_flash
bootdelay=1
baudrate=115200
preboot=echo;echo run "flash_flash" to bring up the kernel;echo;
bootfile="uImage"
mem=63M
phym=64M
ipaddr=192.168.1.1
serverip=192.168.1.100
ethaddr=00:E0:92:00:01:40
netdev=eth0
console=ttyS0
tftppath=
loadaddr=0x80800000
rootpath=/mnt/full_fs
rootfsmtd=/dev/mtdblock2
nfsargs= setenv bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
ramargs=setenv bootargs root=/dev/ram rw
addip=setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):$(netdev):on
addmisc=setenv bootargs $(bootargs) console=$(console),$(baudrate) ethaddr=$(ethaddr) phym=$(phym) mem=$(mem) panic=1 mtdparts=$(mtdparts) init=/etc/preinit vpe1_load_addr=0x82000000 vpe1_mem=1M ethwan=$(ethwan)
flash_nfs=run nfsargs addip addmisc;bootm $(kernel_addr)
net_nfs=tftp $(loadaddr) $(tftppath)$(bootfile);run nfsargs addip addmisc;bootm
net_flash=tftp $(loadaddr) $(tftppath)$(bootfile); run flashargs addip addmisc; bootm
net_ram=tftp $(loadaddr) $(tftppath)$(bootfile); run ramargs addip addmisc; bootm
u-boot=u-boot.ltq
rootfs=rootfs.img
firmware=firmware.img
fullimage=fullimage.img
totalimage=totalimage.img
load=tftp $(loadaddr) $(u-boot)
update=protect off 1:0-2;era 1:0-2;cp.b $(loadaddr) B0000000 $(filesize)
flashargs=setenv bootargs root=$(rootfsmtd) rw rootfstype=squashfs
flash_flash=sf probe 3; bootm 0x80800000
update_uboot=tftp $(loadaddr) $(tftppath)$(u-boot); nand write.partial $(loadaddr) 4000 $(filesize);reset
update_kernel=tftpboot $(loadaddr) $(tftppath)$(bootfile);upgrade $(loadaddr) $(filesize)
update_bootloader=update_uboot;update gphyfirmware
update_rootfs=tftpboot $(loadaddr) $(tftppath)$(rootfs);upgrade $(loadaddr) $(filesize)
update_firmware=tftpboot $(loadaddr) $(tftppath)$(firmware);upgrade $(loadaddr) $(filesize)
update_fullimage=tftpboot $(loadaddr) $(tftppath)$(fullimage);upgrade $(loadaddr) $(filesize)
update_totalimage=tftpboot $(loadaddr) $(tftppath)$(totalimage);upgrade $(loadaddr) $(filesize)
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot-2010.06-svn11047-LANTIQ-v-2.3.08
ethact=vr9 Switch
Environment size: 2105/8188 bytes
So on LEDE 2.4ghz wifi works, on w8980/w9980 (precutted images taken from youtube) only the 5ghz wifi works....
-
Just a question which country you in?
Sent from my MotoG3 using Tapatalk
-
Just a question which country you in?
Italy. and yes I set Italy on the w9980/8980 fw but not on lede I just forget it xD
-
EDIT: Just read the reply proper was on D2 and using phone, The images on Youtube link are pre-cut meaning you do not need to cut the firmware at all its been done for you.
It took me a while to sort the files out as these was the files used in the video, which is why the files are less then 8mb in size because i have already removed the u-boot part from the files.
So you have been basically cutting pre-cut files hence your issue.
So using TFTP you just flash w9980.bin then after you have factory reset the router when it asks if it asks yolu then flash the W9980WebGUIUpdate.bin via the webgui (or you can use the latest file).
I will make a new pre-cut image in a bit and upload it then link it here. Uncompress -1 tends to be the image didn't successfully flash over.
Updated Pre-Cut W9980.bin file, Download and replace the file in the TFTP folder. DO not try cutting the file.
https://mega.nz/#!WQlmGaJB!r_VqFAcKeA_xmBeXayIKOZ6VvGvtNrp06wxRNBuGLBo
-
Thank you so much. I didn't have time to try your new image yet but I do some new research.
1. I didn't try to cut your pre cutted images but the images downloaded from the tp-link website.
2. If you look here (https://forum.openwrt.org/viewtopic.php?id=67548) you will see a person who had my similar problem. And I think that it's pretty certain that the info in my memory location between 1EC00 and 1FC00 is lost.
Now the only thing in the world I can do is to take that memory dump (but I suspect that it will be empty), open it with a hex editor and replace the mac adress.
The problem is that mac adress are factory unique if I lost my router Mac adress I can't recover it in any way or I have to generate a random ma adress
-
Mac address are on the label with WPS pin and WPA code. Or its inside the router on the yellow plastic i have an mtd 4-6 atm just need your mac so i can add it didt you gt my pm??
-
Dear Crossflashers,
during my effort to analyse the new RSA signed firmware, I found a way to crossflash routers which have already a RSA signed firmware installed, without opening the devices at all. Anyone who is interested in more detailed information, can get them from https://github.com/xdarklight/mktplinkfw3/blob/master/README.md.
All that has to be done, is to alter the first firmware header:
1. replace the values at the hex positions 0x34 to 0x3F of the to-be flashed firmware with the values of an stock firmware, that matches the running firmware (if the currently running firmware is a W8980 firmware use the values from a stock W8980 image, if the currently running firmware is a W8980B firmware use the values from a stock W8980B image and so on)
2. temporary replace the md5 hash at hex position 0x40 to 0x4F with 8C EF 33 5F D5 C5 CE FA AC 9C 28 DA B2 E9 0F 42
3. calculate the the md5 hash/checksum of the whole file
4. replace the temporary md5 hash at hex position 0x40 to 0x4F with the value from 3.
Now the firmware should be accepted by the the routers firmware upgrade page. Don't forget to restore the factory defaults afterwards.
I've made a video for the younger ones among us:
[youtube]https://youtu.be/noEVttStvSw[/youtube]
// Edit: temporary md5 hash was wrong
Please, this method did not work on my TD-W8970v3.
Can you tell me how to do this to work the TD-W8970v3?
-
EDIT: Just read the reply proper was on D2 and using phone, The images on Youtube link are pre-cut meaning you do not need to cut the firmware at all its been done for you.
It took me a while to sort the files out as these was the files used in the video, which is why the files are less then 8mb in size because i have already removed the u-boot part from the files.
So you have been basically cutting pre-cut files hence your issue.
So using TFTP you just flash w9980.bin then after you have factory reset the router when it asks if it asks yolu then flash the W9980WebGUIUpdate.bin via the webgui (or you can use the latest file).
I will make a new pre-cut image in a bit and upload it then link it here. Uncompress -1 tends to be the image didn't successfully flash over.
Updated Pre-Cut W9980.bin file, Download and replace the file in the TFTP folder. DO not try cutting the file.
https://mega.nz/#!WQlmGaJB!r_VqFAcKeA_xmBeXayIKOZ6VvGvtNrp06wxRNBuGLBo
How can you mount a .bin of this for me to record directly to the eeprom of the TD-W8970v3 using the eeprom recorder CH341A?
-
The 8970v3 is completely different hardware to the devices in this thread, and therefore cannot use the 9980 firmware.
-
I did the procedure on my TD-W8970v3 and every time I try to upgrade to the modified firmware it gives the following error: Error code: 4503 "The uploaded file was not accepted by the device"
I used the original firmwares:
TD-W8970v3_0.9.1_2.0_up_boot (160816) _2016-08-16_10.40.57.bin
it's the
TD-W9980v1_0.6.0_1.13_up_boot (160125) _2016-01-25_15.45.32.bin
Could someone help me with this?
-
The 8970v3 is completely different hardware to the devices in this thread, and therefore cannot use the 9980 firmware.
Thank you for helping me with this. Too bad that will not work for me!
-
merhaba, bana yardımcı olur musunuz?
my device w8980 bricked.
ROM VER: 1.1.4
CFG 05
ROM VER: 1.1.4
CFG 05
DDR autotuning Rev 0.3ff
DDR size from 0xa0000000 - 0xa3ffffff
DDR check ok... start booting...
U-Boot 2010.06-LANTIQ-v-2.0.40-svn7369 (Jun 16 2014 - 11:12:49)
CLOCK CPU 500M RAM 250M
DRAM: 64 MiB
Using default environment
In: serial
Out: serial
Err: serial
Net: Internal phy(GE) firmware version: 0x8434
vr9 Switch8192 KiB W25Q64 at 0:3 is now current device
Type "run flash_nfs" to mount root filesystem over NFS
Hit any key to stop autoboot: 0
8192 KiB W25Q64 at 0:3 is now current device
8192 KiB W25Q64 at 0:3 is now current device
Uncompressing ... LZMA: uncompress or overwrite error 1 - must RESET board to recover