knowhost.blogg.se

1. #HOW TO REMOVE TP LINK DRIVERS HOW TO#
2. #HOW TO REMOVE TP LINK DRIVERS CODE#
3. #HOW TO REMOVE TP LINK DRIVERS WINDOWS#

Hexstr=hexstr + "0" + (hexStr).strip() # insert pre 0 if needed HexStr=hex(ord(str)) # convert bin to hex If len(hexStr) 0: # are the some bytes missing after last block?įor z in range(0, Rest): # loop on missing bytes after last block HexStr=hex(ord(str)) # converting missing bytes to hex If x+4 <= len(str): # are there some bytes missing?įor y in range(1, 4): # yes, fill in the missing bytes of block Hexstr=hexstr + (hexStr).strip() # first byte of block Hexstr=hexstr + "0" + (hexStr).strip() # insert pre 0 if needed + first byte of block If len(hexStr) < 2: # checking on 1 collum only HexStr=hex(ord(str)) # converting bin to hex Str = open(“openwrt.bin”,”rb”).read() # Define Filename inįor x in range(0, len(str), 4): # Loop on str var with step 4 # Reading bin file, converting to hex, ordering to 4 Byte Blocksīinarray= # Init Array Offset = 0x81000000 # Start Adress in RAM For your information: Sending OpenWRT Image to device needs 02:12:00 houres…. In the next days or weeks i will spend some time to optimate the code. It is a little python script, looks like a “Quick Hack”, and written in 20 minutes.

#HOW TO REMOVE TP LINK DRIVERS CODE#

But the code is not released or best praxis at the moment. If someone is interested in getting the source code…. I´m felt glad to found a way unbricking the device without any money or desoldering. after “done….” sending bootm 0x9f020000 (booting kernel from flash) After that change the automating console to human console inputĩ. Read the answer of device with Adress and Content like “0x81000000 : 0xffffffff ? ”Ħ Bilding a loop to send all the 4 Byte blocks to Device with new Content Answers.Ĩ. Automate the first command “mm 0x81000000”ĥ. Automating the Bootloader stop command with “tpl”Ĥ. Ordering all bytes in blocks of 4Bytes (same order als mm command need)ģ. The answers was writing a little programm with this functions …Ģ. Ok… thats fine, but how can i automate the input of all 4Byte blocks in the boot loader console? The way is to use the mm command (memory manipulating command of u-boot). After some time reingeneering the cripped u-boot i found a way to manipulate the RAM content very easy with only some possibilities of commands.

#HOW TO REMOVE TP LINK DRIVERS HOW TO#

I have found and checked a way to unbrick a TP-Link Device with a cripped Bootloader (Bootloader without working TFTP Client) without desoldering and external flashing.Īt first, the problem is how to get the new Firmware in RAM without TFTP transfert. The flash is logically divided into five parts which are as follows: Preparing the firmwareīefore I flashed a new firmware into the desoldered flash had to prepare a file containing a good one. In any case you might cause a severe damage on the device. If you have a soldering tweezers it is a bit easier.

Attention: desoldering a SOP-8 chip requires good soldering skills.

To flash it from outside of the device it needs to be desoldered. Unfortunately it can’t be flashed while soldered. It is located next to the UART header JP1 (unpopulated in this picture). In the picture below I marked the flash on the PCB. The very first step was to identify the flash chip itself. For this purpose I’ve installed Cygwin which provides me a lot of non-Windows tools I’m regularly using.

#HOW TO REMOVE TP LINK DRIVERS WINDOWS#

I mainly work with a Windows machine but regularly use a *nix like environment on that machine. But at intermediate level…īefore I go into the details a hint about the commands I use to create files and stuff like that. How to unbrick this device? Is it possible at all? To anticipate the answer: It is. The impact of this bug was that you’re not able to load something via TFTP from the bootloader. After having done so I furthermore realized that the bootloader in my TL-WA801ND v2.1 was the current one and therefore contains a bug (or maybe it was deliberately crippled?). Sometimes you just flash the wrong firmware. Experimenting with embedded devices is fun but things not always work as expected.